Forum Discussion
JPlendo
Sep 19, 2024Brass Contributor
Azure Virtual Desktop - Black Screens on logins - What we've tried so far
TLDR - Azure Virtual Desktop Black Screens. Could be 2 Min long, could be much longer. Tried removing stuck profiles, spun up all new VMs to see if that would fix it, finally disabled an applicatio...
KevHal
Sep 30, 2024Iron Contributor
Indeed, the lack of updates or awareness from Microsoft to the issue has shown a complete disconnect between us (who take the flack from customers) and Microsoft. There is no clear feedback mechanism to these issues when we need it.
The whole saga has been going on far too long now and has left a sour taste.
djordan1910
Sep 30, 2024Copper Contributor
So, we are having the same problem with ours as well. I cannot find a published KB or fix for this.
For a quick workaround, what we HAVE found, is that if you RDP to the host, open task manager, find the user with the black screen in the 'details' tab. Look for their explorer.exe process, right click on it and choose 'analyze wait chain'. You'll notice there is an associated svchost.exe process. Hit the checkbox and kill just that svchost.exe process and their desktop will pop right up.
For a quick workaround, what we HAVE found, is that if you RDP to the host, open task manager, find the user with the black screen in the 'details' tab. Look for their explorer.exe process, right click on it and choose 'analyze wait chain'. You'll notice there is an associated svchost.exe process. Hit the checkbox and kill just that svchost.exe process and their desktop will pop right up.
- VOatMH1265Sep 30, 2024Copper ContributorDid you notice if this results in Appx packages being broken for that user?
- djordan1910Oct 01, 2024Copper Contributor
VOatMH1265 yes, killing associated svchost process in the chain did break all AppX packages badly. However, See below, the KIR appears to be working ok. Will update once our users flood the servers in the morning.
- dit-chrisOct 01, 2024Brass Contributordjordan1910 that doesn't surprise me; I think that is basically what happens anyway - just after a not insignificant timeout period by default the AppX package processing times-out and is forced closed and eventually the black screen will clear - but with a load of broken AppX packages.
- djordan1910Sep 30, 2024Copper ContributorNo, so far we're not seeing anything negative by doing this. We're a pretty simplistic setup with 2 hostpools, 10 or so VDI hosts using FSLogix to keep track of userprofiles.