--- title: "Windows 11 Black Screen After Sign-In: Microsoft Confirms Virtual Desktop Issue" url: "https://kesuk.net/windows-11-black-screen-after-sign-in-virtual-desktop.md" canonical: "https://kesuk.net/windows-11-black-screen-after-sign-in-virtual-desktop/" published: "2026-09-26" modified: "2026-09-26" author: "KES Team" tags: - "Microsoft 365" - "News" - "Azure Virtual Desktop" - "FSLogix" - "IT Support" - "Windows 11" - "Windows updates" --- # Windows 11 Black Screen After Sign-In: Microsoft Confirms Virtual Desktop Issue **A black screen after signing in may be a Windows desktop-loading problem, not a broken monitor.** Microsoft has acknowledged a new issue primarily observed in Azure Virtual Desktop environments. For businesses with affected staff, the priority is to restore access safely and give the IT provider enough information to identify the cause. *Guidance checked on 26 September 2026. This article concerns a specific known issue, not every black-screen fault.* ## What has Microsoft confirmed? Microsoft opened its [Windows release-health notice](https://learn.microsoft.com/en-us/windows/release-health/status-windows-11-25h2) on 24 September. It links the problem to the August non-security preview update, KB5120998, and later updates. Reports mainly involve Azure Virtual Desktop hosts using FSLogix, particularly some existing user profiles. Symptoms include a black screen after sign-in, a desktop that does not load automatically and Windows Explorer crashes in application logs. The affected client versions are Windows 11 24H2, 25H2 and 26H1; Windows Server is not listed as affected. The status is **mitigated, not fully resolved**. Microsoft is working on a future update. Its temporary user workaround is to open Task Manager with **Ctrl+Shift+Esc**, choose **Run new task**, enter **explorer.exe** and select **OK**. On a managed desktop, check with IT before trying this. ## Why are virtual desktops mentioned? A virtual desktop runs your working environment remotely rather than solely on the computer in front of you. That distinction matters when reporting a fault: support needs to know whether the local laptop is blank or the remote work session is blank. [Microsoft describes FSLogix](https://learn.microsoft.com/en-us/fslogix/overview-what-is-fslogix) as technology that supports user profiles in virtual environments. Its profile containers hold a user's profile in a virtual disk, helping that profile follow the user across sessions. Staff do not need to manage these containers themselves. Our recommendation is to ask the provider which environment is involved before replacing equipment, creating a new account or attempting a profile reset. ## What should your IT provider check? 1. **Record the point of failure.** Does the local Windows desktop work, and does the problem start only after opening the remote session? 2. **Capture the affected scope.** Note the first occurrence, users, session hosts and whether colleagues can still work. Avoid sharing confidential screen contents in public support forums. 3. **Compare the environment with the live Microsoft notice.** Record operating-system versions, recent updates and relevant application logs. Similar symptoms do not establish the same cause. 4. **Agree a managed recovery plan.** Test the chosen mitigation on an appropriate affected system, arrange any interruption and confirm that the user's normal applications open afterwards. 5. **Keep a follow-up owner.** Track the permanent resolution and review temporary measures when it arrives. This is a practical support checklist, not a direction to apply a policy to every PC. Avoid ad-hoc deletion of user profiles or broad update removal before the cause has been assessed. Practical Windows support ## Staff unable to reach their working desktop? KES can help review the symptoms and coordinate the next steps with the provider responsible for your virtual desktops. - Identify the affected users and environment - Plan a supported recovery approach - Verify access and keep staff informed Talk to KES about desktop support → ### Have these details ready When did it start? Is the local PC or remote desktop affected? What does the user see after signing in? Share screenshots only through your approved support route. Use the KES support route → ## What is Known Issue Rollback? For managed devices, the incident notice provides version-specific Known Issue Rollback (KIR) policies. Your administrator should select the correct package and follow the linked deployment instructions, including the required restart. [Microsoft's KIR guide](https://learn.microsoft.com/en-us/troubleshoot/windows-client/group-policy/use-group-policy-to-deploy-known-issue-rollback) explains that KIR reverses a particular non-security change while leaving the other changes in place. It is not the same as uninstalling an entire cumulative update. Microsoft documents both Group Policy deployment and a separate Intune approach; the administrator should use the method appropriate to the environment. For business owners, the useful question is: “Have you confirmed that the mitigation applies, tested it and verified that staff can work again?” ## What happens if we do nothing? If staff cannot reach their working desktop, invoices, appointments and customer responses may be delayed. Repeated sign-in attempts also consume time without establishing the cause. The business response should include a named support contact, a short update to affected staff and an agreed way to handle urgent work. Do not move sensitive documents to personal email or unapproved storage just to work around an outage. Ask IT which existing, authorised alternatives are suitable. Our guide to [keeping work moving during a Microsoft 365 outage](https://kesuk.net/how-to-keep-your-business-running-when-microsoft-365-goes-down/) covers continuity planning; it is not a diagnosis of this Windows issue. Once access is restored, record what worked. A managed follow-up helps prevent a temporary recovery step from becoming an undocumented routine. For the wider approach, see [how to reduce recurring downtime](https://kesuk.net/how-to-reduce-recurring-downtime/).