Microsoft has officially acknowledged an issue affecting Windows 11 version 24H2, where monthly cumulative updates released on or after July 2025 are breaking multiple core system features.
The problematic update, tracked as KB5072911 (KB5062553), is causing widespread failures in essential Windows components, including the Start Menu, Taskbar, System Settings, and File Explorer.
Critical Shell Components Failing Across Systems
The issue primarily impacts users during their first logon after applying the cumulative update.
Additionally, all user logons to non-persistent OS installations, such as virtual desktop infrastructure (VDI) environments, are experiencing these failures because application packages must be reinstalled with each logon session.
Users affected by this update may encounter Explorer.exe crashes, the Start menu failing to launch with critical error messages, System Settings silently failing to open, and ShellHost.exe crashes.
In some cases, Explorer runs without displaying a taskbar, while other XAML-based views fail to initialize at all.
Root Cause Identified
Microsoft has traced the problem to XAML component dependency packages that are not registered in time after the update is installed.
The affected dependency packages include MicrosoftWindows.Client.CBS, Microsoft.UI.Xaml.CBS, and MicrosoftWindows.Client.Core.
These packages are essential for rendering shell components and user interface elements throughout Windows 11.
The timing issue prevents critical shell components from loading properly, causing cascade failures across StartMenuExperienceHost, Search functionality, SystemSettings, Taskbar operations, and the ImmersiveShell framework.
While Microsoft works on a permanent resolution, affected users can manually register the missing packages to restore functionality.
The workaround involves running PowerShell commands to register each missing XAML package in the user session, followed by restarting the Shell Infrastructure Host (SiHost) service.
For enterprise environments using non-persistent VDI deployments, Microsoft recommends implementing a logon script approach.
This involves creating a batch file wrapper that executes synchronously before Explorer launches, effectively blocking the shell from starting until required packages are fully provisioned.
Microsoft stated it is “working on a resolution,” but has not provided a specific timeline for when a fix will be available.
Organizations deploying Windows 11 24H2 updates across their infrastructure should evaluate whether to delay deployment until a permanent solution is released or implement the recommended workarounds to mitigate user impact.
System administrators managing VDI environments are particularly urged to test these workarounds thoroughly before deploying the affected cumulative updates to production systems.
Find this Story Interesting! Follow us on Google News, LinkedIn and X to Get More Instant Updates
%20(2)%20(1).webp?fit=1600,900&ssl=1&description=The problematic update, tracked as KB5072911 (KB5062553), is causing widespread failures in essential Windows components, including the Start Menu, Taskbar, System Settings, and File Explorer.){kind=link}