Jul 06 2021 04:27 AM
Intel NUC with Logitech TAP
Error you'll need a new app to open this skype-mrx
The popup is blocking the MTR from signing in, its currently happening on 2 devices, will troubleshoot and update, unless someone has any hints/tips
Jul 06 2021 02:59 PM
May 13 2022 09:57 AM
Did you ever find a fix for this? We are seeing this on a new Logitech Tap room install after doing a manual update.
May 16 2022 08:56 AM
I'm afraid not, the only fix was to reset the unit following the recovery tool guide
Use the Microsoft Teams Rooms recovery tool - Microsoft Teams | Microsoft Docs
May 16 2022 09:05 AM
May 25 2022 01:18 PM
@cjohnston Did Logitech ever get this sorted out for you? I have the same issue on a few of my units.
May 29 2022 05:04 PM
May 29 2022 05:29 PM
May 30 2022 12:03 PM
@justinbliss I'll give it a go. Logitech's first impulse was to create an RMA to swap out the unit. This didn't seem right since we're presumably dealing with a software vs. hardware issue. What little help they do have online points to running standard OS and device updates and if all else fails using the MTR Recovery Tool. We'll see if my request for a Logitech specific recovery image gets us anywhere tomorrow.
Jun 01 2022 12:37 PM - edited Jun 02 2022 09:33 PM
….
Jun 02 2022 08:27 AM
Jun 03 2022 07:15 AM
Jun 06 2022 08:52 AM
Jun 06 2022 10:17 AM
Jun 07 2022 05:37 AM
Jun 08 2022 01:21 PM
Same issue with 5 Poly Lenovo MTR computes surfaced this week for us. Case opened with MSFT and escalated to product group. Nothing back from MSFT so far.
Jun 08 2022 05:56 PM
Jun 09 2022 05:43 AM
Same problem here. It is really taking a lot of time to fix this issue. Where did You contact Logitech? @Shervan_Torabi
Jun 09 2022 05:52 AM
SolutionJun 09 2022 06:04 AM - edited Jun 09 2022 06:08 AM
Thanks for saving and reposting. No idea why my initial post got removed. Even the replies of some folks saying that it worked were also removed....
Additionally, you need to have the out-of-band (KB5015020) patch installed that corrects the error which was caused by the original May 2022 Cumulative Update.
May 19, 2022—KB5015020 (OS Builds 19042.1708) Out-of-band (microsoft.com)
I presume that as people stumble across this issue post-June updates that the June 2022 Cumulative will contain the corrected fix as well.
Jun 09 2022 05:52 AM
Solution