This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
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.
Accessing Microsoft Teams using organizational or personal credentials
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.
It is interesting that you do not offer a solution to the current problem, just tell us about the risk of downgrade, which is ridiculous!
I reset machine. Logged in as Skype. Configured the teams using my domain account works. The reset gave back the previous version but once I logged in to teams again it auto updated.
Sounds like a sad result, I'm trying to reset the machine and try to find a way to disable updates
New thread somewhat similar to this one.
Downgrade link below, however you'll need to run the powershell to remove the existing MTR:
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.