NEWS

Microsoft Confirms Recent Windows Updates Cause Desktop Loading Failures

August and September 2026 Windows updates can leave users stuck on a black screen after sign-in, mainly hitting Azure Virtual Desktop hosts.

Dylan H.

News Desk

September 26, 2026
4 min read
Microsoft Confirms Recent Windows Updates Cause Desktop Loading Failures

Black Screens After Sign-In Traced to August/September Updates

Microsoft has confirmed that a run of August 2026 preview updates and subsequent cumulative updates can cause desktop loading failures on Windows 11, most notably a black screen after sign-in that leaves the desktop inaccessible. The company says the problem mainly affects Azure Virtual Desktop (AVD) hosts running FSLogix — the profile-container technology widely used to speed up sign-in and roam user profiles in virtual desktop environments — though it can surface on other Windows 11 machines as well.


Details

AttributeValue
Affected updatesKB5120996 (Windows 11 26H1), KB5120998 (Windows 11 24H2/25H2), plus September Patch Tuesday updates KB5124008 and KB5122880
Primarily affectedAzure Virtual Desktop (AVD) hosts using FSLogix profile containers; also reported on some standard Windows 11 installs
SymptomBlack screen after sign-in; desktop and taskbar never load
Related event log entryWindows Explorer crashes recorded in the Application event log
Manual workaroundLaunch explorer.exe via Task Manager's "Run new task"
Mitigation for enterprisesKnown Issue Rollback (KIR) group policy — KB5124006 (26H1), KB5124010 (24H2/25H2)
Permanent fixPending in a future cumulative update

What's Happening

Affected devices sign in normally but never render the desktop — the screen stays black, and the Application event log records Windows Explorer crashing repeatedly as it fails to initialize. The issue clusters heavily around Azure Virtual Desktop hosts using FSLogix, since profile-container loading interacts with the same shell-initialization path that the updates altered, but Microsoft has acknowledged reports from standard Windows 11 endpoints too.

Immediate Workaround

Users stuck on a black screen can recover the current session manually:

  1. Press Ctrl+Shift+Esc to open Task Manager.
  2. Select File > Run new task.
  3. Type explorer.exe and press Enter.

This restarts the Windows shell for that session but does not prevent the issue from recurring on the next sign-in.

Microsoft's Fix Path

For managed fleets, Microsoft has published a Known Issue Rollback (KIR) — a Group Policy-deployed rollback of the specific code path causing the regression — via KB5124006 for Windows 11 version 26H1 and KB5124010 for versions 24H2 and 25H2. KIR requires enterprise admins to deploy the associated group policy; it is not automatic for unmanaged consumer devices. A permanent, non-rollback fix is expected in a future cumulative update.

Recommendations

  • AVD administrators: prioritize deploying the KIR group policy (KB5124006/KB5124010) to golden images and host pools before pushing any further cumulative updates, since FSLogix-backed hosts are the most exposed.
  • IT admins managing standard fleets: hold or pilot-test KB5120996, KB5120998, KB5124008, and KB5122880 in a ring before broad deployment if desktop-loading regressions would be disruptive.
  • Helpdesk teams: document the explorer.exe Task Manager workaround for frontline support to resolve black-screen tickets quickly while the KIR policy rolls out.
  • Track Windows Release Health for confirmation once the permanent fix ships in a future cumulative update, and remove the KIR policy once superseded per Microsoft's guidance.

Key Takeaways

  1. Microsoft confirmed that updates KB5120996, KB5120998, KB5124008, and KB5122880 can cause black-screen desktop loading failures on Windows 11.
  2. The issue primarily hits Azure Virtual Desktop hosts using FSLogix, though some standard Windows 11 devices are also affected.
  3. A manual workaround exists (explorer.exe via Task Manager), and Microsoft has shipped a Known Issue Rollback (KB5124006/KB5124010) for managed environments.
  4. A permanent fix has not yet shipped — it's expected in a future cumulative update.

Sources