Touchpad Gestures Gone After Update: Restore Precision Touchpad Features

The mental model: why gestures vanish while the cursor lives

Treat your touchpad like a small input “subsystem,” not a single device. In Windows, gesture support
(two/three/four-finger actions, palm rejection, smooth scrolling, etc.) depends on multiple layers:

• Hardware transport: Most modern internal touchpads are on I2C (common) or SPI (less common). Older models used PS/2 emulation.
• Device identity: Windows needs to recognize the pad as a Precision Touchpad (PTP). If it falls back to a vendor legacy stack, Windows gestures can disappear (or become vendor-specific).
• Drivers: You usually need an I2C controller driver plus a HID miniport path (and sometimes vendor filter drivers).
• Services and policies: A corporate policy can disable gestures; accessibility settings can alter behavior; “enhancements” can be toggled off by an update.
• Settings UI wiring: The Settings page can disappear if the device is no longer classified as PTP.

When an update changes a driver binding, Windows may still see “a mouse-like thing” and move the pointer,
but the gesture pipeline is gone. That’s why you can click and drag, yet two-finger scrolling is dead.

One quote worth keeping in mind—because troubleshooting input devices is basically incident response in miniature:
“Hope is not a strategy.” (paraphrased idea often credited in engineering/operations circles)

You’ll do better if you stop hoping and start checking which layer broke.

Fast diagnosis playbook (check first/second/third)

First: confirm whether Windows still thinks it’s a Precision Touchpad

Go to Settings → Bluetooth & devices → Touchpad. If the page is missing, sparse, or lacks gesture options,
that’s a strong signal the device is no longer enumerating as PTP.

Decision: If Windows doesn’t recognize PTP, skip tweaking gesture settings. You need driver enumeration fixed first.

Second: check Device Manager for the usual offenders

• Human Interface Devices: look for “HID-compliant touch pad” and any device with a yellow bang.
• Mice and other pointing devices: if you only see “HID-compliant mouse,” you might be on the fallback path.
• System devices: check “Intel(R) Serial IO I2C Host Controller” (or AMD equivalent). Missing or errored I2C kills modern pads.

Decision: If I2C/Serial IO is broken, fix that first. A perfect touchpad driver can’t talk to a dead bus.

Third: verify Windows didn’t replace the vendor driver with a generic one

Updates sometimes “helpfully” swap drivers to a Microsoft inbox driver. Sometimes that’s fine; sometimes gestures
move from vendor UI to Windows UI; sometimes everything degrades. Check the driver provider and version and compare
with your OEM’s expected package.

Decision: If the driver provider changed recently and gestures disappeared the same day, roll back or re-install the OEM package.

Fourth: validate policies, accessibility, and “disable touchpad when mouse connected”

Especially in corporate builds: Group Policy, MDM, or OEM utilities can disable gestures silently. Also check that
you didn’t connect a USB mouse and trigger a setting that disables the touchpad.

Interesting facts and context (so the weirdness makes sense)

1. Precision Touchpad is a Windows program, not a brand of hardware. Microsoft defines the behavior contract; vendors build to it.
2. PTP started gaining real traction around Windows 8/10 era when Microsoft pushed for consistent gestures and settings across OEMs.
3. Legacy PS/2-style touchpads can move a cursor without exposing modern gesture telemetry. That’s why “it moves” doesn’t mean “it gestures.”
4. I2C became common for internal touchpads because it simplifies integration and power management versus older interfaces.
5. Vendor drivers often include filter components that can conflict with Windows updates or security hardening, especially around input injection.
6. Windows Settings shows different UI depending on device classification. If PTP status is lost, gesture toggles may disappear entirely.
7. Driver updates can change device IDs and binding. Same hardware, different INF match, different stack.
8. Some OEMs ship “custom” gesture apps even on PTP hardware; uninstalling those can return control back to Windows—or remove needed filters.
9. Fast Startup can mask driver initialization bugs. A full shutdown/power-cycle sometimes “fixes” it because it forces hardware re-enumeration.

Hands-on diagnostic tasks (commands, outputs, decisions)

These tasks assume Windows. The shell prompt below is a convenience wrapper—run them in PowerShell as Administrator
unless noted. Don’t just run everything blindly; each command exists to answer a question and drive a decision.

Task 1: Confirm touchpad settings page exists (PTP hint)

cr0x@server:~$ start ms-settings:devices-touchpad
...Windows Settings opens to the Touchpad page (or shows an error / different page)...

What it means: If it opens to a detailed page with gesture options, Windows likely sees a PTP-capable device.
If it errors or lands somewhere generic, enumeration may be broken.

Decision: Detailed page present → focus on settings/policies. Missing page → focus on drivers and device classification.

Task 2: List PnP devices that look like touchpads

cr0x@server:~$ powershell -NoProfile -Command "Get-PnpDevice | ? { $_.FriendlyName -match 'touch|track|i2c|hid-compliant touch' } | Select Status, Class, FriendlyName, InstanceId | Format-Table -Auto"
Status Class                 FriendlyName                 InstanceId
------ -----                 ------------                 ----------
OK     HIDClass              HID-compliant touch pad      HID\VEN_SYNA&DEV_2B5D&COL01\5&2A...
OK     System                Intel(R) Serial IO I2C Host Controller - A0E8 PCI\VEN_8086&DEV_...

What it means: You want to see a touchpad device plus the I2C controller (on many systems).
If the touchpad device is missing or “Unknown device,” that’s your problem.

Decision: Missing I2C controller → reinstall chipset/Serial IO drivers. Missing touchpad device → check BIOS setting and driver binding.

Task 3: Inspect the driver provider for the touchpad

cr0x@server:~$ powershell -NoProfile -Command "$d=Get-PnpDevice -FriendlyName '*touch pad*' -ErrorAction SilentlyContinue; if($d){Get-PnpDeviceProperty -InstanceId $d.InstanceId -KeyName 'DEVPKEY_Device_DriverProvider' | Select-Object -ExpandProperty Data}else{'not found'}"
Synaptics

What it means: Provider “Microsoft” often indicates an inbox driver; “Synaptics/ELAN/ALPS/Lenovo/Dell/HP”
suggests OEM packages.

Decision: If provider changed right after the update, consider rollback or OEM reinstall.

Task 4: Check for problem devices (yellow bangs) quickly

cr0x@server:~$ powershell -NoProfile -Command "Get-PnpDevice | ? { $_.Status -ne 'OK' } | Select Status,Class,FriendlyName,InstanceId | Format-Table -Auto"
Status Class  FriendlyName                                 InstanceId
Error  System Intel(R) Serial IO I2C Host Controller - A0E8 PCI\VEN_8086&DEV_...

What it means: An errored I2C controller is basically “the bus is down.” Touchpad gestures won’t survive that.

Decision: Fix the controller driver first (chipset/Serial IO), then re-check the touchpad device.

Task 5: Verify HID service is running

cr0x@server:~$ powershell -NoProfile -Command "Get-Service hidserv | Format-List Status,StartType,Name,DisplayName"
Status    : Running
StartType : Manual
Name      : hidserv
DisplayName : Human Interface Device Service

What it means: If HID service is stopped/disabled, some HID features degrade in strange ways.

Decision: If disabled, set to Manual/Automatic and start it; then re-test gestures.

Task 6: Pull recent driver install events (did Windows update your input stack?)

cr0x@server:~$ powershell -NoProfile -Command "Get-WinEvent -FilterHashtable @{LogName='System'; ProviderName='Kernel-PnP'; Id=20001,20003,21001} -MaxEvents 20 | Select TimeCreated,Id,Message | Format-Table -Wrap"
TimeCreated           Id Message
-----------           -- -------
02/03/2026 09:14:10 20001 Driver package added: oem42.inf (SynTP.inf)...
02/03/2026 09:14:12 21001 Device configured (HID\VEN_SYNA...)...

What it means: Kernel-PnP logs tell you whether a new driver package was added or a device was reconfigured around the time gestures died.

Decision: Clear correlation with update → rollback driver or reinstall OEM package.

Task 7: Check the touchpad device status and problem code

cr0x@server:~$ powershell -NoProfile -Command "$d=Get-PnpDevice -FriendlyName '*touch pad*' -ErrorAction SilentlyContinue; if($d){$d | Format-List Status,Problem,Class,FriendlyName,InstanceId}else{'not found'}"
Status     : OK
Problem    : 0
Class      : HIDClass
FriendlyName : HID-compliant touch pad
InstanceId : HID\VEN_SYNA&DEV_2B5D&COL01\5&2A...

What it means: “Problem: 0” means Windows thinks the device is happy. That doesn’t guarantee gestures are enabled,
but it rules out obvious enumeration failure.

Decision: If OK but gestures missing → likely classification/settings/policy/vendor utility conflict.

Task 8: Validate I2C controller device status (for modern internal pads)

cr0x@server:~$ powershell -NoProfile -Command "Get-PnpDevice -Class System | ? { $_.FriendlyName -match 'I2C Host Controller|Serial IO I2C|AMD I2C' } | Select Status,FriendlyName,InstanceId | Format-Table -Auto"
Status FriendlyName                                         InstanceId
------ ------------                                         ----------
OK     Intel(R) Serial IO I2C Host Controller - A0E8        PCI\VEN_8086&DEV_...

What it means: If the controller is not OK, the touchpad might fall back or disappear.

Decision: Controller not OK → reinstall chipset/Serial IO; consider BIOS updates if it recurs.

Task 9: Check if Windows thinks the device is “Precision Touchpad” via registry hints

There isn’t a single blessed “PTP = 1” flag that always works across OEMs, but for many systems you can check for
PrecisionTouchPad status under the current user and device keys. Use this as a hint, not as gospel.

cr0x@server:~$ powershell -NoProfile -Command "reg query 'HKCU\Software\Microsoft\Windows\CurrentVersion\PrecisionTouchPad' /s 2>$null | select -First 20"
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\PrecisionTouchPad
    AAPThreshold    REG_DWORD    0x0
    CursorSpeed     REG_DWORD    0xa

What it means: If this key exists, Windows has at least loaded PTP configuration for the user profile.
It doesn’t prove hardware support, but it suggests Windows gesture plumbing is present.

Decision: If keys exist but Settings page missing → device classification likely broke. If keys don’t exist → you may be on legacy driver UI.

Task 10: Check if group policy/MDM might be stomping touchpad settings

cr0x@server:~$ powershell -NoProfile -Command "gpresult /r | Select-String -Pattern 'Applied Group Policy Objects|Device Installation|MDM' -Context 0,2"
Applied Group Policy Objects
-----------------------------
    Corp-Base
    Endpoint-Restrictions

What it means: This doesn’t list touchpad policies directly, but it tells you whether you’re in a managed environment.
If yes, assume someone can disable drivers or settings centrally.

Decision: Managed device → check with IT or review local policy/MDM restrictions before doing driver gymnastics that will get reverted overnight.

Task 11: Identify recently installed updates (the “what changed?” step)

cr0x@server:~$ powershell -NoProfile -Command "Get-HotFix | Sort-Object InstalledOn -Descending | Select-Object -First 10 HotFixID,InstalledOn,Description | Format-Table -Auto"
HotFixID  InstalledOn Description
-------   ----------  -----------
KB503xxxx 2/3/2026    Security Update
KB503yyyy 2/2/2026    Update

What it means: If the touchpad broke right after a specific update, you have a clean rollback candidate.

Decision: Consider uninstalling the suspect update if it clearly correlates and you have a maintenance window (yes, even on a laptop).

Task 12: Enumerate installed third-party drivers (hunt the touchpad INF)

cr0x@server:~$ powershell -NoProfile -Command "pnputil /enum-drivers | Select-String -Pattern 'Synaptics|ELAN|ALPS|TouchPad|Precision' -Context 0,6"
Published Name : oem42.inf
Original Name  : SynTP.inf
Provider Name  : Synaptics
Class Name     : HIDClass
Driver Version : 19.5.35.69

What it means: This shows whether the OEM driver package is installed in the driver store.
The package can be present even if the device is not currently bound to it.

Decision: If the OEM package is missing, install it. If present, consider forcing rebind (Device Manager uninstall + rescan) or rollback.

Task 13: Roll back the touchpad driver (when it’s the obvious culprit)

cr0x@server:~$ powershell -NoProfile -Command "devmgmt.msc"
...Device Manager opens; you use: HID-compliant touch pad → Properties → Driver → Roll Back Driver...

What it means: Rollback is the fastest “undo” if Windows updated the driver and gestures died immediately.

Decision: If rollback restores gestures, stop there. Then block that driver update (temporary) in managed environments.

Task 14: Remove the broken driver package from the driver store (the nuclear-but-clean option)

cr0x@server:~$ pnputil /delete-driver oem42.inf /uninstall /force
Microsoft PnP Utility

Driver package deleted successfully.

What it means: This removes the driver package and uninstalls from devices using it. Windows will then re-enumerate and bind to another compatible driver.

Decision: Do this when a specific package is clearly defective, or when you want Windows to fall back so you can re-apply the OEM driver cleanly.

Task 15: Check for “disable touchpad when mouse connected” and current touchpad state

cr0x@server:~$ powershell -NoProfile -Command "reg query 'HKCU\Software\Microsoft\Windows\CurrentVersion\PrecisionTouchPad' /v 'LeaveOnWithMouse' 2>$null"
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\PrecisionTouchPad
    LeaveOnWithMouse    REG_DWORD    0x1

What it means: On many builds, LeaveOnWithMouse=0 can disable the touchpad when an external mouse is present.
It doesn’t usually kill gestures only, but it’s a classic “I swear it worked yesterday” trigger.

Decision: If behavior changes when mouse is plugged in, set to 1 (or toggle in Settings) and retest.

Task 16: Force a real shutdown (not Fast Startup) to reset hardware enumeration

cr0x@server:~$ shutdown /s /t 0
...system powers off fully...

What it means: This bypasses hybrid shutdown. It can clear a bad post-update hardware state, especially on I2C devices.

Decision: If gestures return after full shutdown but not after restart, suspect firmware/driver init timing. Consider BIOS update and chipset driver refresh.

Joke #1: If your touchpad only scrolls when the moon is full, congratulations—you’ve discovered “firmware-driven user experience.”

Restore paths: pick the right fix for your laptop

Path A: Windows no longer shows Precision Touchpad options

If the touchpad Settings page is missing gesture controls, treat it as a classification problem, not a UI problem.
Windows isn’t hiding the options to spite you; it’s not convinced the device supports them.

1. Check Device Manager for “HID-compliant touch pad.” If absent, you may have an unknown device or a disabled device.
2. Verify I2C/Serial IO controller status. If that controller is errored or missing, fix chipset/Serial IO drivers.
3. Reinstall OEM touchpad driver package (Synaptics/ELAN/etc.) that matches your exact model. Not “close enough.”
4. Uninstall the touchpad device (Device Manager) and check “Delete the driver software for this device” if available, then reboot and reinstall OEM driver.
5. Update BIOS/UEFI if OEM release notes mention input/I2C stability or if the issue appears after firmware changes.

Avoid random “driver updater” tools. They optimize for clicks, not correctness. In production we call that “introducing entropy.”

Path B: Precision Touchpad options exist, but gestures are disabled or inconsistent

Here the device is likely recognized properly, and you’re dealing with settings, policies, or a vendor utility that’s intercepting gestures.

1. Reset touchpad settings in Settings if the option exists. Re-enable two-finger scroll and three/four-finger gestures.
2. Check for OEM touchpad applications (control panels, gesture managers). They can override Windows gestures or disable them.
3. Check accessibility features (Sticky Keys, Filter Keys) and third-party mouse utilities that hook input events.
4. Test in a clean boot (disable non-Microsoft startup items) to rule out software interception.

Path C: Gestures work until sleep/hibernate, then die

That’s often a power management edge case on I2C devices: the controller resumes, the touchpad doesn’t, and Windows quietly falls back.

1. Disable Fast Startup temporarily and retest across multiple sleep/wake cycles.
2. Update chipset and Serial IO drivers (or AMD I2C). Sleep bugs live there.
3. Check power management tabs (where present) on the I2C controller and HID device: “Allow the computer to turn off this device to save power.” Toggle to test.
4. Update BIOS if the vendor has touched power management recently.

Path D: Touchpad is fine; only multi-finger gestures are gone in specific apps

Some apps implement their own gesture handling. Browsers, remote desktop clients, VM consoles, and CAD tools are frequent offenders.

1. Test gestures in Windows itself (Task View, desktop switching), not only in one app.
2. Check remote session settings: some clients map two-finger scroll differently or disable it.
3. Update the app or reset its input preferences.

Three corporate mini-stories from the trenches

1) The incident caused by a wrong assumption

A company rolled out a laptop fleet refresh. Same OEM, same model line, same Windows image. The deployment team assumed
“touchpad is touchpad” and decided to standardize on a single vendor driver package to reduce complexity.
It worked in their lab. It worked for the first batch. Then the tickets started.

Users reported that the cursor moved but two-finger scrolling was gone after Patch Tuesday. Three-finger gestures vanished,
and the Touchpad settings page looked oddly minimal. Helpdesk tried reinstalling the standardized package; no change.
They replaced a few units, because that’s what you do when you’re out of ideas and have budget.

The wrong assumption: the “same model line” shipped with different touchpad hardware revisions across regions.
One batch had ELAN hardware on I2C, another had Synaptics, and a third used a slightly different device ID.
The standardized package matched some IDs and not others. After the Windows update, driver ranking changed and Windows bound
the non-matching devices to a generic HID path. Cursor survived. Gestures didn’t.

The fix was boring: detect hardware IDs during imaging and install the correct driver per device family.
They also added a post-update health check: validate PTP settings page presence and a simple two-finger scroll test.
Tickets dropped because they stopped pretending hardware is uniform just because procurement said it was.

2) The optimization that backfired

Another org wanted faster boot times. They enabled Fast Startup across the fleet and shaved seconds off the startup metric.
The dashboard turned green. Leadership smiled. Then input weirdness arrived like it had been waiting in the parking lot.

The touchpad gestures worked after a cold boot, but after a restart—sometimes—gestures were missing.
Or after docking/undocking. Or after sleep. It was inconsistent, which is the worst kind of consistent.
The team chased driver versions and even blamed a security agent that hooks input for “anti-keylogging.”

The root cause: Fast Startup kept the system in a hybrid state where the I2C controller and touchpad firmware didn’t always
reinitialize cleanly after certain update sequences. A subset of machines would wake into a state where the device enumerated
but didn’t expose the full gesture capability, so Windows defaulted to mouse-like behavior.

They rolled back Fast Startup for that hardware generation, and the incident stopped.
Boot time got slightly worse. User productivity got meaningfully better.
Performance metrics without reliability context are just spreadsheet cosplay.

3) The boring but correct practice that saved the day

A security update caused touchpad regressions on a set of laptops used by a finance team during quarter close.
The environment was managed, tightly. The SRE-ish desktop engineering group had two things going for them:
disciplined change tracking and a pre-approved rollback path for driver updates.

Their process was painfully unsexy: every driver pushed via management had a package ID, a pilot ring, and a known-good rollback.
They also archived OEM driver bundles internally and validated them against hardware IDs before wide rollout.
No heroics. No midnight “download from random forum” adventures.

When the touchpad gestures died, they correlated the exact time with Kernel-PnP events and the management deployment log,
then reverted the specific driver package only for affected hardware IDs. They didn’t touch unrelated machines.
They didn’t pause all updates. They didn’t break compliance.

The finance team got their gestures back the same day. The next week, engineering worked with the OEM package that restored
PTP classification while keeping the security baseline intact. The victory wasn’t cleverness; it was having receipts.

Common mistakes: symptom → root cause → fix

1) Symptom: Cursor moves, but two-finger scroll and three-finger gestures are gone

Root cause: Touchpad bound to a generic HID mouse path or legacy vendor driver that doesn’t expose PTP gestures.

Fix: Verify PTP settings page; reinstall correct OEM touchpad driver; ensure I2C/Serial IO is healthy; roll back the last driver update.

2) Symptom: Touchpad settings page is missing entirely

Root cause: Windows no longer recognizes a touchpad device (disabled in BIOS, driver missing, device ID mismatch, I2C controller broken).

Fix: Check Device Manager for I2C controller errors; reinstall chipset/Serial IO; enable internal pointing device in BIOS/UEFI; rescan hardware.

3) Symptom: Gestures work after shutdown, break after restart

Root cause: Hybrid boot/Fast Startup leaving device firmware in an odd state.

Fix: Disable Fast Startup to test; update BIOS and chipset drivers; use full shutdown as a workaround.

4) Symptom: Gestures work in Windows UI, not in one specific application

Root cause: App intercepts gestures or remaps scrolling (common with remote desktop/VM console tools).

Fix: Test outside the app; update/reset app settings; adjust remote session input mapping.

5) Symptom: Touchpad stops when a USB mouse is connected

Root cause: “Disable touchpad when mouse connected” setting or registry flag.

Fix: Toggle that setting; set LeaveOnWithMouse to enabled; verify OEM utility isn’t enforcing it.

6) Symptom: Only tap-to-click is broken; physical click still works

Root cause: Tap gestures disabled in settings or a vendor utility overwrote defaults during update.

Fix: Re-enable taps in Settings; reset touchpad settings; remove conflicting vendor gesture apps if you want Windows to own gestures.

7) Symptom: Touchpad disappears randomly from Device Manager

Root cause: I2C controller instability, power management, or firmware bug; sometimes a loose internal connection (rare but real).

Fix: Update BIOS/chipset; adjust power management; if it persists across OS reinstalls, consider hardware service.

Joke #2: Driver updates are like office coffee—most days they help, and occasionally they ruin everything before 9 a.m.

Checklists / step-by-step plan

Checklist 1: Five-minute triage (don’t overthink it)

1. Open Settings → Touchpad. If gesture toggles are missing, assume classification/driver binding issue.
2. Check Device Manager for yellow bangs on I2C/Serial IO and HID devices.
3. Unplug external mouse/dock. Verify touchpad is not being disabled due to “mouse connected.”
4. Do a full shutdown (not restart) and power back on.
5. If still broken, identify last change: update/driver install, OEM utility update, security agent update.

Checklist 2: Driver and classification recovery (the reliable path)

1. Record current state: export driver provider/version (Task 3/12), and capture Kernel-PnP events (Task 6).
2. Fix bus first: if I2C controller is erroring (Task 4/8), reinstall chipset/Serial IO.
3. Roll back touchpad driver if a recent driver install correlates with breakage.
4. Uninstall device in Device Manager, optionally delete driver software, reboot.
5. Install the OEM driver package that matches your laptop model and hardware ID.
6. Verify PTP settings page and re-enable gestures/taps/scroll.

Checklist 3: Corporate-managed machines (don’t fight your tooling)

1. Run gpresult /r (Task 10) to confirm management scope.
2. Check if a driver was deployed by management around the time gestures failed.
3. Coordinate rollback via your endpoint management platform instead of local hacks, or it will be undone.
4. If you must fix locally, document hardware ID + driver package so it can be turned into a controlled deployment.

Checklist 4: Sleep/wake gesture failures

1. Disable Fast Startup to test.
2. Update chipset/Serial IO/I2C driver.
3. Update BIOS/UEFI.
4. If the issue persists, test with vendor driver vs Microsoft inbox driver to see which stack resumes reliably.

FAQ

1) Why does the touchpad move the cursor but not scroll?

Because cursor movement can be provided by a basic HID mouse-compatible path, while multi-touch gesture support requires
a Precision Touchpad-capable stack and correct driver binding. You’re seeing a fallback mode.

2) How do I know if my touchpad is a Precision Touchpad?

In Windows, you typically see a rich Touchpad settings page with gesture configuration. In Device Manager you’ll often
see “HID-compliant touch pad.” If the settings page is missing gesture options, Windows may not be treating it as PTP.

3) Should I install a Synaptics/ELAN driver from another laptop model?

No. “Close enough” is how you get intermittent behavior, broken sleep/wake, and driver ranking surprises after updates.
Use an OEM package intended for your exact model or hardware ID family.

4) Is it safe to uninstall a touchpad driver?

Usually, yes—Windows can fall back to a generic driver or re-detect on reboot. But have a USB mouse handy.
If you’re on a managed corporate machine, coordinate with IT so your fix isn’t immediately overwritten.

5) My Touchpad settings page disappeared. Is that a Windows bug?

Sometimes it’s triggered by an update, but the root cause is generally device detection/classification.
Start with I2C/Serial IO controller health and driver binding, not Settings resets.

6) Why did this happen right after a Windows update?

Updates can install new drivers, change driver ranking, or adjust security and power behavior. Any of those can alter
how the touchpad enumerates. Kernel-PnP logs help confirm the timeline.

7) Do I need to update BIOS to fix gestures?

Not always, but if the issue is tied to sleep/wake, I2C instability, or repeated post-update regressions, BIOS updates
can be the difference between stable and haunted. Update cautiously and only from the OEM.

8) Can Group Policy or MDM disable gestures?

Yes. Managed environments can restrict device installation, block certain drivers, or enforce settings.
If your fix doesn’t “stick,” you’re probably fighting policy.

9) Two-finger scrolling is missing only in Remote Desktop. What now?

That’s often client-side mapping. Confirm gestures work locally (Windows UI). Then adjust the remote client’s input/scroll settings
or update the client. Don’t reinstall drivers for an app-specific issue.

Next steps that keep gestures working

Restoring gestures once is nice. Keeping them through the next update is the real win.
Here’s what I’d do if this were my laptop—or a fleet I had to support without losing my weekends:

1. Capture the known-good state: driver provider/version and the presence of PTP settings. If it breaks again, you’ll diff reality, not feelings.
2. Prefer OEM chipset + Serial IO packages when I2C is involved. “Generic works” is fragile under sleep/wake and updates.
3. Be deliberate about driver updates: if you find a stable version, don’t chase new ones unless you need a fix or security patch.
4. Disable Fast Startup as a test tool when issues appear after updates. It’s a cheap way to separate initialization bugs from configuration bugs.
5. In corporate environments: push driver changes through rings/pilots and keep rollback ready. The boring practice scales; heroics do not.

If you run the diagnostic tasks above and still can’t get PTP gestures back, the remaining suspects are hardware/firmware
(touchpad module, cable, controller), or a policy layer you don’t control. At that point, stop burning hours and escalate with evidence:
PnP device status, Kernel-PnP timeline, driver store inventory, and whether the Settings page identifies a Precision Touchpad.