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: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2025-02-02T13:17:30+00:00

    After trying several solutions, after downgrading, we are online again!

    Was this answer helpful?

    0 comments
  2. Anonymous
    2025-01-14T17:22:21+00:00

    We are running into this same issue after moving to 5.2 on our windows system. Sometimes if you restart multiple times it will work. Today's fix was to change the sign in to another conference room, save and exit. It works then go back into settings and sign it back in as the conference room account that wasnt working and save and exit and it worked.

    This really needs to get fixed.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2025-01-06T19:16:25+00:00

    Downgrade link below, however you'll need to run the powershell to remove the existing MTR:

    https://agent.rooms.microsoft.com/files/public/softwareupdates/onboarding/Appx/Microsoft.SkypeTeam.RigelApp_5.1.28.0_x64_Ship.appx_Windows10_PreinstallKit.zip

    We had two rooms impacted, and this got us back online.

    Thank you so much for this! Our Intel NUC is running Windows 10 Pro so not sure if there are some incompatibilities there. Either way, this fix got us back up and running after almost 4 hours troubleshooting.

    Was this answer helpful?

    0 comments