New Teams prompting "The parameter is incorrect" error.

Thank You for Your suggested solution. If have this issue in several laptops, only on Windows 10.

So far I ran into the situation, that You aren't able to start the Teams Classic and any updates fails.

Uninstalling New Teams and using teams classic fails also, because MS want stop Classic Teams and will switch You to New Teams. The obligated update will fail and You stuck without teams.

The strange thing, the problem occurs only sometimes, but if it occurs, there seems only two solutions:

• reinstall windows 10
• grant access rights to the teams folders.

I did two things and all seems to be working so far.

On both pools that I am running, I have teamsbootstrapper.exe and MSTeams-x64.msix in a folder "C:\Teams" and I uninstalled New Teams from the Gold Image using teamsbootstrapper.exe with this at a command prompt .\teamsbootstrapper.exe -x

I then reinstalled with bootstrapper.exe using this .\teamsbootstrapper.exe -p -o "c:\teams\MSTeams-x64.msix"

On my AV pool that I am testing, I added these exclusions

\Program Files\WindowsApps\MSTeams_*\ms-teams.exe
\Program Files\WindowsApps\MSTeams_*\ms-teamsupdate.exe
\Program Files\FSLogix\Apps\frxsvc.exe

Just wanted to say thanks for your information. I've been spent the last 4 days trying to figure out this issue. We're using Horizon 8 Instant Clone with FSLogix containers and Sentinel One AV. Your steps seems to work things out for me. I was installing from a UNC path and could never get the success statement unless I omitted -o. The only thing left that's puzzling is that on first load in for a user, it seems to take up to 20 minutes before we're able to launch Teams. It's like it's handling the install for the user during that time frame. After that and on subsequent logins, it works as expected.

Back to getting the error.

Hey Microsoft, can you help AT ALL!

I did two things and all seems to be working so far.

On both pools that I am running, I have teamsbootstrapper.exe and MSTeams-x64.msix in a folder "C:\Teams" and I uninstalled New Teams from the Gold Image using teamsbootstrapper.exe with this at a command prompt .\teamsbootstrapper.exe -x

I then reinstalled with bootstrapper.exe using this .\teamsbootstrapper.exe -p -o "c:\teams\MSTeams-x64.msix"

On my AV pool that I am testing, I added these exclusions

I have been having the same issue. We are on a VDI system with VMware, so that complicates updates slightly. I have found that if I wait a few minutes after logging on and then try to open Teams, it seems to open. Autostart does not work. I have not tries this enough to know that it is consistent.