Question Locked

Turning off Num Lock at boot up

0 helpful
5 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Hey guys. How are you doing?
I have a problem, well, not a problem but an annoyance.
I have a Toshiba L20 laptop, the thing is that when Windows boots up the numeric keypad automatically turns itself on. As I have to enter a password I have to turn manually off and then type it.
Other thing I noticed is that when I logg off the numeric keypad is turned on again, this is really strange.
I have been using laptops for a while and this is the first time I've seen this behavior.
Does anyone knows if this is normal o there is a way to avoid this situation?

Thanks a lot
Kind regards,
Alfonso

5 replies

by retro77

Go into the BIOS and make sure numlock is off at bootup

At Windows start, dont do anything except turn numlock off, then log in as the local admin. If numlock turnerd back on, turn it off. Reboot.

by alfa11

Checked the registry and the value was already "0".
The first instructions worked for me.
Thanks a lot to both of you.

by crazy taco

I've found that usually if the numlock is coming on by default, it is because it is set turn on by default in the BIOS. Try going into your BIOS on bootup and checking to make sure the numlock isn't set to come on automatically.

If that isn't the case though, I've found that there are a few places in the Windows registry that can be causing this problem. If it only happens for your account, you can go to the following registry location: HKEY_CURRENT_USER > Control Panel > Keyboard. Then check your InitialKeyboardIndicators variable. If this is 2 (or if the number in binary would have the 2^1 bit set) then the number lock is on. Change to 0 to turn off the numlock.

If, however, you see that the numlock light is coming on for every account, and it isn't because of the BIOS, then you will need to check a different registry location. Go to HKEY_USERS > .DEFAULT > Control Panel > Keyboard, and then see if InitialKeyboardIndicators is set to 2 here as you did in the last step. If it is, change it to 0.

I had this same issue and was able to fix it with the third option, but have also fixed numlock issues using option one.

This discussion is closed to new replies.