Forum Discussion
WVD Issue -Explorer Constantly Crashing and Restarting
Mark Aldridge Hi Mark, I'm seeing the same issue occur every now and then. It's caused by the Windows Search service. If you restart this service the issue stops (you don't need to restart the host and you can restart the service with everyone else logged on).
I've had to created a scheduled task to restart this service at logon. Far from ideal though. I assume it's yet another bug in Win10 2004...
On top of a major bug in FSLogix (which breaks OneDrive Files on-Demand) I'm getting pretty fed up with Microsoft right now.
Mark Aldridge Hi Mark, I'm seeing the same issue occur every now and then. It's caused by the Windows Search service. If you restart this service the issue stops (you don't need to restart the host and you can restart the service with everyone else logged on).
I've had to created a scheduled task to restart this service at logon. Far from ideal though. I assume it's yet another bug in Win10 2004...
On top of a major bug in FSLogix (which breaks OneDrive Files on-Demand) I'm getting pretty fed up with Microsoft right now.
tilikumtim thanks for that information.
I've created a scheduled task within group policy to restart the Windows Search Service when a event is logged based off explorer crashing. Hopefully this will fix it and I wont see this issue again.
See the attached screenshots of how I have configured this for anyone else that has this problem.
Here's the event log XML filter I used.
<QueryList>
<Query Id="0" Path="Application">
<Select Path="Application">*[System[(EventID=1000)]] and *[EventData[Data[1]='explorer.exe']]</Select>
</Query>
</QueryList>
Hi Mark, I tried your workaround, however I am still getting the explorer crashing and restarting, any other suggestion? This is on the hosts and they are definitely getting the policy, thanks in advance. Mark Aldridge
UoS70 and you have confirmed that the scheduled task is working correctly?
Can see from the history that it's stopping and starting the service. You should be able to see the event in Event Viewer to confirm the service is being stopped and statured as well.
Mark Aldridge Hi Mark, initially the policy was set to run with a service account, not sure how that happened, I changed that to the correct account and the task is no running, thanks again for your help.
Thanks for taking the time to post this and share workaround. I've reached out to the Search team and asked which logs would be required to root cause this issue. Let me circle back as soon as I hear more.
This turns out to be a known issue (internal tracking number is 21167387) and fixed in future builds of Windows. I will start our backport process as soon as possible to make sure we service current in-market versions of Windows 10 Enterprise multi-session.
Thanks,
Pieter
Hi Pieter,
Do you got any update regarding this issue? Just saw the same behaviour with the Windows 10 Enterprise multi-session, Version 2004 + Microsoft 365 Apps image from the gallery.
This is not acceptable for any production environment at the moment!
With kind regards,
Stefan Dingemanse
