Forum Discussion
Azure Virtual Desktop - Black Screens on logins - What we've tried so far
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.
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.- To be fair that is basically the line I had from them - slightly different build numbers (but I think that was likely an error - the KIR references 5040525 in the file name) as they had said the July patch Tuesday build rather than July preview (for August' patch Tuesday) that they wanted us to uninstall... well having uninstalled KB5043064 and it reverted to KB5041580 we couldn't then get back past that anyway and their efforts to do so involved "editing it out" via the registry (which I am yet to be convinced wasn't just removing they systems knowledge of the patch existing for reporting/display purposes to make it look removed as winver still shows 4780 as the build number) which in the process totally screwed up the VMs; completely broke all local printers so no one can PDF any documents etc.
But basically that 3rd week October another way of saying it will be in the November patch Tuesday release - just you can have it in October for anyone brave enough to install a preview release onto a session host and risk jumping from the frying pan into the fire! (or am I just rather cynical of Microsoft's release testing these days 😂) - it won't be releasing tomorrow although I guess it might get mentioned on the known issues list; although at the moment they are doing a fairly good job at covering this up as it probably isn't a very good look for trying to sell AVD and FSLogix as a product to admit a regression originating in late July isn't going to be fixed for 3-4 months!
HelenaKohler we setup an entirely separate host pool with just a few machines without FSLogix.. and a small test pool of 5 users. made no difference. Still had black screens issues
- Odd djordan1910, my understand was it was connected to (or exacerbated by) how FSLogix loaded and unloaded profiles as one of the "fixes" we were given was to disable the removal/cleanup of profiles on log off as option in FSLogix... I assumed that would then stop it maybe triggering a full AppX refresh when the profile was loaded. That made me suspect it likely this maybe also happens on normal users on a desktop/laptop too - but if it only happens at the first login/once post update then I suspect you just go "its taking a while to login this first time" but then due to fast user switching/fast boot it maybe doesn't show again as the profile is still in c:\users (unless you have like roaming users on pool devices) - I suspect FSLogix you get a cleanup process post logoff so that every login is seen as a "new" one as we see it say it is deploying ~70 AppX packages in FSLogix profile logs.
Be good if they provided some proper details on what the issue is wouldn't it!
