Microsoft has formally confirmed a vital situation affecting enterprise and managed environments working Home windows 11 variations 24H2 and 25H2.
The bug, first triggered by cumulative updates launched in July 2025, causes widespread failures in important UI elements, rendering the desktop unusable for a lot of customers.
In keeping with an up to date help doc launched on December 2, 2025, the problem stems from a timing failure within the registration of XAML-dependent packages.
When these updates are utilized, the mandatory Extensible Utility Markup Language (XAML) dependencies, particularly packages like MicrosoftWindows.Consumer.CBS fails to register earlier than the Home windows Shell initializes. This race situation successfully breaks the visible layer of the working system earlier than the consumer may even work together with it.
Home windows 11 25H2 UI Options Damaged
The core of the issue lies within the dependency chain between the Home windows Shell and its underlying AppX packages. Trendy Home windows interface components, such because the Begin Menu and Taskbar, depend on “CBS” (Element Primarily based Servicing) consumer packages to render their UI.
Microsoft recognized that the next particular dependencies are failing to register in time through the logon sequence:
MicrosoftWindows.Consumer.CBS_cw5n1h2txyewy
Microsoft.UI.Xaml.CBS_8wekyb3d8bbwe
MicrosoftWindows.Consumer.Core_cw5n1h2txyewy
When Explorer.exe or SiHost.exe (the Shell Infrastructure Host) makes an attempt to name these lacking assets, the processes crash or grasp, resulting in a “black display screen” state or a non-functional desktop.
Whereas private gadgets are largely unaffected, the influence on enterprise environments is important. The difficulty is most prevalent in Digital Desktop Infrastructure (VDI) and different non-persistent OS installations.
In these environments, the place a recent OS occasion is provisioned for each consumer logon, the race situation happens repeatedly as a result of the applying packages have to be reinstalled and registered at each single sign-in occasion.
Beneath is the breakdown of failure signatures directors could encounter:
Binary ComponentFailure Signature / Person ExperienceExplorer.exeUsers go browsing to a very black display screen; Taskbar fails to render; Explorer crashes instantly upon begin.StartMenuExperienceHostThe Begin menu fails to open or shows a “Crucial Error” message to the end-user.ShellHost.exeThe Shell Infrastructure Host crashes repeatedly, stopping UI initialization.Consent.exeThe Person Account Management (UAC) dimming display screen and immediate fail to seem.SystemSettingsThe Settings app (Begin > Settings) fails to launch silently with no error message.XAML Appsvarious trendy inbox apps crash instantly upon initialization.
Microsoft is at present growing a everlasting decision, however has not supplied a particular timeline for the repair. Within the interim, IT directors should manually intervene to revive performance.
For persistent environments, directors can manually register the lacking packages by way of PowerShell by focusing on the AppxManifest.xml recordsdata within the C:WindowsSystemApps listing.
For non-persistent VDI environments, the place guide intervention per session is unimaginable, Microsoft recommends a synchronous logon script.
This script acts as a wrapper, forcibly registering the Microsoft.UI.Xaml and Consumer.CBS packages earlier than permitting explorer.exe to launch. This sequence ensures the dependencies are totally provisioned, stopping the race situation that results in the UI failure.
Comply with us on Google Information, LinkedIn, and X for day by day cybersecurity updates. Contact us to function your tales.
