Your touchpad tracks smoothly in the BIOS, then dies the second Windows finishes loading. If you just searched "How to Fix Touchpad Works In Bios But Not Windows on a Gaming Laptop", the good news lands early: the hardware isn't broken. Windows simply lost its handshake with the device somewhere between the firmware and the desktop.
Most gaming laptops wire the touchpad as a HID over I2C device, identified in ACPI as PNP0C50. That one detail explains the whole split, because the BIOS reads the device directly while Windows needs a driver chain to reach it. As of 2026 that's still the standard on nearly every Intel and AMD gaming chassis.
Here's how those layers stack up, and where to look first.
How to Fix Touchpad Works In Bios But Not Windows on a Gaming Laptop
Start by pressing the Fn touchpad lock key on your keyboard. Then open Device Manager and look for a touchpad entry. Reinstall the chipset and I2C controller drivers next.
Remove any flagged device, reboot, and rescan for hardware changes. Finish with the OEM touchpad driver from your laptop maker's support page.
Why Your Touchpad Works in BIOS but Dies in Windows
The BIOS doesn't need a driver. It talks to the touchpad controller directly and moves the pointer itself.
Windows can't do that. It has to build a stack first, and that stack has four links.
- ACPI spots the device and hands Windows a hardware ID.
- The I2C host controller driver comes online, either Intel Serial IO or the AMD equivalent.
- The HID class driver claims the device.
- A precision or vendor driver layers on top and translates gestures.
Snap any one of those and the cursor stops. The touchpad never knew anything changed, which is exactly why it still works in the firmware.
Our research into driver-failure reports keeps landing on the same conclusion. Something in the chain got replaced, disabled, or never installed in the first place.
It's the same story as an update overwriting the correct driver on the GPU side, just pointed at an input device instead.
If your keyboard is acting up too, that points at the same ACPI layer. Our guide to keys that stop responding covers the overlap.
The Two-Minute BIOS Test That Splits Every Case in Half
Before you touch a single driver, run this test. It costs two minutes and tells you whether you're fixing software or hardware.
Restart the laptop. Tap F2, or Delete on some MSI and Alienware units, to enter the BIOS. Once the setup screen loads, try moving the cursor with the touchpad.

Image source: Openverse / electricderosa (PDM 1.0)
What working in BIOS actually proves
If the pointer moves, the sensor, ribbon cable, and controller are all fine. Your problem lives in Windows. That's the good branch.
If the pointer is dead in the BIOS too, stop here. This isn't a driver issue at all. Suspect the ribbon cable or a failed module, and check your warranty terms before opening the chassis.
The Fn-key lock and the Internal Pointing Device setting
Some gaming laptops ship with touchpad support switched off in firmware. Look for "Internal Pointing Device" under Advanced or Main and set it to Enabled. ASUS boards tend to use that exact label.
Then try the Fn lock. ASUS is usually Fn+F10, Lenovo Fn+F8, MSI Fn+F9. Labels shift between generations, so read the silkscreen on your function row.
One stray tap and you'll spend an hour reinstalling drivers for nothing.
Finish with an EC reset. Unplug the charger, hold the power button for 30 seconds, then plug back in. A stuck embedded controller state can mute the touchpad in Windows only.
Branch One: Device Manager Doesn't List the Touchpad at All
No touchpad entry, no unknown device, nothing. Windows never saw the hardware. This is an enumeration failure, and it's the most common version of the problem.
Press Windows+X, open Device Manager, then hit View and Show hidden devices. Check Human Interface Devices and Mice and other pointing devices.
Missing Intel Serial IO or AMD I2C controller driver
Here's the part most people miss. A HID over I2C touchpad stays invisible until the I2C host controller has a working driver. No controller driver means no bus, and no bus means no touchpad.
Microsoft's HID over I2C driver documentation lays out how the transport stack loads, and the controller has to be ready first.
So install in this order:
- Chipset driver, straight from Intel or AMD.
- Serial IO or I2C controller driver, from your laptop maker.
- Touchpad driver, from that same support page.
Use the page for your exact model number, never a generic bundle. A clean Windows install with the wrong chipset driver produces this same blank Device Manager.
Show hidden devices and the HID-over-I2C enumeration check
Still nothing after that? Look at the I2C controller itself for a yellow mark. If the controller is flagged, the touchpad will never show up, no matter what you install.
And if this started after a Windows 11 update, assume the upgrade dropped the OEM driver. Reinstalling it usually closes the case.
Branch Two: The Touchpad Shows a Yellow Triangle or Error Code
A listed device with a warning means Windows found the hardware but can't start it. The code tells you which repair to run.
| Code | What it usually means | First move |
|---|---|---|
| 10 | Device failed to start | Reinstall the touchpad driver |
| 28 | No driver installed | Install the OEM driver |
| 39 | Corrupt driver registry entry | Clear stray filter values |
| 43 | Device reported a failure | Power drain, then reinstall |
| 45 | Device not connected | Reseat ribbon, or RMA |
Decoding Code 10, 28, 39, and 43
Code 28 is the easy one. Windows spotted the touchpad and has nothing to drive it with. Install the OEM package and you're done.
Code 39 usually means a leftover filter driver from an app you uninstalled badly. Check the HID class in the registry, delete stray UpperFilters and LowerFilters values, then reboot. Export the key first as a backup.
Code 10 and Code 43 often clear with the same 30-second EC reset from earlier. If they don't, the driver copy itself is damaged.
Uninstall, delete the driver, reboot, rescan
Work through these steps in order:
- Right-click the touchpad and choose Uninstall device.
- Tick Delete the driver software for this device.
- Shut down fully. Don't use restart.
- Boot up, then open Device Manager and pick Action, Scan for hardware changes.
- Install the OEM driver last.
This is the standard fix when an update swaps out the right driver for a generic one. Removing the bad copy is what forces Windows to accept the correct one.
Branch Three: It's Listed and Healthy but the Cursor Won't Move
Status reads "This device is working properly", there are no warnings, and the pointer still refuses to budge. Annoying, but this branch has the shortest fix list.
Open Settings, then Bluetooth and devices, then Touchpad. If that page exists, your driver is loaded and the toggle is live. If the page is missing, you're actually back in Branch One.
Next, check "Leave touchpad on when a mouse is connected". It's buried, some OEM images enable it by default, and it kills the touchpad the moment you plug in a mouse.
Vendor control centers overriding Windows settings
Armoury Crate, MSI Center, Lenovo Vantage, Razer Synapse, and PredatorSense all ship their own touchpad controls. They write over the Windows settings, so the two panels can flatly disagree.
Open your vendor app, set the touchpad to enabled there, then close it and leave it alone. Aggregate support threads suggest this resolves a surprising share of healthy-but-dead reports.
Fast Startup, clean boot, and Safe Mode as tiebreakers
Fast Startup isn't a real shutdown. It saves a hibernation image of the kernel, so a broken touchpad state survives every restart you attempt. Switch it off in Control Panel, then Power Options, then Choose what the power buttons do.
Do a full shutdown after that, not a restart. If your laptop also restarts instead of waking, the same setting is usually behind both.
Still stuck? Run a clean boot through msconfig. If the touchpad returns, a startup service is blocking it.
Working in Safe Mode but not normally points to the same answer.
As a last software step, run sfc /scannow, then DISM with the RestoreHealth flag. If neither helps, a System Restore point from before the failure will.
Mistakes That Send People Shopping for a New Touchpad
Most wasted money on this problem traces back to skipping the BIOS check. Ten minutes of free testing beats a $40 replacement part.
A few other traps show up constantly in support threads:
- Ordering a module first. If the pointer moves in firmware, the sensor and ribbon are fine. Don't buy hardware for a driver fault.
- Letting Windows Update pick the driver. Generic HID drivers load without complaint, then quietly drop Precision gestures like three-finger swipe.
- Installing the touchpad driver before the chipset driver. HID over I2C stays dark until Intel Serial IO or the AMD I2C controller is running.
- Flashing BIOS on a whim. Only do it when the release notes name your exact fix.
- Grabbing files from "driver pack" sites. Use your maker's own page. ASUS's support site, for instance, hosts per-model packages with matching BIOS and EC versions.
- Opening the chassis too early. That can void coverage on a laptop still under warranty.
One warning worth repeating: back up your BitLocker recovery key before touching BIOS, Secure Boot, or TPM settings. A firmware change can trip the TPM and lock you out of your own drive. Pull the key from account.microsoft.com/devices/recoverykey while you can still log in.
Quick Decision Guide: Match Your Symptom to the Fix
Work down the table and start at the top. The order matters, because the cheapest checks clear most cases.
| What you see | Likely cause | Time | Your move |
|---|---|---|---|
| Dead in Windows, alive in BIOS | Software or enumeration fault | 2 min | Fn lock check, then EC reset |
| Absent from Device Manager | I2C controller or HID stack missing | 15 min | Chipset, then Serial IO, then touchpad driver |
| Yellow triangle, Code 10 or 43 | Failed or corrupt driver | 10 min | Uninstall, delete driver, full shutdown, rescan |
| Code 28 | No driver installed at all | 5 min | OEM driver for your exact model |
| Healthy device, no cursor | Settings or vendor utility override | 5 min | Windows touchpad page, then Armoury Crate or MSI Center |
| Bad state survives every restart | Fast Startup caching it | 5 min | Disable Fast Startup, then full shutdown |
| Works in Safe Mode only | Startup service blocking it | 15 min | Clean boot through msconfig |
| Dead in BIOS and Windows | Real hardware fault | Varies | Ribbon cable check, then RMA |
Know when to stop. Once System Restore and an in-place repair install both fail, you've exhausted the software side. At that point a warranty claim is the sensible move, not another weekend of driver hunting.
Frequently Asked Questions
Does the touchpad working in BIOS mean it isn't broken?
Yes, in nearly every case. The firmware talks to the controller directly with no driver involved. If the pointer moves there, the sensor, ribbon cable, and controller are all passing.
Whatever's wrong lives in Windows.
Will a Windows reset fix a touchpad that vanished after an update?
Usually yes, but it's overkill. A reset wipes your apps and eats an hour or more. Reinstalling the OEM touchpad and I2C controller drivers fixes the same fault in roughly ten minutes.
Keep the reset as your fallback.
Why did my touchpad stop working after a BIOS update?
A BIOS or embedded controller update can reset ACPI settings and ship a new touchpad firmware version. Windows then holds a driver that no longer matches. Re-enter the BIOS, confirm Internal Pointing Device is set to Enabled, then reinstall the touchpad driver from your model's support page.
Can I use a Linux live USB to confirm it's a Windows problem?
Yes, and it's a clean test. Boot Ubuntu from a USB stick without installing anything. Modern kernels support HID over I2C natively, so no setup is needed.
If the touchpad works there but not in Windows, you've confirmed a driver or settings fault.