SOLVED
Home

Problem with Keyboard Display in Skype Rooms System after Win10 update 1703

%3CLINGO-SUB%20id%3D%22lingo-sub-92107%22%20slang%3D%22en-US%22%3EProblem%20with%20Keyboard%20Display%20in%20Skype%20Rooms%20System%20after%20Win10%20update%201703%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-92107%22%20slang%3D%22en-US%22%3E%3CP%3EHello%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20are%20using%20Skype%20Rooms%20System%20v2%20with%20Logitech%20SmartDock.%3C%2FP%3E%3CP%3EThis%20week%20the%20OS%20on%20Surface%20tablet%20was%20updated%20to%20version%201703%20and%20after%20that%20we%20are%20experiencing%20a%20strange%20problem%20with%20the%20interface.%20Whenever%20we%20try%20to%20invite%20someone%20to%20a%20meeting%20the%20display%20keyboard%20does%20not%20appear.%20You%20can%20clearly%20see%20that%20the%20taps%20on%20the%20display%20are%20recognized%20and%20in%20the%20other%20menus%20where%20you%20can%20type%20something%20the%20keyboard%20appears.%20It%20was%20working%20properly%20before%20the%20update.%20As%20a%20temporary%20work-around%20we%20have%20attached%20a%20USB%20keybaord.%3C%2FP%3E%3CP%3EDoes%20anyone%20else%20who%20use%20this%20system%20have%20the%20same%20problem%20after%20the%20update%20and%20sollution%20for%20it%20%3F%3C%2FP%3E%3CP%3EThe%20SRSv2%20software%20is%20running%20version%203.0.6.0%20on%20Win10%20version%201703.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-92107%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EConferencing-Meeting%20Join%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-270237%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20Problem%20with%20Keyboard%20Display%20in%20Skype%20Rooms%20System%20after%20Win10%20update%201703%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-270237%22%20slang%3D%22en-US%22%3E%3CP%3ESame%20problem%20here%20on%20a%20new%20HP%20Elite%20Slice.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20DWORD%20already%20existed%2C%20and%20toggling%20the%20switch%20did%20nothing.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESo...%20I%20need%20a%20keyboard%20with%20the%20dock%20now%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-187491%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20Problem%20with%20Keyboard%20Display%20in%20Skype%20Rooms%20System%20after%20Win10%20update%201703%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-187491%22%20slang%3D%22en-US%22%3E%3CP%3EI've%20followed%20steps%20from%20Michael%20and%20Chi%20without%20success.%26nbsp%3B%20I%20still%20do%20not%20get%20the%20KB%20to%20come%20up%20when%20attempting%20to%20invite%20a%20participant%20to%20a%20new%20meeting.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-92946%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20Problem%20with%20Keyboard%20Display%20in%20Skype%20Rooms%20System%20after%20Win10%20update%201703%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-92946%22%20slang%3D%22en-US%22%3EI%20had%20already%20tried%20the%20suggestion%20by%20Michael%20about%20the%20toggled%20off%20option%20few%20days%20ago%20but%20it%20did%20not%20work%20for%20us%2C%20the%20keyboard%20was%20still%20missing.%3CBR%20%2F%3EThe%20registry%20key%20fix%20which%20Chi%20Hang%20Lo%20suggested%20is%20the%20one%20which%20solved%20it.%3CBR%20%2F%3EThank%20you%20for%20the%20replies!%3CBR%20%2F%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-92894%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20Problem%20with%20Keyboard%20Display%20in%20Skype%20Rooms%20System%20after%20Win10%20update%201703%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-92894%22%20slang%3D%22en-US%22%3ELook%20at%20the%20link%20form%20MS%20%3CA%20href%3D%22https%3A%2F%2Fsupport.microsoft.com%2Fen-in%2Fhelp%2F4037694%2Fvirtual-keyboard-missing-in-skype-room-systems-v2%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fsupport.microsoft.com%2Fen-in%2Fhelp%2F4037694%2Fvirtual-keyboard-missing-in-skype-room-systems-v2%3C%2FA%3E%20Resolution%20Warning%20Follow%20the%20steps%20in%20this%20section%20carefully.%20Serious%20problems%20might%20occur%20if%20you%20modify%20the%20registry%20incorrectly.%20Before%20you%20modify%20it%2C%20back%20up%20the%20registry%20for%20restoration%20in%20case%20problems%20occur.%20To%20resolve%20this%20issue%2C%20create%20a%20%22EnableDesktopModeAutoInvoke%22%3Ddword%3A00000001%20registry%20entry%20under%20HKEY_LOCAL_MACHINE%5CSOFTWARE%5CMicrosoft%5CTabletTip%5C1.7.%20To%20do%20this%2C%20follow%20these%20steps%3A%20Open%20Registry%20Editor.%20Tap%20and%20hold%20the%20task%20bar%2C%20and%20then%20tap%20Show%20touch%20keyboard%20button.%20A%20keyboard%20icon%20should%20appear%20on%20the%20right%20side%20of%20the%20task%20bar.%20Tap%20the%20Search%20icon%20on%20the%20left%20side%20of%20the%20task%20bar%20to%20open%20the%20search%20box.%20Tap%20the%20Search%20box%2C%20type%20regedit%20on%20the%20virtual%20keyboard%2C%20and%20then%20tap%20regedit%20in%20the%20search%20results.%20If%20Registry%20Editor%20doesn't%20open%2C%20swipe%20from%20the%20left%20side%20of%20the%20screen%20and%20tap%20Registry%20Editor.%20In%20Registry%20Editor%2C%20navigate%20to%20the%20following%20path%3A%20HKEY_LOCAL_MACHINE%5CSOFTWARE%5CMicrosoft%5CTabletTip%5C1.7%20Tap%20and%20hold%20the%201.7%20folder%2C%20tap%20New%20%26gt%3B%20DWORD%20(32-bit)%20Value.%20Enter%20the%20name%20EnableDesktopModeAutoInvoke%20and%20then%20tap%20Enter%20on%20the%20virtual%20keyboard.%20Double-tap%20the%20EnableDesktopModeAutoInvoke%20registry%20entry%2C%20enter%201%20under%20%22Value%20data%2C%22%20and%20then%20tap%20OK.%20Wish%20it%20could%20help.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-92882%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20Problem%20with%20Keyboard%20Display%20in%20Skype%20Rooms%20System%20after%20Win10%20update%201703%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-92882%22%20slang%3D%22en-US%22%3E%3CBLOCKQUOTE%3E%3CHR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F69826%22%20target%3D%22_blank%22%3E%40michael.dibenedetto%3C%2FA%3E%20wrote%3A%3CBR%20%2F%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EIn%20this%20new%20Windows%2010%20world%20we%20live%20in%20it's%20difficult%20to%20turn%20updates%20off.%20We%20bought%20this%20system%20pre-configured%20from%20the%20vendor%20which%20means%20we%20did%20not%20create%20the%20image%20and%20therefore%20have%20little%20to%20no%20control%20over%20updates%20without%20other%20advanced%20configuration%20connecting%20it%20to%20WSUS%20or%20other%20management%20systems.%20Microsoft%20should%20figure%20out%20that%20if%20they%20want%20to%20force%20updates%20every%20six%20months%20that%20they%20need%20to%20deal%20with%20these%20potential%20compatibility%20issues%20or%20allow%20exceptions.%3C%2FSPAN%3E%3C%2FP%3E%3CHR%20%2F%3E%3C%2FBLOCKQUOTE%3E%3CP%3E%3CSPAN%3EI%20totally%20agree.%20We%20are%20currently%20testing%20out%2010%20SRS-units%20in%20our%20company.%20Our%20plan%20is%20to%20install%20them%20in%20all%20our%20branch%20offices.%20If%20we%20can't%20trust%20the%20appliance%20to%20function%20properly%20after%20regular%20software%20updates%2C%20I%20fear%20we%20have%20to%20reconsider%20this%20solution.%20This%20is%20a%20major%20issue%20that%20Microsoft%20has%20to%20address%20if%20this%20product%20is%20going%20to%20live%20in%20the%20future.%20We%20can't%20have%20a%20situation%20where%20we%20need%20to%20send%20out%20our%20IT%20staff%20to%20manually%20fix%20these%20things.%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EDoes%20Microsoft%20monitor%20these%20discussions%3F%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-92698%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20Problem%20with%20Keyboard%20Display%20in%20Skype%20Rooms%20System%20after%20Win10%20update%201703%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-92698%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20had%20reviewed%20that%20same%20article%20and%20I'd%20say%20the%20text%20is%20confusing.%20I%20read%20that%20as%201607%20is%20not%20supported%20for%20the%20image%20creation.%20Here%20is%20the%20exact%20text%20from%20the%20article%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CEM%3EFailure%20to%20create%20your%20console%20image%20according%20to%20these%20instructions%20will%20likely%20result%20in%20unexpected%20behavior.%20Windows%2010%20Enterprise%20Creators%20Update%20(build%201703)%20is%20not%20supported%20for%20Skype%20Room%20Systems%20v2%20image%20creation.%3C%2FEM%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EIn%20this%20new%20Windows%2010%20world%20we%20live%20in%20it's%20difficult%20to%20turn%20updates%20off.%20We%20bought%20this%20system%20pre-configured%20from%20the%20vendor%20which%20means%20we%20did%20not%20create%20the%20image%20and%20therefore%20have%20little%20to%20no%20control%20over%20updates%20without%20other%20advanced%20configuration%20connecting%20it%20to%20WSUS%20or%20other%20management%20systems.%20Microsoft%20should%20figure%20out%20that%20if%20they%20want%20to%20force%20updates%20every%20six%20months%20that%20they%20need%20to%20deal%20with%20these%20potential%20compatibility%20issues%20or%20allow%20exceptions.%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-92695%22%20slang%3D%22en-US%22%3ERe%3A%20Problem%20with%20Keyboard%20Display%20in%20Skype%20Rooms%20System%20after%20Win10%20update%201703%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-92695%22%20slang%3D%22en-US%22%3E%3CP%3ESo%20we%20found%20the%20solution%20for%20our%20system.%20It%20seems%20that%20there%20is%20a%20setting%20for%20this%20which%20must%20have%20changed%20when%20the%20OS%20went%20from%201607%20to%201703.%20We%20plugged%20in%20an%20external%20keyboard%20to%20test%20and%20then%20thought%20about%20manually%20launching%20the%20on-screen%20keyboard%20while%20being%20in%20the%20app%20and%20the%20on-screen%20keyboard%20came%20up%20and%20worked.%20After%20some%20searching%20we%20found%20this%20article%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fwww.windowscentral.com%2Fauto-display-touch-keyboard-windows-10-desktop-mode%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fwww.windowscentral.com%2Fauto-display-touch-keyboard-windows-10-desktop-mode%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Ewhich%20directed%20us%20to%20the%20appropriate%20setting%20which%20was%20off%20when%20we%20checked%20it.%20We%20toggled%20the%20last%20option%20from%20off%20to%20on%20and%20all%20works%20now%20as%20it%20did%20before.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20639px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F18107iE230B0463C5A675A%2Fimage-dimensions%2F639x355%3Fv%3D1.0%22%20width%3D%22639%22%20height%3D%22355%22%20alt%3D%22keyboard-setting.PNG%22%20title%3D%22keyboard-setting.PNG%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-92276%22%20slang%3D%22en-US%22%3ERE%3A%20Problem%20with%20Keyboard%20Display%20in%20Skype%20Rooms%20System%20after%20Win10%20update%201703%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-92276%22%20slang%3D%22en-US%22%3ESee%20%3CA%20href%3D%22https%3A%2F%2Ftechnet.microsoft.com%2Fen-us%2Flibrary%2Fmt790558.aspx%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Ftechnet.microsoft.com%2Fen-us%2Flibrary%2Fmt790558.aspx%3C%2FA%3E%20%22Windows%2010%20Enterprise%20Creators%20Update%20(build%201703)%20is%20not%20supported%20for%20Skype%20Room%20Systems%20v2%20image%20creation.%22%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-92201%22%20slang%3D%22en-US%22%3ERe%3A%20Problem%20with%20Keyboard%20Display%20in%20Skype%20Rooms%20System%20after%20Win10%20update%201703%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-92201%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20have%20the%20exact%20same%20problem.%20Logitech%20Smartdock%2C%20working%20before%20the%20update%20to%201703.%20The%20on%20screen%20keyboard%20does%20not%20appear%20anywhere%20in%20the%20app%2C%20whether%20to%20invite%20other%20participants%20or%20in%20the%20settings%20screens.%20Exiting%20to%20the%20OS%20allows%20the%20keyboard%20to%20work%20with%20no%20problems.%20T%3CSPAN%3Ehe%20SRSv2%20software%20is%20running%20version%203.0.6.0%20on%20Win10%20version%201703%3C%2FSPAN%3E%26nbsp%3Bfor%20us%20as%20well.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20haven't%20had%20a%20solution%20yet%20and%20are%20debating%20doing%20a%20reset%20to%20see%20if%20that%20will%20resolve%20the%20issue.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Ivan Terziev
New Contributor

Hello,

 

We are using Skype Rooms System v2 with Logitech SmartDock.

This week the OS on Surface tablet was updated to version 1703 and after that we are experiencing a strange problem with the interface. Whenever we try to invite someone to a meeting the display keyboard does not appear. You can clearly see that the taps on the display are recognized and in the other menus where you can type something the keyboard appears. It was working properly before the update. As a temporary work-around we have attached a USB keybaord.

Does anyone else who use this system have the same problem after the update and sollution for it ?

The SRSv2 software is running version 3.0.6.0 on Win10 version 1703.

9 Replies

We have the exact same problem. Logitech Smartdock, working before the update to 1703. The on screen keyboard does not appear anywhere in the app, whether to invite other participants or in the settings screens. Exiting to the OS allows the keyboard to work with no problems. The SRSv2 software is running version 3.0.6.0 on Win10 version 1703 for us as well.

 

We haven't had a solution yet and are debating doing a reset to see if that will resolve the issue.

See https://technet.microsoft.com/en-us/library/mt790558.aspx "Windows 10 Enterprise Creators Update (build 1703) is not supported for Skype Room Systems v2 image creation."

So we found the solution for our system. It seems that there is a setting for this which must have changed when the OS went from 1607 to 1703. We plugged in an external keyboard to test and then thought about manually launching the on-screen keyboard while being in the app and the on-screen keyboard came up and worked. After some searching we found this article:

 

https://www.windowscentral.com/auto-display-touch-keyboard-windows-10-desktop-mode

 

which directed us to the appropriate setting which was off when we checked it. We toggled the last option from off to on and all works now as it did before.

 

keyboard-setting.PNG

We had reviewed that same article and I'd say the text is confusing. I read that as 1607 is not supported for the image creation. Here is the exact text from the article:

 

Failure to create your console image according to these instructions will likely result in unexpected behavior. Windows 10 Enterprise Creators Update (build 1703) is not supported for Skype Room Systems v2 image creation.

 

In this new Windows 10 world we live in it's difficult to turn updates off. We bought this system pre-configured from the vendor which means we did not create the image and therefore have little to no control over updates without other advanced configuration connecting it to WSUS or other management systems. Microsoft should figure out that if they want to force updates every six months that they need to deal with these potential compatibility issues or allow exceptions.


@michael.dibenedetto wrote:

 

 

In this new Windows 10 world we live in it's difficult to turn updates off. We bought this system pre-configured from the vendor which means we did not create the image and therefore have little to no control over updates without other advanced configuration connecting it to WSUS or other management systems. Microsoft should figure out that if they want to force updates every six months that they need to deal with these potential compatibility issues or allow exceptions.


I totally agree. We are currently testing out 10 SRS-units in our company. Our plan is to install them in all our branch offices. If we can't trust the appliance to function properly after regular software updates, I fear we have to reconsider this solution. This is a major issue that Microsoft has to address if this product is going to live in the future. We can't have a situation where we need to send out our IT staff to manually fix these things. 

 

Does Microsoft monitor these discussions?

 

Solution
Look at the link form MS https://support.microsoft.com/en-in/help/4037694/virtual-keyboard-missing-in-skype-room-systems-v2 Resolution Warning Follow the steps in this section carefully. Serious problems might occur if you modify the registry incorrectly. Before you modify it, back up the registry for restoration in case problems occur. To resolve this issue, create a "EnableDesktopModeAutoInvoke"=dword:00000001 registry entry under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\TabletTip\1.7. To do this, follow these steps: Open Registry Editor. Tap and hold the task bar, and then tap Show touch keyboard button. A keyboard icon should appear on the right side of the task bar. Tap the Search icon on the left side of the task bar to open the search box. Tap the Search box, type regedit on the virtual keyboard, and then tap regedit in the search results. If Registry Editor doesn't open, swipe from the left side of the screen and tap Registry Editor. In Registry Editor, navigate to the following path: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\TabletTip\1.7 Tap and hold the 1.7 folder, tap New > DWORD (32-bit) Value. Enter the name EnableDesktopModeAutoInvoke and then tap Enter on the virtual keyboard. Double-tap the EnableDesktopModeAutoInvoke registry entry, enter 1 under "Value data," and then tap OK. Wish it could help.
I had already tried the suggestion by Michael about the toggled off option few days ago but it did not work for us, the keyboard was still missing.
The registry key fix which Chi Hang Lo suggested is the one which solved it.
Thank you for the replies!

I've followed steps from Michael and Chi without success.  I still do not get the KB to come up when attempting to invite a participant to a new meeting.

Same problem here on a new HP Elite Slice.

 

The DWORD already existed, and toggling the switch did nothing.

 

So... I need a keyboard with the dock now?