Hybrid boot: Num lock is on at the login screen if you warm boot the computer (restart). Num lock is off at the login screen if you cold boot the computer (turn on from unpowered state). Registry setting is ignored. Normal boot: Num lock is always on at the login screen no matter if you restart or cold boot. Registry setting is respected. This is what matches previous Windows versions' behavior.
This is something that annoys the crap out of me.. i use the pin code to login.. my password is an ass to type .. doesnt matter what boot cold/hybernate/sleep/warm whatever my Numberlock key is always off.. i figured it had something to do with Logitech drivers tho.
Nice, I thought it was just me / my motherboard. Very annoying when you use a passcode as your login... I hope they get that fixed soon or at least a workaround is found. Thing is it may actually be a problem on the UEFI side - in hybrid boot many initialization functions are being bypassed including keyboard initialization.
It could be the same problem.. infact it probably is related to the UEFI mentioned by docdocdoc9 above... im not sure it has anything to do with logitech drivers i just thought it might have been but if loads of other people are having it maybe its not .. i thought it was those drivers and never bother to look into it more as the logitech drivers at the time were a little buggy with remembering macros and using the LCD display correctly.
I don't seem to have a problem with this once i turned it on with the following Num Lock keep turning off 1. Go to start and type regedit.exe. 2. Navigate to HKEY_USERS\.Default\Control Panel\Keyboard. 3. You'll see an entry on the right called InitialKeyboardIndicators. The "usual" default value is 0. Double click on this entry and change the value to 2. 4. Close registry editor.
my default setting was 2147483648.. set it to 2 shut down and restarted .. still no Numberlock on /edit after some research there doesnt appear to be a way to enable it BEFORE putting in the pin pass... even using a logon script to send a NumLock keypress doesnt happen till after login. however you can get it to work via the registry setting IF you disable Fastboot... (which im not going to to)...
Another obvious bug in Windows 8 is the 'Disk Error 135' randomly. Mostly affected by SSD users. Even Enabling Hyper-V, bcdedit fix won't resolve the issue.
Additional information: I have an older motherboard with no UEFI support, so it cannot be an UEFI problem. The registry setting mentioned above is the one I mentioned in the OP. Completely ignored unless hybrid boot is turned off.
Concerning the Num Lock off or on, I made a lot of installations on differents HHDs, sometimes it's on or off, even if it is active in BIOS or with registry modifications. This is a randomly problem with Windows 8 and never had it on Windows 7 versions.
If you never completely shutdown, it will never initialize the registry. Disabling fast-boot is the only way to do a registry mod and have it actually do something..
Considering how many times a user logs in during the lifetime of an OS, yes it is. Just imagine that it was Windows XP doing this. So many people pressing the key for more than 10 years every day or even more often... That's millions of unnecessary keystrokes in the world, maybe even more than that. The only winners here are the keyboard manufacturers, how will certainly sell more products because of dead keys. Considering how many people use laptops these days where replacing the keyboard is not a trivial thing and costs a lot, it's tons of money thrown out of the windows because of a little stupid bug.