Forum Discussion
Teams not working in Windows 11 AVD + FSLogix
I can confirm from my experience simply swapping to a v4 vm has solved most if not all of the Teams issues. Early testing but after 5 logins, no Teams crash yet.
Thanks for the heads up. Complex / silly issue, easy fix (long term hopefully) Will try v5 vms again at some point.
hgf12345 Hey! Last update in thread is quite old. Is the fix still to use a v4 image? I'm also experiencing this issue of Teams whitescreen/crashing using the latest fslogix and Teams machine-wide versions, but just using the small B2s VM size for testing; does not specify what version it's running on.
Just hoping someone can confirm.
Thanks,
Josh
- Thanks. The only reason we are switching is due to support for fixes being dropped for Universal Print on Win 10. We just rolled out Win 10 AVD to 200 users and had an issue. MS dropped the bomb on us that they are no longer fixing UP issues on Win 10 AVD. Nice.
- Good luck, we have been using
Standard D16ads v5 and have been sweet for 3 or 4 months now. - Gotcha. That's the version I'm using. Will take a few weeks to get results.
- 2.9.8612.60056
sgajula Crucial thing for us was not necessarily the SKU, but to ensure it had a TEMP drive build in to handle the pagefile. And ensure you have enough resources overall per VM per person.
Not sure on Win11, we only used Win 10.
My advise would be to boot up a really beefy VM with a TEMP drive, and see if the issue occurs for a day or so. yes it will cost, but then you will know if this is the issue or not.
After battling intermittent issues for 1year + for us, this was the fix. has been sweet ever since.
- Changing SKU doesn't help. Provisioned V4 generation VM. Still teams crashing.
- I tested it only on Windows 11 22H2 . Tried it with Profiles containers, ODFC Containers, and Cloud cache. All combinations failed. Same White screen issue while attending meetings and calls. Once in a while AVD session also freezes. I am looking for a solution for this issue.
I think, I must try once by resizing the VM to v4 version. - Have you tried the beta and seen if that worked better/worse? We aren't looking to implement Windows 11 until we have to. It barely runs right on a local machine let alone in a multisession environment. Ya'all crazy moving to it so early. 11 will be the new 8.1.
Looks like this issue still persists in AVD. D8as v5 + Windows 11 +FSLogix combination is still causing this issue. Has anyone found the permanent solution for this issue? Which combination is not causing Azure Teams blank screen issues on Multisession hosts? Kindly suggest.
- We experienced 'random' white screens in Teams and other app crashes for many of our users as the day would go on. We have been battling this issue for past year and have now determined after much testing this was related to VM size, specifically the lack of Temp drive/pagefile.
We used Standard D16s v5 and have now switched to Standard D16ads v5. For the first time ever in the past two days we have not had Teams whitescreen/edge crash.
Advise for anyone one with these types of issues is to ensure you have appropriate VM size, session limits. No amount of application level changes helped.
note: we have only used Windows 10, Win 11 was trash for us in POC and wont be looking at implementing unless forced. - I would love to understand why Win11 hates the v5 resources so much. We got crushed for MONTHS trying to use Windows 11 on the d8as_v5 resource. I can't tell you the amount of time and energy and articles and uninstalling and reinstalling we spent on Teams issues, only to have to abandon Win11 altogether.
- We use the Windows 10 22H2 EVD + MS 365 Apps Gen2 (multi-session). I can't recall the differences between Gen 1 and Gen 2, but we have not experienced any issues with this image in reference to Teams or Office installations.
- My latest AVD project was on Win 10 (v5 vm and no issues) and haven't tried Win 11 AVD again. I also haven't been brave enough to move the Win11 project to v5 vms, but can confirm everything works well with v4 vms when using Win11.
I would try D2 v4, even for a short time, and see if that helps. tamaneri Thanks. Will give Win10 AVD a go. Any suggestion on which Win10 image to choose? IE. Have you found any differences between say Win 10 Enterprise Multisession 22H2 vs. 22H2 Gen2? I've heard staying away from the "+ Microsoft 365 Apps" since those images tend to causes issues b/c the custom registry settings, not specifically built for non-persistent AVD with FSLogix - it's best to follow the FSLogix 365 apps/OneDrive/Teams install guides.
We never got to the bottom of the issue(s) we were experiencing with Teams. Ultimately, we abandoned Windows 11 in our AVD environments, and all those annoying issues disappeared and have not resurfaced. My take is that Windows 11 was just not ready and too buggy. Painful to say the least.
