Microsoft has recently addressed significant issues affecting Windows 11 versions 24H2 and 25H2, which have led to critical user interface failures in certain enterprise environments. These problems, documented under update advisory KB5072911, are associated with cumulative updates released after July 2025, including KB5062553 and KB5065789.
The primary impact of these issues has been observed in enterprise-managed systems and virtualized environments, rather than on personal devices. Users may experience severe disruptions in usability immediately following the installation of updates, particularly when these updates are applied before the first user logon or within non-persistent environments such as Virtual Desktop Infrastructure (VDI).
Windows 11 24H2/25H2 Bug Causes UI Failures
Core Windows components, including Explorer.exe, StartMenuExperienceHost, and shellhost.exe, may fail to initialize or crash unexpectedly in affected systems. Users logging into these environments often encounter a black screen instead of the desktop, while the Start menu may refuse to open or display critical error messages. Additionally, the taskbar may fail to render entirely, resulting in systems that are largely unusable.
The issue extends beyond the shell, impacting multiple XAML-dependent applications. For instance, System Settings may silently fail to launch, and other applications reliant on XAML frameworks can crash during their initialization phase. Even User Account Control prompts, managed by Consent.exe, may not function correctly due to the same underlying dependency failure.
Microsoft has identified the root cause as a timing issue, where required XAML-related application packages are not properly registered during the update process. Specifically, packages such as MicrosoftWindows.Client.CBS, Microsoft.UI.Xaml.CBS, and MicrosoftWindows.Client.Core fail to initialize in time, preventing dependent components from loading effectively.
This situation is particularly problematic in non-persistent environments, where application packages must be reinstalled at every user logon. The failure to register dependencies before Explorer launches leads to repeated failures across sessions, significantly impacting productivity in enterprise settings.
To address these concerns, Microsoft has released updates starting June 23, 2026, under KB5095093. This fix is being gradually rolled out and is expected to become widely available through subsequent monthly updates. Organizations are strongly encouraged to install the latest updates to mitigate these issues and restore normal system functionality.
For systems still operating on affected builds, Microsoft has provided temporary workarounds. IT administrators can manually register the missing XAML packages using PowerShell commands, which involves registering the affected app packages located in the SystemApps directory and restarting shell components to allow for proper initialization.
In non-persistent environments, Microsoft recommends deploying a logon script that ensures required packages are registered before Explorer.exe launches. This approach helps prevent the premature loading of shell components, ensuring a stable user experience during session initialization.
This incident highlights the complexities of dependency management in modern Windows environments, particularly within enterprise and virtualized deployments. It also emphasizes the importance of staged update rollouts and validation in controlled environments prior to broad deployment. Organizations relying on VDI or managed Windows deployments should review their update procedures and implement safeguards to prevent similar disruptions in the future.
Strengthen Your SOC by Accelerating Threat Detection & Rapid Investigations. -> Integrate ANY.RUN With Your SOC Now.