Forum Discussion
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...
KB's are not helping, we are progressing further with the below registries deployed across our hotspools and it seems fixing the MS apps issues.
Registry Hive: HKEY_LOCAL_MACHINE
Registry Path: SOFTWARE\FSLogix\Profiles
RoamIdentity
Type: DWORD
Default Value: 0
0: Don't roam credentials and tokens within the container.
InstallAppxPackages
Type: DWORD
Default Value: 0
The KB504559 has fixed 100% of our black screen issues, I removed the KIR and still no more black screens. We do still have the SSO issues when users open Outlook/Onedrive, this presents in different ways from a need password message with no window, to a stuck connecting message at the bottom of outlook.
Removing all credentials from credential manager and logging off the host pool fixes this every time not matter the issue.
I'm trying the 2 reg keys mentioned above now, at this stage I'll literally try anything. I agree its not an FSLogix issue but if disabling roamIdentity within the fslogix profile fixes it, that's good enough for now, I just need to remember to change them back when "IF" a proper fix comes along.
Will report back in 18 hours
Removing all credentials from credential manager and logging off the host pool fixes this every time not matter the issue.
I'm trying the 2 reg keys mentioned above now, at this stage I'll literally try anything. I agree its not an FSLogix issue but if disabling roamIdentity within the fslogix profile fixes it, that's good enough for now, I just need to remember to change them back when "IF" a proper fix comes along.
Will report back in 18 hours
- Well here is the Service Health Advisory update....
Workaround: This issue can be reduced significantly by installing this latest patch. An alternative workaround is available but may not be feasible for all customers. The suggested alternate workaround for the issue is for customers to move to Windows 11, as the issue is less likely to occur on this operating system.
