Forum Discussion
Azure Virtual Desktop - Black Screens on logins - What we've tried so far
JPlendo
Microsoft have updated their status page on 1st November to say Oct Preview does not 100% fix our issues. And that they are still investigating:
Windows 10, version 22H2 | Microsoft Learn
Quote:
November 2024
AVD users might experience extended black screen during logon and SSO failures
Expand table
Status Originating update History
Confirmed OS Build 19045.4717
KB5040525
2024-07-23 Last updated: 2024-11-01, 14:11 PT
Opened: 2024-11-01, 14:11 PT
After installing the July 2024 non-security preview update (KB5040525), released July 23, 2024, or subsequent updates, you might experience an extended black screen that stays between 10 to 30 mins when you login to Azure Virtual Desktop (AVD). Additional symptoms you might experience include:
Failures related to single sign-on (SSO) experience on Office applications such as Outlook and Teams, which could prevent you from connecting to backend services or synchronizing data.
Office apps display losing network connectivity even though other applications, such as Edge, retain intranet and internet access.
This issue is caused by a deadlock in the interactions between the Azure Active Directory(AAD) broker and the underlying AppX deployment service(AppxSvc) and Background tasks infrastructure service.You are more likely to experience this issue if you are using FSLogix user profile containers on multi-session environments. FSLogix is a Microsoft tool that helps manage and speed up user profiles on computers, especially in virtual environments like remote desktops.
Please note that this issue is different from the scenario where the AppX Deployment Service (AppxSvc) was in an invalid state, causing a black screen. That issue was resolved with Windows updates released on October 22, 2024 (KB5045594), and later.
Windows 10 Education edition users and home users of Windows using Home or Pro editions are unlikely to face this issue as Azure Virtual Desktop is more commonly used in enterprise environments.
Next Steps: We are investigating the issue and provide an update where more information is available.
Affected platforms:
Client: Windows 10, version 22H2
Server: None
Fills you with confidence that they have now decided there is also an issue with Microsoft.AAD.BrokerPlugin_cw5n1h2txyewy also originated in July now it's early November... it's as if they went "oh that preview update we issued for the other issue doesn't seem to have stopped back screens at login" maybe we need to consider there is also another issue to look at when we have been reporting that weeks since they issued the KIR!