Users may need to summon Explorer manually after signing in
Microsoft has said that some Windows 11 virtual desktops may fail to load after sign-in, leaving users staring at a black screen until they launch Explorer manually.
The glitch affects devices running the August 2026 non-security preview update or later releases and, according to Microsoft, "has been primarily observed on Azure Virtual Desktop (AVD) hosts, using FSLogix."
Windows Explorer crashes may appear in the affected device's Application event log. Users can temporarily recover the desktop by opening Task Manager and running explorer.exe as a new task.
Microsoft has also issued a Known Issue Rollback (KIR) that administrators can deploy through Group Policy. This disables the offending change until a permanent fix arrives. "We are working on a resolution for this issue, and it will be released in a future Windows update," the company said.
This is distinct from another problem introduced by the same August preview update, which replaced some customized desktop backgrounds with solid black. Microsoft fixed that in September, but has not explained precisely what causes this latest failure. It said only that the problem "appears to occur more frequently with some existing user profiles."
That will be of limited comfort to users glumly firing up Task Manager to launch their desktops manually.
Windows 11 versions 26H1, 25H2, and 24H2 are affected. Microsoft does not list Windows 10 or Windows Server among the affected platforms.
The stream of problems introduced by Microsoft's August and September updates is becoming relentless, undermining the company's claims that Windows is getting better. Quality improvement promises made earlier this year by Windows chief Pavan Davuluri are ringing hollow. If this is how Microsoft plans to "win back" its fans, as Satya Nadella said it must, the response may well be: thanks, but no thanks. ®