Build 10130 - explorer.exe crash on shutdown or restart

Hi All, I've updated to build 10130 and now every time I restart or shutdown the laptop I'm getting this error.

I've tried searching but haven't seen other examples of a similar issue. Has anyone experienced this and been able to fix it?

I did a clean install creating an ISO from the install.esd and installed onto a clean formatted hdd.



Also noticed that the OOBE crashed on first login as well (has happened for me on every build I've tried so far).

I'm getting the same shutdown error after a clean install of 10130.

Yes, there are few of us having this problem.
10130 install

I'm getting the same shutdown error after a clean install of 10130.

Same here... It did diaper on a previous clean install of 10130. but I don't know what occurred to stop it.

Clean installing of your diaper is good, Bunny

It is most likely application(s) under heavy load using a lot of memory and is hung to kill.
Most often the OS/applications will learn to 'use' memory properly in short order, however,
2 Reg tweaks will take of it immediately though:

Change the value of or create and set the value of the following Strings:

HKEY_LOCAL_MACHINESYSTEMControlSet001Control
String: WaitToKillServiceTimeoutValue: 2000

HKEY_CURRENT_USERControl PanelDesktop
String: WaitToKillAppTimeout Value: 2000

You shouldn't see the error any more.

Mine is set to 5000. Why would shortening that time fix it? If anything I would think making it longer would help.

I'll try it anyway though and report back.

Edit: No change, still get the error.

Edit2: Found there is another location that maybe should be changed?


I'll try it and see what happens.

Fast Startup has been known to sometimes cause shutdown issues. You might turn it off as a test to see if it may help.

Fast Startup - Turn On or Off in Windows 10

I have already tried disabling Fast start up, reg editing, neither of them seems to fix this.

This is a widespread problem, and has been reported in multiple feedbacks. I expect it to be fixed soon.

If you encounter a problem like this, get into Windows Feedback and do a search - 9 times out of 10 you'll find that it's a well-known bug, and has been reported.