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
    2024-10-11T17:27:44+00:00

    how do you block it from upgrading to the latest version ?

    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.

    Or you can block the update in the Microsoft Teams Room Pro Management Portal (if you are using that).

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  2. Anonymous
    2024-10-11T17:11:55+00:00

    how do you block it from upgrading to the latest version ?

    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.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  3. Anonymous
    2024-10-10T02:07:59+00:00

    We're experiencing the same issue.

    A workaround that got the rooms back online but running an older version:

    1. Login to the hub as the Local Administrator
    2. From a powershell prompt, run: Get-AppxPackage -Name "Microsoft.SkypeRoomSystem" -AllUsers | Remove-AppxPackage -AllUsers
    3. Switch users to "Skype" user
    4. From a powershell prompt, run: ."C:\Rigel\x64\Scripts\Provisioning\InstallSkype.ps1"
    5. Start the Teams Room app

    You might need to change the execution policy on the device to get the above to run.

    I haven't yet tried bringing the rooms back up to the latest version post-reinstall, I will report back.

    EDIT: Bringing the app back up to 5.2.115.0 does not fix. Just recreates the issue.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  4. Anonymous
    2024-10-09T19:42:19+00:00

    Excellent.... Thank you

    Our rooms started working as of yesterday. We reset the Teams Room app, removed the assigned license, left it overnight, and then reassigned the license.

    Image

    Image

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  5. Anonymous
    2024-10-09T14:54:54+00:00

    What I already tried with no success:

    • used different Login details. Checked Teams Room Licence for the ressource.
    • reset the Teams Room app from within the app and also from the Windows Apps and Features Menu.
    • uninstalled the Temas Room App, restarted and installed it again.
    • removed Room Licence from the ressource, reset inside the app, waited 4 hours, gave Licence back and logged in again.
    • Updated to Windows 11 23H2 latest Build.
    • tried some settings with the Skypesettings.xml file that you can copy to the App Folder location, which the app picks up and applies.
    • The device has internet access and checked the computeraccount + Useraccount.
    • Device drivers are up to date.
    • reinstalled the MS Edge Webview2 Runtime using local admin account as suggested in another article to this issue.

    One important note:

    We do not use the default "Skype" user and have instead domain user accounts with autologin and Teams Room system in autostart.

    This has worked the previouse 4-5 years until now.

    I already started the Windows 10 IOT re-image process via USB-stick on one of the devices.

    This time the device will work with default settings ("Skype" account) and outside of our domain.

    I will update here if it works.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments