Numpad Not Working? Check Num Lock and Mouse Keys
If your numpad types arrows, first check Num Lock. If it moves the pointer, check Mouse Keys. If it produces nothing, use the numpad test and compare another application before assuming the keypad is broken.
Match the behavior
| What you observe | First check |
|---|---|
| 2, 4, 6 and 8 act as navigation | Toggle Num Lock, where available |
| Those keys move the pointer | Review Mouse Keys in accessibility settings |
| Letters become numbers on a compact laptop | Check the model's embedded-numpad or Fn layer |
| One keypad key fails everywhere | Compare mapping, connection and that physical key |
| A decimal comma appears instead of a point | Check input language and the application's number format |
Test digits and the separate keys
Press each digit, decimal key, operators and keypad Enter individually. NumpadEnter and the main Enter are separate positions; a working main Enter does not test the keypad switch. Keypad sizes vary, so use the keys your device actually has.
On Windows, Num Lock commonly selects digits versus navigation. Compact keyboards may require a model-specific combination. An Apple keypad may have Clear instead of Num Lock; do not assume every keypad has the same mode switch.
The browser's reported modifier state is only a hint. Some platforms do not expose Num Lock consistently. Compare what arrives in a text editor or spreadsheet as well as the indicator on the keyboard.
Check Mouse Keys without guessing a shortcut
Windows and macOS can use keypad keys to move the pointer. Open the operating system's accessibility settings and inspect Mouse Keys. If you depend on the feature, record your setting before a temporary comparison. Shortcut behavior can be configured, so repeatedly pressing a guessed shortcut is less useful than checking the setting itself.
If keys still do not arrive
Try a direct connection instead of a hub, another USB port, or another computer. If the keypad works elsewhere, compare local remapping software and application settings. A single missing browser event cannot tell you whether a switch, socket, controller or software layer caused it.
A recurring fault across computers deserves manufacturer support. Do not open the case or change registry values as a first test. If numbers work after login but Num Lock resets at startup, consult the device and operating-system documentation for startup behavior; there is no universal firmware setting that fixes every machine.
For extra events, use the double typing test. For a highlighted key that does not release, use the stuck key test.
Sources
- Microsoft: input accessibility settings describes Mouse Keys and keyboard controls.
- Apple: keys not responding includes Mouse Keys and other causes.
- How browser results should be interpreted.