Forum Discussion
Teams not working in Windows 11 AVD + FSLogix
I am currently setting up and testing a Windows 11 AVD environment for future use, but I am having trouble with getting Teams to work properly. When a user logs in for the first time I am able to...
We have done tests on two more Windows 11 multi-session machines in our own environment.
- One with the same Virtual Desktop Optimisation Tool applied.
- One clean image without any additional stuff applied.
Both tests show the same Teams problems, so it seems to be limited to the Windows 11 multi-session image or FSLogix.
I'm awaiting to be sent the new public preview version of FSLogix in the hopes that this may contain some fix (FSLogix Release Notes - FSLogix | Microsoft Docs).
- tomdw. Which azure vm size you are using? We have the same problems, when we are using v5 vm sizes. When we go back to a v4 vm size, everything works fine. We have also issues with Outlook and Edge, when we using v5 sizes.
- We have indeed only been testing with v5 machines (D4as v5 in specific).
One thing I noticed with these machines is that the pagefile is not configured, since the D4as v5 VM comes without a temp storage. I haven't been able to test if this has anything to do with it.
But surely an interesting find that it works on v4 vm's!- We have test with d4ds_v5, d4ads_v5 and e4ads_v5. All have temp storage, but all have the problem. The v4 size also with temp storage have no problem.
- When you clear appdata for a user do you notice or have Teams show a solid purple bar on the left and then tell you it needs to restart at the top? Once restarted that bar on the left becomes white?
That's our dilemma and it the "purple bar" build works the "white bar" build does not.
We have ticket open with Microsoft atm.After deleting cache we have a purple bar but no restart message, when we restart teams we get white screens and error messages en teams will never start normal again.
When we exclude the user from using fslogix and give a local profile teams works fine. Does it also works fine without fslogix for you?
- Try an older version of Teams, like 1.4.00.XXXX this fixed out problems (pretty sure, doing more testing, but initial behavior is back to normal).
