Replies: 2 comments 10 replies
-
Yep, booted Windows 11 this morning to a black screen after logging in. Windows had installed updates prior to this (including KB5023706) I was able to start Firefox, start a cmd session with Administrator privileges, and run It seems like Microsoft touched ExperienceHost and/or removed the Windows 10 theme fallback. That's just my gut feeling. |
Beta Was this translation helpful? Give feedback.
-
I faced the same problem yesterday - as much as I love the ExplorerPatcher, this was REALLY a huge problem. Took me more than an hour to finally fix it (after identifying what even the problem was). Solution was a rollback to the windows-update before. However - I was not running the latest EP version when the bug happened. |
Beta Was this translation helpful? Give feedback.
-
This broke my W11 installation when I updated this week. Took a long time to figure out the problem. W11 booted, but the UI and desktop was a mess and was not functional. Only thing that partially worked was Task Manager. Solved problem after going to an earlier restore point, uninstalling ExplorerPatcher, and then installing the update. Explorerpatcher appears to alter basic W11 files rather than just run in the background. Because of this, I could find no way to kill the program in Task Manager in order to allow W11 to fully boot. As much as I like this little program, I don't think I will reinstall as the Dev recommends. It is just too risky. Open Shell is still working.
Beta Was this translation helpful? Give feedback.
All reactions