Forum Discussion
Joe Cistaro
Feb 13, 2018Brass Contributor
Skype for Business meeting displays black screen and pause icon
Hello,
I received a notice from a user in our Enterprise. She is connecting to a meeting and the following is displayed when the presenter tries to share her screen. Look familiar to anyone? ...
- Feb 21, 2018So, we ended finally found this https://support.microsoft.com/en-us/help/3150900/black-or-frozen-screen-when-you-share-your-screen-in-skype-for-busines We don't know how or when but several of our users had that registry key. When a user w/out that key was initiating a screen share it would pause (black screen with white pause icon in top left). If a user with those registry keys initiated the screen sharing it works because those w/out the reg key would I guess "fall back" to RDP protocol. So we're working on collecting all machines in our firm that have that registry key and removing.
Feb 21, 2018
Is this person a presenter in the meeting or a attendee?
- Creighton_BarnesFeb 21, 2018Brass ContributorSo, we ended finally found this https://support.microsoft.com/en-us/help/3150900/black-or-frozen-screen-when-you-share-your-screen-in-skype-for-busines We don't know how or when but several of our users had that registry key. When a user w/out that key was initiating a screen share it would pause (black screen with white pause icon in top left). If a user with those registry keys initiated the screen sharing it works because those w/out the reg key would I guess "fall back" to RDP protocol. So we're working on collecting all machines in our firm that have that registry key and removing.
- John HavertyFeb 21, 2018Iron ContributorGlad to hear you got it figured out. What is odd that the registry keys were changed and started causing the issue.
John- Creighton_BarnesFeb 21, 2018Brass ContributorYa, that's the head scratcher. We did some further testing too using the scrub vbs files for 15 and 16 to see if those keys would go away. They remain even after running the Microsoft office scrub vbs and me manually uninstalling every Microsoft Office product. The HKUM 16.0 key was left behind with the P2P override key in place. So we're going to be writing a ps script to check for it and delete it on all machines. Or we're thinking of just pushing out a deployment of Office to all machines and adding a task to purge the Office reg key all together for all machines. Wipe the slate clean.
Creighton