Windows 11 Black Screen After Sign-In Fix: AVD/FSLogix Patch

Microsoft has resolved a known issue that caused black screens, desktop loading failures, and Explorer crashes right after sign-in on some Windows 11 systems.

The company says the Windows 11 black screen after sign-in fix is included in Windows updates released on October 13, 2026, and later, naming KB5127648 as an example of a resolving update.

Microsoft's notice focuses specifically on Azure Virtual Desktop hosts using FSLogix, where the problem was primarily observed, rather than Windows 11 PCs broadly.

A separate Microsoft Q&A report describes a standalone-PC case with a similar-looking Explorer crash involving an Intel graphics component, which is a different scenario worth keeping distinct from the AVD issue covered here.

What is the Windows 11 black screen after sign-in fix?

Microsoft's Windows release-health documentation lists the issue as resolved in Windows updates released on or after October 13, 2026, naming KB5127648 as an example. The company's guidance says no workaround is needed after installing an update that includes the fix.

Before the October fix, the bug affected devices running several specific Windows updates. These included KB5120996 on Windows 11 26H1 and KB5120998 on Windows 11 24H2 and 25H2, with later September updates also affected while a permanent resolution was pending.

Because Microsoft names KB5127648 as an example rather than providing it as a universal update for every affected Windows release, administrators should verify the applicable cumulative update for the Windows 11 version running on each host.

Who is affected by the Windows 11 FSLogix black screen issue?

Affected sessions can show a consistent pattern: a black screen appears immediately after sign-in, the Windows desktop doesn't load automatically even though the session has started, and Application event logs record Explorer crashes.

Microsoft says the issue has primarily been observed on Azure Virtual Desktop hosts using FSLogix.

Consultant Justin Verstijnen also reported the problem across Windows 11 versions 24H2, 25H2, and 26H1 and noted that Windows Server wasn't listed among the affected platforms. He observed that existing user profiles appeared to encounter the problem more frequently than newly created ones, although Microsoft hasn't documented that profile-age pattern as part of its official description.

Given that scope, home users on standalone PCs aren't the primary audience for Microsoft's notice.

A Microsoft Q&A report involving a personal PC described an Explorer crash involving an Intel graphics DLL. That report points to a different suspected cause and doesn't establish that the standalone-PC problem shares the AVD/FSLogix fix.

A black screen on an individual Windows 11 PC therefore still requires its own diagnosis rather than an assumption that this particular patch applies.

What caused the Windows 11 black screen Explorer crash?

Microsoft says the issue could cause explorer.exe to crash during sign-in, preventing the Windows desktop from loading correctly.

Explorer.exe provides major parts of the Windows shell, including the desktop, taskbar, and Start menu. When Explorer fails during startup, the underlying Windows session can remain active even though the normal desktop interface doesn't appear.

That distinction explains why manually launching Explorer could restore the desktop without reconnecting the entire remote session.

Reporting from Verstijnen linked the problem to changes introduced by the affected Windows updates and noted its higher occurrence in FSLogix environments. Microsoft hasn't publicly provided a detailed root-cause explanation for why FSLogix-based sessions were particularly susceptible.

Explorer workaround and Known Issue Rollback for admins who can't update yet

Microsoft's documented session-level workaround is to open Task Manager with Ctrl+Shift+Esc, select Run new task, enter explorer.exe, and select OK.

That starts Explorer manually for the current session. The workaround may need to be repeated after another sign-in if the affected Windows update remains installed without the permanent fix.

Microsoft also released Known Issue Rollback packages for managed environments that couldn't immediately deploy the resolving update: KB5124006 for Windows 11 26H1 and KB5124010 for Windows 11 24H2 and 25H2.

Administrators can deploy the appropriate KIR through Group Policy. Microsoft notes that managed devices require the special Group Policy associated with the affected Windows version to install and configure the rollback.

A KIR rolls back the specific non-security change responsible for a known issue rather than uninstalling the entire Windows update.

These measures are now fallback options for systems that haven't received the permanent resolution. Microsoft says the workaround isn't necessary after installing a Windows update released on or after October 13 that includes the fix.

Administrators who already deployed a KIR should manage or retire that policy through their existing device-management process after confirming the permanent fix is installed rather than simply deleting it on assumption.

What to do now

Azure Virtual Desktop and FSLogix administrators should prioritize installing a Windows update released on or after October 13 that contains Microsoft's resolution.

Check the Windows 11 version and installed update on each affected host rather than treating KB5127648 as the required KB for every configuration. Microsoft cites that update as an example of a release containing the fix.

Once a resolving update is confirmed, the manual Explorer workaround is no longer needed for this known issue.

Systems that can't update immediately can still use Ctrl+Shift+Esc to launch Explorer manually or deploy the appropriate Known Issue Rollback: KB5124006 for Windows 11 26H1 or KB5124010 for Windows 11 24H2 and 25H2.

Standalone PC owners encountering a black screen after sign-in should treat it as a separate troubleshooting case unless their environment matches Microsoft's documented conditions.

Microsoft's resolved issue is primarily associated with Azure Virtual Desktop hosts using FSLogix, and a visually similar black screen can have unrelated graphics, driver, shell, or system causes.