Teams AVD Optimized forcing unusable build (Preview maybe?) after the applications first run.

Question

This started happening mid January - User contacts me saying their File Area inside of all the channels in their Teams (of Microsoft Teams) in AVD do not work. Also hear complaints of white screening, Spellcheck 100% doesn’t work. All apps fails to open UNLESS you pop them out.

I clear /Microsoft/Teams in the Roaming Appdata and its fixed, so I thought. Weeks go on and we hear this more and more, turns out the entire company has this problem only in AVD. Fast forward to now and it's still an issue and we can't figure out why.

We use: FsLogix, Nerdio, Windows 10 Multisession - Again this all worked fine up until Mid January 2022. The issue does not occur with AVD Optimized Teams when FsLogix is removed from the picture. FsLogix is on 2.9.7838.44263

What we do know:
The build that works has a solid purple navigation/appbar on the left.
The build that doesn't work, that is auto-imposed after restart/sign out/force kill and stays in effect forever (unless you remove the appdata or delete the profile) has a light purple/lavender navigation bar.

Good Build - see how it wants to auto-impose the new meeting experience?

Bad Build – Color scheme changes completely and all the features are broken.

Both builds show the same version which has jumped from a 1.4 to a 1.5 build over the course of this issue.

Neither show the Activate Public Preview mode
![175468-image.png][3]

Last Friday we noticed we had Teams has Preview Features Enabled in the Teams Admin, we turned that to Not Enabled last Friday (almost a week ago) we also changed Office Update policy to the 6 month channel. Still didn't fix the issue.

I've ruled out GPO and the image. I ruled out the image by building a 100% bare Windows 10 Multisession image and only installed Fslogix and Teams through Nerdio with the AVD RegEdit and WebRTC all of which are the latest versions because the script used calls out to Microsoft for the version and installs it. Same issue occurs. I've deleted appdata and my own profile 100 times in the past few weeks trying to figure this out.

1: /api/attachments/175409-goodbuild.png?platform=QnA [3]: /api/attachments/175468-image.png?platform=QnA

Answer 1

Thank you so much, @Dalton Reeves for troubleshooting this and sharing your solution. I'm reposting this here for additional visibility:

At this moment I believe I have figured out a solution. Appears at some point (around mid January or possibly even late 2021) there was a Teams update that started the breakage, and slowly got more... broken :)

All in all I installed an earlier version of Teams - 1.4.00.19572 and everything works fine from what I can tell. I do urge you to do your due dilligence when locating 3rd party repositories for former version of Teams and scan/sandbox/test the installers for safety. I'm trying to get verification on a known Microsoft Approved repository for Old Teams Versions, but I don't have that info yet.

Edit: Updated (see @Dalton Reeves answer below for URL)

So a few things to add here as I am 99% sure we have this fixed in our environment.

1. I found a safe way to get old versions of Teams - use this link and sub the version (replace 1.3.00.14461 for instance) for any valid version you want to use - (URL in answer below) - this of course if for the MSI version (64 bit) so you can install the Machine Wide Installer needed for VDI installation. - https://learn.microsoft.com/en-us/azure/virtual-desktop/teams-on-avd
2. IMO you'll want to use the ALLUSER=1 switch (stops auto updating) which is what got us in this mess. - https://learn.microsoft.com/en-us/microsoftteams/teams-for-vdi#deploy-the-teams-desktop-app-to-the-vm
3. Also, don't forget the current WEBRTC download and make sure you install the Regedit for AVD optimized. We used Nerdio in the past so this was all automated and we had to adjust our deployment method - https://learn.microsoft.com/en-us/azure/virtual-desktop/teams-on-avd#prepare-your-image-for-teams

Answer 2

So a few things to add here as I am 99% sure we have this fixed in our environment.

1. I found a safe way to get old versions of Teams - use this link and sub the version (replace 1.3.00.14461 for instance) for any valid version you want to use - https://statics.teams.cdn.office.net/production-windows-x64/1.3.00.4461/Teams_windows_x64.msi - this of course if for the MSI version (64 bit) so you can install the Machine Wide Installer needed for VDI installation. - https://learn.microsoft.com/en-us/azure/virtual-desktop/teams-on-avd
2. IMO you'll want to use the ALLUSER=1 switch (stops auto updating) which is what got us in this mess. - https://learn.microsoft.com/en-us/microsoftteams/teams-for-vdi#deploy-the-teams-desktop-app-to-the-vm
3. Also, don't forget the current WEBRTC download and make sure you install the Regedit for AVD optimized. We used Nerdio in the past so this was all automated and we had to adjust our deployment method - https://learn.microsoft.com/en-us/azure/virtual-desktop/teams-on-avd#prepare-your-image-for-teams

Answer 3

@Anonymous - I just sent a PSR of the issue, current MSFT tech is having me try compatibility modes to see if the behavior persists - it did. But the PSR I just sent will show the issue in detail if you have access to that. There was also other PSRs sent to that current ticket as well outlining the issue.

If you want I can also send it directly to you if you want to send a me a repository link or an email.

Thanks,

-DR

Answer 4

was this ever fully resolved, besides going back to a very old version of Teams?