This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
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.
Can you send me your support case number? I will make sure this gets closed since there is no troubleshooting needed.
The fix will come in the next FSLogix release, as soon as we have an ETA I will update here in this thread
For us it's working for some tenant but not all tenants same non persistant image, same gpo, same licensing, same teams policies, same fslogix storage and config.
Have not been able to figure out the difference yet.
We have had it working now in our environment since March 31. One "trick" we found that needed to be done was to have users open Teams on the Web and make sure to switch to new Teams there as well. After we did that, New Teams has been loading ok. There are several shortcomings we have found. Will not open in background (regardless of checking status in settings), very poor audio performance from Echo cancellation standpoint, difficulty joining Teams Meetings from links sent by others. All-in-all, a pretty poor program, but we are forced in many cases to use it.
Yep an ETA when this will be resolved will be very handy. I'm very concerned this is not giving us enough time to properly test New Teams in VDI before the end of June 2024 deadline to move over to New Teams in vdi.
when can we expect a fix for this?
support want to start troubleshooting for known issues with is of no help