Microsoft: Windows 11 24H2 bug crashes Explorer and Start Menu

Microsoft has confirmed a critical Windows 11 24H2 bug

"Microsoft has confirmed a critical Windows 11 24H2 bug that causes the File Explorer, the Start Menu, and other key system components to crash after installing cumulative updates released since July 2025.

"This bug affects users who log in after applying the cumulative updates and those using non-persistent operating system installations (such as virtual desktop infrastructure environments), where app packages must reinstall each session. On impacted systems, it causes issues for multiple essential Windows 11 shell components when XAML dependency packages fail to register properly after updates.

"This causes shell components such as Explorer.exe, StartMenuExperienceHost, and ShellHost.exe to crash with visible errors or fail silently, leaving users with partially functional systems that cannot display various navigation tools.

"Affected users can experience a wide range of problems, including Start menu crashes (often accompanied by critical error messages), missing taskbars even when Explorer.exe is running, the core ShellHost (Shell Infrastructure Host or Windows Shell Experience Host) system process crashing, and the Settings app silently failing to launch.

"After provisioning a PC with a Windows 11, version 24H2 monthly cumulative update released on or after July 2025 (KB5062553), various apps such as StartMenuExperiencehost, Search, SystemSettings, Taskbar or Explorer might experience difficulties," Microsoft said.

Source: Bleeping Computer - November 24, 2025 https://www.bleepingcomputer.com/news/microsoft/microsoft-windows-11-24h2-bug-crashes-key-system-components/

 

2,623 views 3 replies
Reply #1 Top

Most importantly, nothing to do with Start11 :)

Reply #2 Top

Just posting because there have been quite a few reports of Explorer crashes and they might be tied to this issue with Windows 11 and not Start11. :grin:  

+1 Loading…
Reply #3 Top

Quoting pelaird, reply 2

Just posting because there have been quite a few reports of Explorer crashes and they might be tied to this issue with Windows 11 and not Start11. :grin:  

Thought exactly the same when I read about it earlier, pelaird.