Microsoft Confirms Windows 11 25H2 UI Features Broken Along With 24H2 Following Update
Microsoft has identified a critical issue impacting enterprise and managed environments using Windows 11 versions 24H2 and 25H2.
Microsoft has identified a critical issue impacting enterprise and managed environments using Windows 11 versions 24H2 and 25H2.
The issue, initiated by cumulative updates in July 2025 , disrupts essential UI components, rendering the desktop non-functional for many users.
An updated support document published on December 2, 2025, indicates the issue arises from a timing error in the registration of XAML-dependent packages.
When these updates are applied, the necessary Extensible Application Markup Language (XAML) dependencies, specifically packages like MicrosoftWindows.Client.CBS, fail to register before the Windows Shell initializes. This race condition disables the visual layer of the operating system before user interaction is possible.
The core issue pertains to the dependency chain between the Windows Shell and its underlying AppX packages. Modern Windows interface elements, such as the Start Menu and Taskbar, depend on "CBS" (Component Based Servicing) client packages to render their UI.
Microsoft has identified specific dependencies that fail to register during the logon sequence:
MicrosoftWindows.Client.CBS_cw5n1h2txyewy Microsoft.UI.Xaml.CBS_8wekyb3d8bbwe MicrosoftWindows.Client.Core_cw5n1h2txyewy
When Explorer.exe or SiHost.exe (the Shell Infrastructure Host) attempts to call these missing resources, the processes may crash or hang, resulting in a "black screen" state or a non-functional desktop.
While personal devices are largely unaffected, the impact on enterprise environments is considerable. The problem is most prevalent in Virtual Desktop Infrastructure (VDI) and other non-persistent OS installations.
Microsoft has identified a critical issue impacting enterprise and managed environments using Windows 11 versions 24H2 and 25H2.
In these settings, where a fresh OS instance is provisioned for each user logon, the race condition recurs because the application packages must be reinstalled and registered at every sign-in.
Administrators may encounter the following failure signatures:
Binary Component Failure Signature / User Experience
Explorer.exe Users log on to a completely black screen; Taskbar fails to render; Explorer crashes immediately upon start.
StartMenuExperienceHost The Start menu fails to open or displays a "Critical Error" message to the end-user.
ShellHost.exe The Shell Infrastructure Host crashes repeatedly, preventing UI initialization.
Consent.exe The User Account Control (UAC) dimming screen and prompt fail to appear.
SystemSettings The Settings app (Start > Settings) fails to launch silently with no error message.
XAML Apps Various modern inbox apps crash immediately upon initialization.
Microsoft is developing a permanent solution, though a timeline for the fix has not yet been provided. In the meantime, IT administrators must intervene manually to restore functionality.
For persistent environments, administrators can manually register missing packages using PowerShell by targeting the AppxManifest.xml files in the C:\Windows\SystemApps\ directory.
In non-persistent VDI environments, where manual intervention is impractical per session, Microsoft advises using a synchronous logon script.
This script functions as a wrapper, forcibly registering the Microsoft.UI.Xaml and Client.CBS packages before allowing explorer.exe to launch. This sequence ensures the dependencies are adequately provisioned, preventing the race condition that causes UI failure.
Based on reporting by Cyber Security News.