Dec 15 2022 02:21 AM - edited Dec 16 2022 01:27 AM
Teams updated version 1.5.00.33362 will not launch correctly when users have special characters in their display name. App crashes, or prompts for a sign in which will not be successful.
A similar issue was seen back in Feb 2022 when Microsoft rolled out Teams version 1.5.00.2164. The same root cause was identified, special characters in the display name. Teams version 1.5.00.2164 bug - Microsoft Q&A
A support case is open with Microsoft, though please do raise your own cases with them to ensure they pick up this issue. Mobile and web versions of teams remain unaffected by this latest bug.
Clearing teams folders in %appdata%\Microsoft\Teams and restarting teams may provides some relief for a short period of time.
Dec 15 2022 09:04 AM
Dec 15 2022 09:22 AM
Dec 15 2022 09:57 AM
Same here. It's unbearable - we are trying to use the version from before. Hope that will be fixed soon.
Dec 15 2022 11:36 AM
Same as everyone else we also have the same issue. I am not sure why there is not wider call for this.
At the moment we just either use the app on phone or the web version.
Anyone from Microsoft could provide some feedback and how we can fix this?
Dec 15 2022 02:00 PM
I have been seeing this across 3 of our users with very regular issues. ie. not opening at least once a week. -- This is resolved by clearing the cache in %appdata%/Microsoft/Teams however constantly doing this is not ideal.
reported and verified issue: They open their PC in the morning - Teams loads as a white or black window and will not fully boot. - Windows10 users will receive message notifications but not be about to open them. Windows 11 users get nothing.
We do not see sign-in prompts however.
Dec 15 2022 10:02 PM
Dec 16 2022 12:05 AM
Hello, we have the exact same problem. We were able to find out that the problem only exists, if we have local usernames (AzureAd\Username+Special Character) or profiles path with special charackters. On the same Devices Users without special chracters are able to use the Teams App in the new version 1.5.00.33362. By Azure Ad Only Devices and AzureAd Only Users the localusername is generated by Windows from the displayname in AzureAD. We have no option to exclude any special charcters in this case. If we change the Displayname after the first logon, the windows client is not able to change the local username anymore. So because of same special charcters in the displaynmae all of our devices/user have this impact (at the moment about 600 User).
Dec 16 2022 12:58 AM
Thanks for sharing the special characters, this certainly fits the criteria for the issues we are seeing. I seem to recall this happening on a few previous versions back, with special characters being the cause again!
Hopefully they will sort this out asap.
Dec 16 2022 09:12 AM
Dec 18 2022 07:01 PM
Dec 19 2022 12:34 AM
I had an update on the case I raised with Microsoft on Friday evening...
"We can confirm that reported issues has been highlighted to our engineering team to fix the issues in near feature with upcoming firmware versions and there is no ETA for now."
We have rolled back to version 1.5.00.31168 which is stable for our user base.
I hope Microsoft have pulled 1.5.00.33362 otherwise it will be a question of time before devices pick up the bugged version again!
Dec 19 2022 01:17 AM - edited Dec 19 2022 01:18 AM
Good morning,
any ideas where I could download the previous version?
It seems nearly impossible to find any download sources for Teams versions.
I used to have a FTP link when this last happened, but can't find it anymore :(
Dec 19 2022 02:03 AM
Dec 19 2022 02:08 AM
Dec 19 2022 02:18 AM
Dec 19 2022 02:26 AM
Dec 19 2022 02:49 AM
Dec 19 2022 03:34 AM