Windows 10: Enable or Disable Num Lock on Sign-in Screen in Windows 10

thanks for the info, madmax2



registry scan above

 

Here's how I did it. I think it's easier. Please see my "Steps 1 and 2" on this page (the 2nd post) for the fastest way, using the PIN, and disabling the Logon Lock Screen . . . With this BIOS setting, why isn't NumLock enabled / "On" whe... - HP Support Forum - 6186353

 

Num Lock at log in screen after boot has been automatically enabled since intro of Creators Update, 1703.

 

I recently updated to Win 10 version 1709, which is the latest, and it's not "on" for the Logon PW after a cold boot.

What if I want NumLock "on" for convenience, in case I want to Logon by Password?

None of the following worked, so that I can get NumLock "on" from a cold boot (Restart/warm boot, yes, it stays "on").

HKEY_USERS \ .DEFAULT \ Control Panel \ Keyboard \ InitialKeyboardIndicators
Default = 2147483648 . . . Change it to (none of these have any effect):
2147483650
2
80000002 . . . in HEX

HKCU \ Control Panel \ Keyboard \ InitialKeyboardIndicators
Default = 2 . . . I see that it resets itself to this . . . Change it to (none of these have any effect):
2147483650 . . . no effect
80000002 . . . in HEX

BIOS Setup (F10) / Advanced / System Options / NumLock on at Boot /
. . . Disable (default?) / Enable . . . I tried all of the above with this on "Enable" - and it had no effect

So, using the PIN, where NumLock is not on, and I don't have to press "Enter," is the way to go.

 

I read that the "on" setting can work, or not, based on your hardware.

Why do people think "Fast Boot" off would be the fix? I think it's doing a fast boot in some way like hibernation (using cached data and settings), so what makes someone think that it would skip over the NumLock "on" setting?

 

"I recently updated to Win 10 version 1709, which is the latest, and it's not "on" for the Logon PW after a cold boot. .....None of the following worked, so that I can get NumLock "on" from a cold boot (Restart/warm boot, yes, it stays "on").

HKEY_USERS \ .DEFAULT \ Control Panel \ Keyboard \ InitialKeyboardIndicators
Default = 2147483648 . . . Change it to (none of these have any effect):
2147483650

HKCU \ Control Panel \ Keyboard \ InitialKeyboardIndicators
Default = 2 . . ."

In 1607, changing the value to 2147483650 fixed the Num Lock problem for me. Ever since 1703 and incl 1709, I have not had to do anything at login screen. These are my registry values. I cold boot every morning and use PIN. Update: Just Shut down (Shift+Shut Down) and signed in with MS pass. Num lock was auto On so I just typed in using number pad.

 

I'm curious . . . from a cold boot, if you have that setting, and instead of PIN, do "logon with password" . . . do you see that your NumLock is "on" . . . or not?

 

I figured this out, from where you said to use (Shift+Shut Down) - thank you!

I'll add the following to my post on the HP site:

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

What if I want NumLock "on" for convenience, in case I want to Logon by Password?

. . . and that Registry setting doesn't work? . . . I see that it's because . . .

I'm using Classic Shell 4.3.1 . . . and it's necessary to [un-check] "Enable hybrid shutdown"

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Classic Start Menu Settings / Main Menu / [un-check] Enable hybrid shutdown
. . . Then this setting that you make in the Registry will work, to make NumLock "on":

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

HKEY_USERS \ .DEFAULT \ Control Panel \ Keyboard \ InitialKeyboardIndicators
Default: 2147483648
Change it to: 2147483650

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

The way I figured this out is - if you bypass Classic Shell, and do a Windows Shutdown:
Shift + Classic Shell Start button . . . then . . . Windows "Power" button + Shutdown
after I re-booted with the above Registry setting, NumLock was on.
So, I looked in Classic Shell to see what shutdown options were available . . .
. . . there is just that one, so I tried that, and it worked.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

The shutdown and boot-up times for these are not much different, and vary (seconds):
Classic Shell, hybrid shutdown "on" . . . 15-19 / 21
Classic Shell, hybrid shutdown "off" . . . 13-17 / 22
Windows, hybrid shutdown "off" (must be) . . . 14 / 22

 

"instead of PIN, do "logon with password" . . . do you see that your NumLock is "on" . . . or not? .....
I'm using Classic Shell 4.3.1 . . . and it's necessary to [un-check] "Enable hybrid shutdown"

The num lock is always on, password or PIN. My screenshot is of the default 1709 registry values. This was introduced in 1703 (This is probably why the thread has been dormant all year. ) -
https://www.howtogeek.com/278132/wha...eators-update/

• Improved PIN Login: When signing in with a numerical PIN, you don’t have to worry about pressing the Num Lock key. The PIN field will behave as if the Num Lock key is always enabled. No more fighting with Num Lock!

I also use Classic Shell but do not use Hybrid shutdown, as I have hibernation (hence Fast startup) disabled. Thanks for your time in deciphering that scenario for older versions.