Microsoft Teams Rooms - Logitech Tap Units Black Screen Content Share Issue

%3CLINGO-SUB%20id%3D%22lingo-sub-3253797%22%20slang%3D%22en-US%22%3EMicrosoft%20Teams%20Rooms%20-%20Logitech%20Tap%20Units%20Black%20Screen%20Content%20Share%20Issue%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3253797%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20have%20found%20that%20with%20our%20Cat5%20Models%20of%20the%20Logitech%20Tap%20Units%20have%20screen%20share%20issues%20with%20version%204.11.12.%20The%20fix%20for%20us%20has%20been%20to%20update%20to%204.11.17.%3C%2FP%3E%3CP%3EThe%20issue%20was%20that%20after%20joining%20a%20meeting%2C%20the%20content%20share%20(in%20our%20case%20an%20attached%20PC)%20would%20show%20a%20black%20screen.%20The%20only%20workaround%2Ffix%20would%20be%20to%20join%20a%20meeting%20or%20to%20reboot%20the%20device.%26nbsp%3B%3C%2FP%3E%3CP%3EWith%20the%20update%20to%204.11.17%20we%20no%20longer%20have%20this%20issue.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-3253797%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EConversations%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EMeetings%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EMicrosoft%20Teams%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3300510%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Teams%20Rooms%20-%20Logitech%20Tap%20Units%20Black%20Screen%20Content%20Share%20Issue%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3300510%22%20slang%3D%22en-US%22%3EHello%2C%3CBR%20%2F%3Ewe%20have%20the%20same%20problem.%3CBR%20%2F%3EIt%20seemed%20fixed%20after%20updating%20but%20the%20problem%20returned.%3CBR%20%2F%3EDoes%20it%20still%20work%20for%20you%3F%3C%2FLINGO-BODY%3E
Occasional Visitor

We have found that with our Cat5 Models of the Logitech Tap Units have screen share issues with version 4.11.12. The fix for us has been to update to 4.11.17.

The issue was that after joining a meeting, the content share (in our case an attached PC) would show a black screen. The only workaround/fix would be to join a meeting or to reboot the device. 

With the update to 4.11.17 we no longer have this issue. 

1 Reply
Hello,
we have the same problem.
It seemed fixed after updating but the problem returned.
Does it still work for you?