Forum Discussion
Teams update to 1.5.00.33362 - will not launch or crashes
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.
- Issue appears to have been resolved with teams release 1.5.00.36367 - all appears to be working fine here.
- We have found that running the current version of Teams in compatibility mode (windows 😎 seems to fix the issue
Jay_Willis
Does this mean, you have to run teams in compatibily mode once and afterwards the bug is fixed, even if you return to windows10-mode? Or does this work with the compatibily mode, only?
RolandGood question - I just set it up as compatibility mode and left it so didn't bother changing it back - will give it a try over the next couple of days and let you know if reverting back to Win 10 mode works
Same problem for us (again!). It appears a similar root cause to the 1.5.00.2164 bug last February.
Affected users are those with an AAD joined device and using a work account where the display name contains special characters. This results in a user profile folder name that contains special characters. Must admit we haven't investigated as thoroughly as the 1.5.00.2164 bug. Life is far too short. Currently, affected users have just uninstalled the desktop and are living with the web. I sent some extremely frustrated feedback to Microsoft. This really smells of poor development and basic failure to escape/delimit strings appropriately. Maybe it's more subtle than that but I doubt it.
C'mon please Microsoft, this is getting really boring!
- StaceeFrane
Microsoft
If you are looking for technical support, please contact Microsoft Answers. Thank you.
https://answers.microsoft.com/There is no good support there Stacee. I can see others have reported the same issue, but nothing from Microsoft!
This appears to have been a known issue since December 7th, yet nothing in our own tenant health centre relating to it. Yet others who have commented are seeing the issue in their health centre!
This forum provided assurances that the issue was from Microsoft, not from our setup. I don't think I would have got that from the recommended forum!- Yes, this is ridiculous from Microsoft. The support is providing workaround solutions and I guess many of us have that experience troubleshooting.
I am still waiting to get the notification about this issue in my tenant health centre. SHeathfield Thanks for sharing the screenshot.
Is anyone having any luck with Microsoft support? I'm getting the usual diarrhoea responses (even calling it firmware! !!
)
Hello Bryan, Greetings of the day!
Please be informed that we have highlighted again the reported issues to our engineering team to fix the issues in near feature with upcoming firmware versions/existing and there is no ETA for now. Thanks for your understanding!
Based on their confirmation latest version of MS Teams is in rolling out phase and once its fully rolled out we didn't get any user reported issues and it will be mitigated ASAP.- Microsoft have posted this issue to the health center. https://admin.microsoft.com/Adminportal/Home#/servicehealth/:/alerts/TM486857
SHeathfield That is not appearing in our UK admin centre, which country are you in?
"Something went wrong, you don't have permission to access this post."
- Actually it seems that microsoft stopped delivery version 1.5.00.33362. We are now just able to get the old november update (1.5.00.31168) via teams desktop client. Maybe anybody else could confirm this?
- Just uninstalled and installed via default MS downloader, 3 times.
33362 was installed every time, so no I can not confirm this, at least not in Germany atm- We setup teams via system wide installer. So the teams client starts with the version from the system wide installer. After the first start we search for updates and just get the november version.
- BJW, Glad its not only me. Seems to be the same bug we are having. Although it looks to be related to the Display and local user profile directory. We either get a conditional error message, or removing that we get teams just loading and closing. All users so far have a special character in the name.
Anyone got any feedback from MS?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!
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).
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.
- Locate or search for the Microsoft Teams app. Then, click the three-dots menu next to the app name and select Advanced options. Scroll down to the Reset section and click on Repair. Windows will start repairing the app and show a checkmark after the repair is complete.
Regards,
Rachel Gomez- Im sorry, I do not feel like we are on the same OS.
We are using Windows 10 and/or Windows 11 with the Microsoft Teams for School/Business
I can repair from the Control Panel however if this will achieve the same result
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?
