# Touchpads, pens and Precision drivers

> Which driver your touchpad is using, where gesture settings actually live, and why pen pressure stops working after an update.

**Tested on**

- Build: 26300.9457
- Edition: Pro (26H2)
- Architecture: x64
- Evidence: E1
- Verified: 2026-10-29

## The short answer

Two touchpad worlds exist, and they are not the same product:

| | **Precision touchpad** | **Legacy (vendor) touchpad** |
|---|---|---|
| Settings live in | **Settings → Bluetooth & devices → Touchpad** | the OEM control panel |
| Gestures | standard Windows set | vendor-defined, may differ |
| Driver | Microsoft HID class driver | OEM filter driver |
| Updates | Windows Update | OEM tool |

If your touchpad settings appear in Settings, it is Precision. If they appear only in a vendor app (Synaptics/ELAN control panel), it is legacy — and Windows gestures will be inconsistent.

## Identify what you have

```powershell
Get-PnpDevice -Class Mouse,HIDClass | Select-Object FriendlyName,Status,InstanceId
Get-CimInstance Win32_PnPSignedDriver |
  Where-Object { $_.DeviceName -match 'touchpad|trackpad|synaptics|elan|precision' } |
  Select-Object DeviceName,DriverProviderName,DriverVersion,DriverDate
```

A Precision touchpad reports as a HID-compliant device with `DriverProviderName : Microsoft`. A vendor name means a legacy stack.

## Gestures belong to the driver, not the app

- Precision: three/four-finger gestures are configured by Windows, and apps receive them as **touch** input.
- Legacy: gestures are synthesised by the OEM driver, often as **keyboard shortcuts** — which is why they behave differently in different apps, or not at all in a Remote Desktop session.

That difference explains a classic complaint: "three-finger swipe works locally but not over RDP". It is not a Windows bug.

> **Tip: Palm rejection is a driver feature**
>
> If typing on a laptop causes cursor jumps, the fix is in the vendor driver settings (palm rejection / sensitivity), not in Windows. Precision touchpads expose a basic sensitivity setting; legacy ones do not.

## Pens

A pen reports **pressure, tilt, eraser and barrel button** through HID. Windows delivers them to apps that ask for them (Ink, WinTab-compatible apps, and most creative software).

Common failures:

| Symptom | Cause |
|---|---|
| Pen moves the cursor but no pressure | app not listening for pen input, or driver reverted to mouse emulation |
| Pressure works in one app only | that app uses WinTab/its own API; others get generic pointer data |
| Pen stops after an update | OEM pen driver replaced by a generic HID driver |
| Buttons do nothing | barrel button mapped in the OEM tool, not Windows |
| Jitter / offset near edges | digitiser calibration; run the OEM calibration tool |

```powershell
# pen/touch devices and their power state
Get-PnpDevice -Class HIDClass | Where-Object FriendlyName -match 'pen|stylus|touch' |
  Select-Object FriendlyName,Status,InstanceId
```

## Settings that matter

| Setting | Where | Effect |
|---|---|---|
| Touchpad sensitivity | Settings → Touchpad | cursor speed/acceleration |
| Three/four-finger gestures | Settings → Touchpad | task view, desktop, media |
| "Leave touchpad on when a mouse is connected" | Settings → Touchpad | stops the pad when docked |
| Pen shortcut (single/double click) | Settings → Pen & Windows Ink | launches an app |
| "Show visual effects for touch" | Settings → Pen & Windows Ink | visual feedback |

## When to reinstall a driver

Only when the device is in an error state or gestures stopped after an update:

1. Note the current driver version.
2. Download the OEM package for **your exact model**.
3. Uninstall the device (keep the driver removal checkbox if offered), reboot, install.
4. Verify settings appear in the expected place.

A generic HID driver often "works" for the touchpad but loses gestures and palm rejection — which is why the OEM package matters.

## Related

- [USB devices that are not recognised](https://windows.homes/en/windows/peripherals/usb-device/)
- [Bluetooth audio](https://windows.homes/en/windows/peripherals/bluetooth-audio/)
- [High DPI and scaling](https://windows.homes/en/hardware/display/dpi-scaling/)

## Lab boundary

E1. HID and pen architecture is documented by Microsoft. The lab has no physical touchpad or pen, so no gesture or pressure behaviour was measured.

## Sources

- [Microsoft Learn — HID architecture](https://learn.microsoft.com/en-us/windows-hardware/drivers/hid/)
- [Microsoft Learn — Pen devices](https://learn.microsoft.com/en-us/windows-hardware/design/component-guidelines/pen-devices)
- [Microsoft Learn — Touchscreen devices](https://learn.microsoft.com/en-us/windows-hardware/design/component-guidelines/touchscreen-devices)

---

Source: https://windows.homes/en/windows/peripherals/touchpad-pen/