Forum Discussion
Azure Virtual Desktop - Black Screens on logins - What we've tried so far
Applying the KIR has not worked for my org. We have tried with the Sept CU update both installed and uninstalled.
I'd also like to share some odd behavior.
Prior to applying the KIR, we saw crashes with faulting application name: svchost.exe_appXSvc, faulting module name: appxdeploymentserver.dll
After applying the KIR, we now see a crash with faulting application name: svchost.exe, faulting module name: aphostservice.dll.
Additionally we are seeing the following:
- When the issue occurs, users who are already logged onto a host see app instability, for example Outlook or OneDrive crashes.
- If a user logs on for the first time whilst the issue is occurring (i.e. they do not have an existing FSLogix profile), SSO will not work for OneDrive, and 365 shared licensing will be broken.
This has been a complete nightmare, not only can users not logon but existing sessions are affected. My org is reevaluating its use of AVD.
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.
- 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!dit-chris
100% agree with you.Has anyone tried disabling FSLogix? We are running some tests right now and it seems that the issue does not occur when FSLogix is disabled.
(Not a solution for our productive workloads, of course.)
- we were testing the behaviour with FSL set to 0 (enable=0) and we did not experience any blackscreens during log in. What is more, we also have Personal hostpools in our org, on which we do not have FSL at all - and everything works there. No blackscreens, so for sure its related.
Today we got the following message from MS :
"Please note this issue started with KB 5040525: July 23, 2024—KB5040525 (OS Build 19045.4717) Preview
so we recommend uninstalling this and one, also KB 5041580: August 13, 2024—KB5041580 (OS Builds 19044.4780 and 19045.4780) and
KB 5043064: September 10, 2024—KB5043064 (OS Builds 19044.4894 and 19045.4894)
The fix will be included on the KB5045594, which will be released 3rd week of October.
"
So it looks that we are all getting different answers in regards to potential fix.... its crazy.
Experienced the same issues since mid September. Logged a MS case and still pending feedback. Apart from the usual 'log gathering' , create memory dumps etc..... there does not seem to be permanent fix or a 'confirmation' of a larger AVD service issue.
Also had the AppXSvc service hammering the VM's.
svchost.exe 8224 AppXSvcGot fed up and re-imaged the first batch of hostpools VM's on the 2nd & 3rd October and so far, all is 'ok'
Waiting 'patiently' for Oct update and then we re-image the weekend again. Holding thumbs, it does not get broken again.
