Touchpad failures have a peculiar trait: the fix is usually embarrassingly simple, but people skip the simple checks because “it was working yesterday” makes hardware failure feel more plausible than an accidental keypress. In reality, the ranking is clear — function-key disable first, Settings toggle second, driver problems third, hardware a distant fourth. This guide follows that ranking strictly, so the most likely fix is always the next thing you try.

Keep a USB mouse handy during this process. You’ll need it for the steps where the touchpad is the patient, not the tool.

Why this happens

  • Touchpad disable function key pressed. The top cause — accidental Fn-key toggle during typing.
  • Touchpad turned off in Settings. The software toggle, sometimes flipped by updates.
  • “Disable when mouse connected” stuck on. The auto-disable feature misfiring.
  • Driver replaced by Windows Update. Precision/Synaptics driver swap breaking the device.
  • Touchpad disabled in BIOS. Firmware-level disable hiding it from Windows.
  • Corrupted precision touchpad driver. Driver loads but the device doesn’t respond.
  • Failed touchpad hardware or ribbon cable. Rare — confirmed by elimination.

How to fix it

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

Fix 1: Press the touchpad toggle key

The fix behind most “suddenly stopped” reports.

  1. Look at your function keys for a touchpad icon (a rectangle with a finger, often F5/F7/F9) — press Fn + that key.
  2. Some laptops toggle with the key alone (no Fn) — try both.
  3. Watch for an on-screen notification confirming “Touchpad on/off.”
  4. Test the touchpad immediately after each press — the toggle is instant.
  5. If you keep hitting it accidentally, most vendor apps let you disable the Fn-key toggle or require Fn-lock.

Fix 2: Enable the touchpad in Settings

The software master switch.

  1. Settings > Bluetooth & devices > Touchpad — ensure the Touchpad toggle is On.
  2. Enable “Leave touchpad on when a mouse is connected” — this defeats the auto-disable feature that misfires.
  3. Unplug any USB mouse temporarily and test — if the touchpad works with the mouse unplugged, auto-disable was the culprit.
  4. Check the touchpad cursor speed slider isn’t at zero — a zeroed speed looks like a dead touchpad.
  5. Scroll down to “Reset touchpad settings” and reset to defaults — corrupted gesture configs can freeze response.

Fix 3: Reinstall the touchpad driver

The core fix for driver-level failures.

  1. Device Manager > Human Interface Devices (or Mice and other pointing devices) → find the touchpad entry (I2C HID Device, Synaptics, ELAN).
  2. Right-click → Uninstall device → check “delete the driver software” → restart.
  3. Windows reinstalls a baseline driver — test before installing anything else.
  4. Download the touchpad driver from your laptop maker’s support page (Dell , Lenovo ) and install it — this is critical for Synaptics/ELAN models where Windows’ generic driver lacks features.
  5. If the touchpad broke after a Windows update, use Roll Back Driver instead.

For Synaptics-specific deep repair, see how to fix the Synaptics touchpad not working . The general driver method is how to update drivers on a Windows 11 laptop .

Fix 4: Fix precision touchpad driver conflicts

For gesture loss and “not a precision touchpad” issues.

  1. In Device Manager, check whether the touchpad shows as I2C HID Device with warnings — a failed precision driver load.
  2. Some laptops need the Intel Serial IO driver (I2C controller) working before the touchpad functions — update the chipset driver from the maker’s site.
  3. If Windows Update installed a Synaptics driver over your precision setup (or vice versa), uninstall it and install the manufacturer-specified driver.
  4. Settings > Bluetooth & devices > Touchpad should show “Your PC has a precision touchpad” — if that line is missing, the wrong driver is loaded.
  5. After driver changes, cold-boot (Shift + Shut down, then power on) — touchpad controllers sometimes need the full power cycle.

Fix 5: Check BIOS and power states

Firmware-level and power-related disables.

  1. Enter BIOS/UEFI → look for Touchpad or Internal Pointing Device → ensure Enabled.
  2. Test the touchpad in the BIOS menus if the BIOS supports mouse input — response in BIOS means Windows-side (driver/settings).
  3. Disable fast startup (Power Options → Choose what the power buttons do) — it preserves broken device power states.
  4. Perform a full power drain (shutdown, unplug, hold power 30 seconds) — resets the embedded controller that manages the touchpad.
  5. Check your vendor app (Vantage, MyASUS) for touchpad settings that might override Windows.

Fix 6: Rule out software conflicts

Third-party interference with the input stack.

  1. Uninstall or disable third-party mouse/touchpad utilities — they hook the input stack and can freeze the touchpad.
  2. Boot into Safe Mode and test — a working touchpad in Safe Mode means a third-party driver or startup app is the culprit.
  3. Check Task Manager > Startup for input-related apps and disable suspects one at a time.
  4. Terminal (Admin): DISM /Online /Cleanup-Image /RestoreHealth then sfc /scannow — repairs the input framework.
  5. Create a fresh Windows user profile and test — corrupted per-user input settings are rare but real.

Fix 7: Verify the hardware

The final verdict.

  1. If the touchpad is dead in BIOS too (where supported) and after a power drain, suspect hardware.
  2. Physical symptoms — clicks not registering, cursor jumping, dead zones — can indicate a swollen battery pressing on the touchpad from below. Check whether the trackpad area bulges or the clicks feel stiff; a swelling battery is a safety issue — stop using the laptop and get it serviced.
  3. On out-of-warranty machines, the touchpad ribbon cable can be reseated — it requires removing the bottom panel and battery connector first.
  4. Replacement touchpads are model-specific but inexpensive; the repair is moderate difficulty.
  5. A USB mouse is a fine permanent workaround — and honestly, many people prefer it.

Closing

Touchpad repair is ranked by probability, not by drama: the function-key toggle, the Settings switch, the mouse-connected auto-disable, then the driver. The swollen-battery check in Fix 7 deserves emphasis — a touchpad that gradually stops clicking is a classic early warning of battery swelling, and that’s a safety matter, not a driver matter. Work the ranked sequence, keep a USB mouse nearby, and you’ll have the cursor moving again in minutes rather than hours.

Frequently asked questions

Why did my touchpad suddenly stop working?
The most common cause is accidentally pressing the touchpad disable function key (often Fn+F5/F7/F9 with a touchpad icon) — it happens constantly during normal typing. The next most common causes are Windows Update replacing the precision touchpad driver and the touchpad being disabled in Settings. Check the function key and Settings toggle before any driver work.
How do I know if my touchpad is disabled or broken?
Open Settings, Bluetooth and devices, Touchpad — if the page shows the touchpad as off, it’s disabled (toggle it on). If Device Manager shows the touchpad with a warning or as missing, it’s a driver problem. If the touchpad is enabled, the driver is clean, and there’s still no response at all — including in BIOS — it’s hardware.
What is the difference between precision and Synaptics touchpad drivers?
Precision touchpad drivers use Microsoft’s standardized driver model with gestures handled by Windows; Synaptics/ELAN drivers use the vendor’s own software. Many laptops can run either, and Windows Update sometimes swaps one for the other, breaking gestures. The manufacturer’s support page specifies which driver your model should use — install that one.
Can an external mouse disable the touchpad?
Yes — many laptops have a setting that disables the touchpad when a USB mouse is connected, and it sometimes gets stuck on. Check Settings, Bluetooth and devices, Touchpad for an option like ‘Leave touchpad on when a mouse is connected’ and enable it. Unplugging the mouse temporarily also tests whether this is the cause.