New Teams prompting "The parameter is incorrect" error.

Anonymous
2023-11-28T13:43:19+00:00

New Teams has been advertising itself to many of my users. Majority of the company has made the switch, but others are running into a parameter error. Strange bit is, I can get it to work for about 5 days. Afterwards, I'm guessing an update takes place, and New Teams refuses to open and throws a parameter error. I've tried reinstalling the application multiple times and downloading the app installer. Nothing seems to work.

C:\ProgramFiles\WindowsApps\MSTeams_23285.3607.2535.937_x64__8wekyb3d8bbwe\ms-teams.exe

The parameter is incorrect.

Microsoft Teams | Microsoft Teams for business | Meetings and calls | Other

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

56 answers

Sort by: Newest
Most helpful Newest Oldest
  1. Anonymous
    2024-02-21T22:43:10+00:00

    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.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  2. Anonymous
    2024-02-20T14:29:34+00:00

    We are also seeing this in Azure AVD as of 2/20 with over 100 users. Nothing I have found has resolved.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2024-02-13T21:22:52+00:00

    Got off the phone with Microsoft today, February 13, 2024. It was for another issue with New Teams (Try a different browser...). The solution was to revert to Classic Teams. That users are experiencing a lot of issues with New Teams and it is "not ready". Meanwhile on the Teams Admin Center it says this -

    Please get this thing right Microsoft!

    Was this answer helpful?

    0 comments
  4. Anonymous
    2024-02-13T14:41:00+00:00

    Back to getting the error.

    Hey Microsoft, can you help AT ALL!

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  5. Anonymous
    2024-02-02T13:24:02+00:00

    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

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments