Forum Discussion

JPlendo's avatar
JPlendo
Brass Contributor
Sep 19, 2024

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's avatar
djordan1910
Copper Contributor
yes, 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.
paulcruwys's avatar
paulcruwys
Copper Contributor
Oct 03, 2024
Is 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-chris's avatar
    dit-chris
    Brass Contributor
    Oct 03, 2024
    From 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.
    • dit-chris's avatar
      dit-chris
      Brass Contributor
      Oct 03, 2024
      So I have spent all afternoon trying to get MSRD-Collect to run for Microsoft, interestingly on two hosts that we are now having issues with Entra auth it can't run the following command - I had targeted those two hosts because they were having issues currently to capture the logs.

      dsregcmd /status

      Which of course is related to the machine Entra join status which I guess is perhaps not totally unsurprising considering the issues being experienced.
      • Robert_Hurd's avatar
        Robert_Hurd
        Brass Contributor
        Oct 03, 2024
        We started having the Defender Network Protection and Defender Exclusions issue on our Win 10/11 AVD multi-session pools about mid Sept, have been working with MS for 3 weeks. Yesterday black screens at logins starting happening on mass. Outlook issues in AVD session, etc. I have applied the fix for the black screens and seems resolved. Also found that the Defender Antimalware Client Version: 4.18.24080.9 that was released on Sept 17 is causing the defender NP and exclusion issue. MS is going to revert back or at least fix the issue for go forward. I have shared all this info with MS and my open ticket. You can temp fix the issue my reverting your version with this command.
        run
        "C:\programdata\microsoft\Windows Defender\Platform\4.18.24080.9-0\MpCmdRun.exe" -revertplatform
    • HelenaKohler's avatar
      HelenaKohler
      Copper Contributor
      Oct 04, 2024

      dit-chris
      I noticed the same behavior, users #1-4 were okay, but user #5 started having issues (e.g. Outlook), so I reduced the number of maximum concurrent sessions per host to 4. We installed the KIR, too, and rebooted the machines several times. Unfortunately, we still have some users reporting the issue. 

      Such a mess!

      Next, we want to roll out new session hosts from old image (August patch version) and disable updates. We'll see how that goes 😞

      • borisg1's avatar
        borisg1
        Copper Contributor
        Oct 04, 2024

        HelenaKohler Removing September's CU didn't work for us but we didn't use the KIR. Rollback of the faulty patch probably left some rubbish on the hosts that caused a continuation of the problem. We decided to do exactly what you're planning and reinstated the image with an August patch level that's never been exposed to KB5043064. It's been three days without a complaint of a black screen on those hosts. I'm hoping it's mitigated for now until we can get the October CU tested and rolled out.

Resources