Hi Wilson Charlie,
How is your issue going? Has it been resolved yet? If it has, please consider accepting the answer as it helps others sharing the same problem benefit too. Thank you :)
VPHAN
Resolving HID Input Mapping and Gesture Redirection Failures in Remote Desktop for iPadOS
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(99.2, 19%, 19%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EWC%3C/text%3E%3C/svg%3E)
Wilson Charlie
0
Reputation points
We have deployed iPadOS 17.1 devices running the Microsoft Remote Desktop client (v10.5.2) to access our Windows infrastructure but critical input discrepancies're hindering productivity in specialized design suites. Specifically, native multi-touch gestures and peripheral inputs, such as utilizing the Magic Trackpad for pinch-to-zoom or the mouse scroll wheel for magnification fail to pass into the remote browser, instead scaling the client application itself. Essential modifier click combinations used for canvas panning in tools like Axure remain unresponsive, and standard navigation keys including Home or end are not being recognized by the host OS. Despite adjusting the local tablet accessibility settings for scroll-zoom, these input commands are not successfully traversing the RDP tunnel. Is there an administrative configuration or a specific input mode within the Windows client that allows for transparent passthrough of these specialized hardware interrupts and HID commands?
Windows for business | Windows 365 Enterprise
2 answers
Sort by: Most helpful
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(275.2, 16%, 36%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EV%3C/text%3E%3C/svg%3E)
VPHAN 31,830 Reputation points Independent Advisor2026-05-13T06:37:41.2633333+00:00 -
VPHAN 31,830 Reputation points Independent Advisor
2026-05-11T16:41:02.7466667+00:00 Hi Wilson Charlie,
The failure is probably a result of the Remote Desktop client's input abstraction layer. To rectify this, you must engage Touch mode via the in-session connection bar. This configuration forces the client to utilize the RDP Touch Injection API, allowing the remote Windows environment to receive raw multi-touch packets.
Also, you must ensure the keyboard setting is explicitly set to Scancode mode within the client's connection properties. On the host side, you should verify that the Windows environment is prepared to accept high-precision input by checking the registry key at HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations. Ensure that the entry for fEnableRemoteFXAdvTouch is set to 1. If your environment uses Group Policy, you should also enable the policy for "Use hardware graphics adapters for all Remote Desktop Services sessions" located under Computer Configuration, Administrative Templates, Windows Components, Remote Desktop Services.
Hope this answer brought you some useful information. If it did, please hit “accept answer”. Should you have any questions, feel free to leave a comment.
VPHAN