Jan 25 2024 11:44 PM
Hello
We have a serious issue with the new Teams client in our VDI (Horizon) environment. After running fine for a while (can be multiple hours up to days) Teams crashes / vanishes with the following error.
We suspect it might happen during an automatic update. The same error is displayed when trying to launch ms-teams.exe from that path manually. This never happened with classic Teams. We have no idea what causes this and how to fix it, any help is appreciated.
Feb 02 2024 12:31 AM
I have the exact same problem with a client, I've tried erasing all that has to do with teams and reinstalling but still get the same error, the old teams works fine. @MTU42
Feb 02 2024 02:33 AM
Feb 22 2024 12:40 AM
Feb 23 2024 05:56 AM
Feb 26 2024 08:14 AM
Mar 05 2024 03:23 AM
Mar 12 2024 12:42 PM
@MTU42 I do, but I we use Citrix. We tested this with and without folder mirroring, and there seems to be an issue with my inclusions when I use mirroring. So I have to sort it out and I wouldn't say this is an FSlogix issue.
Mar 15 2024 12:58 AM
Mar 25 2024 08:18 AM
@MTU42 We do use FSLogix, but we are not including Teams in that container, just Outlook and OneDrive. I believe this has to do with our Citrix profile exclusions.
Mar 26 2024 10:10 AM
@jcarbajal Any news after reinstalling?
Mar 26 2024 11:44 AM
I had to reinstall the OS then the problem did not come back @Prcontr
Mar 28 2024 08:14 AM
May 02 2024 09:56 AM
Jun 01 2024 06:30 AM - edited Jun 02 2024 11:09 PM
Hey Guys,
I've been trying to debug this this for WEEKS. At some point I certain that I've had surfed EVERY page on the web, but nobody came up with a fix that solved this problem in my envoiroment . Finally, just today, I managed to solve the problem for good.
My Users got exactly this error when tying to start the New Teams Client:
We are using a Remote Desktop Session Host envoiroment (RDSH, a.k.a. Terminalserver, operating on Windows Server 2022 (but I had the same error prior the InPlace-Upgrade on Server 2019), however we are NOT using FSLgix, like a hundred other buddys i found out there on the web, trying to solve this problem (apperantly they solved their problems by upgrading FSLogix).
My solution may sound stupid, but works 100% for two ADs that i manage. So... "If it's supid, but it works: It ain't stupid" 😉
In the end, the problem was caused by a GPO. I was able to solve the issue by adjusting this user-trageted GPO:
User Configuration > Preferences > Control Panel Settings > Internet Settings > Internet Explorer 10 > (Tab: General) > (Section Browsing history) > Settings. Here, my users hat an alternative path for their TEMP-Files:
I updated this setting by removing the path and leaving the setting blank:
I saved the GPO and as soon as my users logged in, the New Teams Client started like nothing ever happened.
Surely, I didn't go for this setting in the first place, but I found out that RDSH-Users without GPO could start the New Teams Client, users with a GPO assigned could not. So I narrowed it down, by cloning my PROD-GPO, assigning the Clone to a test user. Then I removed GPO-settings from the Clone bit by bit until I had a working New Teams - until finally, I narrowed it down to THIS specific setting.
I have no idea, why this setting is responsible for causing the problem, but after weeks of frustration, I only care for the problem to be finally fixed. All my >250 RDSH-Users are able to use the New Teams Client now.
EDIT: For everyone who is facing the same problem: My problem might have been caused in the first place by a registry setting, that we had in one of our user GPOs. This Registry-Setting is basically the same like the Internet Explorer 10 setting mentioned above. So if your system has the same issues like mine, it's work checking this setting too: User Configuration > Settings Registry
Jun 03 2024 10:10 AM
Jul 01 2024 02:56 AM
Sep 03 2024 03:26 AM - edited Sep 03 2024 03:41 AM
Iam still facing issues with the Teams UWP app shortcut in startmenu.
W2019 RDSH. FSLogix 2210 HF4 with correct exclusions in redirection.xml. Internetoptions in place like described by ehm-weh. No redirection of INetCache in place. No Citrix UPM. NTFS security settings on C:\Programs\WindowsApps are correct (same as in a know-good environment). AllowAppInstallation etc. has been set (via GPO and via Registry prior Teams Installation).
Iam still getting ms-teams.exe: parameter is incorrect on all existing user profiles when using the UWP shotcut in the startmenu. Also on new user profiles. Also after a complete uninstall and reinstall of Teams. Teams on RDS is a real pita...
Any ideas? I sure can place an additional shortcut into the startmenu / on the desktop which points to ms-teams.exe and it will work fine. Thats kind of a workaround. BUT: That faulting UWP shortcuts also stays in the startmenu. My guess is that something goes wrong when the Teams app registers itself, but I cannot seem to get my hand on "why".
Sep 04 2024 10:46 AM
SolutionSep 04 2024 11:09 AM
Sep 04 2024 10:46 AM
Solution