Windows 10 File Explorer hanging / Build error screen

[mulderite]

I am still in the testing stages of Windows 10 and have a handful of workstations in school running the latest build of the Educational version with ClassicShell handling Start Menu duties (the test users have roaming profiles). The few test users I have are reporting that File Explorer will periodically 'freeze' on them on a daily basis, which also has the effect of rendering the taskbar to be completely inert. The calendar, volume slider, Start Menu and any minimized apps will not show when clicked on them (right click functionality DOES work however) and the only option to get everything back to life is to log off then on again. The freezing seems completely random and doesn't seem to be associated with anything obvious in terms of a particular program or task. On checking Event Viewer it seems to be whenever this happens there are two logged faults, one relating to Explorer.exe and the other to ShellExperienceHost.exe. I’ve searched dozens of articles about this issue and most of the ‘fixes’ revolve around using dism or sfc to repair corrupted images – either of which have never found any faults when I have tried them.

 

Secondly I have an issue whereby when building a workstation using MDT, the build will get so far and then display a blue screen with the message “Why did my PC restart?” This will then give you a ‘next’ button which just restarts the PC and comes up with the same screen again. What’s odd about this is that at this point in the build the workstation has successfully joined the domain and installed the assigned software, as though it is failing at the final stages. Again event viewer draws up a blank with no obvious errors relating to what is causing this issue. Even weirder, if I try a rebuild there is a 1 in 3 chance it will just suddenly work and go through the build successfully, other times it will fail with the aforementioned screen.

 

Has anyone else experienced either of these issues and if so, have you managed to find a resolution to them? Thanks everyone.

[ADMaster]

The first issue sounds like the trouble I previously had with classic shell. Another quick fix to that one is to kill the exploer.exe and re run it, not the most intuitive for an end user.

 

I ended up removing classic shell from my build. It worked great for W8 but not W10.

[denmyos]

@mulderite

Did you ever get the "Why did my pc restart" to go away.

We are having the same problem when deploying windows 10.

[Arthur]

Has anyone else experienced either of these issues and if so, have you managed to find a resolution to them?

We are having the same problem when deploying windows 10.

This article might help?

 

https://sccmentor.com/2018/08/13/why-did-my-pc-restart-windows-10-post-configmgr-osd

 

The problem occurs due to the following group policy being set and impacts Windows 10 1703 and above.

 

Computer Configuration\Administrative Templates\Windows Components\App runtime\Block launching Windows Store apps with Windows Runtime API access from hosted content.

 

You should set the Enabled policy to Not Configured as a workaround.

 

Microsoft recently posted a support article on the problem Event 5963 and a “Block launching Windows Store apps with Windows Runtime API access from hosted content” error prevents an OOBE deployment in Windows 10 and it looks like the issue will be addressed with future releases of Win 10.