Microsoft has officially confirmed a interface bug affecting enterprise users on Windows 11 version 24H2 and the upcoming version 25H2.
Documented in support bulletin KB5072911, the issue causes core UI elements such as the Taskbar, Start menu, and File Explorer to fail or crash unexpectedly.
According to Microsoft, the problem stems from cumulative updates released on or after July 2025, including KB5062553 and KB5065789.
While widespread, the bug is specific to managed enterprise environments and is “very unlikely” to impact personal home devices.
The Technical Root Cause
The failures are triggered when Windows updates are installed during provisioning, specifically before the first user logs onto a persisted OS or during logons on non-persistent setups like Virtual Desktop Infrastructure (VDI).
The core issue is a timing mismatch. Essential XAML-dependent packages fail to register correctly before the user session begins.
Because modern Windows interface elements rely heavily on XAML (Extensible Application Markup Language), this failure breaks the visual shell of the operating system.
Microsoft identified three specific dependency packages causing the crash:
MicrosoftWindows.Client.CBS_cw5n1h2txyewyMicrosoft.UI.Xaml.CBS_8wekyb3d8bbweMicrosoftWindows.Client.Core_cw5n1h2txyewy
When these packages fail to register, the consequences are severe for the end-user experience. Users may log in to a completely black screen, find that the Start menu refuses to open, or watch Explorer.exe crash repeatedly.
Other modern apps, including System Settings and Windows Search, may also silently fail to launch.
Microsoft is currently developing a permanent resolution. In the meantime, IT administrators must manually register the missing packages.
For persistent environments, administrators can run PowerShell commands to register the AppxPackages specifically for the Client CBS, UI Xaml, and Client Core components.
For non-persistent VDI environments, Microsoft recommends a logon script approach. Admins should create a batch file wrapper that executes synchronously before explorer.exe launches.
This ensures the required XAML packages are fully provisioned before the desktop interface attempts to load, preventing the black screen crash.
A sample script provided by Microsoft utilizes Add-AppxPackage -Register commands directed at the C:\Windows\SystemApps paths for the affected packages, ensuring the “Immersive Shell” can locate the necessary UI components.
Find this Story Interesting! Follow us on Google News, LinkedIn and X to Get More Instant Updates
%20(1).webp?fit=1600,900&ssl=1&description=Documented in support bulletin KB5072911, the issue causes core UI elements such as the Taskbar, Start menu, and File Explorer to fail or crash unexpectedly.){kind=link}