Keyboard Tester: Test Every Key Before You Buy One

Your keyboard is doing something odd and you want to know whether the fault is the hardware or Windows. Before you order a replacement, there is a way to find out in about two minutes.

Windows ships a tester and does not call it one. It is already on your machine, on every version, with nothing to install.

I will take the test first, then what each result actually tells you.

The tester Windows already has

The On-Screen Keyboard, which almost everybody thinks is only for touchscreens.

Documented by Microsoft on its On-Screen Keyboard page: on Windows 11, "Go to Start, then select Settings > Accessibility > Keyboard, and turn on the On-Screen Keyboard toggle."

And the Windows 10 route, which is different: "Settings > Ease of Access > Keyboard, and turn on the toggle under Use the On-Screen Keyboard."

⭐ Now press keys on the real keyboard and watch the screen. Each key you press highlights on the on-screen one. That is the test. The whole test.

⚡ Faster route: hold Windows and R, type `osk`, press Enter. Same thing, three seconds.

One wording to be careful about

Small, and it saves you hunting for a setting that means something else now.

On Windows 10, Microsoft describes an option as: "Show keys to make it easier to move around the screen. Use this option if you want the keys to light up as you type."

⚠️ The Windows 11 page uses the same option name for something else, describing keys "for repositioning it on your screen".

⭐ Ours, and marked as ours: the highlight-as-you-press behavior works on both versions here without touching that option. So run the test first and only go looking if nothing lights up.

Windows probably thinks you have several keyboards

Worth knowing before you conclude anything from Device Manager.

Ours, and counted on the machine in front of me. Asking Windows what keyboards it has returned four entries, on a desk with one keyboard on it.

⭐ A Standard PS/2 Keyboard, two USB Input Devices and an HID Keyboard Device, all reporting OK. None of them names the keyboard you can see.

⚡ Read yours with one line in PowerShell:

Get-CimInstance Win32_Keyboard | Select-Object Name, Description, Status

⛔ So a keyboard listed as OK in Device Manager proves nothing. The entry that says OK may not be the physical keyboard you are testing at all.

⭐ Which is exactly why the on-screen test is better than the device list. It responds to the keyboard actually in front of you.

A key that never lights up

The first of the three results, and the clearest one.

⭐ Nothing on screen means the key press never reached Windows. That is the switch. Or the membrane, or something under the cap.

⚡ Try it once more with the keyboard tilted and tapped. Crumbs and hair under a cap are ordinary. This is the point to find out.

⛔ If it stays dead, that key has failed. No driver, no setting and no update brings it back. You can stop investigating.

⚠️ On a laptop that means a keyboard replacement or an external keyboard. The wider version of that decision is a page of its own.

A key that lights up and still types nothing

The second result, and this one is good news.

⭐ The press reached Windows. So the hardware is fine. Something above it is eating the key.

⚡ Test in Notepad rather than in the app that was misbehaving. An app with its own shortcuts is a common and invisible cause.

⚠️ Then check the accessibility keys. Filter Keys deliberately ignores brief presses, which looks exactly like a dead key, and it turns on from holding right Shift.

⛔ A key typing the wrong character is a layout, not a fault. Ours: check the language on the taskbar before anything else, because one wrong layout explains every odd symbol at once.

Keys that repeat when you did not hold them

The third result, and there is a number behind it you can read.

⭐ Ours, and read from the machine here: Windows stores a repeat delay and a repeat rate, and this machine sat at the fastest rate with the shortest delay.

⚡ Change them in the old dialog. Windows key and R, type `control keyboard`, press Enter. Two sliders, and the test box under them is live.

⚠️ Slow the repeat rate down before you blame the keyboard. A maximum rate with a short delay produces doubled letters on a keyboard that is working correctly.

⛔ If one specific key repeats and the others do not, that is a sticking key and it has its own answers.

One key against the whole keyboard

The split that decides everything else, and it takes ten seconds.

⭐ If some work and some do not, you are looking at the keyboard. Windows has no mechanism that disables a handful of individual keys.

⚡ Every key dead points the other way. A connection, a driver, or a keyboard that lost power. None of that is a failed switch.

⚠️ And if everything works but arrives late, lag is a separate problem with separate causes. The tester will show the key, just slowly.

Online keyboard testers, and whether to bother

Being fair about them, since that is what most people find first.

⭐ They do work, and some show key-hold duration and rollover, which the on-screen keyboard does not.

⛔ But a browser sees fewer keys than Windows does. Function keys, media keys and the Windows key itself are often intercepted before the page ever hears them.

⭐ Ours, and marked as ours: I start with the on-screen keyboard, because it sits below the browser and catches more. Use a web tester afterwards only if you want rollover or timing figures.

⚠️ Do not test a keyboard on a sign-in screen to save time. Some keys behave differently there and you will draw the wrong conclusion.

Status: tested here 24 August 2026, Windows 11 and 10 both. Microsoft documents both routes into the On-Screen Keyboard, and its Windows 10 page is quoted for keys lighting up as you type. The Windows 11 page uses that same option name for repositioning instead, so the highlight behavior on 11 is reported as observed. Four keyboard entries and the repeat values were read on a machine here.

Is there a keyboard tester built into Windows?

Yes, though Microsoft does not call it that. Open the On-Screen Keyboard, then press keys on your real keyboard. Each one highlights on screen as it registers. Windows key and R, then osk, is the fastest way in.

How do I know if a key is broken or if it is Windows?

Watch the on-screen keyboard while you press it. No highlight means the press never reached Windows, so the key itself has failed. A highlight with nothing typed means the hardware is fine and something in software is swallowing it.

Why does Device Manager say my keyboard is fine when it is not?

Because Windows usually lists several keyboard devices. Four showed up on the machine tested here, on a desk with one keyboard. An entry reporting OK may not be the keyboard you are holding, which is why the on-screen test is the better check.

Why does my keyboard repeat letters by itself?

Often the repeat rate rather than the keyboard. Windows key and R, then control keyboard, opens the two sliders with a live test box under them. Slow the repeat rate and lengthen the delay before deciding a key is sticking.

The Short Version

• The On-Screen Keyboard is a key tester. Windows key and R, then osk, opens it.
• Press real keys and watch the screen. That single test splits hardware from software.
• No highlight means the key has failed. Nothing in Windows brings it back.
• A highlight with no letter means the hardware is fine and something above it is eating the key.
• Windows lists several keyboard devices. Four appeared on the machine tested here.
• So an OK in Device Manager does not prove the keyboard in front of you is fine.
• Repeated letters are often the repeat rate. control keyboard opens both sliders.
• Web testers miss function and media keys that a browser never receives.

Where to Next

Open the on-screen keyboard and run your fingers across every key once. Two minutes, and you will know which of the three results you have.

If nothing lights up for one key, stop there. That key has failed and no further settings work will change it.

If everything lights up but the typing is wrong, check the language on the taskbar and then Filter Keys. Those two explain most of the remainder.

Did the trouble start with a beep and a dialog rather than a dead key? five taps of Shift is what fired.

Where the entry carries a warning triangle rather than reporting OK, the code beside it says what actually happened.

And if you find a key that highlights in the on-screen keyboard but never types in any app at all, tell me which key in the comments. That combination is unusual and worth collecting.