Teams version 1.5.00.2164 bug

IBN 4,401

Hello Community,

The Teams desktop app on version 1.5.00.2164 has a bug that shows: Something went wrong You can't make or get calls right now.

Try restarting the app. That might solve the problem. When people try to join a meeting or a call. It also seems to not be able to access the microphone/speakers.

The workaround currently is to roll back to a 1.4 version however it's affecting multiple machines and doing this is not an option any more.

JimmyYang-MSFT 53,121 Reputation points Microsoft Vendor

2022-02-11T06:19:27.093+00:00

Hi @IBN

Have you tried to update the version to the newest to see if works?

I check my Teams version. The newest version is 1.5.00.3866 (64-bit). It was last updated on 2/10/2022.
Jamie 1 Reputation point

2022-02-15T17:02:26.657+00:00

Tested this on multiple devices we're having the issue with, it doesn't resolve the problem sadly. Exact same issue persists :(

Only fix is to install V1.4 or use the web app which isn't ideal.
Justin Terry 11 Reputation points

2022-02-16T16:11:29.027+00:00

Hi @JimmyYang-MSFT ,

We are also experiencing this issue with Teams desktop 1.5.00.2614. For certain users it totally breaks the meeting/calling experience in the desktop app. This also appears to affect voice calls with Phone System. There is a suggestion here https://techcommunity.microsoft.com/t5/microsoft-teams/teams-version-1-5-00-2164-bug/m-p/3150143 that this affects 365 accounts with parentheses in the display name. That fits our profile exactly, we use "FirstName LastName (Company Name)" in our standard setup.

You mention Teams client version 1.5.00.3866, but I am unable to find that anywhere. Latest version via update from the app is 1.5.00.2614, which also has the same date as the latest MSI installer for enterprise. Is 1.5.00.3866 a preview build? How can we get that update?

1 answer

Kevinscholiers 1 Reputation point

2022-02-16T18:58:52.003+00:00

We installed first the new version (1.5.00.3866) but that didn't solve the issue, a roll back to V1.4.00.2781 solved the issue.
Off course this is just temporary like already mention here with the auto-update on.

Would be nice to have a permanent solution for this, more and more people are having this issue.

We also tried updating the Teams client with the 'Check for update' option in Teams client but until now we didn't received any update.

We used to following link to install the new version: https://statics.teams.cdn.office.net/production-windows-x64/1.5.00.3866/Teams_windows_x64.exe and this one for the old version: https://statics.teams.cdn.office.net/production-windows-x64/1.4.00.2781/Teams_windows_x64.exe
Hopefully this can help you until the new version is ready and without issues, fingerscrossed.

Maybe good to mention you don't need to be an admin to install this
Please sign in to rate this answer.
Justin Terry 11 Reputation points

2022-02-16T19:34:08.203+00:00

Hi @Kevinscholiers ,

Thanks for the CDN links to other Teams client versions. I have verified, as you said, that rollback to v1.4.00.2781 does fix our problem. As you note it's a useful workaround, but unfortunately it has short life (my Teams updated again on the very next app quit/restart).

I did capture the Teams Manage Account - Settings - Devices for both versions. On v1.4.00.2781 the audio and camera devices are mapped normally: -

Clearly there is a problem in v1.5.00.2164. No audio or camera devices are found and the dropdowns to select anything are disabled. No audio in/out and No camera = No meeting or calling possible, I guess that makes sense at least!

Would appreciate hearing back from Microsoft on this one, as soon as possible. Thanks

Justin Terry 11 Reputation points

2022-02-16T20:37:49.037+00:00

Completed some further testing ...

Created 3 new local user accounts. Logged in to each, installed Teams desktop client 1.5.00.3866 (64-bit). Logged into Teams using Microsoft 365 account.

Results from Teams - Manage Account - Settings - Devices: -

LocalUser1 - All good, audio and camera devices detected and mapped correctly

LocalUser2(x) - All good, audio and camera devices detected and mapped correctly

LocalUser3(xx - Failure, neither audio nor camera found and controls to configure disabled.

This suggests that an unbalanced opening parenthesis in the account name is significant. Renamed account 3. to be just LocalUser3, which does not rename the user profile, it remains "C:\Users\LocalUser3(xx". This further suggests that the cause lies with the profile name rather than the account name per se.

Our AzureAD standard user display names are "FirstName LastName (Company Name)". I suspect we have this issue whenever the login to Windows is a "work or school account" and it is getting transformed into a truncated profile name like "FirstNameLastName(Comp".

Maur73 0 Reputation points

2023-03-08T15:42:32.35+00:00

Hello

In my work (almost 2K users) we're experiencing the same situation with Teams drop calls randomly, I mean some users unexpectedly receive the Call error message and no audio or camera devices are found. After a while, it fixes itself. In some cases, the issue is triggered when a user closes its Teams Client or after a Windows restart.

This issue started on Teams Windows Client 1.6.00.376 version released at the finish of January 2023. Apparently, the problem begins with the last change of version (1.5.00 -- > 1.6.00).

Are you experiencing the same issue recently?.

I appreciate your help or any comments about it.
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

Teams version 1.5.00.2164 bug

1 answer

Your answer