Teams update to 1.5.00.33362 - will not launch or crashes

Final status: Our fix deployment has completed, and we've internally validated that it has addressed the offending code regression and remediated the impact.

Scope of impact: Your organization was affected by this event, and users with usernames containing a left parenthesis while omitting a right parenthesis couldn't sign into the Microsoft Teams desktop client with the latest version of Microsoft Teams.

Start time: Wednesday, December 7, 2022, 6:21 PM (6:21 PM UTC)

End time: Tuesday, January 17, 2023, 7:29 PM (7:29 PM UTC)

Root cause: The most recent Microsoft Teams desktop client update introduced a code regression inhibiting users with usernames containing a left parenthesis while omitting a right parenthesis from signing into the Microsoft Teams desktop client.

Next steps:
- We're further analyzing the Microsoft Teams desktop client update along with the introduced code regression to help us identify similar problems during our validation process and before they're able to produce impact.

This is the final update for this event.

thanks for sharing. I have an active ticket with Microsoft who said they would keep it open to provide updates, but that isn't happening! so appreciate you posting it! :-)...

January 13, 2023 6:44 PM

Title: Some users can't sign into the Microsoft Teams desktop client with the latest version of Microsoft Teams

User Impact: Users can't sign into the Microsoft Teams desktop client with the latest version of Microsoft Teams.

More info: Those able to revert to a previous build report that this bypasses the issue. Additionally, users who have access to the Microsoft Teams web or mobile apps can use those connection methods to avoid this problem. We recommend users manually install the Microsoft Teams version 1.5.00.31168 as an immediate remediation action to access the Microsoft Teams desktop client. This version can be found here: https://statics.teams.microsoft.com/production-windows-x64/1.5.00.31168/Teams_windows_x64.exe.

While we continue to work on fully resolving this issue, we recommend that users periodically check their Microsoft Teams desktop client version to ensure that they're using the aforementioned previous version. Those who have reverted their clients but are back on their current impacted build should uninstall the client and reinstall using the previous link provided, reach out to their support representative, and request that automated updates should be halted until the resolution of this event.

Current status: The fix deployment is approximately 50 percent complete, and we suspect that the fix will complete deployment by Tuesday, January 17, 2023.

Scope of impact: Your organization is affected by this event, and users with usernames containing a left parenthesis while omitting a right parenthesis can't sign into the Microsoft Teams desktop client with the latest version of Microsoft Teams.

Start time: Wednesday, December 7, 2022, 6:21 PM (6:21 PM UTC)

Estimated Time to Resolve: We anticipate impact to be fully resolved by Tuesday, January 17, 2023.

Root cause: The most recent Microsoft Teams desktop client update introduced a code regression inhibiting users with usernames containing a left parenthesis while omitting a right parenthesis from signing into the Microsoft Teams desktop client.

Next update by: Tuesday, January 17, 2023, 10:00 PM (10:00 PM UTC)

Hi from Hamburg, Germany
We have the same problem with serveral windows10-notebooks since early december. Windows 11 machines don't seem to have the problem, here v1.5.00.33362 works correctly. It's a lousy service that Microsoft is obviously unable to fix the bug caused by its own update in early December. Due to the automatic update, which cannot be switched off, Teams is shot down every day and the old version (v1.5.00.31168) has to be reinstalled manually. We handle all communication including phone via teams, currently no joy
Roland

Dear Pernille-Eskebo, Can you please fix this soon? I have to uninstall v1.5.00.33362 every day and install the latest working version: v1.5.00.31168. Can you make v1.5.00.31168 the current version (maybe you want to call it v1.5.00.34...) and disable the auto-updates please? Sounds like a quick and easy fix to me.
Thanks,
Edgar Walther