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...
paulcruwys
Oct 03, 2024Copper Contributor
The KB removal worked for us in terms of login speed was much faster and no black screen.
Anyone else had an issue with Outlook starting and just hanging showing loading profile?
I tested after the KB removal of one user and it opened fine but since they are all logged in the Outlooks are all frozen so noone can use now.
Have attempted to remove local profiles via C:\Users\ and rename the folder to say XXX to force a rebuild on the next login but nothing worked. Users are currently on webmail 365 for now.
- djordan1910Oct 03, 2024Copper Contributoryes, read up a few responses from the past two days. Outlook is still wonky even after removing the KB or doing the KIR. Its not an issue for everyone, but we see it in about 1 of 20 logins to the VDIs. We are simply kicking them from the host and they reconnect to a different one and the problem goes away.
- paulcruwysOct 03, 2024Copper ContributorIs it host specific then? I mean if that use comes back to the same (faulty) host - do they suffer the same issue? Mine is affecting approx 80% of users not opening outlook right now.
- dit-chrisOct 03, 2024Brass ContributorFrom what we are seeing users 1-5 (say) might log in ok and can open MS apps, has number 6 has an issue (normally link to a black screen - but now shorter, I suspect because a timeout value), the AADbroker fails to load via AppReadiness and then no user beyond that point get to be able to authenticate to Outlook, Onedrive (and probably Teams), normally with no significant login delay (I suspect because the AAD auth is just not processed!). We then drain mode the host to divert new logins and it will remain like that until the current user are logged off and the host is rebooted, that works well until 80% of your hosts are affected.