Which components are important for Tablets / Touch Input?

[Gambatte]

Hello!! (sorry in advance if my English sounds wonky, as it is not my first language - but I'll try my best!)

I have recently customized a Windows 10 LTSC ISO with the attached preset from this reddit post. Unfortunately the person who posted that preset has deleted their account, so asking them is impossible. I really want this slimmed-down version of Windows to run on my Windows tablet. I created a backup of the necessary drivers from a working Windows 10 using DoubleDriver and slipstreamed these drivers using NTLite. The installation went lightening-fast and there are no unknown devices in the device manager after installation. Great!

But here comes the big caveat: touch input doesn't work. Because of course it doesn't. If it did, it would be too easy, eh?
So I checked the device manager again and found out that the "HID-compliant touch screen" is missing in the "input devices"-section. So adding the Goodix touch screen driver to the Windows ISO didn't do anything because Windows thinks that there's no touch screen whatsoever.

Surely this must be the result of removing one too many components? Could someone help me pinpoint the components that are important for touch input in Windows? I have already taken a look at the .xml and removed lines related to the touch screen (so that these components will be included), but it unfortunately didn't fix the issue. I'll greatly appreciate your help!

 

[garlin]

Touch devices normally communicate over the Serial I/O chipset (I2C). Without I2C drivers, many touch devices don't work.

I would restore these devices (by editing the preset in NotePad, and removing these lines).

                <c>driver_iai2c.inf</c>
                <c>driver_ialpss2i_i2c_bxt_p.inf</c>
                <c>driver_ialpss2i_i2c_cnl.inf</c>
                <c>driver_ialpss2i_i2c_glk.inf</c>
                <c>driver_ialpss2i_i2c_skl.inf</c>
                <c>driver_ialpssi_i2c.inf</c>

                <c>driver_sensorshidclassdriver.inf</c>

 

[Gambatte]

Thank you so much for your swift reply!! Sadly it did not make a difference. :/

In order to be sure if touchscreen controls even work on a not-debloated LTSC version, I installed it without touching it (except including the drivers of course). The touchscreen worked and both the "Goodix Touch Panel driver" and the "touch screen device" showed up in the device manager. I only took a quick glance, but quite frustratingly it seems that those two aforementioned devices are the only ones NOT working in the debloated version!!

Hm... any other ideas? I would gladly accept a different "minimal" preset, if there is one. Does it make sense to simply include all the drivers? Surely they would only take up space and not actually slow the system down?

 

[garlin]

Try:

                <c>mobilepc</c>

 

[Gambatte]

Thank you, I just tried it! But sadly there's still no change - touch input still doesn't work and the devices don't show up.

 

[Gambatte]

Alright, I tried a couple more things and found the culprit!! At least when it comes to the "touch screen input device".
If this line is removed, the touch screen works again:

<c>gpiobuttons 'General-Purpose I/O (GPIO)'</c>

What still isn't working is the on-screen touch keyboard. I sadly haven't found a solution to that problem yet. (I do not mean the accessibility on-screen keyboard btw. - I mean the touch screen keyboard, which is different and automatically pops up when you are in an input field).

If I add the touch screen keyboard button to the taskbar and touch it, this thing pops up:
[see attached image]

This clearly isn't working. Removing

<c>osk 'On-Screen Keyboard (Tablet PC)'</c>

and

<c>tabletpc 'Tablet PC'</c>

doesn't help.

Any idea where the problem lies? Pretty please?

 

[garlin]

You removed German language and keyboard maps?

                <c>kl-00000407 'German'</c>
                <c>kl-00000807 'Swiss German'</c>
                <c>kl-00010407 'German (IBM)'</c>
                <c>langgerman 'German'</c>

 

[Gambatte]

It sadly did not fix the problem, but I have found the solution.

It's the dumbest solution I have ever seen, but... connecting the device to the Internet for approximately 1 minute has fixed the touch keyboard issues. It now pops up again.

I do not know what Windows is doing in the background when connected to the Internet, but it has fixed the issue. It is probably recognizing that I'm on a touchscreen device and that something important is missing, so it quietly re-installs the missing component for this particular thing. When the touch screen popup is working again, it is working without an Internet connection as well.

Would have been great if it was working right out of the box though...

 

[garlin]

That sounds like a driver issue. Windows can't download a full update in one minute, but it can find a touchscreen driver in that short time. I would load the live system in NTLite, and review the host's driver list. Export the drivers to a folder, so they can be added to your next image.