Laptop Keyboard Stopped Working After a Windows Update
The timing makes this feel like Microsoft broke your laptop, and occasionally that is close to true — but not in the way it seems. Updates do not damage keyboard hardware. What they do is replace drivers, reset power settings, and reboot in a way that can leave the keyboard controller in a state it will not come out of on its own.
Nearly all of these cases are recoverable in ten minutes, and most are fixed by the first step.
Before anything: how to type while the keyboard is dead
You will need input to fix this, so set it up first.
The On-Screen Keyboard is the quickest route. From the sign-in screen, the accessibility icon in the bottom-right corner opens it. Once logged in, Win + Ctrl + O normally does it, but obviously that requires a keyboard — so instead click Start, then Settings, then Accessibility, then Keyboard, and switch on the on-screen keyboard.
A USB keyboard plugged in works too, and if you have one it is easier. It also gives you useful diagnostic information: if the external keyboard works fine, the problem is specific to the built-in one, which rules out a whole category of system-wide causes.
1. Full shutdown, not a restart
This fixes more of these cases than everything else combined, and it takes two minutes.
Windows has a feature called Fast Startup that does not truly shut the machine down — it hibernates the kernel and restores it on boot. That means a "shutdown and power on" often does not reinitialise hardware at all, and a keyboard controller stuck in a bad state stays stuck through as many of those as you like.
To do a real one: hold Shift while clicking Shut down in the Start menu. That bypasses Fast Startup. Then, once it is off, unplug the charger, and if your laptop has a removable battery take it out. Hold the physical power button down for thirty seconds — this drains residual power from the board and forces the embedded controller to reset. Reconnect and power on.
On laptops with a sealed battery, some manufacturers provide a pinhole reset button on the underside, and Lenovo in particular documents this. Check your model's manual.
If the keyboard comes back here, you are done — and it was never a driver problem.
2. Reinstall the keyboard driver
If a full power cycle did not do it, the update probably left a driver mismatched.
- Right-click Start → Device Manager.
- Expand Keyboards. Look for a yellow warning triangle — that is a strong hint on its own.
- Right-click the entry (usually "Standard PS/2 Keyboard" or "HID Keyboard Device") and choose Uninstall device.
- If there are several entries, uninstall all of them.
- Restart normally. Windows redetects the keyboard and installs a fresh driver.
If Windows reinstalls the same broken driver, try Update driver → Browse my computer → Let me pick, and choose the generic PS/2 Standard Keyboard rather than a vendor-specific one. The generic driver is less capable — you may lose some Fn key functions — but it is considerably more reliable, and you can put the vendor driver back once things are stable.
3. Roll the update back
If the keyboard worked the day before and nothing else has helped, remove the update.
Go to Settings → Windows Update → Update history → Uninstall updates, and remove the most recent one. For a feature update rather than a cumulative patch, there is a separate Recovery → Go back option, available for ten days after the upgrade.
Bear in mind you are removing a security patch, so treat this as a temporary measure. Check the laptop manufacturer's support site for an updated driver, install that, then let the Windows update reapply.
4. Check the things updates quietly change
Two settings get reset by updates often enough to be worth looking at:
Filter Keys. Settings → Accessibility → Keyboard. When on, it ignores brief keypresses, which makes a working keyboard feel completely dead. Updates have been known to re-enable it.
USB selective suspend. Control Panel → Power Options → Change plan settings → Change advanced power settings → USB settings. Set selective suspend to Disabled. This matters more for external keyboards than built-in ones, but it costs nothing to rule out.
Also open Device Manager, find the keyboard, go to the Power Management tab if it has one, and untick "Allow the computer to turn off this device to save power".
5. Separate hardware from software for certain
If none of the above works, you need to know whether the keyboard hardware is alive. Two tests settle it.
The BIOS test. Restart and enter BIOS or UEFI setup (usually F2, F10 or Del during startup — and yes, you need the keyboard to work for a moment to get in, which is itself informative). If you can navigate the BIOS menus with the built-in keyboard, the hardware is fine and the problem is entirely within Windows.
The browser test. Back in Windows, open the keyboard test and press keys. Sometimes a keyboard is partly working — a block of keys dead, the rest fine — and that pattern points to a ribbon cable connection rather than a driver, because drivers fail all-or-nothing.
A partial failure that survives a driver reinstall and appears in BIOS too is physical. On a laptop that usually means the ribbon cable has worked loose from its connector, which is a repair worth having done if the machine is otherwise healthy.
Check exactly which keys are responding, once you have input back.
Open the keyboard test →FAQ
Can a Windows update physically damage a keyboard?
No. Updates change software — drivers, settings, power configuration. They cannot damage switches, membranes or cables.
What they can do is leave a controller in a state that a normal restart does not clear, which is why a full power drain fixes so many of these.
Why does a full shutdown work when restarting does not?
Because of Fast Startup. A normal shutdown hibernates the kernel rather than fully powering down, so hardware is restored from a saved state instead of reinitialised.
Holding Shift while clicking Shut down bypasses it, and removing power afterwards forces the embedded controller to reset properly.
Some keys work and others do not. Is that still a driver problem?
Unlikely. Drivers fail as a unit — you do not get a driver that handles half the keys.
A contiguous block of dead keys points at the ribbon cable or a damaged section of the membrane, both of which are physical. Check whether the dead keys form a row or a column, which is a strong signal for a matrix connection fault.
Should I roll back the update permanently?
No — you would be declining security patches indefinitely, and Windows will try to reinstall it anyway.
Use the rollback to get working, then install the manufacturer's current driver for your model, then let the update reapply. That usually sticks.