https://support.microsoft.com/en-us/kb/2929203 This is the same problem that I am having with multiple PCs and laptops that have had a clean install of windows 10 pro anniversary. I've looked at a lot of answers from a lot of different sources, and nothing seems to fix the problem. Any ideas or suggestions would greatly be appreciated.
Last edited by speedtrap; 13 Aug 2016 at 19:07.
still digging have not found the answer yet.
Thanks Spunk for your input. I've covered that list already ... no change, but I'm still digging.
I've had this same error on shutdown for several months now and it's been driving me nuts. It didn't start with the Anniversary Update, but it did carry on after updating. A few weeks ago I did a clean install and everything was fine for a few days, then the problem came back. After extensive testing, I was able to to narrow it down to a few suspect processes and now I'm fairly sure I finally solved the issue.
The culprit for me was iCloudPhotoStream.exe, which installs with iTunes/iCloud. I assume this program is doing some sort of indexing in the background and if you shutdown while this is happening, it causes explorer.exe to crash. I noticed that even when I terminate the process in Task Manager manually without shutting down, it will sometimes cause explorer to crash, although with no error message.
Anyway, I disabled all the iTunes/iCloud startup processes for good measure and have not had the error occur ever since. Have experienced 6-7 clean shutdowns in a row now so I'm fairly confident I found the fix for my particular situation.
I understand this won't solve the problem for everyone as iTunes is probably not software many Windows users would install. I personally don't like the software myself, but use it for managing my iPod. If you do not have iTunes or iCloud installed, I would suggest disabling all your startup processes and see if you still get the error. Then enable the essential processes one at a time and see if you can pinpoint what is causing the problem. It is most likely going to be a process that has hooks into explorer.
Hope this helps solve the issue for some. It has frustrated me for months on end and all the digging I did on various forums and support sites had no mention of iTunes causing the problem.
Quote