{"id":436,"date":"2015-08-24T08:57:09","date_gmt":"2015-08-24T08:57:09","guid":{"rendered":"http:\/\/borncity.com\/win\/?p=436"},"modified":"2023-09-22T00:43:32","modified_gmt":"2023-09-21T22:43:32","slug":"windows10-upgrade-on-screen-keyboardtouchscreen-fix","status":"publish","type":"post","link":"https:\/\/borncity.com\/win\/2015\/08\/24\/windows10-upgrade-on-screen-keyboardtouchscreen-fix\/","title":{"rendered":"Windows 10 upgrade: On-Screen-Keyboard\/Touchscreen fix"},"content":{"rendered":"

Some People updating a Windows 8.1 tablet pc or hybrid-device with touchscreen will be confronted with a negative surprise: The On-screen keyboard doesn't popup anymore, if the user select an input box in tablet mode. I've had this situation on a hybrid device (Medion Akoya P2214T) and will show, how I've fixed it. The solution should work for all devices with a eGalax touchscreen<\/p>\n

<\/p>\n

Problem: On-screen keyboard doesn't show automatically<\/h3>\n

\"\"Microsoft has changed several things in Windows 10 Tablet mode. Therefore I don't mind, after I noticed, that the On-screen keyboard doesn't show automatically after I hit an input box within an app. I also received comments from Surface Pro 3 owners, claiming that the On-Screen keyboard didn't show every time after hitting an input box. On my test machine, I was able to use the taskbar's icon to show the the On-screen keyboard (see screenshot from my German Windows below). <\/p>\n

\"\" <\/p>\n

In German Microsoft Answers forum I found several users blaming Windows 10 not to show On-screen keyboard automatically. A Lenovo Yoga tablet pc user mentioned, that in his case a  Yoga Transition software from Lenovo was a show stopper. But I don't have had a Lenovo device. So I decided to post this issue in Microsoft's internal Windows 10 influencer forum. My MVP colleague Barb Bowman<\/a> mentioned, that the behavior of the On-screen keyboard may be changed within settings, and posted this settings screenshot.  <\/p>\n

<\/p>\n

My first thought was \"hell, was I stupid\", but investigating my Typing settings<\/em> page showed only Spelling options \u2013 nothing for touchscreen. <\/p>\n

<\/p>\n

This brought me to the conclusion, that something went terrible wrong on my machine. I digged a bit a around, but was not able to find a quick solution. Time for a deeper investigation. <\/p>\n

Checking drivers in device manager<\/h3>\n

First I decided to press key combination Windows+X <\/em>and select Device manager in quick launch menu. Then I inspected the devices within device manager. There are two entries for input devices: Human Interface Devices<\/em> and Mice and other pointing devices<\/em>. <\/p>\n

<\/p>\n

In a German forum thread<\/a> somebody mentioned, that on his Medion P2214T a eGalax Touch Controller c 030 was shown under Mice and other pointing devices<\/em>. Below is a screenshot of the driver properties (still in German). <\/p>\n

\"\"<\/p>\n

So the issue was clear: the driver was detected wrongly as a mice device and Windows 10 identified it as a mouse. Searching the web for eGalax C030 showed my several hits<\/a> (beside a driver page<\/a>, I found users of several Tablet PCs with issues, here<\/a> HP Envy TS15, here<\/a> ASUS und HP Envy TS15, here<\/a> and here<\/a>). Some users mentioned, that reverting back to the previous driver has solved their issue in Windows 10. But I haven't this option \u2013 after \"switching to the old driver\", the driver was gone. Unfortunately, my test machine was a pre series device withouth a driver partition. I tried this driver<\/a>, but without success. The touchscreen was still recognized as a mice device. <\/p>\n

On reader of my German blog mentioned, that the touchscreen on his slate was identified as a HID-compliant touch screen<\/em>. <\/p>\n

Solving the eGalax driver issue<\/h3>\n

Using the hint given above, first I found this TOUCHPANEL INSTALLATION FIX<\/a> package provided by Lenovo German subsidiary Medion. The package provides a batch file, that removes the mice device driver for eGalax touchpad and reinstall a HID-compliant touch screen<\/em> driver. Also I found this eGalax web site<\/a>, providing a patch tool to fix the driver issue. This solution should fix the issue on all machines, using a eGalax USB touchscreen. After executing the fix solution, as \"Run as administrator\", the USB eGalax C030 mouse driver was uninstalled via RemovexTouch.exe<\/em>. <\/p>\n

<\/p>\n

Checking my device manager after applying this fix showed me a  HID-compliant touch screen<\/em> entry. Then I used the Action Center<\/em> to switch to Tablet mode (tile Tablet mode <\/em>as shown below) and rebooted Windows 10. <\/p>\n

<\/p>\n

Afterward the issue was solved. My touchscreen was identified properly, and Windows 10 invokes On-screen keyboard automatically, if I type into an App's input box. Also my settings Typing page shows now the required options. <\/p>\n

<\/p>\n

I hope, the explanations given above may help to fix also touchscreen issues on other devices. Comments are always welcome.  <\/p>\n

Other articles:
Win10 Wiki<\/a>
<\/strong>Windows 10: Upgrade error 0xC1900101-0\u00d720017\/0x30017<\/a>
Windows 10: Upgrade error 0xC1900101-0x2000A<\/a>
Windows 10: Upgrade error 0x80200013<\/a>
Windows 10: Upgrade error 0x8007002C-0x4000D<\/a>
Windows 10: Upgrade error 0x8007002C-0x4000D<\/a>
Is EaseUS Partition Master 10.5 a Windows10 upgrade killer?<\/a>
Windows 10: Upgrade error 80240020<\/a>
Windows 10: Dropping App Store Error 0x803F7003<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"

Some People updating a Windows 8.1 tablet pc or hybrid-device with touchscreen will be confronted with a negative surprise: The On-screen keyboard doesn't popup anymore, if the user select an input box in tablet mode. I've had this situation on … Continue reading →<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[2],"tags":[143,35,76],"class_list":["post-436","post","type-post","status-publish","format-standard","hentry","category-windows","tag-touchscreen","tag-troubleshooting","tag-windows-10"],"_links":{"self":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts\/436","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/comments?post=436"}],"version-history":[{"count":0,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts\/436\/revisions"}],"wp:attachment":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/media?parent=436"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/categories?post=436"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/tags?post=436"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}