Microsoft fixes issues affecting Windows 11 versions 24H2 and 25H2, which are causing critical user interface failures, including black screens, Start menu malfunctions, and taskbar crashes in certain enterprise environments.
The problem, documented under update advisory KB5072911, is linked to recent cumulative updates released after July 2025, such as KB5062553 and KB5065789.
According to Microsoft, the issue primarily impacts enterprise-managed systems and virtualized environments rather than personal devices.
The failures are tied to XAML-dependent components, which are essential for rendering modern Windows interface elements.
Affected systems may experience severe usability disruptions immediately after update installation, particularly when updates are applied before the first user logon or within non-persistent environments like Virtual Desktop Infrastructure (VDI).
In impacted environments, core Windows components such as Explorer.exe, StartMenuExperienceHost, and shellhost.exe may fail to initialize or crash unexpectedly.
Users logging into affected systems often encounter a black screen instead of the desktop, while the Start menu may refuse to open or display critical error messages. The taskbar may also fail to render entirely, leaving systems largely unusable.
Windows 11 24H2/25H2 Bug Causes UI Failures
The issue extends beyond the shell, affecting multiple XAML-dependent applications. System Settings may silently fail to launch, while other applications relying on XAML frameworks can crash during initialization.
Even User Account Control prompts, handled by Consent.exe, may not function correctly due to the same underlying dependency failure.
Microsoft attributes the root cause to a timing issue in which 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.
This issue is particularly problematic in non-persistent environments where application packages must be reinstalled at every user logon.
In such setups, the failure to register dependencies before Explorer launches leads to repeated failures across sessions, significantly impacting enterprise productivity.
Microsoft has addressed the issue in updates released starting June 23, 2026, under KB5095093. The fix is being gradually rolled out and is expected to become widely available through subsequent monthly updates. Organizations are strongly advised to install the latest updates to mitigate the issue and restore normal system functionality.
For systems still running affected builds, Microsoft has provided temporary workarounds. IT administrators can manually register the missing XAML packages using PowerShell commands.
This involves registering the affected app packages located in the SystemApps directory and restarting shell components to allow proper initialization.
In non-persistent environments, Microsoft recommends deploying a logon script that ensures required packages are registered before Explorer.exe launches.
This approach prevents premature loading of shell components and ensures a stable user experience during session initialization. The incident highlights the complexity of dependency management in modern Windows environments, especially in enterprise and virtualized deployments.
It also underscores the importance of staged update rollouts and validation in controlled environments before broad deployment.
Organizations relying on VDI or managed Windows deployments should review update procedures and implement safeguards to prevent similar disruptions in the future.
Windows 11 25H2 (2025 Update) Known Issues and Workarounds – June 24, 2026
Windows 11 Out of band update KB5070773 (emergency update out to fix Recovery failure in Windows 11 25H2 / 24H2)
Windows 11 Patch Tuesday January 2026 (KB5074109, KB5073455)
Microsoft makes potential CPU, RAM, disk hogging feature default on Windows 11 25H2, 24H2