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)
After updating a some HP Conferencing units to Teams Rooms 4.19.57.0, I get an error:
"Microsoft Teams Room device isn't certified.
You must insert the HDMI adaptor that came with this device. If you continue to have problems, contact your organisation's admin or IT support desk."
These systems worked perfectly well on the 4.18 versions.
I have tried with & without the HDMI adaptor.
Is there a way to downgrade Teams Rooms versions at all? I've tried "Reset this PC" multiple times but it only seems to re-install the 4.19 version.
Additional chat-related features and issues within Microsoft Teams for business
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.
I´ve just started a new system and got the same issue.
I didn´t have Logitech TAP connected, so I connected it and re-installed the Teams app 4.19.57.0 and that worked for me.
Can you tell me how you got past the error/restart and logged into the computer?
Just connecting a touchpanel, in this case a Logitech TAP solved it.
I´ve seen the same problem with Yealink and that got solved by connecting a Mtouch panel.
Darn, I was loading on a Surface which is a touch device and I'm still having the problem. Might try again with a micro form factor machine I've got here and round up a different touch panel. Thanks
Has anyone seen this issue since installing the latest 4.19.82.0 update? "Other bug fixes and improvements" is listed in the release notes so i'm wondering if this issue is one of the bugs.