The Synaptics touchpad is in millions of laptops, and when it dies the laptop becomes a two-handed paperweight — you’re reaching for a mouse just to open Settings. The failure has a familiar pattern: it often follows a Windows update, the touchpad vanishes from Settings, or the cursor moves but gestures and scrolling die.

Synaptics touchpads live at an awkward intersection: the hardware speaks Synaptics’ protocol, Windows increasingly wants Microsoft precision drivers, and laptop vendors ship their own customized versions. When those three disagree — which updates cause regularly — the touchpad loses. Here’s how to make them agree again.

The pattern is so consistent you can almost diagnose it from the calendar: touchpad dies within a day of Patch Tuesday, Device Manager shows a generic “HID-compliant mouse” where Synaptics used to be, and Settings loses the touchpad page. That’s the driver swap, and the fix is putting the vendor’s driver back and keeping it there.

Why this happens

  • Windows update replaced the driver: generic driver swapped in for the vendor Synaptics version.
  • Driver corruption: the Synaptics driver binding broke.
  • Touchpad disabled: Fn-key toggle or Windows setting turned it off.
  • Synaptics vs. precision mismatch: wrong driver model for the hardware.
  • BIOS touchpad setting: the touchpad disabled at firmware level.
  • Power management: USB power saving suspends the touchpad (USB-connected models).
  • Conflicting mouse software: third-party mouse utilities hijacking the device.
  • Hardware failure: the touchpad cable or unit itself died (least common).

How to fix it

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

Fix 1: Check the touchpad toggle keys

  1. Look for a touchpad icon on your function keys (often F5, F6, or F9) — press Fn + that key to toggle.
  2. Some laptops have a physical touchpad disable zone (double-tap the corner) — check for an indicator light.
  3. Go to Settings > Bluetooth & devices > Touchpad and ensure the touchpad is On.
  4. Uncheck “Leave touchpad on when a mouse is connected” temporarily during testing — this setting confuses diagnosis.
  5. This sounds trivial, but accidental Fn-key presses are a top cause — rule it out in ten seconds.

Fix 2: Verify in BIOS

  1. Restart and enter BIOS/UEFI setup.
  2. Look for a Touchpad or Internal Pointing Device setting — ensure it’s Enabled.
  3. Some BIOS versions offer “Advanced” vs “Basic” touchpad modes — try Advanced for full Synaptics functionality.
  4. If the touchpad works in BIOS menus, hardware is fine and this is purely a Windows driver issue.
  5. Save and boot to Windows.

Fix 3: Reinstall the Synaptics driver from the vendor

  1. Open Device Manager, expand Human Interface Devices and Mice and other pointing devices.
  2. Right-click the Synaptics device > Uninstall device, checking “Attempt to remove the driver.”
  3. Download the touchpad driver from your laptop manufacturer’s support page (not Synaptics’ generic site) — vendor customization matters.
  4. Install and reboot. Check Settings > Bluetooth & devices > Touchpad for the touchpad’s return.
  5. If the vendor only offers the driver via Windows Update, check Optional updates after the uninstall.
  6. If the vendor’s installer refuses (“no compatible hardware”), extract the driver files and install manually via Device Manager > Update driver > Browse my computer — installer version checks are stricter than the driver itself.

Fix 4: Stop Windows from replacing the driver

  1. After installing the working vendor driver, prevent Windows Update from “upgrading” it again.
  2. Use the Show or hide updates troubleshooter to hide the touchpad driver update, or set a group policy to exclude drivers from Windows Update.
  3. This breaks the frustrating cycle where every Patch Tuesday kills the touchpad again.
  4. Revisit this after major Windows feature updates, which can reset the policy.
  5. Microsoft’s Windows support pages document the update-hiding tool if you need the official steps.

Fix 5: Check power management

  1. In Device Manager, find the Synaptics device’s Power Management tab (under Human Interface Devices or USB).
  2. Uncheck “Allow the computer to turn off this device to save power.”
  3. In Power Options > Advanced, disable USB selective suspend — USB-connected touchpads are vulnerable to it.
  4. Test on charger vs. battery — touchpads that die only on battery are power-plan victims.
  5. Vendor power utilities (Lenovo Vantage, Dell Power Manager) may have their own touchpad power settings — check those too.

Fix 6: Remove conflicting software

  1. Uninstall third-party mouse/touchpad utilities (old Synaptics apps conflicting with new drivers, mouse gesture tools).
  2. Check Task Manager > Startup for touchpad-related entries fighting over the device — you want exactly one driver stack.
  3. If both a Synaptics app and Windows precision settings try to manage the pad, pick one: uninstall the Synaptics app or disable precision handling.
  4. Clean-boot (msconfig) to test whether a startup program is the culprit.
  5. Keyboard and touchpad failures often share causes — see laptop keyboard fixes if both died together.

Fix 7: Consider the precision-driver switch (carefully)

  1. Research your exact model on forums — some Synaptics hardware runs Microsoft precision drivers beautifully, others break.
  2. If confirmed working for your model: uninstall the Synaptics driver, then install the precision driver package (often via a community guide for your model).
  3. Back up first with a restore point — this is an experimental change.
  4. If gestures improve and stability holds for a week, keep it; if anything degrades, roll back to the vendor Synaptics driver.
  5. When in doubt, stay with the vendor driver — “working” beats “theoretically better” for a pointing device.

Closing

Synaptics touchpad failures are almost always driver politics: Windows Update swapping drivers, vendor customizations conflicting with generic ones, or the device simply toggled off. The BIOS test is your anchor — works in BIOS, fix in Windows; dead in BIOS, think hardware. Get the vendor’s driver installed, block Windows from replacing it, and the touchpad stays working. It’s a ten-minute fix once you know which driver your laptop actually wants. When the keyboard dies alongside the touchpad, laptop keyboard fixes cover the shared causes. Running Windows 11 specifically? Our Synaptics touchpad guide for Windows 11 covers the driver-model changes and precision-driver quirks unique to that OS.

Frequently asked questions

Why did my Synaptics touchpad stop working after a Windows update?
Windows updates frequently replace the vendor’s Synaptics driver with Microsoft’s generic precision driver or a mismatched version. The touchpad may vanish from settings or lose gestures. Reinstalling the Synaptics driver from your laptop manufacturer’s support page — the version built for your exact model — usually restores it immediately.
How do I know if my touchpad uses Synaptics or Microsoft precision drivers?
Check Device Manager under Human Interface Devices or Mice: ‘Synaptics’ in the name means vendor driver; ‘HID-compliant’ or ‘precision touchpad’ entries suggest Microsoft’s driver. Also check Settings > Bluetooth & devices > Touchpad — precision touchpads show Microsoft’s settings page, Synaptics ones often show a vendor tab or app.
Can I switch from Synaptics to precision touchpad drivers?
Sometimes, and many users prefer precision drivers for better gestures. But it’s model-dependent — some Synaptics hardware runs precision drivers fine, others lose features or break entirely. Only attempt it if your laptop community confirms it works for your exact model; otherwise stick with the vendor Synaptics driver.
Why does my touchpad work in BIOS but not Windows?
That proves the hardware is fine — BIOS uses basic PS/2 emulation that doesn’t need Windows drivers. The problem is purely the Windows driver stack: corrupt Synaptics driver, a Windows update replacement, or the device being disabled in Windows. Focus all effort on drivers, not hardware.