Forum Discussion
New Teams Update Issues
Hi,
Just getting to grips with the new Teams in AVD.
Can see in the client that there is an update, select Update and Restart, it closes. Then it re-opens and shows that it still requires an update.
I then looked at the event log and can see that it has indeed errored, anyone come across this?
Thanks.
Please install KB5039299 for Windows 10 to fix this issue.
https://www.catalog.update.microsoft.com/Search.aspx?q=KB5039299
After a lot of troubleshooting with Microsoft Support and Engineering teams, the issue has been solved! I was told that it had something to do with a known bug in sysprep when using the /mode:vm switch causing issues with preregistering Teams.
I'm not sure if the bug itself has been fixed, but for Teams the issue has been resolved after installing the June preview update (KB5039299)
- Hello everyone,we have experienced the identical behavior:Here our test steps:
- Create Ref-VM based on Win 10 Ent Multisession 22H2 from the Azure store
- Start, VM, Login as Local Admin, uninstall FSLogix version X
- Reboot Ref-VM
- Install FSLogix version 2.9.8784.63912
- Set registry keys:
HKLM\SOFTWARE\Microsoft\Teams
name: IsWVDEnvironment
type: DWORD
value: 1
HKLM\SOFTWARE\Microsoft\Teams
name: disableAutoUpdate
type: DWORD
value: 1 - Install New MS Teams Version Teamsbootstrapper.exe -p -o c:\install\MSTeams-x64.msix
- check MS Teams status with: PS>Get-AppxPackage -Name msteams*
8. run Sysprep.exe /generalize /oobe /quiet /shutdown /mode:vm9. capture the image -> Azure Compute Gallery10. create Test-VM from new Gallery Image11. login with local admin12. check MS Teams status with: PS>Get-AppxPackage -Name msteams*Icon in the start menu -> greyed out...
Teams doesn't start......
Conclusion:
Once we change the sysprep command from:
Sysprep.exe /generalize /oobe /quiet /shutdown /mode:vm
to ...Sysprep.exe /generalize /oobe /quiet /shutdown
the problem seems to be solved... but the provisioning process for new vm's needs more time
Question:
What is the exact funtion of the sysprep switch mode:vm?
Regards, PatrickI can confirm new teams works fine when omitting the /mode:vm. For here's MS explanation of /mode:VM: Sysprep Command-Line Options | Microsoft Learn
Does anyone have updates from their tickets with microsoft?
- I also confirmed this with Microsoft Support. I have collected logs and the support agent is currently reviewing these logs. I'll post an update when there's something new to report 🙂
- /mode:vm does something relating to drivers. So /mode:vm will skip drivers because its hypervisor so no drivers. that's why it takes longer without it. thank you though for posting this, i'm gonna sysprep without /modeVM and run with it. i of course waited till the last minute to test this before deploying my new image overnight tonight.
- I'm currently facing the same issue, thank you for sharing this.
Currently in the process of troubleshooting this with Microsoft support.
Kidd_Ip Just to add what I said before. This seems to be the issue. So I install the new Teams using the bootstrapper on the image. All looks fine. I then Sysprep and deploy. This is all the user gets.
New Teams is greyed out:
When you click it you get the following error:
We have the latest FSlogix hotfix 3 installed. Even logged in with a local account outside of FSLogix, same issue. Patched to March.
If I were to deploy this to 30 session hosts I can't be logging into each one of them to manually fix. Also when it comes to redeploy again i'll be in the same boat.
Followed the instruction to the letter, including installing bootstrapper -p -o and using the msix file.
New Teams opens fine before Sysprep. Any ideas what could be wrong?
Thanks.
- I've raised this to Microsoft Support. Done it at several clients now where the New Teams is disabled/broken after sysprep.
- Hi,
Thanks for this, I did indeed just re-install again, but had only just installed it for the first time the day before. I'm finding all sorts of issues with deploying this in AVD.
Have just done one now where its fine on the image using the bootstrapper install, sysprepped, deployed, the users then found the new teams icon greyed out and an error stating it needs re-installing. Not too mention the Outlook addin not always staying installed.
Things have got to improve.
