Windows 11 24H2, 25H2 Bug Triggers Black Screens, Start Menu Failure

Key Takeaways

• A critical bug in recent Windows 11 24H2 and 25H2 updates caused severe UI failures, including black screens and non-responsive Start menus.
• The issue primarily affected enterprise-managed systems and virtualized environments, not personal devices.
• Failures stemmed from XAML-dependent components failing to initialize correctly due to a timing issue during the update process.
• Microsoft has addressed the issue with updates released starting June 23, 2026, under KB5095093, and recommends immediate patching.

Windows 11 Bug Triggers Enterprise UI Catastrophe

Microsoft has recently resolved significant issues impacting Windows 11 versions 24H2 and 25H2, which led to severe user interface malfunctions. These critical failures, observed in certain enterprise settings, manifested as black screens, non-functional Start menus, and taskbar crashes.

The problem, officially documented in update advisory KB5072911, emerged following cumulative updates released after July 2025, specifically citing updates such as KB5062553 and KB5065789 as triggers.

According to Microsoft’s analysis, the bug predominantly affected corporate-managed systems and virtualized infrastructures, largely sparing individual consumer devices.

These widespread failures are directly linked to XAML-dependent components, which are fundamental to rendering the contemporary Windows graphical interface.

Systems that received the problematic updates often experienced immediate and severe usability disruptions. This was particularly evident when updates were applied prior to the initial user logon or within non-persistent environments, such as Virtual Desktop Infrastructure (VDI) deployments.

Core System Components Crippled

In affected environments, essential Windows components, including Explorer.exe, StartMenuExperienceHost, and shellhost.exe, either failed to launch or crashed unexpectedly. Users attempting to log in frequently encountered a black screen instead of their desktop. The Start menu would often fail to open or display critical error messages, while the taskbar might not render at all, rendering the system largely unusable.

The impact extended beyond the shell, affecting numerous other XAML-dependent applications. System Settings, for instance, could silently fail to launch, and other applications relying on XAML frameworks were prone to crashing during their initialization phase.

Even critical system prompts, such as User Account Control (UAC) dialogs managed by Consent.exe, exhibited malfunctions due to the underlying dependency breakdown.

Root Cause: A Timing Issue

Microsoft has identified the root cause as a timing issue where essential XAML-related application packages failed to register correctly during the update installation process. Specifically, packages like MicrosoftWindows.Client.CBS, Microsoft.UI.Xaml.CBS, and MicrosoftWindows.Client.Core did not initialize in time, consequently preventing dependent components from loading properly.

This issue proved especially disruptive in non-persistent environments where application packages must be reinstalled at each user logon. In such configurations, the failure to register these critical dependencies before Explorer launches led to recurring failures across user sessions, severely impacting enterprise productivity.

Microsoft Issues Fix and Workarounds

Microsoft has addressed the issue in updates released beginning June 23, 2026, under KB5095093. This fix is being deployed incrementally and is anticipated to be broadly available through subsequent monthly updates. Organizations are strongly advised to install the latest available updates to mitigate this problem 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 specific PowerShell commands. This process involves registering the affected app packages located in the SystemApps directory and then restarting the shell components to ensure proper initialization.

In non-persistent environments, Microsoft suggests implementing a logon script to ensure that the required packages are registered before Explorer.exe is launched. This proactive measure prevents the premature loading of shell components, ensuring a stable user experience during session initialization. This incident underscores the inherent complexities of dependency management within modern Windows ecosystems, particularly in large-scale enterprise and virtualized deployments. It also highlights the critical importance of conducting staged update rollouts and thorough validation in controlled environments before widespread deployment. Organizations leveraging VDI or managed Windows deployments should meticulously review their update procedures and implement robust safeguards to prevent similar disruptions in the future.

What You Should Do

• Apply Latest Updates: Immediately install all available Windows updates, especially KB5095093 and subsequent monthly cumulative updates, to remediate the issue.
• Implement Workarounds (if unable to update): For systems still on affected builds, consider implementing Microsoft’s recommended PowerShell commands to manually register missing XAML packages.
• For Non-Persistent Environments: Deploy a logon script to ensure critical XAML packages are registered before Explorer.exe launches.
• Review Update Procedures: Evaluate current update deployment strategies, particularly for VDI and managed environments, to incorporate staged rollouts and rigorous validation.

Disclaimer: HackersRadar reports on cybersecurity threats and incidents for informational and awareness purposes only. We do not engage in hacking activities, data exfiltration, or the hosting or distribution of stolen or leaked information. All content is based on publicly available sources.