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...
djordan1910
Oct 18, 2024Copper Contributor
It lives in Windows 11 as well - we tried. I guess not enough companies use the virtual desktop environment to make this a priority fix. Our company is transitioning to a different ERP system by October 2025 that will no longer require the use of these Microsoft services. Maybe it will be fixed sometime before then?
DCozzy
Oct 18, 2024Copper Contributor
Do you know the KB in windows 11?
- djordan1910Oct 18, 2024Copper ContributorI do not. We tried the vanilla Win 11 images in a different hostpool to give it a try and even without FSLogix in the mix, still had black screens, random start bar failures, random authentication issues with Outlook etc etc. So whatever the issue is, it applies to Win 11 as well. We just trashed all those Win 11's and did the KIR for our Win 10 hostpools. We get a few complaints of black screens daily, but nothing like before doing the KIR. So.. its not fixed.. but its not as bad as it was before they pushed the KIR out.
- parentcharlesOct 18, 2024Copper Contributor
We've migrated a customer and all the problem were resolves with Windows 11 24h2.
I'm kind of skeptic to migrate another customer now that you say you do still have issues in Windows 11. :').
Where is the fix Microsoft? We are currently questioning the solution as we were affected by the memory leak this spring and it was still because of a faulty update. It's out of control and ridiculous.
- Oliver_KrageOct 21, 2024Brass ContributorCan anyone else confirm that Windows 11 24H2 fixes the issues? 🙂
- Mikey_DoesntLikeItOct 18, 2024Copper Contributor
I know this may not be ideal for some... but here are some things I've observed so far.
- My RDP sessions to a host only seem to be affected if I have a user on that host who is experiencing the black screen issue. This leads me to believe that the issue still lies with a user, and might be more tied to performance on the host at the time.
- I've begun to test actually nuking a users fslogix profile and having them sign back in. (I have appx disable regkey in place now). This seems to be successful as those users did not have black screen on next login.
I'm still learning from the behavior, learning from you all and waiting for MS to provide a solid RCA. Thank you all for your information and help so far.