"You will need to install and configure the Group Policy for your version of Windows to resolve this issue. You will also need to restart your device(s) to apply the group policy setting," Microsoft said.
Microsoft confirmation and the environments affected
Microsoft has confirmed that some Windows users may experience desktop loading issues — including black screens — after installing the August 2026 preview updates and subsequent updates. The company says the problem mainly affects Azure Virtual Desktop (AVD) hosts that use FSLogix, a software solution that speeds up user profile loading in virtual desktop environments.
Microsoft also noted earlier this month it had resolved separate known issues that wiped mouse and desktop settings on some Windows 11 systems after installing the KB5120998 August 2026 optional update.
Symptoms: black screens after sign‑in and Explorer crashes
Windows systems encountering the known issue can present multiple, related symptoms. The most common symptom reported is a black screen immediately after sign‑in, leaving users unable to access their desktop until the desktop session is started manually. Application event logs may also record Windows Explorer crashes, indicating the desktop shell is failing as part of the same problem.
Audit-ready is a season. It shouldn't be.
Evidence in spreadsheets, controls drifting between audits, frameworks multiplying on flat headcount. Nubivance runs continuous compliance on Rapid7 Cyber GRC - SOC 2, HIPAA, ISO 27001, PCI, CMMC.
End the scrambleImmediate user workaround: start Windows Explorer manually
Until Microsoft ships a permanent fix, affected users can regain access to their desktop by manually launching Windows Explorer. The steps Microsoft published are:
- Open Task Manager (Ctrl+Shift+Esc)
- Select "Run new task"
- Enter explorer.exe
- Click OK
That manual launch restores the desktop shell and allows the user to continue working while a broader remediation is applied.
Enterprise mitigation: Known Issue Rollback and the required Group Policies
For enterprise-managed devices, Microsoft has mitigated the issue using Known Issue Rollback (KIR), a Windows feature that can reverse buggy changes delivered via Windows Update. IT administrators can apply the mitigation by installing the appropriate Group Policy for their Windows build:
- Windows 11, version 26H1: KB5124006 Known Issue Rollback
- Windows 11, version 25H2 and Windows 11, version 24H2: KB5124010 Known Issue Rollback
Microsoft warned administrators that they must both install and configure the Group Policy for the device version and then restart devices to apply the setting. "Note that this Group Policy will disable the change causing this issue until a resolution is released in a future Windows update," Microsoft said. Administrators can find further guidance on deploying and configuring KIR group policies on Microsoft's support website.
How IT administrators, AVD hosts using FSLogix, and end users are likely to respond
IT administrators: Expect to download and apply the KB5124006 or KB5124010 KIR Group Policy appropriate to your Windows 11 build, then restart affected devices. Follow Microsoft's published deployment guidance to ensure the rollback is applied consistently across enterprise-managed endpoints.
AVD hosts using FSLogix: Virtual desktop operators should monitor for black‑screen sign‑in failures and Explorer crash entries in application logs. Where incidents occur, operators can instruct users to use the Task Manager workaround and prioritize applying the KIR Group Policy to affected hosts.
End users: If you see a black screen after sign‑in, you can restore your desktop by launching explorer.exe from Task Manager as described above. If your device is managed by an organization, contact your IT team to confirm whether the KIR mitigation has been applied.
Microsoft’s guidance makes clear this is a reversible change: group policies will disable the update change causing the issue until Microsoft ships a permanent resolution in a future Windows update. Administrators and users affected by the August 2026 preview updates should apply the prescribed mitigations and watch for the forthcoming corrective update.
