Start11 1.41: Windows KB5023706 kills Explorer.exe

I had an issue where an automatic install of Windows Update KB5023706 on my Win 11 PC with Start11 1.41 caused explorer.exe (the Windows desktop UI) to crash on reboot and fail to run when manually launched. KB5023706 replaces may files, including explorer.exe, rendering the PC unusable except for Task Manager. The symptom is a black screen with an arrow cursor. It is possible to launch rstrui.exe through the Task Manager to restore to a pre-update condition. I was able to do this and have paused Windows updates until a fix is published.

Note that Microsoft's page on this update discusses a known issue with 3rd party software that customizes the UI, which Start11 does do, so this should be investigated.

2,714 views 4 replies
Reply #1 Top

Hello,
Sorry to hear you are having issues. What you could/should do is uninstall Start11 reboot immediately after and test if the issue stop with Start11 uninstall. If the issue does not appear. Than re-download the latest Start11 V1.4.11 from your account page. Install it. Reboot after the reinstall. Retest if the issue reappear. If it does. Report back.

Also, If you have time please read through this thread where other user post their issue with Start11 once updated to the latest Win11 22H2, 22621.1344 https://forums.stardock.com/517335/

Thanks
Basj,
Stardock Community Assistant.

Reply #2 Top

Are you sure you do not have something else installed like explorer patcher?

We have no reports of this and the reference to third party customising software is not in reference to Start11.

Also are you using bit defender?

If you are not using explorer patcher then it would be very helpful if you could get us a DMP file of the crash.

https://support.stardock.com/space/SHC/1347321935/Manually+Collecting+Start+Crash+Dumps

Reply #3 Top

OK, I will try this when I have time to experiment. I don't have any other UI tweakers installed, aside from Start11 and Fences. I had PowerToys installed, but removed it and still had the issue recur.

Reply #4 Top

Apparently, the problem is NOT related to Start11 or Fences after all, as I have uninstalled them for now, and yet the explorer.exe failure still happens. I am going to try a "clean boot" to be sure nothing else I am optionally running is at fault.