Forum Discussion
Edge - On-Screen Keyboard - Not Working
Thanks for getting in touch with us! As Fawkes mentioned, Kiosk is a work in progress for us...so all feedback is welcomed and keenly listened to. I'm pumped to hear that you are using the new Edge for your Kiosk needs! 🙂
Just curious: Are your Kiosk devices all touch-only, meaning they do not have a physical keyboard or other forms of physical input devices and hence the question?
I detached the keyboard base in my Surface Book running Windows 10 - to mimic a touch only setup. Then I tried navigating to bing.com in Edge Stable and also in IE. I was able to tap into the address bar in Edge (or IE) or the search bar in Bing page and the on-screen keyboard promptly popped up. If I dismissed the keyboard, all I had to do was tap again in the address bar or the search box to have it pop up again. This was the same behavior in Edge Stable and IE too.
Are you by chance still using Windows in "Desktop mode" - meaning Windows possibly thinks you have a keyboard attached? Or maybe you want the virtual keyboard to popup, even with a physical keyboard attached? Here are a few links I thought might be helpful for you:
https://support.microsoft.com/en-us/help/4027960/windows-10-turn-tablet-mode-on-or-off
https://www.windowscentral.com/auto-display-touch-keyboard-windows-10-desktop-mode
Hopefully these will help resolve your problem. If not, I'll need more help from you to try to reproduce the scenario on my end. Are you trying this on a specific website? If so, can you try this in a non-Kiosk touch device that you may have access to, to see if this is a site-specific issue? Maybe the site is not using the right HTML element, etc that helps Edge and Windows understand that it needs a keyboard? How did you configure the Kiosk setup? Is Edge in fullscreen mode or does the address bar show up? Anything else you can share about your setup, including which site you are trying this on?
Feel free to message me directly in case you do not want to share all the above information in this public post. I'll also be very interested to learn more about your Kiosk scenario and needs.
Microsoft
Thanks for getting in touch with us! As Fawkes mentioned, Kiosk is a work in progress for us...so all feedback is welcomed and keenly listened to. I'm pumped to hear that you are using the new Edge for your Kiosk needs! 🙂
Just curious: Are your Kiosk devices all touch-only, meaning they do not have a physical keyboard or other forms of physical input devices and hence the question?
I detached the keyboard base in my Surface Book running Windows 10 - to mimic a touch only setup. Then I tried navigating to bing.com in Edge Stable and also in IE. I was able to tap into the address bar in Edge (or IE) or the search bar in Bing page and the on-screen keyboard promptly popped up. If I dismissed the keyboard, all I had to do was tap again in the address bar or the search box to have it pop up again. This was the same behavior in Edge Stable and IE too.
Are you by chance still using Windows in "Desktop mode" - meaning Windows possibly thinks you have a keyboard attached? Or maybe you want the virtual keyboard to popup, even with a physical keyboard attached? Here are a few links I thought might be helpful for you:
https://support.microsoft.com/en-us/help/4027960/windows-10-turn-tablet-mode-on-or-off
https://www.windowscentral.com/auto-display-touch-keyboard-windows-10-desktop-mode
Hopefully these will help resolve your problem. If not, I'll need more help from you to try to reproduce the scenario on my end. Are you trying this on a specific website? If so, can you try this in a non-Kiosk touch device that you may have access to, to see if this is a site-specific issue? Maybe the site is not using the right HTML element, etc that helps Edge and Windows understand that it needs a keyboard? How did you configure the Kiosk setup? Is Edge in fullscreen mode or does the address bar show up? Anything else you can share about your setup, including which site you are trying this on?
Feel free to message me directly in case you do not want to share all the above information in this public post. I'll also be very interested to learn more about your Kiosk scenario and needs.
I have an ASUS All In One Touch Screen Desktop. I have installed Windows 10 Enterprise on it and got all the latest patches to date. When logged as a user and switching on Tablet mode, I see the virtual keyboard but when I switch to Kiosk mode, the virtual keyboard won't show. I have unplugged the physical keyboard and rebooted the machine and still no virtual keyboard. I have even tried adding these three keys to registry
HKCU\Software\Microsoft\TabletTip\1.7\EnableDesktopModeAutoInvoke = 1
HKCU\Software\Microsoft\TabletTip\1.7\DisableNewKeyboardExperience = 1
HKCU\Software\Microsoft\windows\CurrentVersion\ImmersiveShell\TabletMode = 1
and still no luck. The app I am using is Microsoft Edge.
Not sure how @Keith Davis got it working on his HP All in One.
- Raj_GSThe_Naval_Museum, thanks for the ping! I'm assuming you're referring to the new Edge's kioks mode?
Keith should have setup kiosk with the new Edge EITHER in a normal user setup (with/without ShellLauncher configured to launch Edge in kiosk mode) OR using the Windows Assigned Access multi-app kiosk mode - both of which were supporting the new Edge ever since it released to Stable a couple of years ago.
1. Are you using the Settings UI's "Setup a kiosk (assigned access)" option (which started supporting the new Edge in Insider builds very recently)? If not, could you please let me know how you are setting up the kiosk experience?
2. What version of Windows (as seen when you run 'winver') and what version of Edge (and what channel of Edge) are you using to setup the kiosk?
The above info will help root cause the issue on our end.Raj_GS , thanks for the quick response.
Here is the screen capture from my winver:
And here is my Kiosk Setup
Settings when logged on as Admin:
Virtual keyboard shows up just fine when logged in as Admin but not when logged in as Kiosk.
Thanks.
- Raj_GS
The_Naval_Museum , thanks!
We'll try this on our end and loop in the right folks regarding this. In case there's a short-term workaround that'll get you unblocked, I'll let you know.