My Keyboard Is Not Working: Step-by-Step Troubleshooting Before You Replace It

When nothing types anywhere, treat the problem as power, connection, or host software before you open a switch or call repair. A cable seated halfway, a Bluetooth board that lost pairing, or a USB hub that dropped power can silence the entire deck while the computer still looks fine. When only a zone fails—number row, arrows, or punctuation—the checker map usually shows a contiguous block missing, which hints at flex-cable damage, liquid bridges, or a single controller region rather than random bad luck.

Split the story early: whole-keyboard silence versus partial zones versus keys that register but feel wrong. Each pattern routes to a different fix list. Whole silence often clears with a port swap or reboot; partial zones need a slow key map; sticky or double characters need debounce and cleaning paths instead of replacement shopping.

Try another USB port or a phone OTG adapter when the host might be the problem. Laptops with USB-C docks fail in confusing ways: the dock powers but the keyboard path stalls. Unplug everything except the keyboard and retest before you blame the board itself.

Document whether failure is constant or intermittent. Intermittent silence that returns after sleep often points to power management or wireless reconnect rules rather than a dead matrix. Constant silence across reboots and hosts strongly favors cable, port, or board replacement paths.

Single-key mysteries belong in keyboard key not working when one switch misbehaves while neighbors stay clean. This guide stays at whole-deck and zone level so you do not mix cable fixes with solder stories.

Wireless boards fail at three layers: battery, pairing, and interference. Replace or charge batteries before firmware adventures. Delete the Bluetooth pairing on both sides and pair again on a clean profile—stale pairings survive reboots and look like dead hardware. Wired boards need a direct port when possible; avoid unpowered hubs during diagnosis.

USB-C and multi-host KVM setups add swap latency. Confirm the active machine actually owns the keyboard before you declare failure. Some docks require an explicit input switch; others grab focus only after a second keypress wakes the path.

Bluetooth dropouts masquerade as total failure when the board reconnects only after sleep cycles. Bluetooth keyboard connection test walks pairing hygiene and dongle placement when wireless is your daily driver.

Built-in laptop keyboards share DNA with external troubleshooting but add ribbon and hinge stress—laptop keyboard not working fixes when internal zones fail while USB boards still pass the checker.

Restart the machine after connection checks. Filter Keys, Sticky Keys, and gaming overlays can block or duplicate input in ways that feel like hardware death. Disable accessibility toggles you did not mean to enable, then test in a private browser window with extensions off so nothing intercepts keystrokes.

Reinstall or update the keyboard driver from Device Manager on Windows; on Mac, remove Bluetooth pairings and pair again for wireless boards. If keys work in firmware settings but fail in the operating system, suspect drivers or security software rather than a dead matrix.

When only one app loses keys

Browsers and games sometimes capture keys exclusively. Run the [online keyboard checker](/labs/keyboard-test) first, then a plain text editor. If the checker works everywhere else, adjust in-app bindings instead of replacing hardware. Sticky keys turn-off guide clears the most common OS-level mimic of broken decks.

Liquid history changes the software story—spilled liquid on keyboard before you assume a driver fix will hold when corrosion is still spreading under keycaps.

Open the online checker, reset the map, and press every key slowly—including modifiers, punctuation, and function layers you rarely use. Screenshot or note contiguous dead regions. Support teams approve RMA faster when you show a complete map instead of saying “some keys broke.”

Include Print Screen, Scroll Lock, and Pause when your workflow uses them; they share controller blocks with the function row on many boards. Layout dropdowns matter for ISO, ANSI, and regional variants—online keyboard test guide when travel boards surprise you with different key shapes.

Exam and interview rooms deserve the same sweep on the actual board you will type on—test keyboard before exams when timing pressure makes skipped punctuation keys expensive.

Fn-lock and media-layer confusion looks like dead function keys—function keys F1–F12 guide when the row works in the checker only with Fn held.

Consumer desktop keyboards under a certain price point cost more to diagnose than replace. Laptop integrated boards follow similar economics: replacement assemblies are standard service items when flex reseat does not hold. Document failing keys with checker screenshots before you call support—it speeds approval and prevents repeat shipping.

Sticky keys after gentle cleaning still showing constant press in the checker usually mean assembly replacement on ultrathins—not endless clip chasing. How to fix sticky keyboard keys when feel is gummy but electrical behavior is partial rather than dead.

When repair is deferred, verify an external board on the same checker, then use the one-minute typing embed below only after input is honest. Benchmarking on a failing deck trains corrections you will need to unlearn after replacement.

Deep diagnostics live in keytest online diagnostic when you need event-log detail beyond the color map. Return here for the first-pass whole-deck story whenever a keyboard goes silent without warning.