Description: A black screen after logging into Azure Virtual Desktop can mean Windows Explorer failed to start. Learn which Windows 11 sessions are affected, how to recover work safely, and which October 2026 update fixes the problem.
If your Azure Virtual Desktop session accepts your sign-in but never shows a desktop, you may be seeing a confirmed Windows Explorer startup bug. Microsoft identified the issue mainly on AVD hosts using FSLogix and fixed it in the October 13, 2026 update KB5127648.[1][2]
Does your problem match?
This is primarily a managed, multi-user virtual desktop issue. FSLogix loads user profiles into remote sessions, and Microsoft observed the symptoms more frequently with some existing profiles. The problem was documented after the August 2026 preview KB5120998 and later updates.[3]
The distinctive sequence is: sign-in succeeds, the desktop and taskbar never load, and explorer.exe may fail to start or crash repeatedly. Application event logs can provide evidence. A black screen on a personal laptop before sign-in is a different diagnostic situation.
Recover the session without wiping anything
- In the affected remote session, press Ctrl + Shift + Esc to open Task Manager.
- Choose Run new task, type
explorer.exe, and confirm. Microsoft lists this as a temporary workaround.[2] - If the desktop returns, save your work. Tell IT the time, session host, and whether starting Explorer helped. Keep user-identifying logs in approved support channels.
- An administrator should check
winverand Windows Update history on the remote host. KB5127648 corresponds to build 26100.9711 for 24H2, 26200.9711 for 25H2, and 26300.9711 for 26H2.[1]
The permanent fix
Microsoft marks this specific issue resolved on October 13, 2026. Installing KB5127648 or a later update on Windows 11 24H2, 25H2, or 26H2 session hosts is the official fix. Before that update, IT could use a special Known Issue Rollback policy; it is unnecessary for this issue after the corrected update is installed.[2]
Do not delete FSLogix profiles, wipe profile containers, or reset Windows just because the screen is black. These steps can put work files and settings at risk. If the problem continues on a corrected host, IT should investigate other Explorer crashes and profile-loading failures separately.
Bottom line
Start Explorer to rescue the session, then ask IT to verify KB5127648 or newer on the host. The desktop may have missed its entrance; your files do not need to exit with it.
References (3)
[1] Microsoft Support, KB5127648 (2026-10-13). https://support.microsoft.com/en-us/servicing/os/windows-11/2026/10/kb5127648-windows-11-24h2-25h2-26h2-security-update
[2] Microsoft Learn, resolved issues in Windows 11 26H2 (2026-10-13). https://learn.microsoft.com/en-us/windows/release-health/resolved-issues-windows-11-26h2
[3] Microsoft Support, KB5124010 (2026-09-22). https://support.microsoft.com/en-us/servicing/os/windows-11/2026/09/kb5124010-windows-11-24h2-25h2-update
