Forum Discussion
Azure Virtual Desktop - Black Screens on logins - What we've tried so far
The only time i've seen issues like this was caused by not applying Defender Exceptions, we have them all added and then some. I wonder if there was a definition update on Monday that is causing this. The first few logons are fine, but then one further user may get the black screen, the App Readiness service stalls, this then causes a cascading effect with further logons. You can sometimes free or complete logons by restarting the App Readiness service.
I have no other workaround, its just pot luck.
What really ticks me off is that this started after the outages and when we asked MS if the outages could have an effect on this they of course said "no, the outages wouldnt do that"
MS support is so incompetent, they didnt announce the outages the last two weeks until hours after people started complaining about it. Then when the outage was cleared, MS support called me to "work on the issue"....work on what issue? The issue was resolved by YOU. How does your support stafff not know that? I will tell you how, cause MS could care less about giving great support. They have such a hold on so many companies and they know no one is gonna leave. What are you gonna do, make all your non IT workers learn how to use Linux OS? Yeah, good luck with that. MS knows it and shows it by just not caring about support levels any longer. They dont stick to their SLAs and the support staff you do get on the phone is normally not very good. And of course MS is the BEST as asking you questions you've answered in the ticket you submitted or asking you to run processes you already ran and showed them, again. Its sickening how little they seem to give a crap about users anymore.
Anyone in this thread had any change in status? We continue to have the same problem, and we're now in our fourth day of a near complete outage.
We blew away our host pools and session hosts, then recreated them. On the new hosts, we didn't install ANYTHING (including updates) in hopes that a clean install would fix the problem, but it doesn't.
There is no rhyme or reason to when these failures occur. We are capturing traffic via Fiddler in hopes that we can point MS to the spot that is failing. Our best guess is that one of the dark blue boxes from this Microsoft diagram is where the problem actually lies: https://learn.microsoft.com/en-us/azure/virtual-desktop/media/service-architecture-resilience/service-components-management.svg