Forum Discussion
Ivan Terziev
Aug 01, 2017Copper Contributor
Problem with Keyboard Display in Skype Rooms System after Win10 update 1703
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 in...
- Aug 03, 2017Look 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.
michael.dibenedetto
Aug 01, 2017Copper Contributor
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.