Keyboard Not Working in Game: Why Keys Stop Registering

A keyboard that works everywhere except in game is almost always one of four things: ghosting when several keys are held, a Windows accessibility feature you switched on by accident, a layout that changed under you, or a program that receives the keypress before the game does. None of them are a broken keyboard, and all four are separable with one test: press the failing keys in a tester outside the game and see whether they register there. That single check splits hardware from software before you touch a single setting.

Short answer

Test the dead keys outside the game first — a keyboard tester shows what the system actually receives.
Keys vanishing only in combinations is ghosting, a matrix limit, not a game bug.
A dialog and a beep before it broke means Sticky Keys or Filter Keys; both switch off under Windows Accessibility.
WASD dying after Ctrl+Shift is a layout switch, and Microsoft documents that shortcut.
Macro tools, remappers and overlays sit in front of the game and are the first software to disable for a test.

Does the key work outside the game?

Start here, because the answer decides which half of this guide you need. Open the keyboard tester and press the keys that fail, one at a time and then in the combination that breaks.

Three outcomes, three different guides:

The key does not register anywhere. Hardware or connection. Try another port, another cable, another machine.
Single presses register, the combination does not. Ghosting. Next section.
Everything registers in the tester and fails in game. Software in front of the game, or that game's own input handling. Skip to the accessibility and layout sections.

There is a fourth case worth naming because it wastes hours: the key works, but the game never had it bound. Rebinding chaos is a category of its own, and the gaming keybinds guide covers the layouts that survive contact with a real match.

Ghosting and rollover: why the third key disappears

This is the classic "I can't crouch while sprinting diagonally" problem, and it is physics, not a patch.

Most keyboards do not wire every key separately. They use a matrix of rows and columns without isolation diodes, on the assumption that only a few keys are held at once. Wikipedia's rollover article describes the failure exactly: when three keys that form three corners of a rectangle in the matrix are pressed, the current also routes through a fourth intersection, and the controller registers a key that nobody touched — or misses one that was.

Manufacturers lay out the matrix so that common sequences survive, which typically yields four- to five-key rollover for the combinations people actually type. Game movement is not typing. Forward plus strafe plus sprint plus crouch plus jump is five simultaneous keys before you have shot at anything.

A keyboard with n-key rollover scans every key independently and does not have this limit.

The USB side has one more twist worth knowing. There are two protocols: the boot protocol, used by very limited hosts such as a BIOS, which carries eight modifiers plus a maximum of six key codes, and the HID report protocol, which operating systems use and which imposes no such restriction. Wikipedia adds the honest caveat: the HID specification sets no rollover requirement, so a low-end keyboard may impose the same limits regardless.

The practical test is free. Hold the combination that fails in the tester and count what lights up. If the fifth key never appears, no amount of driver reinstalling will change it — rebind to keys on different matrix rows, or use a keyboard with full rollover.

Sticky Keys, Filter Keys and the beep before the trouble

Windows ships two accessibility features that are one accidental shortcut away and that mangle exactly the input games depend on.

FilterKeys makes Windows ignore brief or repeated keystrokes. It exists to help people with hand tremors, and it is enabled by holding the right Shift key for eight seconds — with an audible cue and a popup to confirm. Eight seconds of held Shift is not a strange thing to do while sprinting. The result is a keyboard that "misses" taps, which reads as a broken key.

Sticky Keys serialises modifiers: press and release Shift, and it stays active until another key is pressed. In a game that means a crouch or sprint that latches on when you did not ask.

Both live in the same place. Press Windows key + U to open Accessibility, choose Keyboard, and switch off Sticky keys, Filter keys and Toggle keys. Toggle keys is the harmless one — it only plays a sound on Caps, Num and Scroll Lock — but if it is on and you did not turn it on, something else turned it on for you.

Why does WASD stop working after Ctrl+Shift?

Because Ctrl+Shift changes the keyboard layout when more than one layout is installed. That is not folklore; it is in Microsoft's own shortcut list, alongside Windows key + Ctrl + Spacebar for returning to a previously selected input option.

The reason it breaks some games and not others is in Microsoft's raw input documentation: the keyboard generates a device-specific scan code, and the system hands the application a virtual key code instead. An application that registers for raw input receives the low-level data directly. So one engine can read the physical key position and keep working after a layout switch, while another reads the translated character and loses the binding.

Two durable fixes, both under Windows language settings: remove the second layout if you do not need it, or move the switching shortcut off a combination you press in play. Ctrl+Shift is the default worth changing, because holding Ctrl and Shift together is the most ordinary thing in the world during a fight.

Programs that get the keypress before the game

Anything that hooks the keyboard sits between you and the game: remappers, macro utilities, streaming overlays, chat clients with global hotkeys, screenshot tools, and the software your own keyboard shipped with.

Anti-cheat vendors are explicit about part of this. BattlEye's FAQ states they ban for actual cheats, and that they may decide to kick — not ban — for a specific program such as a macro tool, without that marking you as a cheater. Non-cheat overlays are generally supported unless a specific game blocks them. Read that as a practical warning rather than a green light: macro software is both a kick risk and a common source of keys that behave strangely.

The test is the same one that works everywhere in this guide: close them all, confirm the keyboard behaves, then re-enable one at a time. If the game itself started misbehaving around the same time — crashing, or refusing to launch — that is a different branch entirely, and it starts at game crashes on startup.

What usually goes wrong

Blaming the game for ghosting. Symptom: the fifth key stops working only during movement. Why: a matrix without diodes. Fix: confirm it in the tester, then rebind to keys that do not collide, or move to an NKRO keyboard.
Filter Keys switched on mid-match. Symptom: taps stop registering, a beep happened earlier. Why: right Shift held for eight seconds. Fix: Windows key + U → Keyboard → Filter keys off.
A second layout nobody added on purpose. Symptom: keys work in one game, not another, after a Ctrl+Shift. Why: layout switching plus different input handling per engine. Fix: remove the layout or rebind the shortcut.
Keyboard software fighting the game. Symptom: a remapped key sends the old binding, or nothing. Why: a profile applied at the device or driver level. Fix: reset the profile to default and re-bind inside the game only.
A USB hub in the chain. Symptom: intermittent dropouts, often with lighting on. Why: shared bandwidth and limited port current; the Wooting write-up also notes lighting effects load the keyboard's own microcontroller. Fix: motherboard port, lighting off for the test.

If the tester shows everything arriving correctly and the game still ignores you, the remaining suspect is that game's input configuration rather than your hardware. While you are in a testing mood, the gamepad tester also settles whether a connected controller is quietly taking over the inputs.

For click-speed questions the CPS test and the guide on clicking faster are the right stop instead, and if the mouse is misbehaving alongside the keyboard, both may share a cause: mouse lag and stutter covers the shared USB and power-saving side of it. Keys that arrive but arrive late are a third thing again — that is a frame-pacing symptom, and it belongs to FPS drops and stutters.

FAQ

Why do some keys stop working when I hold several at once?

That is ghosting, and it is a hardware limit rather than a game bug. Most keyboards use a switch matrix without isolation diodes, and Wikipedia's rollover article shows how pressing three keys that form three corners of a rectangle in that matrix makes a phantom fourth appear or a real one vanish. Common matrices manage four to five keys in the sequences people actually type; NKRO keyboards scan every key independently and have no such limit.

Is NKRO over USB real, or marketing?

It is real, with a caveat Wikipedia states directly. USB has two modes: boot protocol, used by very limited hosts such as BIOS, which is capped at eight modifiers plus six key codes, and HID report protocol, which operating systems use and which imposes no such limit. But the HID specification sets no rollover requirement either, so a cheap keyboard can still restrict itself in either mode.

Why did a dialog appear and my keys stopped working?

You almost certainly triggered an accessibility feature. Holding the right Shift key for eight seconds turns on FilterKeys, which makes Windows ignore brief or repeated keystrokes — exactly what tapping a movement key looks like. Both FilterKeys and Sticky keys have switches under Windows Accessibility settings, and turning them off there is permanent.

Why does WASD stop working after I press Ctrl+Shift?

Because Ctrl+Shift switches the keyboard layout when more than one is installed, as Microsoft's own shortcut list states. Some games read scan codes and some read the translated character, so a layout change can leave you moving in one game and stuck in another. Remove the extra layout, or move the switching shortcut off a combination you use in play.

Can macro software get me banned?

It can get you kicked. BattlEye's FAQ says they ban for actual cheats, and that they may decide to kick — not ban — for a specific program such as a macro tool, without that flagging you as a cheater. Different games and anti-cheats have different rules, so the safe answer is that macro utilities are a risk you take knowingly, and a common cause of keys that behave oddly in game.