Synaptics touchpads are in millions of Windows laptops, and their driver stack is one of the most update-sensitive in the machine. One Windows Update can swap the working Synaptics driver for a generic fallback — leaving you with a dead touchpad, or a touchpad that moves but has lost every gesture.

The failure modes map cleanly to fixes: no movement at all is usually the toggle, the bus driver, or a missing device; movement without gestures is the wrong driver; intermittent freezing is power management or the bus. The steps below are ordered to match that diagnosis.

Why this happens

  • Windows Update replaced the Synaptics driver with a generic or mismatched version.
  • Touchpad toggle (Fn key) accidentally disabled the device.
  • SMBus/I2C bus driver corrupted, so the touchpad’s interface cannot start.
  • Touchpad disabled in Windows Settings or in the BIOS.
  • Power management suspending the touchpad and failing to wake it.
  • Synaptics app/service not running, killing gestures and advanced features.
  • Loose ribbon cable or failed touchpad, typically after drops or battery swelling.

How to fix it

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

Fix 1: Check the toggle and Windows Settings

Press the touchpad Fn key (varies by brand — look for the touchpad icon on the function row) and check Settings > Bluetooth & devices > Touchpad to confirm the master switch is on. Also enable ‘Leave touchpad on when a mouse is connected’. These instant checks resolve the embarrassing cases before any driver work begins.

  1. Press the touchpad Fn toggle key once and test.
  2. Open Settings > Bluetooth & devices > Touchpad and enable it.
  3. Tick ‘Leave touchpad on when a mouse is connected’.
  4. Test movement and two-finger scroll.

Fix 2: Install the Synaptics driver from the laptop maker

Download the touchpad driver from the laptop maker’s support page for your exact model — this is the single highest-yield fix. Uninstall the current touchpad/Synaptics entries in Device Manager first, deleting the driver software. Install the maker’s package and reboot. For ASUS models on this stack, the ASUS Synaptics guide has brand-specific notes.

  1. Download the Synaptics/touchpad driver from the laptop maker.
  2. In Device Manager, uninstall touchpad and Synaptics entries, deleting drivers.
  3. Install the downloaded package and reboot.
  4. Verify movement, scroll, and gestures.

Fix 3: Fix the SMBus/I2C bus driver

Modern Synaptics pads ride the SMBus or I2C bus, and a flagged ‘Synaptics SMBus Driver’ or ‘I2C HID Device’ in Device Manager means the bus failed, not the pad. Uninstall the flagged bus device (deleting its driver), then scan for hardware changes. Reinstall the chipset driver from the laptop maker too, since the bus controller lives in the chipset. Microsoft’s driver guidance is in the Windows support hub .

  1. Find the flagged SMBus or I2C device in Device Manager.
  2. Uninstall it, deleting the driver software.
  3. Scan for hardware changes.
  4. Install the latest chipset driver from the laptop maker and reboot.

Fix 4: Disable power management on the touchpad

When the touchpad works after boot but dies after sleep, power management is the culprit. In Device Manager, open the touchpad’s Properties > Power Management and untick ‘Allow the computer to turn off this device’. Also set the USB selective suspend and PCI Express link-state power management to off or moderate in the power plan if the pad is USB-attached.

  1. Open the touchpad’s Properties > Power Management in Device Manager.
  2. Untick ‘Allow the computer to turn off this device to save power’.
  3. Test across a sleep/wake cycle.
  4. If fixed, leave the setting off permanently.

Fix 5: Restore the Synaptics control panel and gestures

If the cursor moves but gestures are dead, the Synaptics app layer is missing. After installing the maker’s driver, open Settings > Bluetooth & devices > Touchpad and configure gestures there (Windows 11 handles gestures natively for precision setups). For legacy Synaptics control panels, check the system tray or the app’s own settings for accidentally disabled gestures.

  1. Confirm the maker’s Synaptics driver is installed (not generic).
  2. Configure gestures in Settings > Bluetooth & devices > Touchpad.
  3. Check the Synaptics system-tray app for disabled features.
  4. Test two-finger scroll, pinch, and three-finger gestures.

Fix 6: Check the BIOS touchpad setting

Reboot into the BIOS and verify the internal pointing device is enabled. Some BIOS versions offer PS/2 versus I2C/SMBus mode for the touchpad — match it to what the driver expects (I2C/SMBus/Advanced for modern drivers). A wrong mode here produces exactly the ‘device with warning’ symptom in Windows. The Windows 11 Synaptics walkthrough covers mode-matching in more detail.

  1. Enter the BIOS setup on boot.
  2. Enable the internal pointing device.
  3. Set the touchpad mode to Advanced/I2C/SMBus if offered.
  4. Save, boot, and reinstall the driver if needed.

Fix 7: Test for hardware failure

If the touchpad is absent from Device Manager even with hidden devices shown, and the BIOS shows no pointing device, suspect the ribbon cable or the pad. A swollen battery under the palm rest kills touchpads mechanically — check for a raised palm rest. Otherwise, touchpad modules are inexpensive but model-specific; a repair shop can replace one quickly.

  1. Show hidden devices in Device Manager and search for the pad.
  2. Check for a swollen battery lifting the palm rest.
  3. Boot a Linux live USB — no pad there means hardware.
  4. Replace the module or cable, or get a repair quote.

Closing

Synaptics touchpad failures are driver-bus problems in disguise: the pad is usually fine, but the Synaptics driver, the SMBus/I2C bus beneath it, or the Fn toggle is not. The laptop maker’s driver package for your exact model is the fix that matters most — generic drivers give you a cursor without gestures, or nothing at all. Match the driver to the model and the bus, and the touchpad comes back. When Windows Update is the repeat offender, consider pausing driver updates after a good install, and keep the maker’s driver installer somewhere safe — touchpad drivers are small, and having the known-good version on hand turns the next update mishap into a five-minute reinstall instead of another afternoon of troubleshooting.

Frequently asked questions

Why does my Synaptics touchpad vanish after Windows updates?
Windows Update routinely replaces the vendor’s Synaptics driver with a generic Microsoft driver — or a mismatched Synaptics version — that cannot drive the touchpad’s SMBus or I2C interface. The touchpad then disappears from Device Manager or appears with a warning. Reinstalling the Synaptics driver from the laptop maker restores it.
Should I install the driver from Synaptics or my laptop maker?
From the laptop maker, always. Synaptics provides chip drivers, but the laptop maker customizes them for the exact touchpad firmware, bus (PS/2, SMBus, or I2C), and hotkey integration. The maker’s package is the one validated for your machine; Synaptics’ generic package is a fallback when the maker abandoned the model.
What is the difference between PS/2, SMBus, and I2C touchpads?
They are the buses the touchpad uses to talk to the system. Older Synaptics pads use PS/2, most modern ones use SMBus or I2C. The bus matters because the driver must match: an I2C touchpad with a PS/2-mode driver will not start. The BIOS sometimes lets you switch modes, which is why a BIOS check is part of the fix.
Why do gestures stop working but basic movement still works?
Basic movement can run on a fallback PS/2-compatible driver while multi-finger gestures need the full Synaptics driver with its gesture engine. When an update swaps in the fallback driver, you get a dumb cursor with no scroll or gestures. Installing the full Synaptics package from the laptop maker restores the gesture engine.