Dead cursor, dead gestures, dead touchpad. The Synaptics pad that handled two-finger scroll yesterday does nothing today, and the 24H2 update is the obvious suspect — because it almost always is. Device Manager shows the Synaptics entry with a yellow warning, or under a generic name, or not at all.

The mechanism is consistent: Windows 11’s update replaced the Synaptics SMBus driver with a generic PS/2 driver that cannot speak the touchpad’s protocol. The hardware is untouched; the software binding is wrong. Fix the binding — rollback, clean reinstall, vendor package — and the touchpad revives. Keep a USB mouse plugged in while you work; it uses an independent driver path. (ELAN touchpad instead? Our ELAN repair guide covers that hardware.)

Why this happens

  • 24H2 swapped in a generic PS/2 driver. It cannot communicate over the SMBus interface the touchpad uses.
  • Synaptics SMBus driver corrupted. The update damaged the driver package mid-install.
  • Touchpad toggle flipped off. Settings > Bluetooth & devices > Touchpad got disabled during migration.
  • Fn-key toggle engaged. The firmware-level touchpad shortcut is in the off position.
  • Stale Synaptics app conflicting. Old control-panel software blocks the new driver from binding.
  • SMBus controller driver broken. The underlying bus driver the touchpad rides on is damaged.
  • BIOS internal pointing device disabled. A firmware update toggled the touchpad off.
  • Embedded controller wedged. The EC bridging the touchpad needs a power-drain reset.

How to fix it

Work through these in order — diagnose first, then act.

Fix 1: Check the toggle and the Fn key

Open Settings > Bluetooth & devices > Touchpad and confirm it is On — 24H2 migration flips this off on some machines. Then press the touchpad Fn combination (Fn + F5/F7/F9 depending on brand; look for the touchpad icon). Test the cursor after each. If either was the culprit, you are done in under a minute. Do not skip this: technicians waste real time on driver surgery for touchpads that were simply toggled off.

Fix 2: Roll back the driver

Open Device Manager, find the Synaptics entry under Human Interface Devices or Mice and other pointing devices, open Properties > Driver, and click Roll Back Driver. Restart and test. Rollback restores the pre-24H2 Synaptics build — the fastest fix when the failure lines up with the update. If the button is greyed out, Windows did a full driver replacement rather than an upgrade, and you need the clean reinstall next.

Fix 3: Clean-reinstall the Synaptics driver

Right-click the Synaptics device, choose Uninstall device, and check Attempt to remove the driver for this device to purge the broken package from the driver store. Click Action > Scan for hardware changes, then restart. Windows installs a driver on boot — test it. If Windows picks the same broken generic driver again, leave it in place for now and move to the vendor package; the clean uninstall was still necessary groundwork.

Fix 4: Install the manufacturer’s Synaptics package

Download the Synaptics touchpad driver for your exact model from Lenovo support , Dell support , or HP support . Install, restart, and verify: cursor movement, two-finger scroll, pinch zoom. The vendor package includes the SMBus driver plus the gesture software, and it registers with Windows Update to resist generic overwrites. This is the definitive fix — most 24H2 Synaptics failures end here. Lenovo owners should also review our Synaptics guide for Lenovo laptops for ThinkPad- and IdeaPad-specific notes. After the install, test every gesture you rely on — a partially bound driver can restore movement while leaving gestures dead, and you want to catch that now rather than mid-workday.

Fix 5: Clear out old Synaptics software

If the vendor package misbehaves, old Synaptics software is likely interfering. In Settings > Apps > Installed apps, uninstall any Synaptics pointing-device software from before the update. Restart, then reinstall the vendor package from Fix 4. The old app’s registry hooks and startup services commonly block the new driver’s gesture layer — producing the “cursor moves but gestures are dead” symptom. Remove-then-reinstall as a pair, never removal alone.

Fix 6: Repair the SMBus controller and check BIOS

In Device Manager, expand System devices and inspect the SMBus controller. A warning here means the touchpad’s bus is broken — update the chipset driver from your laptop maker’s site. The chipset driver rarely needs attention for touchpads, but when the SMBus controller itself shows a warning, nothing else you do will help until the bus is repaired — always check System devices before assuming the touchpad driver is at fault. Then restart into the BIOS (F2, Del, or your brand’s key) and confirm the Internal Pointing Device is Enabled. Some 24H2-era firmware updates disable it. Save and exit. A touchpad invisible to Device Manager after all driver work almost always traces to one of these two.

Fix 7: Power-drain the embedded controller

Shut down, unplug the charger, remove the battery if removable, and hold the power button for 30 seconds. Reconnect and boot. This resets the embedded controller bridging the touchpad’s SMBus to the CPU — the fix of last resort for touchpads that survive every driver repair. Test in the BIOS menus as well: a touchpad that works in BIOS but never in Windows despite the vendor driver suggests deeper Windows corruption (consider an in-place repair install). Dead in BIOS too means the touchpad hardware or cable needs service.

Closing

Synaptics touchpad death after 24H2 is a driver-binding problem: the wrong driver is installed, and the vendor’s Synaptics package is the right one. Toggle check, rollback, clean reinstall, vendor package — that order revives the large majority. Once it is back, guard the working driver against the next update’s enthusiasm for generic replacements, and remember the Fn-key toggle so a future accidental press does not send you down the driver path again.

Frequently asked questions

Why did the 24H2 update kill my Synaptics touchpad?
The 24H2 update commonly replaces the vendor’s Synaptics SMBus driver with a generic Microsoft PS/2 driver. Synaptics touchpads communicate over the SMBus interface, so the generic driver cannot talk to the hardware — the touchpad goes silent or vanishes from Device Manager. Reinstalling the manufacturer’s Synaptics package restores the correct driver binding.
How can I tell Synaptics and ELAN touchpads apart?
Check Device Manager under Human Interface Devices or Mice and other pointing devices. Synaptics hardware shows as Synaptics SMBus TouchPad or Synaptics Pointing Device; ELAN shows as ELAN Input Device. If yours is ELAN, use our ELAN-specific guide instead — the two brands need different drivers and the wrong package will not help.
The touchpad works but gestures don't — is that the same problem?
Related but milder. Basic movement with dead gestures usually means Windows installed a generic driver that handles movement but not the Synaptics gesture layer. Installing the vendor’s full Synaptics package — driver plus control panel software — restores two-finger scroll, pinch zoom, and multi-finger gestures.
Should I update the chipset driver for a touchpad problem?
It can help. The Synaptics touchpad rides on the SMBus, which is driven by the chipset driver. If the SMBus controller in Device Manager shows a warning, or the touchpad is missing entirely after driver fixes, updating the chipset driver from your laptop maker’s site repairs the bus the touchpad depends on.