Microsoft Teams Room version 5.2.115.0 bug: Teams Room account can't login

Anonymous
2024-10-03T09:14:15+00:00

Hello,

I work as an AV integrator and we currently have roughly 100 Microsoft Teams Room machines installed.

Since last tuesday we have been notified of multiple rooms (10 so far) where the Microsoft Teamsroom account cannot login.

All these rooms have in commen that the Microsoft Teams Room application has been updated (automatically) to version 5.2.115.0

Previous versions of the Microsoft Teams Room application do not show these issues.

Is there a way we can downgrade these machines to an older working version?

Hope to hear from you soon.

Microsoft Teams | Microsoft Teams for business | Sign up and Sign in | Sign in

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

83 answers

Sort by: Newest
Most helpful Newest Oldest
  1. Anonymous
    2024-10-11T07:41:55+00:00

    after so many peoply complaining that App Version 5.2.115.0 is stuck at loading into the account, you are not aware of that yet?

    We are right now re-imaging all devices with Win10 IOT, so that at least the systems work again.

    After reinstallation, the Teams Room App Version is on 4.14.24.0.

    I belief that it will get stuck again, if the App Version gets updated to the latest 5.2.115.0.

    I don't understand, why every company is still rolling out untested updates after the crowdstrike incident.

    Was this answer helpful?

    3 people found this answer helpful.
    0 comments
  2. Anonymous
    2024-10-11T02:50:18+00:00

    An update,

    We had one domain joined hub.

    Following steps from microsoft support, I

    1. Logged into the machine as Administrator
    2. Removed it from the domain
    3. Ran the MTRP provisioning tool: https://aka.ms/mtrp/mtrpprovisioningtool

    This took about 1.5 hours, but it has restored the domain joined device to a fully working state. It even carried across the signed in room account.

    I will attempt this on a non-domain joined device and report back.

    EDIT: It appears that this process installs Teams Room Application version 5.1.28.0

    EDIT: Happy to say that the MTRP Provisioning tool fixed a non-domain joined version.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2024-10-10T20:29:21+00:00

    See here a screenshot of our RMM with the versions running.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2024-10-10T20:19:11+00:00

    In some of the testing I've been doing for this, it seems like the issue where you get the "It's taking longer than expected" message after upgrading may be related to the OS edition.

    I've been able to deploy a Teams Room to a Windows 10 Enterprise system, but that same process deploying a Teams Room to a Windows 10/11 Pro system results in the "It's taking longer than expected" message. This process used to work on Windows 10 Pro on versions earlier than 5.2.115.0, but no longer does.

    For those of you still getting this error, what OS Edition are you running on?

    Was this answer helpful?

    0 comments
  5. Anonymous
    2024-10-10T18:28:55+00:00

    We are a system integrator that installs and maintains Teams Rooms for our customers. We do have access to the rooms (RMM) but no access to the TAC of our customers. What is the best way to submit a ticket with logs for us? There are now approximately 40 rooms that no longer work for different customers. We use several brands, they all have the same problem. (Lenovo, Yealink, Intel Nuc)

    Was this answer helpful?

    0 comments