Touchpad Not Working on Your Laptop? Step-by-Step Fix
A touchpad that suddenly stops responding is far more often switched off than broken. The usual culprits, in order: an accidental Fn-key toggle, an external mouse that auto-disabled the pad, a driver a Windows update swapped, and only rarely a loose ribbon cable or dead module. This guide works them from most to least likely — with the exact combos and menu paths, and the one test that tells you in seconds whether it's software or hardware.
Start here: did you bump the Fn-key toggle?
The most common reason a touchpad "dies" is that a function-key shortcut switched it off — easy to hit by accident, and a ten-second fix. Hold Fn and press the F-row key marked with a smalltouchpad-with-a-slash icon.
There is no universal combo — it's brand- and even model-specific:
| Brand | Common combo(s) | Notes |
|---|---|---|
| Lenovo (ThinkPad / IdeaPad) | Fn+F6, Fn+F8, Fn+F9, Fn+F10 | Newer ThinkPads reshuffled F9–F11; if FnLock is on, press Fn+Esc first. |
| HP | Fn+F6 or Fn+F9 | Some business models have a tap-icon in the pad's top-left corner — double-tap it to toggle. |
| Dell | Fn+F6 or Fn+F9 | Varies by model; Dell's own touchpad KB is the best living reference. |
| ASUS | Fn+F9 (some newer: Fn+F6) | — |
| Acer | Fn+F2, F6, F7, or F10 | The widest variation of any brand. |
Don't know the icon? Hold Fn and press F5 through F12 one at a time, watching the cursor — one of them is the toggle.
Before you reinstall anything, confirm what's actually failing — run theTouchpad Test. Move a finger across the surface, then tap. If the trail draws even a little, or a tap counter climbs, your touchpad hardware is alive and you're looking at a setting or a driver, not a repair. A pad that stays completely dead here even after the software steps below is the real signal it's hardware.
Did you just plug in a mouse? Check the Windows 11 settings
Windows 11 can turn the built-in pad off automatically whenever a mouse is present. OpenSettings (Win+I) → Bluetooth & devices → Touchpad. Two controls matter:
- The master Touchpad switch at the top — make sure it's on.
- "Leave touchpad on when a mouse is connected", directly under it — if this is unchecked, plugging in any mouse (wired, Bluetooth, or a dongle) silently kills the pad. Check it to keep both working.
The setting is backed by the registry value LeaveOnWithMouse underHKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\PrecisionTouchPad (1 = on), if you ever need to flip it without the UI. On a 2-in-1, also check that Windows hasn't misread the hinge and dropped into tablet posture, which disables the pad by design.
Reinstall or roll back the touchpad driver
Pad enabled, mouse coexistence on, still dead? The driver is next. In Device Manager, find the touchpad — it appears as Synaptics, ELAN, anHID-compliant touchpad, an I2C HID Device, or a branded entry.
- Reinstall: right-click the entry → Uninstall device → restart, and Windows re-detects it on boot. Tick "delete the driver software" only if you suspect corruption, not a stuck driver.
- Roll back a bad update: right-click →
Properties → Driver → Roll Back Driver— available only if a prior version is cached, usually a 10-day window after the update landed.
What won't work: forcing a Synaptics driver onto ELAN hardware, or the reverse — different controllers, so the wrong package installs but misbehaves. When in doubt, pull the branded OEM driverfrom your maker's support site by exact model number; it carries the palm-rejection tuning (PalmCheck, SmartSense, ELAN palm tracking) the generic Microsoft Precision driver lacks.
Touchpad broke right after a Windows update?
Windows Update's optional-driver channel occasionally pushes an OEM driver that wasn't tested against every firmware revision, quietly replacing a working one. The clearest case: the 2025-06 preview updateKB5060829, reported by many users to stop touchpads entirely — and a driver reinstall alone didn't always bring them back.
The fix is to remove the update, not just the driver:
Settings → Windows Update → Update history → Uninstall updates.- Remove the most recent cumulative or driver update, then restart and test.
- If that revives the pad,
Settings → Windows Update → Pause updatesfor a few days until the OEM ships a corrected driver, then update again.
Worth knowing: Microsoft never published a formal known-issue notice for KB5060829, so treat it as widely user-reported — but the rollback path is the standard fix whichever update broke your pad.
"I2C HID Device" with Code 10: the fix ladder
A distinct, very common failure — heavily reported on Lenovo, HP, Dell, and Framework machines — is theI2C HID Device showing "This device cannot start (Code 10)" in Device Manager: the bus-level handshake to the pad failed. Work the ladder from least to most invasive; most people are fixed by step 2:
- Device Manager → Human Interface Devices → right-click I2C HID Device → Disable, wait, Enable.
- Same device →
Properties → Power Management→ uncheck "Allow the computer to turn off this device to save power." Selective-suspend cutting the bus mid-session is a known root cause, and this alone fixes a real share of cases. - Right-click → Update driver → Search automatically, or Roll Back Driver if a prior version exists.
- Uninstall the I2C HID Device and its related HID-compliant device(s) with "delete the driver software" ticked (look under Ergonomic Input Devices and System Devices too), then reboot to force a clean re-enumeration.
- Apply the OEM's full BIOS/firmware update — I2C controller firmware bugs are a separate cause from the OS driver.
- Last resort before a repair: hold the power button 30–60 seconds with AC unplugged (pull the battery on removable-battery models). Several Framework users reported this alone cleared it — a firmware handshake glitch, not a Windows fault.
Check the BIOS: is the pointing device even enabled?
Rarely — usually after a BIOS reset or update, or on a corporate-imaged machine — the pad is disabled in firmware. Reboot and tap the BIOS-entry key (commonly Esc, F2, F10, or Del), then look underAdvanced for "Internal Pointing Device" (it may sit under "System Properties," "Keyboard/Mouse Features," or "Device Options") and set it to Enabled.
Some BIOSes also expose a Basic vs Advanced touchpad mode — a handy diagnostic: if the cursor moves in the BIOS screen but not in Windows, the hardware is fine and the fault is entirely software.
When it's actually hardware: ribbon cable and battery swelling
If the pad is dead even in the BIOS setup screen, drivers are ruled out and it's physical. Two causes dominate:
- A loose ribbon (FPC) cable. The pad connects to the board by a flat cable under the palm rest. A drop, repeated flexing, or a recent RAM/SSD/battery swap can partly dislodge it — the tell is intermittent response, not a fully dead pad.
- A swollen battery. A puffed-up cell sits right under the palm-rest deck and can press the pad up from below, jamming the clickpad or crushing the ribbon connector. That's a safety issue, not just a fault: stop using the machine, don't press on the deck, power it down, and get it serviced — swollen lithium cells are a fire and chemical-burn risk.
Other hardware tells: response that changes when you flex near the palm rest, a visibly bulging deck, or a pad that quit the instant after a drop or a case opening.
On a Mac? The trackpad path and the SMC myth
macOS trackpad controls live at Apple menu → System Settings → Trackpad (Tap to Click and friends under Point & Click), consistent across Sequoia and Tahoe. If you're on an external mouse and the built-in pad interferes, useSystem Settings → Accessibility → Pointer Control → "Ignore built-in trackpad when mouse or wireless trackpad is present."
Here's the honest part: an SMC reset does nothing on any Apple Silicon Mac (M1 through the current M-series) — those chips have no separate SMC to reset. The genuine equivalent is a full shutdown (not restart), a 30-second wait, then power on; the low-level controller state resets as part of a cold boot. The old Cmd+Option+P+R and SMC key combos are Intel-only, and running them on an M-series Mac is copy-pasted cargo cult. The real soft reset there is returning trackpad settings to default.
What doesn't fix a dead touchpad
- Reinstalling Windows. A touchpad fault is almost always a driver, firmware, or setting, and a full reinstall doesn't touch BIOS-level or hardware causes anyway — a last-resort myth from "fix everything" listicles, not something Dell, HP, or Microsoft recommend here.
- An SMC reset on Apple Silicon. A no-op, as above — people are unknowingly describing the cold-boot effect.
- Compressed air, always. It helps when the cause is grit under the clickpad edge, but does nothing for driver, firmware, or electrical faults — and blasting an already-opened laptop can drive debris further in.
- Hunting for one universal Fn combo. There isn't one — it's brand- and model-specific, and some laptops have no touchpad key at all, only the Windows setting.
Repair vs replace: what it costs
If the test and the BIOS both show a truly dead pad, price the repair before deciding. A standalone touchpad part is roughly $15–$40. On ultrabooks where the pad is integrated into the keyboard/palm-rest top case, the part jumps to $40–$200. Labor adds about$75 and 45 minutes, so an independent shop repair usually runs$100–$250 all-in — more at an authorized center, and more again if a swollen battery needs replacing and safe disposal. On an older, out-of-warranty machine, a $20 USB mouse is often the rational stopgap while you weigh the repair.
Frequently asked questions
Why is my laptop touchpad not working suddenly?
A pad that dies out of nowhere was almost always switched off, not broken. The top three sudden causes are an accidental Fn-key toggle, plugging in an external mouse (which can auto-disable the built-in pad), and a driver that a Windows update silently swapped. Run the touchpad test first — if a single tap or twitch registers, the hardware is fine and you are chasing a setting.
How do I turn my touchpad back on with the keyboard?
Hold Fn and press the F-row key with a small touchpad-with-a-slash icon. There is no universal combo — commonly Fn+F6 or Fn+F9, but Acer alone ranges across F2, F6, F7, and F10. Can't spot the icon? Hold Fn and try F5 through F12 one at a time while watching the cursor. If FnLock is on, press Fn+Esc first.
Why does my touchpad work in BIOS but not in Windows?
The BIOS setup screen uses its own minimal driver, so if the pad moves the cursor there but dies once Windows loads, the hardware is proven good and the problem is entirely software — a driver, a Windows setting, or a bad update. That single test rules out the touchpad module, the ribbon cable, and the controller in one move, so skip the hardware section and work the driver and settings steps.
How do I fix a touchpad that stopped working after a Windows update?
Go to Settings → Windows Update → Update history → Uninstall updates, remove the most recent cumulative or driver update, and restart. The 2025-06 preview update KB5060829 was widely reported to kill touchpads outright, and a driver reinstall alone did not always fix it — rolling the update back did. Then pause updates for a few days until the corrected driver ships.
How much does it cost to fix a laptop touchpad?
A standalone touchpad part runs about $15–$40. On many ultrabooks the pad is fused into the keyboard/palm-rest top case, pushing the part to roughly $40–$200. Add around $75 and 45 minutes of labor, so an independent shop repair typically lands at $100–$250 all-in — more at an authorized service center, and more again if a swollen battery needs safe replacement and disposal.