If you’re mid-raid and your dodge key ghosts you, or your WASD stutters during a sprint, you already know how disorienting this problem is. The symptom usually looks like this: a key works fine in Notepad or a browser but drops inputs in-game, or it works intermittently — registering on the third or fourth press — or holds down when you’ve released it, or ignores combos like Shift+W entirely. Sometimes only specific keys fail, sometimes it’s everything after a few minutes of play, and sometimes a gamepad plugged in is silently stealing priority.
The good news: this is rarely a dead keyboard. In the overwhelming majority of cases the culprit is software — a polling-rate setting, a filter, a conflicting peripheral, or a power management rule — and it can be fixed in under fifteen minutes. Work through the fixes below in order; they’re sorted easiest-first, and each includes how to reverse it if it doesn’t help.
Likely Causes
| Cause | How to confirm | Fix difficulty |
|---|---|---|
| Filter Keys or Sticky Keys intercepting input | Hold a key for 5 seconds — if a Filter Keys prompt appears, it’s active | Very easy |
| USB selective suspend or a power-saving USB hub | Keyboard is on a hub or front-panel port; fails after idle periods | Easy |
| Ghosting/rollover limits on a membrane keyboard | Only fails during 3+ key combos; passes single-key tests | Easy (settings) / Hardware if inherent |
| Outdated or corrupted keyboard/chipset drivers | Device Manager shows a warning icon or a generic “HID Keyboard Device” duplicated several times | Moderate |
| Vendor software (Synapse, iCUE, G HUB, Armoury Crate) conflicts | Keys fail only when the vendor app is running; works after unplugging/replugging | Moderate |
| Game reading the wrong input device (controller override) | On-screen prompts show controller button icons instead of keyboard keys | Easy |
Fix 1: Turn Off Filter Keys and Sticky Keys
What causes it
Windows accessibility features designed to ignore brief or repeated keystrokes can swallow fast game inputs. Filter Keys is the most common offender; it sometimes activates after holding Shift for 8 seconds, often without you noticing.
How to check
Press and hold the Shift key for about 8 seconds. If a Filter Keys dialog or sound appears, the feature is on and likely triggered accidentally during gameplay.
What to do
Open Settings, go to Accessibility, then Keyboard, and set Filter Keys, Sticky Keys, and Toggle Keys all to Off. While you’re there, expand each option and disable the shortcut that lets them turn on via a key hold — in Filter Keys settings, uncheck “Allow the shortcut key to start Filter Keys.”
How to undo it
Return to the same Settings page and toggle the features back on. Nothing else changes when you disable them.
Fix 2: Plug the Keyboard Into a Rear-Panel USB Port Directly
What causes it
Front-panel ports and unpowered hubs share bandwidth and can drop below the polling rate a keyboard needs, especially with RGB lighting drawing power. Loose or underpowered connections cause intermittent missed inputs.
How to check
Note where your keyboard is currently plugged in. If it’s on a hub, a monitor’s USB pass-through, or a front case port, that’s your suspect. Wiggling the connector while typing in Notepad can reveal a loose port — watch for dropped characters.
What to do
Move the keyboard to a USB port on the rear I/O panel of a desktop, connected directly to the motherboard. Prefer a USB 2.0 port for older keyboards if a USB 3.0 port misbehaves; some legacy devices have driver quirks on 3.0.
How to undo it
Plug it back where it was. This change is purely physical.
Fix 3: Disable USB Selective Suspend
What causes it
Windows can cut power to USB devices to save energy, and some keyboards wake slowly or miss the first few inputs afterward — a classic “key not registering after idle” cause.
How to check
If your keys fail mainly after the PC has been idle or the keyboard hasn’t been touched for a few minutes, selective suspend is a strong candidate. Confirm it’s enabled by opening Control Panel, going to Power Options, clicking “Change plan settings” on your active plan, then “Change advanced power settings,” and expanding USB settings, then USB selective suspend setting.
What to do
In that same dialog, set “USB selective suspend setting” to Disabled for both On battery and Plugged in, then click Apply. Also open Device Manager, expand Universal Serial Bus controllers, right-click each “USB Root Hub,” choose Properties, open the Power Management tab, and uncheck “Allow the computer to turn off this device to save power.”
How to undo it
Re-enable the setting in the same Power Options dialog and re-check the boxes in Device Manager.
Fix 4: Adjust Polling Rate and Disable N-Key Rollover Conflicts
What causes it
Gaming keyboards let you switch polling rates (typically 125 Hz to 1000 Hz). A mismatch between an extremely high polling rate and a game or older USB controller can drop reports. Similarly, some boards’ NKRO mode misbehaves in games using DirectInput.
How to check
Check your keyboard’s manual or vendor app for the current polling rate. If it’s set above 500 Hz, try lowering it. For rollover, look for a keyboard shortcut printed on the board — commonly Fn+N for NKRO or Fn+6-key/flip combination — and note which mode is active.
What to do
Set polling to 500 Hz in your vendor software or via the board’s hardware shortcut, then test. If problems persist in multi-key combos, switch from NKRO to 6-key rollover mode and test again. Many older games handle 6KRO more reliably.
How to undo it
Set polling back to your preferred value (1000 Hz for competitive play) and re-enable NKRO with the same shortcut.
Fix 5: Disconnect Conflicting Controllers and Peripherals
What causes it
Many games auto-detect the most recently active input device. A gamepad, racing wheel, drawing tablet, or even a second keyboard can hijack input priority, making your keyboard seem dead when the game is simply ignoring it.
How to check
If in-game button prompts show Xbox or PlayStation icons instead of keyboard keys, a controller is overriding input. Also test whether the keys work on the game’s main menu — if menus respond but gameplay doesn’t, an input conflict is likely.
What to do
Unplug all controllers and nonessential USB devices, restart the game, and test. If you use Steam, open Settings, then Controller, and set “Guide button focuses Steam” off; in Big Picture controller settings, disable controller support for games that don’t need it. In games with an explicit input device selection, force it to Keyboard.
How to undo it
Reconnect your peripherals and restore Steam’s controller settings to their defaults.
Fix 6: Update or Clean-Reinstall Keyboard and Chipset Drivers
What causes it
Corrupted HID drivers, duplicated ghost devices from years of replugging, or an outdated motherboard chipset driver can cause unreliable key reporting.
How to check
Open Device Manager and expand Keyboards. Multiple identical “HID Keyboard Device” entries, or any entry with a yellow warning icon, indicate driver trouble. Also check “Universal Serial Bus controllers” for warnings.
What to do
Right-click your keyboard entries under Keyboards and choose “Uninstall device,” then restart — Windows reinstalls them automatically. Next, download the current chipset driver package from your motherboard manufacturer’s support page for your exact board model and install it. If you use a gaming keyboard, install the latest firmware from the vendor app (e.g., a “Firmware update” section in G HUB, iCUE, or Synapse) — 2026-era boards increasingly receive input-latency and rollover fixes via firmware.
How to undo it
Roll back a driver from Device Manager (Properties, then Driver tab, then Roll Back Driver) or reinstall an older chipset package if the new one causes issues elsewhere.
Fix 7: Reset or Update Vendor Software Profiles
What causes it
Suite applications like Razer Synapse, Corsair iCUE, Logitech G HUB, and ASUS Armoury Crate store per-game profiles with remapped keys, macros, or disabled keys. A stale or corrupted profile can silently block specific keys in specific games.
How to check
Open your vendor app, go to the profile or game-association section, and look for key remaps, macros bound to your problem keys, or a “disabled” state. Then fully exit the app from the system tray and test the game — if keys work with the app closed, the software is the problem.
What to do
Create a fresh default profile in the app and reassign your lighting and macros from scratch. If the app itself seems broken, uninstall it, reboot, and reinstall the latest version. As a temporary measure, you can run without the vendor software entirely — most boards work as standard HID devices with default behavior.
How to undo it
Reopen the app and reapply your old profile, or restore from a backup if the suite offers profile export/import.
Fix 8: Test With Another Keyboard to Rule Out Hardware
What causes it
Worn membrane domes, cold-soldered switch joints, liquid damage, or a frayed cable cause genuine hardware failures that no software fix will touch.
How to check
Use a keyboard testing website (search for “keyboard tester”) or a game with a visible key-press display, and press the problem key repeatedly. If it drops inputs there too, and every software fix above has failed, the switch or its circuit is suspect. For mechanical boards with hot-swappable switches, swap the suspect switch with a neighboring one — if the problem follows the switch, the switch is dead.
What to do
On hot-swap boards, replace the faulty switch (most modern boards use 3-pin or 5-pin MX-style switches, available individually). On soldered or membrane boards, the practical fix is replacement. Also try the keyboard on another PC to confirm the fault follows the keyboard and not your system.
How to undo it
Swap the original switch back, or return the keyboard to its previous system.
If Nothing Works
If every fix above fails, isolate the variable: test a different keyboard on your PC and your keyboard on a different PC. If your keyboard fails on both machines, replace it — hardware faults in the controller PCB aren’t economically repairable on most consumer boards. If other keyboards also fail on your PC, the issue is your system: try a full Windows in-place repair (Settings, then System, then Recovery, then “Fix problems using Windows Update” or a repair install from installation media), and check your motherboard’s support page for a BIOS update, since USB controller firmware bugs occasionally cause input instability. As a stopgap for competitive play, remapping critical actions to keys that do register reliably — usually in the center cluster rather than the far edges of the board — can keep you playable while you sort out a replacement.
FAQ
Why do my keys work in Notepad but not in games?
Games use different input pipelines (Raw Input, DirectInput, or newer APIs) and often run fullscreen exclusive mode, where driver-level filters, vendor overlays, and rollover limits behave differently than in ordinary apps. A key that types fine can still drop inputs during multi-key game combos or under a high polling rate the game handles poorly.
Can a wireless keyboard cause keys not to register?
Yes. Wireless boards are more prone to missed inputs due to interference, low battery, or a receiver plugged into a USB 3.0 port (which generates RF noise in the 2.4 GHz band). Move the receiver to a front or extension port close to the keyboard, away from USB 3.0 ports, and replace the battery or recharge before assuming a hardware fault.
Does a high polling rate ever hurt gaming performance?
It can. Polling rates above 500 Hz (many boards now offer 4000–8000 Hz) increase CPU interrupt load, and some games or older USB controllers drop reports at extreme rates. If you’re seeing missed keys, drop to 500 or 1000 Hz and test — the practical difference in most games is negligible.
How do I know if it’s ghosting or a real hardware failure?
Ghosting follows a pattern: it only happens during specific combinations of three or more keys and is consistent every time. Test with a keyboard tester while holding two keys and tapping a third. If the same combination always fails on a membrane or budget board, it’s likely a rollover matrix limitation — no fix exists except switching to a keyboard with true NKRO. Random, inconsistent drops point to a loose connection, driver issue, or failing switch instead.
