Software tower · floor

How to fix keyboard not typing when nothing is broken

How to fix keyboard not typing splits into two questions that look identical from the chair: a keyboard that cannot type, and a Windows that has been told to ignore it. Microsoft documents both, and the second one is where to start.

“Turn on the Filter keys switch to set the sensitivity of the keyboard so it can ignore brief or repeated keystrokes.”

Read that as a description of a symptom rather than a feature and the reason it belongs at the top of this page is obvious. Filter keys is a setting whose documented purpose is to make Windows disregard what you type. Switched on unintentionally — and it has a keyboard shortcut of its own — it produces a keyboard that responds to some presses, ignores others, and passes every hardware test you can run on it. Where to look: press Windows logo key + U, or Start → Settings → Accessibility.

Filter keys

ignores keystrokes

Sets keyboard sensitivity “so it can ignore brief or repeated keystrokes”. The one that looks like a broken keyboard.

Sticky keys

changes shortcuts

Lets you “press commands that use multiple keys (such as Ctrl + S) one key at a time”. Shortcuts start behaving oddly rather than not at all.

Toggle keys

adds a sound

Plays a sound “whenever you press the Caps lock, Num lock, or Scroll lock keys”. Harmless, and a useful sign that something in here got switched on.

Those three live together in Accessibility settings and they exist for good reasons — they make a computer usable for people who would otherwise struggle with it. The problem is only that one of them is indistinguishable from a fault when it is on and you did not turn it on. Checking takes ten seconds and rules out the entire software half of the question.

If the switches are off, the question becomes whether the keyboard itself is working, and Microsoft has one step that answers it outright.

“If the device doesn’t appear to work at all… connect the device to another PC and make sure the device works on that PC. If the device doesn’t work on the other PC, you might need to replace it.”

Microsoft’s test, and the only step on the page that produces a verdict instead of another thing to try. Two computers, one keyboard, and the answer is whichever one is the odd one out. Microsoft attaches one caveat worth respecting: “some devices won’t work without installing a driver”, so when testing elsewhere, make sure the right driver is on the other machine — otherwise the second PC produces a false result and you replace something that was fine.

The physical checks, with the detail that matters in each

Microsoft’s list, and none of these is “restart and hope”.

The first item on that list is the one people do wrong, and Microsoft’s wording explains why. Unplugging and immediately plugging back in does not do what unplugging is supposed to do — the instruction is to wait while Windows unloads the driver, and only then reconnect. A two-second reconnection often reattaches to the same broken state.

If it is wireless, there are two reset buttons rather than one. Microsoft: “Look on the bottom of the wireless device for a Reset button… There might also be a Reset button on the USB receiver for your device.” The second one is the forgotten half — the little dongle in the port is a device too, and it can be the one that has lost the connection. For USB wireless, the simpler version is “unplugging the USB wireless receiver, waiting for about 10 seconds, and then plugging the USB wireless receiver back into the USB port”. And if the keyboard connects over Bluetooth rather than a receiver, Microsoft sends you to its Bluetooth troubleshooting instead — a different radio with different failures.

If the keyboard passes the other-PC test and the switches are off, what is left is the driver, and Microsoft gives two routes. The automatic one: type check for updates in the search box, open it, and select Check for updates — with the honest caveat that “there might not be any driver updates available”. The manual one: search for Device Manager, find the device, double-click it, then the Driver tab and Update Driver.

What this page will not do is tell you to reinstall Windows, run a registry cleaner, or install a driver-updating tool. None of that is on Microsoft’s page for this problem, and a keyboard is a small enough device that the answer is nearly always in the four paragraphs above.

It also will not cover a laptop keyboard that has had liquid on it. That is a repair question rather than a settings question, and the honest answer to it is not typed.

The floors below take it three ways: the settings that mimic a fault, the tests that produce a verdict, and the neighbouring device that fails in the same way.

Where to start

Three ways in. Take the first one before you touch any cable.

“Some keys work, some do not.”
Check Filter keys — the settings that mimic a fault
“Nothing at all happens.”
Try it on another PC — the test with a verdict
“It is wireless.”
Two reset buttons, not one — wireless and drivers

The settings that mimic a fault

Filter keys ignores keystrokes by design. Sticky keys changes how shortcuts behave. Both are ten seconds to check and rule out half the question.

A monitor that will not displayThe first check is two keys, not a cable — and a splitter can never extend a screen.Open this floor → Copy and paste on a MacWhere a keyboard shortcut that exists everywhere else is missing.Open this floor → Screenshots on WindowsThe one key on the keyboard, and the two tools that do more than it does.Open this floor → Why a computer is slowThe same question on any machine, in the order the causes actually occur.Open this floor →

The test with a verdict

One keyboard, two computers, and the answer is whichever is the odd one out. Microsoft attaches the caveat about drivers that makes the test honest.

The printer test pageTwo of them exist, they leave from different places, and each answers one question.Open this floor → Checking a drive’s healthThe command every guide names has been deprecated — and Microsoft names the replacement.Open this floor → A phone speaker with no soundTwo published tests whose outcome is a verdict — and one setting that silences a working speaker.Open this floor →

Wireless and drivers

A reset button on the device and possibly another on the receiver, ten seconds unplugged, and two routes to a driver.

Pairing Bluetooth headphonesBoth vendors document one half of this and hand the other to the manufacturer, in writing.Open this floor → A printer that says offlineMicrosoft puts reinstalling sixth of seven — and names the setting that hides step three.Open this floor → Factory resetting Windows 11Two options that sound alike and remove very different amounts.Open this floor →

What this tower will not do

It will not tell you to reinstall Windows or run a cleaner. Neither appears on Microsoft’s page for this problem, and a keyboard is a small enough device that it does not need either.

It will not recommend a driver-updating tool. Microsoft gives two free routes and says plainly that there might not be an update at all.

And it will not cover a keyboard that has had liquid spilled on it. That is a repair question, and the honest answer to it is not typed. What holds instead is simple: the Accessibility route through Windows logo key + U, the descriptions of Filter keys as setting keyboard sensitivity so it can ignore brief or repeated keystrokes, of Sticky keys as allowing multi-key commands to be pressed one key at a time, and of Toggle keys as playing a sound for Caps lock, Num lock and Scroll lock, together with the hardware checks including waiting for the driver to unload before reconnecting, trying another USB port, removing a USB hub, checking cables and batteries and dirt, the reset buttons on a wireless device and on its USB receiver, the ten-second wait for a USB receiver, the instruction to test the device on another PC with the caveat about drivers and the conclusion that a device failing on both might need replacing, and the two driver routes through Windows Update and Device Manager are quoted from Microsoft’s support documentation listed below.

Where this page got its facts

  1. Microsoft, Mouse and keyboard problems in Windows — Microsoft Support, applies to Windows 11 and Windows 10 (the hardware checks of unplugging USB cables and waiting for the device driver to be unloaded by Windows before plugging the device back in, trying a different USB port, ensuring a USB hub has power and removing it to connect the device directly, checking that cables are undamaged, checking that battery-powered devices are charged or have fresh batteries, and making sure there is no dirt blocking keys or sensors; the wireless checks of looking for a Reset button on the bottom of the device and possibly on the USB receiver, unplugging a USB wireless receiver and waiting about 10 seconds before plugging it back in, and referring Bluetooth devices to the Bluetooth troubleshooting page; the instruction to connect the device to another PC to check whether it works there, with the note that a device failing on the other PC might need replacing and the caveat that some devices will not work without the correct driver installed; and the two driver routes, through the taskbar search for check for updates and Windows Update, and through Device Manager, the Driver tab and Update Driver) — support.microsoft.com, read 22 August 2026.
  2. Microsoft, Make your mouse, keyboard, and other input devices easier to use — Microsoft Support, Accessibility (the route to Accessibility settings by pressing the Windows logo key + U or selecting Start, Settings, Accessibility; the description of the Sticky keys switch as letting commands that use multiple keys, such as Ctrl + S, be pressed one key at a time for people who have trouble pressing two keys at the same time; the description of the Toggle keys switch as playing a sound whenever the Caps lock, Num lock or Scroll lock keys are pressed; and the description of the Filter keys switch as setting the sensitivity of the keyboard so that it can ignore brief or repeated keystrokes) — support.microsoft.com, read 22 August 2026.

Written by Alberto Gulotta

Founder and editor of AI Tools Primer, writing from Palermo, Italy. Thirty-five years of taking computers apart, starting with a Commodore 64 — the long version is on the about page.

Something wrong on this page? Write to aitoolsprimer@gmail.com and it gets fixed.

Written on 22 August 2026.

Independence and limits

No affiliate links and no paid placements anywhere on this site. Nobody pays to appear here, and no company has seen this page before you did.

This is general information, not professional advice. Where a page touches money, health, safety or the law, it names its source and the date it was read — and your situation may still differ. See the privacy page and the cookie policy.