Windows 8 / 8.1 - Num Lock on startup screen

Anonymous
2013-11-13T13:32:19+00:00

Hi,

When I start up my pc and get to the screen where I need to enter my password, sometimes the NumLock key is activated, sometimes it isn't. This is really random.

I have the same problem on 2 different pc's, one win 8 and the other win 8.1

***Post moved by the moderator to the appropriate forum category.***

Windows for home | Previous Windows versions | Devices and drivers

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments
Answer accepted by question author
Anonymous
2014-02-14T02:20:14+00:00

I think I found a solution that works permanently:

http://www.youtube.com/watch?v=MiqhMktjD3A

It is also a change in the register but not the one I have read in most posts.

  • You go to the register
  • Open HKEY USERS
  • Open Default
  • Open Control Panel
  • Click on Keyboard
  • On the right side you get 4 keyboard items
  • InitialKeyboardIndicators has a number as data > 2147483648
  • Doubleclick on InitialKeyboardIndicators
  • In the small window you get you change the last 2 numbers from 48 to 50 and get 2147483650
  • Click on ok
  • Close the register window
  • Try again

I have been trying now for more than 10 times and it keeps coming up on time for the login screen no matter if it is a cold start or a restart... I hope it will last :-)

Grts

Nil

Was this answer helpful?

5 people found this answer helpful.
0 comments

85 additional answers

Sort by: Newest
Most helpful Newest Oldest
  1. Anonymous
    2017-09-28T22:59:35+00:00

    I wonder if the reason NOTHING works (to turn on Numlock at startup), is that my keypad and keyboard are completely separate devices.  (Oh, and Tech Support for the manufacturer of both says that Windows only turns Numlock on on the first device it finds.  Sigh.)

    I've tried many things, including:

    Setting ALL the initialkeyboardindicators in my Win8.1 registry (there's about 6 of them) to either 2147483650 or 2.

    Turning off Fast Boot.

    Making sure Numlock On at shutdown.

    Disabling auto-login.

    Turning on Numlock on the Onscreen keyboard at login.

    http://www.softpedia.com/get/System/System-Miscellaneous/Num-Locks-Always-ON.shtml

    Time to give up now, I've wasted 2 days on this.  I guess I'll be pressing Numlock every time I reboot.  Ack!

    Was this answer helpful?

    0 comments
  2. Anonymous
    2017-07-19T07:58:54+00:00

    I have to disable fast start to solve the Numlock problem.

    The problem is, I have to redo this on every pc after every major update!

    Was this answer helpful?

    0 comments
  3. Anonymous
    2017-07-18T16:30:58+00:00

    Do you think, for the new 1703 update, Microsoft has learned from its mistakes?

    Nope.  I still had the numlock problem on 1703.

    Like others above, I just did the registry fix to atleast not have to deal with numlock when waking up the computer, but reboot/shutdowns still have the issue so it's the same behaviour.

    FYI I would stay away from 1703, as it also forced all my networks to private / undiscoverable breaking edge, metro apps, and my VPN adapters.  Multiple attempts from support could not figure it out how to fix it and it took several days between callbacks.  (They removed the necessary feature "make this network discoverable" from the build and had no info on it being remvoed)  I did a fresh install back to the anniversary update after waiting a few more weeks to see if updates would help.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2017-07-18T11:11:58+00:00

    Do you think, for the new 1703 update, Microsoft has learned from its mistakes?

    Was this answer helpful?

    0 comments