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.
Thanks for all the input, but as it turns on it was working after all. We have 2 devices, one was Windows 7 and one was Windows 10. It appeared that Edge on both was not activating the on-screen keyboard, but after further testing, only the Windows 7 machine using Edge was not working. We removed that machine and are using only the Windows 10 one now. FYI, it is a machine that does not have a physical keyboard attached (HP All-in-one).
- Raj_GS
Glad to hear that Keith! 🙂 Feel free to reach out to us in case you need more help.
Raj
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 = 1and 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 Hi Raj, I am attempting to set up an all-in-one touchscreen tablet in kiosk mode to use Edge (a PioneerInc CarisTouch Medical Tablet). I have the osk set to automatically appear when the admin user is signed in and that works well, but once logged in to the kiosk user account the osk disappears. Registry edits I have found in other posts don’t work. Windows version 10.0.18363. Edge version 94.0.992.31. Thanks
Raj,
I've always had excellent luck with Win10 Pro in Kiosk mode. Win11 Pro was good too until this summer. Any system built with the most recent clean ISO (either directly from microsoft.com or from the OEM like Dell) build, including 23H2, refuses to be consistent with the touch keyboard. Of course, there is no "tablet mode" on 11 and it's supposed to work, but even though the About shows "Touch support with 10 points", the display works great as a mouse, but with nothing attached to the PC, in this case an OptiPlex with a fully clean install of 11 Pro with the only changes being allowing it to apply available Updates, the touch keyboard will NOT display in any app, including Edge, which means no Kiosk mode which I need for over 3 dozen aging Windows 10 Pro kiosks. There are a plethora of complaints all over the web about this but none of the hacks seem to work. If I can't find a solution with 11, the other solution that I have already tested and know works is to wipe the 10 machines and go to Ubuntu in Kiosk mode. That keeps my very capable i7/8GB RAM/SSD Optiplexes out of the landfill for several more years and negates the need to pay Dell or Microsoft for more systems. I'd rather go with 11, but at some point Microsoft needs to step up and fix this or at least provide some guidance.
