Microsoft resolves Windows 11 black screen and Explorer crash bug

Microsoft has resolved a known issue in Windows 11 that caused black screens, desktop loading failures, and Windows Explorer crashes after installing updates released since August. The company addressed the bug in cumulative updates distributed during this month's Patch Tuesday cycle.

Which systems are affected by this update bug?

The problem primarily impacts Azure Virtual Desktop hosts that utilize FSLogix for user profile management. According to Microsoft, some existing user profiles were more susceptible to failing to load the desktop session. The issue affects Windows 11 versions 26H2, 26H1, 25H2, and 24H2. Windows Server platforms are not affected by this specific defect.

What symptoms indicate a system is impacted?

Affected users could sign in but encountered a black screen instead of their desktop. They were unable to access the desktop until they manually started the session. Administrators might also observe Windows Explorer crashes in application event logs, which served as a key indicator for identifying affected systems.

How was the issue resolved and mitigated?

Microsoft included the fix in KB5127646 for Windows 11 version 26H1 and subsequent updates. The company marked the issue as resolved on October 13, 2026. For enterprise-managed devices unable to install the immediate fix, Microsoft provided Known Issue Rollback group policies, specifically KB5124006 for 26H1 and KB5124010 for other versions, to disable the problematic change.

What steps should operations teams take now?

Teams should verify that all affected Windows 11 devices have received the October 13 update or later. If devices remain on older updates, administrators can apply the relevant KIR group policy and restart systems. As TechSec Feed reported on October 14, 2026, Microsoft recently fixed other critical flaws, highlighting the importance of keeping runtimes and OS components current.

Questions to ask your suppliers

Operational leaders should ask vendors whether their hosted desktop environments rely on FSLogix or similar profile management tools that might interact with OS updates. Check if suppliers have validated their services against recent Windows cumulative updates to prevent compatibility regressions. Ensure your incident response plan includes clear communication channels for when underlying platform providers resolve bugs that impact user access. Verify that your monitoring tools can distinguish between application crashes and OS-level session failures.

What to do and how to stay safe: Microsoft

• Check your patch management logs to confirm which devices received the October 13 update or later.
• Review application event logs for Windows Explorer crashes to identify any lingering affected systems.
• Verify that Known Issue Rollback group policies are removed from systems that have successfully updated.
• Monitor Azure Virtual Desktop performance metrics for any recurrence of black screen or login delays.

Step-by-step guide: Browser Security Settings for Small Business Teams

General security guidance from the TechSec Feed newsroom. It is not confirmed advice from the organisations named in this story.

Frequently asked questions

Does this bug affect Windows Server?

No, Microsoft stated that this issue does not affect Windows Server platforms.

What is the workaround for systems that cannot update immediately?

Users can open Task Manager, select Run new task, enter explorer.exe, and click OK to manually launch the desktop.

Which Windows 11 versions are affected?

The issue affects Windows 11 versions 26H2, 26H1, 25H2, and 24H2.