Microsoft Acknowledges Windows 11 Black Screen Issue: A Detailed Overview
In a recent announcement, Microsoft has confirmed a critical issue afflicting users of Windows 11, which can leave them staring at a black screen immediately after sign-in or prevent the desktop from loading altogether. This development has raised concerns among users, particularly those operating in Azure Virtual Desktop environments.
The problem primarily impacts devices that installed the August 2026 non-security preview updates, along with potentially later cumulative updates. Users operating in Azure Virtual Desktop environments using FSLogix profile containers seem to be more frequently affected by this malfunction. The issue was officially noted on Microsoft’s Windows release-health dashboard on September 24, where it has been marked as “mitigated,” although no permanent fix has been issued yet.
The predicament centers around the August 27 release, specifically the KB5120996 update for Windows 11 version 26H1, which corresponds to OS Build 28000.2804. Additionally, Windows 11 versions 25H2 and 24H2 are implicated, with KB5120998 identified as the update responsible for issues in those versions as well.
Organizations utilizing Windows 11 should conduct an extensive assessment beyond just the 26H1 version. Affected users may initially authenticate successfully but can then be greeted by a blank black screen in place of the familiar Windows desktop. Furthermore, in some cases, the desktop session fails to initialize automatically. This failure denies users essential access to the taskbar, Start menu, desktop shortcuts, File Explorer, and other crucial functions reliant on the Windows shell.
Microsoft has identified that Application event logs on affected devices may indicate crashes of Windows Explorer. The process explorer.exe plays a significant role in managing the interactive shell for Windows, including rendering visual elements such as the taskbar and desktop. When this process crashes during startup, it may leave a user session active, yet appearing both frozen and unusable.
The problem has been observed predominantly on Azure Virtual Desktop session hosts that utilize FSLogix, which is Microsoft’s profile management technology aimed at virtual desktop deployments. FSLogix is widely recognized for providing roaming profile containers across various desktop environments, including shared, pooled, persistent, and non-persistent setups. Interestingly, Microsoft has noted that this issue seems to disproportionately affect specific existing user profiles.
For those users currently experiencing the black screen, a temporary manual workaround exists that does not necessitate a system restart. Users can invoke Task Manager by pressing Ctrl+Shift+Esc, select “Run new task,” input “explorer.exe,” and then choose OK. This action can initiate the Windows shell and may restore the user session, though it does not resolve the underlying issue regarding the update regression.
For managed environments, Microsoft has proactively released Known Issue Rollback (KIR) Group Policy packages designed to reverse the problematic non-security code change while maintaining the integrity of the rest of the installed update. Specifically, Windows 11 version 26H1 administrators are advised to implement the KB5124006 rollback policy, while devices utilizing Windows 11 24H2 and 25H2 require the KB5124010 version. Administrators need to install and configure the relevant policy according to their Windows version and subsequently restart the affected devices.
This situation serves as a stark reminder of the operational risks associated with broadly deploying optional preview updates across virtual desktop infrastructures. IT departments are encouraged to identify hosts running the affected builds, correlate user-reported issues with logged Explorer crash events, and validate rollback policies against relevant FSLogix profiles. Moreover, it is imperative for organizations to remain vigilant by closely monitoring Microsoft’s release-health guidance as they await a permanent resolution to this significant glitch.
As technology continues to evolve, maintaining system stability and reliability remains paramount for both personal and organizational users alike. Microsoft’s current challenges underscore the complexities of software management and the importance of rigorous testing and user feedback in ensuring a seamless digital experience.