NumLock Not Working: Registry Fix, BIOS Default and Sticky State Explained
Launch Companion Diagnostic Tool
Test your hardware right now in your browser with zero install:
Open Keyboard TesterNumLock not working is caused by one of three things: a Windows registry value that forces NumLock off at every login, a BIOS setting that overrides the OS state at POST, or a stuck modifier flag that the keyboard controller is holding in firmware. The key itself rarely fails mechanically because it rides on the same membrane dome or MX-style switch as every other key, and those switches last tens of millions of actuations. What fails is the software layer that reads and persists the LED state, or the BIOS handoff that happens before Windows even loads the registry hive.
Confirm the Key Is Actually Sending a Scancode
Before touching any settings, verify the NumLock key is transmitting at all. Open the Keyboard Test and press NumLock. You should see key code 144 (0x90) register in the live output. If nothing lights up in the tester, the key is either physically dead or the USB HID descriptor is filtering it out. On a mechanical keyboard with hot-swap sockets, reseat the switch. On a membrane board, press the key hard in all four corners to check for a delaminated dome. If the scancode fires correctly in the tester but NumLock still misbehaves in Windows, the problem is entirely software-side and the sections below will fix it.
Wireless keyboards add one more variable: a depleted battery can cause intermittent modifier key drops because the radio packet gets truncated. Check battery voltage before going deeper into registry edits.
Fix the Windows Registry NumLock Flag
This is the most common cause of NumLock turning off on every reboot. Windows stores the desired NumLock state per user in two registry locations and one system-wide location. A value of 2 means on, a value of 0 means off.
- Press Win+R, type
regedit, press Enter. - Navigate to
HKEY_USERS\.DEFAULT\Control Panel\Keyboard. - Double-click InitialKeyboardIndicators. Set the value data to 2147483650 on Windows 11 (this is the modern combined flag; on Windows 10 and earlier, use 2). Click OK.
- Navigate to
HKEY_CURRENT_USER\Control Panel\Keyboard. - Set InitialKeyboardIndicators to 2 here as well.
- Sign out and back in. Do not just lock the screen; a full sign-out forces Winlogon to re-read the flag.
If NumLock turns off again after the next reboot, a Group Policy or a third-party login manager is resetting the value. Check gpedit.msc under Computer Configuration > Administrative Templates > System > Logon for any NumLock-related policy. Domain machines often have this pushed from the DC.
Override the BIOS POST Default
The BIOS initializes keyboard LED states before the OS bootloader runs. If your BIOS is set to force NumLock off, it will override whatever Windows wants to do during the early boot phase, and on some firmware builds it wins permanently.
Restart and enter BIOS setup. The key varies: Delete on most ASUS and Gigabyte boards, F2 on most ASUS laptops and Intel NUCs, F10 on HP, F1 on Lenovo ThinkPads. Once inside, look for the NumLock setting in these locations depending on your firmware vendor:
| Firmware Vendor | Menu Path | Setting Name | Correct Value |
|---|---|---|---|
| AMI Aptio (ASUS, Gigabyte) | Boot > Boot Configuration | NumLock State | On |
| InsydeH2O (HP, Acer laptops) | Main tab | Num Lock on Boot | Enabled |
| Phoenix SCT (older Dell) | System Configuration | Numlock Key | Enabled |
| Lenovo UEFI (ThinkPad) | Config > Keyboard/Mouse | Boot Time Numlock | On |
Save with F10 and reboot. If your BIOS has no such setting, the POST state is hardcoded and you must rely on the registry fix above to override it after Windows loads.
Clear a Sticky Modifier State
NumLock is a toggle modifier. The keyboard controller tracks its state in a 1-byte HID LED report. If the controller firmware gets confused, typically after a USB reconnect mid-session or a fast-resume from S3 sleep, the LED and the actual layer can desync. The numpad keys send numpad scancodes but the LED shows off, or vice versa.
To clear the sticky state without rebooting:
- Press NumLock twice rapidly. This forces two toggle events and usually resyncs the LED to the layer state.
- If that fails, unplug the keyboard, wait 10 seconds for the controller capacitors to discharge, replug. The firmware reinitializes and reads the current OS LED state.
- On laptops with embedded controllers, a full shutdown (not restart, not sleep) clears the EC state. Hold Shift while clicking Shut Down in Windows 11/10 to bypass Fast Startup and do a true power-off.
Keyboards with onboard memory, such as those running QMK or VIA firmware, store the NumLock layer state in EEPROM. If the EEPROM value is corrupted, you need to flash a reset keymap or use the QMK Toolbox to wipe EEPROM before reflashing.
Laptop-Specific NumLock Issues
On compact laptops without a dedicated numpad, NumLock activates a secondary numpad layer overlaid on the J, K, L, U, I, O, 7, 8, 9 keys. If NumLock is on and you cannot type those letters normally, that is working as designed, not a fault. Turn NumLock off. Some Lenovo and HP business laptops have a NumLock indicator LED separate from the main keyboard backlight; check the indicator row above the function keys rather than looking for a lit NumLock key.
If you need to test whether your laptop keyboard is registering all keys correctly, the Keyboard Test will show you every scancode in real time without installing anything.
Frequently Asked Questions
Why does NumLock turn off every time I restart?
The registry value at HKEY_USERS\.DEFAULT\Control Panel\Keyboard\InitialKeyboardIndicators is set to 0. Change it to 2 (Windows 10) or 2147483650 (Windows 11) and the state will persist across reboots. If it keeps resetting, a Group Policy from a domain controller is overwriting it.
My numpad types numbers even when NumLock appears off. What is happening?
The LED and the HID layer state have desynced. The controller thinks NumLock is on but the LED driver is reading the old state. Unplug the keyboard for 10 seconds and replug. If it persists on a QMK board, wipe the EEPROM via QMK Toolbox and reflash.
Can a faulty NumLock key cause other keys to stop working?
On a matrix keyboard, a shorted NumLock switch can ghost adjacent keys in the same row or column. Desolder and test the switch with a multimeter in continuity mode. Omron D2FC-F-7N and Kailh GM 8.0 replacements are under $5 each and are the most common drop-in options for membrane and mechanical boards respectively.
Does NumLock affect gaming performance?
No. NumLock state does not affect polling rate, input latency, or scancode timing for non-numpad keys. If you want to verify your keyboard is polling correctly, use the Mouse Polling Rate Test for your mouse and the keyboard tester for key registration.
My BIOS has no NumLock setting. What do I do?
Rely entirely on the registry fix. Set InitialKeyboardIndicators to 2 in both HKEY_USERS\.DEFAULT and HKEY_CURRENT_USER. Windows Winlogon reads this value and sends the LED report to the keyboard after the desktop loads, which overrides whatever state the BIOS left the keyboard in.
How do I know if my NumLock key is physically broken versus a software issue?
Use the Keyboard Test. If key code 144 does not appear when you press NumLock, the switch or the trace is dead. If 144 appears but the system behavior is wrong, the switch is fine and you have a software or firmware configuration problem.
Launch Companion Diagnostic Tool
Test your hardware right now in your browser with zero install:
Open Keyboard Tester