Forum Discussion
Azure Virtual Desktop - Black Screens on logins - What we've tried so far
- AdamMcOct 23, 2024Copper ContributorPreview update installed while the KIR is in place? That is good to know
- chrismagaOct 24, 2024Copper ContributorHello, same problems here. Did someone installed the preview update KB5045594 which fixed the problem?
- parentcharlesOct 24, 2024Copper Contributor
Hello, so here's our experience with the issue.
The CU seems to have fixed the root cause issue of black screen/app readiness/AppxSVC, but did not repair or rollback any of the corruption that has been done. In other words, the issue could still persist on a per-user basis depending on which host it would connect because of the resulting corruptions.
We had a chicken and eggs sort of issue where the user AADBroker Plugin was corrupted and some hosts weren't able to redeploy the AADBroker Plugin which would then recreate the black screen issue.
We tried to repair the integrity of the hosts, we tried to reinstall all APPX packages.
We haven't found anything that could make an unstable host stable again.The funny part is that if a user that has corruption have his profile clean and reconnect to a host which can redeploy the AADBroker, then the issue was resolved, but it was a pain to define which hosts were corrupted and which weren't.
Because we didn't want any lingering issues or corruption, we redeployed a new image, which has all the patches, and we're hoping in doesn't come back. With the new image, we can repair the user AADBroker if it persists too.
Hope this is clear.
And btw, we have a case with Microsoft and we haven't received a single solution attempt.
- KevHalOct 23, 2024Iron Contributor
This should not be the case. With the KIR and the preview the Appx service should not be crashing. On the session host that got the black screen, does it show any crashing events in the event log at the time the user logged on?
Outlook and office etc is to do with a broken aad.brokertoken issue for a specific user on a specific session host. Most likely caused by corruption caused by the previous Appx issues. Only solution I have for this it to ditch the affected session host and build a new one from image.