AVD/Teams/Black Screens/Links
Posted by y0da822@reddit | sysadmin | View on Reddit | 25 comments
I am looking at some weird issues that seem to all span from a windows update on 9/15 - KB5043064.
We are having issues where users are taking a long time to login AVD machines - they eventually login but then Teams wont launch - then we notice Teams links and regular links in Outlook dont actually launch anything. Only solution is to migrate users to another host.
These are the reddit posts showing "things in common" - but I wanted to consolidate under a fresh r/sysadmin post to see if anyone got anywhere with this or am I having something going on entirely different?
https://www.reddit.com/r/sysadmin/comments/1feozsr/be_wary_of_kb5043064/?rdt=37594
Braydoherty@reddit
We have same issue and I'm pulling my hair out. Its a moving target and its not happening all the time in the same place and not all users... but many.
I am now resorting to building some Win11 hosts to put in the host pool to see if that gives any results
Proximitynz@reddit
Out of interest, can you share a screenshot of the currently applied updates to the win10 hosts?
y0da822@reddit (OP)
Same here -but we arent going to win 11 yet.
I tried the KIR - no luck.
I am taking the advice of someone else on that forum (last link in my post) and putting my pools into breadth first - maybe spreading the load instead of hitting a machine heavy will make it happen less
mjung79@reddit
Regarding AVD black screens problem, the issue in our environment seems related to load on the session host and a problem with the AppReadiness service. Stopping the AppReadiness service via Powershell Stop-Service didn't work, the service goes to a 'stop pending' state. Getting the process ID via Get-WmiObject and then using Stop-Process did work and immediately allows stuck users to complete their login.
y0da822@reddit (OP)
I am running 16x64 machines with 8 users - what are you running there?
Proximitynz@reddit
Likewise the KIR on its own didnt do anything for us, and the same appreadiness problem was occuring. It wasn't until we applied a CU that superceded the old one that the issue was resolved for us.
y0da822@reddit (OP)
Which cu was that? I did last weeks Tuesday one. I still have the issue with that and the kir
Proximitynz@reddit
When I was looking at it, it was KB5043131 that I applied that resolved the issue, I couldn't say whether that would still be the right KB or not as I'm not in the ops environments day to day, but was just helping out while the team was light on the ground with leave (I'd rather roll up my sleeves and get stuck in instead of calling someone on their well earned holiday :D)
POPUPSGAMING@reddit
Seeing this as well in uk south.
Users reporting black screens when logging into avd about 50% of the user base are effected but it's random
Best way to log users on was to force out their black screen session and put that host on drain. Log them in to another host.
Logged with Microsoft and they basically said they wouldn't touch us without us first updating our fslogix to the latest version which supposedly contains a black screen hot fix? No luck.
We have attempted a full cleanup of the hosts teams installation etc. No luck.
Once users are in they seem to have intermittent connectivity to O365 resources. Connecting to Outlook, onedrive sharepoint etc.
We tried rolling back September's windows updated as well. That didn't help.
Microsoft are asking us to make sure we have defender exemptions in place for fslogix. Working through that now.
We noticed that classic teams is gone but still wants to auto start. Feels like a thread that needs to be pulled.
Techysteve25@reddit
Supposedly this weeks patch from MS will have a fix for AVD black screen upon login....
thesaintjim@reddit
Same behaviors over here in gcc high.
y0da822@reddit (OP)
Same exact behavior sans OneDrive and SharePoint.
We have the latest fslogix since may. Isn’t that the latest? I think it was update 4. Not in front of computer right now but needed for that new teams dumpster fire.
Proximitynz@reddit
Had an environment where this was hitting it really badly. Spent some time digging deep and getting to the bottom of things as MS were giving us (and everyone else by the sounds of things) a useless runaround.
In the end, it was absolutely KB5043064 that was the problem, but as this was part of the image when using the MS provided win10 multi session host build, we couldn't get rid of it, any and every attempt to remove it failed no matter what.
Eventually found that installing KB5043131 would supersede/replace KB5043064 and with that, our issue and all our pain went away; no more black screen, no more appreadiness issues, no more appx failures left right and center; just productive users complaining that their holiday from work by way of IT outages was finally over :)
People may have found other more efficient ways of solving this, if you've come across those please share for those still out there struggling with this!
Smack2k@reddit
Do you know if that update is superceded by the October 2024 updates? I ask as we applied the October updates and it made no difference on our Windows 11 AVD VMs
Proximitynz@reddit
No idea unfortunately :( MS reckoned they were gonna fix it with the October updates but they were very vague and these days they say a lot of meaningless shit with no follow through so I tend not to take their word at face value without someone in my team validating it first.
y0da822@reddit (OP)
Thanks. We have updates run every Sunday.
Will look when I get to desk. When was that in released?
Proximitynz@reddit
Looks like 24/09, there are some pre reqs worth checking.
https://support.microsoft.com/en-au/topic/september-24-2024-kb5043131-os-build-19045-4957-preview-2d4a5c54-ac58-4bdb-8685-57d578650e5f
y0da822@reddit (OP)
You referring to these pre reqs?
Based on your installation scenario, choose one of the following:
For offline OS image servicing:
If your image does not have the July 25, 2023 (KB5028244) or later LCU, you must install the special standalone Oct 13, 2023 SSU (KB5031539) before installing this update.
For Windows Server Update Services (WSUS) deployment or when installing the standalone package from Microsoft Update Catalog:
If your devices do not have the May 11, 2021 (KB5003173) or later LCU, you must install the special standalone August 10, 2021 SSU (KB5005260) before installing this update.
Proximitynz@reddit
Yeah, in my case I just applied whatever updates were available to the machine and then manually applied the MSU without issue, but if you run into problems it's worth keeping in mind.
y0da822@reddit (OP)
Re-reading this. You’re losing me. Most of these other updates are so old. Which msu are you talking about? Wouldn’t they have been all done already or through another CU.
Proximitynz@reddit
Look at it this way. Do you have 5043064? Remove it.
If you can't remove it, install the only MSU I've referred to.
y0da822@reddit (OP)
Got it. Ok will look it all over and take it from there.
Proximitynz@reddit
Let me know how you get on, it's getting late here but hapoy to jump on a teams call if it's giving you grief; this ruined my week so anyone else I can help spare from quite so much misery I'll take :)
y0da822@reddit (OP)
Thanks. Will probably look at it today and if still issue tomorrow (hoping todays windows updates magically do something hahahaha. Plus office is being updated to latest semi monthly tonight).
This has ruined every week since that update was released. I think going on 3 weeks now.
y0da822@reddit (OP)
Ok will look. We update every Sunday via azure update manager.
Feel like that should have been pushed already. Will look.
Thanks