New
#21
lol I hadn't seen that tutorial. The funny thing is that in Vista & Win7, I didn't need to change anything to have Numlock working from boot on any of my home desktops. On Win8 my main desktop required the value '2' for InitialKeyboardIndicators. In Win10, on the rig in my sig, the value '2' only worked from a warm boot but would fail on a cold boot. The only way to get it to work was to change the value to either '2147483650' decimal or '80000002' in hex. The 'Fast Startup' option just appears to make it work for all machines although is not required for mine. Why? I don't know. It just seems that everyone has unique hardware / software configurations that require slightly different settings. It would be much easier if MS had a simple numlock setting for the keyboard in the Control Panel somewhere.
Edit: If you look at another tenforums thread Numlock defaults to off, you can see how the value '2' occasionally fails in a cold boot for other folks too.