Running new Windows 10 Home 64 bit PC for but a few days I have been irritated that as it has booted I always have to switch numlock on. 100% of boot occasions, numlock is turned off. Can anyone tell me where I can configure the machine to stop it doing this?
To enable NUM LOCK before a user logs on, follow these steps:
- Run Registry Editor.
- Move to HKEY_USERS.DefaultControl PanelKeyboard
.- Change the value for InitialKeyboardIndicatorsfrom 0 to 2.
Num Lock - Enable or Disable on Sign-in Screen in Windows 10
WOW that was quick. Many thanks.
this doesn't work when starting from a cold boot... only from a restart
Doesn't it? I'm sure it does with me. I'll have to check.this doesn't work when starting from a cold boot... only from a restart
I just checked. Numlock is on through a restart, but from a cold boot, Numlock is *not* on by default.Doesn't it? I'm sure it does with me. I'll have to check.
IMO, not a huge deal, but there it is...:-)
I did the reg. fix you posted earlier, BTW...
Joe
This solution below works from a cold boot. I've used it on a large number of PCs and always works. I've used it for devices at work, home and for friends.
Num Lock key on at bootSometimes it is not necessary to untick (disable) fast start-up. It just appears to make this solution more universal (although I don't know why)Go to the power options via settings
Make sure the tickbox for "Turn on fast start-up (recommended)" is UNTICKED
Then open up the registry (regedit) and go to
HKEY_USERS.DEFAULTControl PanelKeyboard
Change the value of InitialKeyboardIndicators to 2147483650
80000002 can also work in place of 2147483650 as it is the hexadecimal equivalent.
This is the fix which just worked for me:
Num Lock - Enable or Disable on Sign-in Screen in Windows 10 - Windows 10 blog
• Turn off fast start-up (if not already off)
• Run REGEDIT and go to HKEY_USERS.DEFAULTControl PanelKeyboard
• Change the value of InitialKeyboardIndicators to 2147483650
• Reboot & turn on fast start up (if you want it)
This issue reappeared after the Anniversary Update and the fix at Post 8 worked.
