You boot up your PC, sit down, type your PIN to log in, and... nothing happens. Or worse, you start typing letters and get numbers instead (looking at you, laptop users). You glance down. The little green light is off. Again.
The real chaos started with (enabled by default). When you shut down a modern PC, Windows hibernates the kernel. It often saves the last keyboard state, but ignores the BIOS setting. Meanwhile, your BIOS (the firmware that boots the PC) has its own "Num Lock state" setting. These two often conflict. num lock on startup
Let’s dive into the bizarre BIOS battle, the Windows registry hack, and the quiet war between the numeric keypad and arrow keys. To understand Num Lock, you need to travel back to 1981. The original IBM PC keyboard didn't have separate arrow keys. Instead, the number pad pulled double duty. Num Lock (Numeric Lock) was the toggle that switched the pad from "Numbers" to "Navigation" (Home, End, PgUp, Arrows). You boot up your PC, sit down, type your PIN to log in, and
Fast forward 40 years. We now have dedicated arrow keys. But the hardware standard never fully died. You glance down
Imagine trying to type "Hello" and getting "H3LL4". That is the laptop user's nightmare. For you, keeping Num Lock at startup is the priority. The Ultimate Verdict: Should you fix this? Fix it if: You use a desktop with a full keyboard, or you use an external number pad for Excel/data entry. The productivity gains are worth the 3 minutes of registry editing.
Because manufacturers hide the number pad inside the main keyboard. Look at the keys 7, 8, 9, U, I, O, J, K, L . If Num Lock is , those keys produce 7,8,9,4,5,6,1,2,3 .
