Additional meeting and call-related features and issues within Microsoft Teams for business
Any news on when this is out?
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
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.
Additional meeting and call-related features and issues within Microsoft Teams for business
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.
Any news on when this is out?
For everyone's benefit, the only way to address this issue "the parameter is incorrect" at the root, is to use FSLogix Hotfix 4, which is now planned for GA on May 14th:
Hi. I have now got this and installed inside of a brand new image we have created. However, when I log on as an existing user with an existing FSLogix profile, it is still loading classic teams. New Teams is also on the desktop but it doesn't load that by default. There is no classic teams installer installed on the image as it is a brand new image. How do I stop an existing user fslogix profile from loading classic teams?
Ah, just like Congress, waiting until the last minute to address the issue.
We have installed FSLogix Hotfix 4. So far, "The parameter is incorrect" error has stopped. There are other issued for other threads, but this issue seems to be no longer affecting us.
Is there a possible solution for notebooks that get a pushed windows update or teams update via SCCM?