Forum Discussion

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...

KevHal

Iron Contributor

Oct 07, 2024

It is about time Microsoft publicly acknowledge this issue. I'm watching more and most host pools get this issue on a daily bases.

The KIR is hit and miss. I think the appx issues causes some damage to AAD.brokertoken which is turn breaks authentication to office/teams etc. This is host specific, resetting profiles does not resolve the issue. I have had to rebuild hosts from an older golden image and block updates completely.

Some things really need to happen:

A:) Pull the September update, or
B:) Public OOB hotfix that includes the KIR. Or fixes the issue with appx (End of October is not good)
C:) Patch Tuesday tomorrow (8th Oct), I've heard the KIR will get overwritten by this update, which will still include the Appx issue, so we may be back to square one.
D:) At least some kind of public statement that this is being looked at, several Microsoft support engineers have been giving different answers.

dit-chris

Brass Contributor

Oct 07, 2024

KevHal I agree the KIR doesn't really seem to work and some of the mitigation Microsoft have applied have basically wrecked some of our hosts - to the extent that we have gone into this morning with a half deployed new host pool running a minimum viable product app stack on a clean image - although I do wonder if that is much better as its still got the last 3 months patches on along with the KIR deployed. My thinking is that even having applied the KIR and/or rolled back that September update that the AppX deployment state had got totally screwed up with stuff previously half deployed.

A) probably can't happen as you also need to everything back to July (if not the late June preview) - that is what the KIR targets back to when you look at the KB number
B) agreed
C) my understand is it shouldn't due to the way the KIR works and the fact it relates to a KB from July
D) that is what really irks me... not getting a straight answer, ones even told me there was no known issue because it wasn't on the Windows health dashboard!