I've been wrestling this issue for a couple days now and I can't seem to find the solution.
We have a heavily-restricted, generic domain user account that automatically logs in to several computers in our environment. The restrictions, including an Applocker whitelist, are all set through GPO. Whenever we install Windows updates, the next time that user logs in, explorer.exe crashes and will not run. The only way I can get it working again is to disable the GPO, login the user, and then re-enable the GPO. The account will continue working until the next round of Windows updates. The PCs in question are running Windows 10 LTSB 2016 (1607).
Event viewer logs the explorer.exe crash as follows:
Faulting application name: Explorer.EXE, version: 10.0.14393.2791, time stamp: 0x5c5a431c
Faulting module name: windows.storage.dll, version: 10.0.14393.2848, time stamp: 0x5c7f6600
Exception code: 0xc00000fd
Fault offset: 0x00000000000a7778
Faulting process id: 0x1010
Faulting application start time: 0x01d4da9733f54544
Faulting application path: C:\Windows\Explorer.EXE
Faulting module path: C:\Windows\System32\windows.storage.dll
Report Id: e4a9eebf-eb36-4dec-a03f-c64b1988c95f
Faulting package full name:
Faulting package-relative application ID:
And crash dumps show the following exception for explorer.exe:
This dump file has an exception of interest stored in it.
The stored exception information can be accessed via .ecxr.
(10e4.10e8): Stack overflow - code c00000fd (first/second chance not available)
windows_storage!CFSFolder::_GetLongItemPath+0x38:
00007ff9`6b6d7778 4c894d88 mov qword ptr [rbp-78h],r9 ss:00000000`00603d08=0000000000000000
The crash information makes me think it's something with a network share causing the problem but I don't believe there are any being mapped on that account. I'm hoping someone out there can make sense of these errors to point me in the right direction for getting this figured out.
More...