Touch Keyboard Issue

K

Kombowz

New Member
Messages
27
Reaction score
1
Hi Everyone,

I hope you are all having a great day.

This question is in regards to the on-screen touch keyboard.
The keyboard opens and I can use it just fine if I click the icon in the notification area.
But touching on the screen doesn't seem to bring it up.
I was wondering if anyone may know why that is? it's like the link between clicking the screen and the trigger of the keyboard to open is not working.

I was testing the image here at work so I don't have the profile on hand how, but I figured to ask in case someone knew of something specific that would cause this.

Thank you everyone, I appreciate you all.
 
Last edited:
Removing some components like Client.CBS or features related to Windows Notifications, can break the On-Screen Keyboard (OSK). Without a specific preset, it's hard to narrow down the possibilities.
 
I would look at a few possibilities:
Code: 
                <c>osk_acc 'On-Screen Keyboard (Accessibility tools)'</c>
                <c>uac 'User Account Control (UAC)'</c>

UAC is more likely because a few desktop apps surprisingly require UAC to correctly function.
I've never seen anyone remove OSK (Accessibility Tools), most users just remove the entire OSK. Try that one if restoring UAC doesn't work.
 
Unfortunately, after enabling both of these, the touch keyboard still will not open by touching the screen...
 
Code: 
                <c>accessibility 'Accessibility tools (Ease of Access)'</c>
                <c>langime 'Input Method Editor (IME)'</c>
 
Unfortunately, it's still not working...
This is such a strange problem...

Looks like a notification service was disabled as well, trying it again after reenabling it.
 
Last edited:
Maybe it's your device support. You installed the device driver for touchscreen support?
Code: 
                <c>deviceexperience 'Device Experience'</c>
 
The touchscreen itself is working with no issues, it's just not opening the touch keyboard when you click into a text field etc.

I will try removing that line next.
 
garlin said:
Maybe you didn't enable this setting:
Turn On or Off Automatically Show Touch Keyboard when No Keyboard Attached in Windows 10
Click to expand...
This was my initial thought, but after checking that is when I realized that it was an issue and decided to post here to see what might be the issue.

I'm removing the last suggested line now and testing. Any other suggestions I will just continue to run through them so I can figure this. Seems like this could be important to others to have a solution as well.
 
<c>pcshell 'Taskbar popups (PC Shell 'Tray Flyouts')'</c>
It is related to various taskbar pop-up windows
<c>osk_acc 'On-Screen Keyboard (Accessibility tools)'</c>
Touch keyboard on the taskbar
 
Good morning everyone,

Still a no go on this issue. I'm really baffled at this and starting to think that maybe it's a service or scheduled task that was disabled/removed? If there are any other suggestions, I'd be more than happy to give it a try.

As always, I appreciate all of your help.
 
So after trying the preset without component removal, it's at least confirmed that it's a component that's causing the issue...

Now I can continue to figure out which one it is that's causing the issue.
 
I would follow a divide & conquer strategy on debugging your removals.

1. Make a backup copy of your full preset.
2. Open the preset file in Notepad. For simplifying this exercise, delete all removal lines with the following patterns:
Code: 
<c>driver_*</c>
<c>font_*</c>
<c>hwsupport_*</c>
<c>kl-*</c>

The general goal is to reduce the preset's length, by removing the bulk of non-applicable changes so you have less components to check

3. Save this reduced preset.
4. Remove about half of the remaining removal lines <c>...</c> in the preset (top or bottom half).
5. Now make an ISO and test the OSK feature.
6. If your problem is resolved, you know the offending component was in which half of the list. If the problem wasn't solved, you know the component is in the other half.

7. Continue this exercise by splitting out the removals from the problem half in two (two 1/4 sections). Repeat again.
8. By reducing the problem section of the list every time in smaller halves, you can identify the problem component in less steps.
 
Hi Garlin,

Absolutely, now that I know it's a component specifically, I'm saving categories, then parts of each category.
Once I figure it out I will post here to share with others struggling with this issue.

I appreciate the help as always.
 
You must log in or register to reply here.
Back
Top