Forum Discussion

Copper Contributor

Jan 26, 2024

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...

crash

microsoft teams

parameter is incorrect

VDI

Fernando_Klurfan
Sep 04, 2024
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>

BjoernBeninga

Copper Contributor

Sep 03, 2024

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".

Fernando_Klurfan

Microsoft

Sep 04, 2024

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>

BjoernBeninga
Copper Contributor
Sep 04, 2024
I can happily report, that this Exclusion resolved my issues. Thank you very much, this one was bugging me! 🙂
- BjoernBeninga
  Copper Contributor
  Sep 04, 2024
  FYI - my exclusions are looking like this now:
  
  
  <Exclude Copy="0">AppData\Local\Packages\MSTeams_8wekyb3d8bbwe\LocalCache\Microsoft\MSTeams\Logs</Exclude>
  <Exclude Copy="0">AppData\Local\Packages\MSTeams_8wekyb3d8bbwe\LocalCache\Microsoft\MSTeams\PerfLog</Exclude>
  <Exclude Copy="0">AppData\Local\Packages\MSTeams_8wekyb3d8bbwe\LocalCache\Microsoft\MSTeams\EBWebView\WV2Profile_tfw\WebStorage</Exclude>
  <Exclude Copy="0">AppData\Local\Packages\MSTeams_8wekyb3d8bbwe\LocalCache\Microsoft\MSTeams\EBWebView\WV2Profile_tfw\GPUCache</Exclude>
  <Exclude Copy="0">AppData\Local\Packages\Microsoft.Windows.StartMenuExperienceHost_cw5n1h2txyewy\TempState</Exclude>