A laptop keyboard that stops typing mid-sentence feels like a catastrophe, but the cause is rarely as dramatic as it seems. In most cases I see, the hardware is perfectly fine — a Windows update, a flipped accessibility setting, or a corrupted keyboard driver has simply cut the connection between the keys and the operating system. The good news is that software causes can be eliminated in about fifteen minutes, and even some hardware causes are fixable without a repair shop.
Work through this guide like a technician: start with the zero-effort checks, move to driver-level repairs, and only open the chassis if everything else points at a physical fault. Each step tells you something, so don’t skip ahead.
Why this happens
- Corrupted keyboard driver: The PS/2 or HID keyboard driver can fail after a Windows update, a failed driver install, or a power glitch during boot.
- Filter Keys silently enabled: Holding the right Shift key for eight seconds can turn on Filter Keys, which makes the keyboard ignore brief keystrokes and look dead.
- Fn lock or language layout change: Some keys may appear broken when the keyboard layout switched (for example, to a different language) or when Fn lock remaps the top row.
- Fast Startup holding a bad state: Windows Fast Startup saves driver states between boots, so a one-time driver failure can persist across restarts.
- Loose internal ribbon cable: The keyboard connects to the motherboard through a thin ribbon cable that can creep loose from heat cycles, drops, or past servicing.
- Liquid or debris under keys: Even a few drops of liquid can bridge traces on the keyboard membrane; crumbs can wedge keys physically down.
- BIOS-level hardware failure: A failed keyboard controller or damaged membrane won’t work even in BIOS setup, which rules out every software fix.
- USB power or hub conflicts: On some models, an overloading USB device or a docking station can interfere with the internal keyboard’s power rail during boot.
How to fix it
Work through these in order — diagnose first, then act.
Fix 1: Rule out the quick toggles
- Press and hold Shift for eight seconds. If you hear a beep or see a Filter Keys prompt, turn Filter Keys off in Settings → Accessibility → Keyboard.
- Check the taskbar language indicator (ENG or similar). If it changed, press Windows + Space to cycle back to your layout.
- Try Fn + Esc (or the dedicated Fn-lock key on your model) to release any stuck function lock.
- Test typing in Notepad. If some keys now work, the keyboard itself is alive and you have a settings problem.
Fix 2: Test with an external keyboard
- Plug in any USB keyboard and type for a minute.
- If the external keyboard works perfectly, your Windows input stack is healthy — the fault is isolated to the built-in keyboard’s driver or hardware.
- If neither keyboard works, suspect a Windows-level issue (Fix 4 and Fix 5) rather than the laptop keyboard itself.
- Keep the USB keyboard handy: you’ll need it to navigate while the built-in keyboard is down.
Fix 3: Restart the keyboard driver without rebooting
- Press Windows + X and open Device Manager.
- Expand Keyboards, right-click the built-in keyboard (usually “Standard PS/2 Keyboard” or “HID Keyboard Device”), and choose Uninstall device.
- Restart the laptop. Windows reinstalls a clean copy of the keyboard driver during boot.
- This single step resolves the largest share of post-update keyboard failures because it discards the corrupted driver state entirely. For related peripheral driver recovery, see our guide on fixing function keys .
Fix 4: Roll back a bad driver update
- In Device Manager → Keyboards, right-click the keyboard and open Properties → Driver.
- If Roll Back Driver is clickable, select it and choose a reason — this restores the previous working version.
- If the button is greyed out, the driver was replaced rather than updated; use Update driver → Browse my computer → Let me pick and choose an older listed version.
- Restart and test before letting Windows Update touch the driver again.
Fix 5: Disable Fast Startup to clear the stuck state
- Open Control Panel → Power Options → Choose what the power buttons do.
- Click Change settings that are currently unavailable and uncheck Turn on fast startup.
- Shut down fully (not restart), wait ten seconds, and power on.
- A true cold boot reloads every driver from scratch, which clears faults that Fast Startup’s hibernated state keeps alive.
Fix 6: Boot into BIOS to separate hardware from software
- Restart and press the BIOS key for your brand (F2, F10, Del, or Esc) during the logo screen.
- Try the arrow keys and Enter inside BIOS setup.
- If the keyboard works in BIOS but not in Windows, the hardware is fine — focus entirely on driver and OS fixes.
- If it fails in BIOS too, no Windows repair will help: skip to Fix 7 or plan for replacement.
Fix 7: Reseat the keyboard ribbon cable (advanced)
- Power off, unplug, and remove the battery if it is removable.
- Follow your model’s service manual to remove the bottom cover and locate the keyboard ribbon connector.
- Flip up the connector’s locking latch, slide the cable fully out, blow out any dust, reinsert it squarely, and lock the latch.
- Reassemble and test. This resolves keyboards that died after a drop or a previous repair, and it takes about twenty minutes with the right screwdriver. For a broader walkthrough of keyboard-side failures beyond the ribbon cable, see our keyboard troubleshooting guide .
Fix 8: Block Windows from reinstalling the bad driver
- After you have a working driver, open Settings → Windows Update → Advanced options → Optional updates and uncheck any keyboard driver offers.
- For persistent cases, use the Show or hide updates troubleshooter to hide the offending driver package.
- Microsoft documents current known input issues on the Windows support site , which is worth checking before each monthly update cycle.
Closing
Keyboard failures look frightening but surrender quickly to methodical diagnosis: external keyboard test, driver reinstall, rollback, cold boot, BIOS check, and only then the ribbon cable. Most keyboards come back at Fix 3 or Fix 4. If yours works in BIOS but not in Windows, you will win this fight — it’s just a matter of finding which driver state is stuck.
