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.

BJW 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).

https://statics.teams.cdn.office.net/production-windows-x64/1.5.00.31168/Teams_windows_x64.exe could I just use this?

We have found that running the current version of Teams in compatibility mode (windows 😎 seems to fix the issue

SteWel 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.

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.

Teams update to 1.5.00.33362 - will not launch or crashes

Mario_Scheliga
Copper Contributor
Dec 15, 2022
Same here. It's unbearable - we are trying to use the version from before. Hope that will be fixed soon.
SHeathfield
Brass Contributor
Dec 15, 2022
My org is also seeing problems with this Teams version; users are prompted to log in and then the app sits on a blank screen.
I've shared an old copy of teams for users to roll back to, and then they work fine. Otherwise pointing them at https://teams.microsoft.com/
- SystemsFirst
  Copper Contributor
  Dec 20, 2022
  SHeathfield
  
  I would love to know where you have these Old Versions of Teams - From what I have seen so far, there is no official channel to roll back.
  - SHeathfield
    Brass Contributor
    Dec 20, 2022
    Hi SystemsFirst,
    We use the Teams Machine-Wide installer, as we previously had some problems deploying Teams via intune automatically.
    It downloads as an MSI, so it's super easy to deploy via intune and means any user that logs in to any windows hot desk will always have Teams installed!
    
    Look for the commercial x64 installer:
    https://learn.microsoft.com/en-us/microsoftteams/msi-deployment
    
    Once installed, it will drop a full offline installer into C:\Program Files (x86)\Teams Installer
    
    I just tested for you, and can confirm it installed version 1.5.0.34154 that is working for me.
    
    EDIT: 1.5.0.34154 is also broken, it stopped working a few minutes after I posted this.
    Here is the download link from my browser history for version 1.5.0.31168
    https://statics.teams.cdn.office.net/production-windows-x64/1.5.00.31168/Teams_windows_x64.msi
- benzc
  Copper Contributor
  Dec 15, 2022
  We have the exact same problem. If you roll back on a previous verison it will auto upgrade again tho?
  - SHeathfield
    Brass Contributor
    Dec 20, 2022
    Yes, most days, until Microsoft fixes the problem.
    I shared the process with users to roll back since it does not require any administrative account to authorise and takes all of 20 seconds.

Forum Discussion

Teams update to 1.5.00.33362 - will not launch or crashes

Resources