Windows 11 Black Screen After Login: Microsoft’s AVD Issue

In this guide

A Windows 11 black screen after login does not automatically mean your laptop screen has failed. Microsoft has documented a particular desktop-loading problem, primarily seen in business virtual desktops using Azure Virtual Desktop and FSLogix. It is worth checking in a matching environment before deciding to reinstall Windows.

Guidance checked on 1 October 2026. This article covers the specific September notice. It does not establish the cause of a black screen on an ordinary home laptop.

Windows 11 black screen after login: what Microsoft confirmed

Microsoft describes sessions where sign-in completes but the desktop does not appear. Its current notice lists Windows 11 24H2, 25H2, 26H1 and 26H2 as affected platforms, with reports concentrated on Azure Virtual Desktop hosts using FSLogix. Some existing user profiles appear more susceptible.

For 24H2 and 25H2, the notice points to the August preview update KB5120998 and later updates. The corresponding 26H1 notice names KB5120996. Check the actual Windows version and update history rather than assuming every recent update has the same problem.

Microsoft currently marks the issue as mitigated. That means a workaround is available; it is not a claim that every black-screen fault is fixed. See Microsoft’s current Windows release-health notice for the latest status and affected versions.

What are Azure Virtual Desktop and FSLogix?

In a virtual-desktop setup, the Windows desktop you use may be running remotely rather than on the laptop in front of you. FSLogix is used in managed environments to handle user profiles. The distinction matters: a remote session failing to load is a different starting point from a laptop that cannot display its own startup screen.

Microsoft’s FSLogix known-issues guidance separately records black screens during sign-in after KB5124008, linked to Explorer crashing while the Windows shell starts. That entry lists FSLogix 2210 hotfix 4 or later and remains in progress at the time of writing.

A temporary workaround: start Windows Explorer

For affected sessions, Microsoft’s release-health guidance gives this temporary route:

1. Open Task Manager with Ctrl + Shift + Esc.
2. Select Run new task.
3. Enter explorer.exe and select OK.

This may bring the desktop back for the session. It does not prove that your machine has this particular known issue, and it is not a permanent repair. On a work-managed desktop, tell your IT team what happened so they can investigate the underlying problem.

Known Issue Rollback: a job for the managing IT team

Microsoft provides a Known Issue Rollback, or KIR, for the problematic change. For enterprise-managed devices, administrators must install and configure the policy appropriate to the Windows version, then restart the affected devices. Simply downloading the package is not the complete procedure.

The current notice links a separate package for 26H1 and a shared package for 24H2, 25H2 and 26H2. Use the links in Microsoft’s live notice so the package and instructions match your environment. Do not treat this as advice to remove every recent update or disable updates across the business.

What to check before reinstalling Windows

Our practical recommendation is to record the symptoms and preserve the evidence before making major changes:

• Where is the blank screen? On the laptop itself, or inside a remote work session?
• When does it happen? Before sign-in, immediately afterwards, or when opening a particular application?
• What changed? Note the Windows version, installed updates and when the fault began.
• Does the environment match? Ask the administrator whether Azure Virtual Desktop and FSLogix are involved.
• What do the logs show? In matching cases, the IT team should check Application event logs for Windows Explorer crashes around the failed sign-in.

A reinstall can be disruptive and can remove useful diagnostic evidence. It may be appropriate for some faults, but it should follow an assessment and a check of your backups rather than being the automatic first response.

What if it is your own laptop?

A similar-looking symptom is not a diagnosis. If you do not use a managed virtual desktop, this Microsoft notice alone is not a reason to apply a business rollback policy or assume the display is broken.

Tell us whether you can see the manufacturer’s logo, the sign-in screen or a mouse pointer, and whether the problem starts only after entering your password. Those details help us decide what to investigate. Avoid repeatedly resetting Windows before checking that important files are backed up.

AC Computer Warehouse has been helping customers in Stockport since 2007. For a personal device, see our laptop repair service or PC repairs. For workplace equipment, visit business IT repairs and tell us about the setup. Managed cloud-session changes should be coordinated with whoever administers that environment.

Send a repair enquiry or call 0161 282 2548. Include the device model and what appears before the screen goes black. We assess the fault and confirm a quote before repair work.

Frequently asked questions

Does this Microsoft issue affect every Windows 11 laptop?

No. It has primarily been reported in Azure Virtual Desktop environments using FSLogix. A home laptop with a black screen needs its own diagnosis.

Is starting explorer.exe a permanent fix?

No. Microsoft presents it as a temporary workaround for an affected session. The managing IT team should check whether the known issue and the version-specific rollback apply.

Should I reinstall Windows straight away?

Not solely because of this notice. First establish where the failure occurs, check the relevant environment and logs, and protect your files. Reinstallation should be based on the diagnosis.