Forum Discussion
Azure Virtual Desktop - Black Screens on logins - What we've tried so far
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.)
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.
- dit-chrisOct 07, 2024Brass ContributorTo 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!- chrissmith585Oct 07, 2024Copper Contributor
After a day of production (Mondays have been the worst by far), I can report that the KIR "fixed" the issue entirely. We are back to getting a very timely response on connections, and no user complaints at all. Ready to close out this incident, and we will apply the KIR to all of our AVD servers in our environments.
Strange that this issue and the KIR doesn't seem to be published (if I'm wrong please correct me). I'm only finding forum posts about it. I happened across this one by accident after noticing an interesting error code, and it turned out to be the exact root cause and mitigation we needed. Everyone's been yelling at us about this for almost a month and it went all the way up the chain and no one understood what to do until now.
Thanks everyone for sharing info.
- Oliver_KrageOct 07, 2024Brass ContributorDoes this KIR work on Windows 11 or is it just Windows 10?