Support ForumForums: spacedesk assistanceWindows 11 + iPad – “Multi-touch …

Please or Register to create posts and topics.

Windows 11 + iPad – “Multi-touch feature is not ready” / spacedesk HID device not instantiated

#1 · 14/09/2026, 01:26

Quote from Francesco on 14/09/2026, 01:26
Hello spacedesk Support,

I am experiencing an issue with the multi-touch functionality when using an iPad as an extended display on a Windows 11 ASUS VivoBook notebook.

The spacedesk display functionality itself is now working correctly over Wi-Fi. The iPad is detected as an additional Windows display and I can use it normally in extended desktop mode, including portrait/landscape rotation and Windows display scaling.

The only remaining issue is touch input.

When the iPad connects, spacedesk displays the following notification on Windows:

“Multi-touch feature is not ready. If issue persists, contact spacedesk support.”

Touch input on the iPad does not control the Windows session, regardless of whether I select Absolute Touch or other touch settings.

Environment

OS: Windows 11 64-bit

Computer: ASUS VivoBook 16 Flip OLED, equipped with an integrated touchscreen

spacedesk Windows Driver: V16F

Windows driver/service build shown in Diagnostics: September 10, 2026

spacedesk iOS Viewer: v2.1.6

Client device: Apple iPad

Connection: Wi-Fi / LAN

Windows PC address during testing: 192.168.1.x

Display mode: Windows Extended Desktop

Touch mode tested: Absolute Touch

What is working

iPad discovers the Windows PC correctly.

Network connection between the iPad and the spacedesk server is working.

spacedesk display connection works correctly.

Windows successfully creates the additional virtual display.

Extended desktop works.

Display rotation works.

Windows scaling works correctly.

The ASUS built-in touchscreen works correctly.

Windows Device Manager currently reports no devices with errors.

Troubleshooting already performed

I have investigated the Windows PnP/HID side as well.

The spacedesk HID driver package is correctly installed in the Windows Driver Store:

spacedeskdriverhid.inf

Published as:

oem139.inf

The other spacedesk driver packages are also present, including:

spacedeskdriverandroidcontrol.inf
spacedeskdriverandroidusb.inf
spacedeskdriverbus.inf
spacedeskktminputmouse.inf
spacedeskdisplay.inf
spacedeskdriveraudio.inf
spacedeskvideocapture.inf

However, although spacedeskdriverhid.inf is installed, I cannot find a spacedesk virtual HID/touch device instantiated in Windows Device Manager.

The Windows SetupAPI log also contains:

“Unable to find any matching devices.”

after the spacedesk HID driver package installation.

I also checked:

pnputil /enum-devices /problem

Windows reports:

No devices were found on the system.

In other words, there are currently no PnP devices reporting an error.

I also queried Windows for spacedesk PnP/HID devices. The driver package is present, but I cannot identify an instantiated spacedesk virtual HID touch device using the installed spacedeskdriverhid.inf.

ASUS touchscreen conflict test

Since this ASUS VivoBook has its own integrated HID-compatible touchscreen, I considered a possible conflict between the physical ASUS touchscreen and the spacedesk virtual touch device.

I therefore temporarily disabled the ASUS “HID-compliant touch screen” device in Windows Device Manager, restarted spacedesk and reconnected the iPad.

The result was unchanged:

“Multi-touch feature is not ready.”

I subsequently re-enabled the ASUS touchscreen and it continues to work normally.

Therefore, the presence of the ASUS physical touchscreen does not appear to be the direct cause.

Diagnostics

I have also collected a spacedesk Runtime Diagnostics package while reproducing the problem and can provide/attach the ZIP file.

The display functionality is currently working very well, so I would prefer not to modify or reinstall the working virtual display components unnecessarily.

Could you please help me determine why the spacedesk virtual multi-touch/HID device is not being instantiated by Windows, even though spacedeskdriverhid.inf is correctly installed?

In particular, could you please confirm whether:

there is a known issue with Windows 11 + iPad Viewer v2.1.6 + V16F;

there is any known interaction with notebooks that already have an integrated HID touchscreen;

the spacedesk virtual HID device can be manually checked/recreated;

there are additional logs or diagnostic commands I can provide to identify why the Multi-touch component fails to initialize.

The iPad display functionality itself is working correctly; only the touch/multi-touch input channel is affected.

Thank you for your support.

Hello spacedesk Support,

I am experiencing an issue with the multi-touch functionality when using an iPad as an extended display on a Windows 11 ASUS VivoBook notebook.

The spacedesk display functionality itself is now working correctly over Wi-Fi. The iPad is detected as an additional Windows display and I can use it normally in extended desktop mode, including portrait/landscape rotation and Windows display scaling.

The only remaining issue is touch input.

When the iPad connects, spacedesk displays the following notification on Windows:

“Multi-touch feature is not ready. If issue persists, contact spacedesk support.”

Touch input on the iPad does not control the Windows session, regardless of whether I select Absolute Touch or other touch settings.

Environment

OS: Windows 11 64-bit
Computer: ASUS VivoBook 16 Flip OLED, equipped with an integrated touchscreen
spacedesk Windows Driver: V16F
Windows driver/service build shown in Diagnostics: September 10, 2026
spacedesk iOS Viewer: v2.1.6
Client device: Apple iPad
Connection: Wi-Fi / LAN
Windows PC address during testing: 192.168.1.x
Display mode: Windows Extended Desktop
Touch mode tested: Absolute Touch

What is working

iPad discovers the Windows PC correctly.
Network connection between the iPad and the spacedesk server is working.
spacedesk display connection works correctly.
Windows successfully creates the additional virtual display.
Extended desktop works.
Display rotation works.
Windows scaling works correctly.
The ASUS built-in touchscreen works correctly.
Windows Device Manager currently reports no devices with errors.

Troubleshooting already performed

I have investigated the Windows PnP/HID side as well.

The spacedesk HID driver package is correctly installed in the Windows Driver Store:

spacedeskdriverhid.inf

Published as:

oem139.inf

The other spacedesk driver packages are also present, including:

spacedeskdriverandroidcontrol.inf
spacedeskdriverandroidusb.inf
spacedeskdriverbus.inf
spacedeskktminputmouse.inf
spacedeskdisplay.inf
spacedeskdriveraudio.inf
spacedeskvideocapture.inf

However, although spacedeskdriverhid.inf is installed, I cannot find a spacedesk virtual HID/touch device instantiated in Windows Device Manager.

The Windows SetupAPI log also contains:

“Unable to find any matching devices.”

after the spacedesk HID driver package installation.

I also checked:

pnputil /enum-devices /problem

Windows reports:

No devices were found on the system.

In other words, there are currently no PnP devices reporting an error.

I also queried Windows for spacedesk PnP/HID devices. The driver package is present, but I cannot identify an instantiated spacedesk virtual HID touch device using the installed spacedeskdriverhid.inf.

ASUS touchscreen conflict test

Since this ASUS VivoBook has its own integrated HID-compatible touchscreen, I considered a possible conflict between the physical ASUS touchscreen and the spacedesk virtual touch device.

I therefore temporarily disabled the ASUS “HID-compliant touch screen” device in Windows Device Manager, restarted spacedesk and reconnected the iPad.

The result was unchanged:

“Multi-touch feature is not ready.”

I subsequently re-enabled the ASUS touchscreen and it continues to work normally.

Therefore, the presence of the ASUS physical touchscreen does not appear to be the direct cause.

Diagnostics

I have also collected a spacedesk Runtime Diagnostics package while reproducing the problem and can provide/attach the ZIP file.

The display functionality is currently working very well, so I would prefer not to modify or reinstall the working virtual display components unnecessarily.

Could you please help me determine why the spacedesk virtual multi-touch/HID device is not being instantiated by Windows, even though spacedeskdriverhid.inf is correctly installed?

In particular, could you please confirm whether:

there is a known issue with Windows 11 + iPad Viewer v2.1.6 + V16F;
there is any known interaction with notebooks that already have an integrated HID touchscreen;
the spacedesk virtual HID device can be manually checked/recreated;
there are additional logs or diagnostic commands I can provide to identify why the Multi-touch component fails to initialize.

The iPad display functionality itself is working correctly; only the touch/multi-touch input channel is affected.

Thank you for your support.

#2 · 14/09/2026, 03:16

Hi @francesco-4,

For further analysis of the issue, please send us the logs of your Primary PC by opening the spacedesk Driver console as administrator and clicking on Diagnostics then follow the steps below:

1. Download the DebugView.
2. Check the Diagnostic Collection box.
3. Reproduce the issue e.g. by connecting the spacedesk Viewer app.
4. Uncheck the Diagnostic Collection box.
5. Click “Save All Information” button (this might take a while to finish).
6. Compress/Zip the folder which contains the logs, then attach to your next reply to this post. If the folder exceeds 512kb, you may upload it to Dropbox or Google Drive then include the download link on your next reply.

Thank you.