P
PalaneappanKRajalingam
Guest
Hi,
We use windows 10 for our Kiosks that users use to see the product catalogs.
We use window's TabTip.exe for keyboard input, but after the latest update Kiosk no longer show the keyboard unless windows explorer is running as a process.
We have tried starting the process explicitly at the start of our application and also every time an input field is focused. Even though we could see that the TabTip.exe is in running state, the touch keyboard doesn't show up. Our guess is that UI (touch keyboard) of the TabTip.exe process is dependent on explorer.exe
Or is there any method to keep this functionality as it was pre-update?
We need to have explorer not running at all.
Thanks
I have asked the same question in answers.microsoft.com for which I was asked to repost this issue here for more advanced technical support.
Reply and response for this issue in answers.microsoft.com portal.
Answers for questions in order.
- No, there were no changes made to the device prior to the issue except the new windows 10 update.
- No, I am not getting any error messages.
- I have tried all the troubleshooting steps given in this link [Can't run TabTip.exe without explorer after new windows update]
- There were no error message while trying to run TabTip.exe for keyboard input with or without explorer.exe. Only difference is that with explorer.exe the keyboard gets opened and without explorer.exe keyboard doesn't get opened. However, in both the scenarios the TipTip.exe , TabTip32.exe are running (which I have verified in the details tab of the task manager). Also TabletInputService is running for both the cases.
The issue I am experiencing is exactly the same as in the below link.
More...
We use windows 10 for our Kiosks that users use to see the product catalogs.
We use window's TabTip.exe for keyboard input, but after the latest update Kiosk no longer show the keyboard unless windows explorer is running as a process.
We have tried starting the process explicitly at the start of our application and also every time an input field is focused. Even though we could see that the TabTip.exe is in running state, the touch keyboard doesn't show up. Our guess is that UI (touch keyboard) of the TabTip.exe process is dependent on explorer.exe
Or is there any method to keep this functionality as it was pre-update?
We need to have explorer not running at all.
Thanks
I have asked the same question in answers.microsoft.com for which I was asked to repost this issue here for more advanced technical support.
Reply and response for this issue in answers.microsoft.com portal.
Hello,
The challenge that you're experiencing on your computer might be caused by a system conflict. To isolate the cause of your concern, kindly answer the following questions:
- Were there any changes made on your device prior to the issue?
- Are you getting any error messages?
- What troubleshooting steps have you done so far?
- Can you give us a screenshot of the exact error message while trying to run TabTip.exe for keyboard input with and without explorer.exe?
You can also visit the article on our site to find out how to troubleshoot mouse, touchpad and keyboard problems in Windows 10. It also has easy troubleshooting steps that you can follow at home to resolve the issue.
We're looking forward to your response.
Answers for questions in order.
- No, there were no changes made to the device prior to the issue except the new windows 10 update.
- No, I am not getting any error messages.
- I have tried all the troubleshooting steps given in this link [Can't run TabTip.exe without explorer after new windows update]
- There were no error message while trying to run TabTip.exe for keyboard input with or without explorer.exe. Only difference is that with explorer.exe the keyboard gets opened and without explorer.exe keyboard doesn't get opened. However, in both the scenarios the TipTip.exe , TabTip32.exe are running (which I have verified in the details tab of the task manager). Also TabletInputService is running for both the cases.
The issue I am experiencing is exactly the same as in the below link.
More...