re: Question about 'Force NumLock to Behave'
Sunday, April 3, 2005 at 5:21 pm
Posted by Perry C (1 messages posted)
You need read no further. I have the fix. Instead of messing with all those icky
registry keys, there is a simpler solution. (prepare to bang head on wall)
to permenently change the NumLock state at startup simply put NumLock in the state
of preference (On/Off) and then, when you log off, instead of using Start/Log Off,
Press "Ctrl + Alt + Del", and click on Shut down, and click Log Off from the drop
down menu. This PERMENANTLY sets the NumLock state at Startup.
(At lest it did on my Dell 3000 w/ XP Home Ed.)
re: Question about 'Force NumLock to Behave'
Thursday, April 7, 2005 at 9:44 am
Posted by Mario (1 messages posted)
After banging my head on the wall many times about this, going through all the suggestions
posted above didn't help. I checked all the registry "InitialKeyboardIndicators"
entries were set to "0", I deleted the user profiles from the "Document and Settings"
so that they are recreated and everything started fresh AND STILL the Numlock came
on at Logon.
However, eventually I figured out that I had a group policy buried somewhere in my
domain controller's Active Directory running a vbs script to turn on the numlock...
DUH! I forgot I had added this a long time ago to my Active Directory so I just restricted
the username that logs on to the laptops so that the policy doesn't apply to that
user. However, I want the other users on regular desktop computers to have Numlock
on automatically. But for the laptop user, adjusting the group policy properly took
care of this annoying problem.
I just think this is something to look at in case anyone of you has a domain environment.
re: Question about 'Force NumLock to Behave'
Sunday, September 4, 2005 at 5:39 pm
Posted by Anthony (1 messages posted)
Probably because people find this to be nothing more than an annoyance. It appears that this issue is resolved with a previous post. Start the computer up, but DO NOT log on. Toggle the num-lock so that it is OFF. Reboot the computer, and the num-lock should remain off.
re: Question about 'Force NumLock to Behave'
Friday, December 23, 2005 at 6:45 pm
Posted by Jay McMunn (1 messages posted)
Ok, I will combine ALL of the posts here into one successful solution. I tried several
of the above posts and had moderate success on different occasions. But recently
I joined a different domain than usual on my laptop and this NumLock problem cropped
up again...and now I have the solution.
First the reason: I beleive one of the previous posts is correct, this is due to
a domain policy usually. But, I am not the admin so I can't change that policy for
my user. I do not usually log into this domain, so once I disconnected from the
domain and did the steps below, I was able to resume normal NumLock behavior.
1. - Log on to Windows with your normal user. Turn off numlock, and use Ctrl-Alt-Del
and LOGOFF, NOT Shutdown.
2. - Notice now that you are back to the login window and NumLock is ON again. Turn
it off and then hit Ctrl-Alt-Del again and choose Restart.
By turning it off in both of these locations and in this order, you can be assured
that it shouldn't be on anymore. Doing it in any other order left me with Numlock
on in just about any combination of the steps above in previous posts.
That said, if you have to log into this domain all the time you will still likely
have to deal with this NumLock policy even when not connected to a docking station.
My suggestion at that point is to learn a little C# or VB.Net programming. You
can easily write a service that starts up at the Windows login screen and turns off
NumLock for you, and then have it run at startup again once windows starts. This
service can turn NumLock off for you. For the non-programmers out there, it may
not be worth the time to learn, but it'll only take 10 minutes of research to figure
out how for the programmers.
If you ask me, the domain policy really has no business forcing NumLock ON. That's
why the BIOS and Windows have the settings that they do...so the USER can choose!