Forum Discussion
Solved
"The paramter is incorrent" error in new Teams client (VDI)
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 follo...
- Can you try modifying redirections.xml file in your existing FSLogix implementation, and add a new exclusion for the StartMenuExperienceHost TempState data.
<Exclude Copy="0">AppData\Local\Packages\Microsoft.Windows.StartMenuExperienceHost_cw5n1h2txyewy\TempState</Exclude>
We also have this issue. Will try reinstalling it to see if it helps. We use this for our VDI environment so I won't have an answer right away.
I hope this helps. The reinstall didn't work but here's what I discovered:
Launching the ms-teams.exe file in c:\Program Files\WindowsApps\MSTeams_23320.3021.2567.4799_x64__8wekyb3d8bbwe works. However, in order for this to work I have to change the permissions for WindowsApps to give users read/execute permissions. This required changing the ownership away from TrustedInstaller. Launching the new Teams shortcut in the Start Menu didn't work. Creating a new shortcut from the WindowsApps path works.
I haven't put this into production as it's just part of my troubleshooting. I realize changing ownership and resetting permissions isn't ideal or an option for some. But I hope it sheds light into the root of the issue.
Launching the ms-teams.exe file in c:\Program Files\WindowsApps\MSTeams_23320.3021.2567.4799_x64__8wekyb3d8bbwe works. However, in order for this to work I have to change the permissions for WindowsApps to give users read/execute permissions. This required changing the ownership away from TrustedInstaller. Launching the new Teams shortcut in the Start Menu didn't work. Creating a new shortcut from the WindowsApps path works.
I haven't put this into production as it's just part of my troubleshooting. I realize changing ownership and resetting permissions isn't ideal or an option for some. But I hope it sheds light into the root of the issue.
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.
- btw. looks like there is a similar discussion in the comment section @ https://techcommunity.microsoft.com/t5/fslogix-blog/announcing-general-availability-of-fslogix-2210-hotfix-3/ba-p/4056054
