Ridiculous Numlock Behavior

Hello all, I hope someone can shed some light on this issue that I've been mashing my head against the wall with.

I am actually fairly experienced with computer use and the like... but this one is driving me nuts.
A friend of the family is having this strange problem where the number pad keys do not work. Of course, the problem is that numlock is not on. Easy fix, right? Turn numlock on. Nope.

Numlock *IS* on.

I have read numberous discussons on the topic of numlock being a wierdo, and came accross the InitialKeyboardIndicators registry key. If this is a 0, no locks are set, if it is 2, Numlock is set. The numbers 0 through 7 let you set NumLock, CapsLock, and Scroll lock.

His value was 2147483648.
I changed it to a 2.

The problem persists. I made a startup script containing this:
set WshShell = CreateObject("WScript.Shell")
WshShell.SendKeys "{NUMLOCK}"

This didn't work either.

Why didn't either of these work? Well, because his NumLock *IS* on, and let me explain what I mean by this:
If I remote into his PC, and open OSK, then tell him to type using the numpad, I see the following:
1. Numlock IS highlighted
2. Numlock goes off WHILE HE PRESSES KEYS
3. Numlock goes back on after he is done

This is what happens if I intervene:
1. Numlock IS hightlighted.
2. Numlock goes off for his first NumPad button press.
3. I press numlock remotely (from the OSK)
4. All subsequent NumPad button presses result in numbers
5. The problem is fixed
6. He reboots, problem is back

The registry does not change between boots, and the value of InitialKeyboardIndicators is still 2.
I removed my script to force numlock on because it clearly does nothing.
Oddly enough on my system, that script toggles the state of numlock, on his, it just turns numlock on if it is off, and does nothing if it is already off.
Again, nothing seems to fix the problem except for me pressing "numlock" while he is pressing keys on the NumPad.

Can anyone shed any kind of light on this ridiculous problem?
The other half of the problem is that he is the kind of user who does not know what numlock is. He's had the computer for months now, and the same keyboard for his past few computers, so it's not like new hardware is influencing anything.

Oh, and just incase someone suggests it, NumLock is enabled in the BIOS.

 

First, welcome to Computer Help Forums!
Is this a laptop and if so does it have a full keyboard?

Some laptops that do not have a separate numerical keypad next to the QWERTY keypad have a secondary function that allows certain keys to function like a calculator keypad. It requires the use of the FN key along with the numlock key. In some cases this carries over to their newer models even though there is a separate and distinct keyboard.

Are the numbers over the QWERTY functioning normally?

 

Thanks for the welcome!

This is a desktop PC running Windows 7.
It is a Microsoft MultiMedia Keyboard with a full NumPad.
The numbers over the QWERTY keys are functioning normally.

 

What is the model number of the keyboard? Is it supported by keyboard specific software or is it using generic windows drivers?

 

I don't quite have access to the model number, but it is quite literally the "Microsoft Digital Media Pro Keyboard" so it is likely model number: BX1-00005

The driver running it is Microsoft IntelliType Pro (version 8.20.409.0), and he needs that to run becuase he uses the shortcut keys.

 

My guess is that a setting has been altered or compromised. If the control panel has separate settings for this particular board try restoring defaults. If it has an F-lock key try resetting it and the same if it has an fn key even thought it is not a alptop. See if FN + numlock works.

I would also consider uninstalling the keyboard software and then first try to get it to be recognized with just the generic drivers and see if that cures the specific problem and then reinstall the software after that. I would suggest using Revo since you made registry changes. ( I would also undo the changes using a system restore.)

 

Just so no one thinks I found a solution and have failed to report it, I haven't had an opportunity to try the latest suggestion, but I intend to do so shortly.

Does anyone else have problems with iType (IntelliType)? I don't personally have an MS keyboard, but the person I'm attempting to help has always, and iType is pretty terrible. It constantly fails to run on startup, constantly "forgets" all the favorite key settings, and half of its settings are "read-only" if you access them through the control panel.

It's such terrible software, is there any known freeware or open-source keyboard driver (favorite key assignment) alternatives? I imagine that if I don't use iType at all, everything should still work as keyboards are pretty standardized, my only issue is that the favorite keys absolutely must work, and those are non-standard buttons (I think they translate to strange ALT+number sequences).

 

So I've finally tried removing IntelliType, and reinstalling it, etc.

No joy, I think I need a service to run on startup, check to see if Numlock is on, if not, force it on and put the keyboard into state 2 (numlock only).

 

For everyone ever having problems with NumLock and Windows 7, this is the solution:

Go to Accessories
then choose easy of access
then start ease of access control center.
choose make the keyboard easier to use,
uncheck the box infront of 'turn on mouse keys'
then press apply,then ok,and make sure the NUMB LOCK key is engaged.

"Mouse Keys" allows you to move the mouse with your numpad. It randomly gets turned on my accident sometimes.
It will make your numpad behave incredibly strangely. So, if your OSK (on screen keyboard) is doing different things than your actual keyboard, "mouse keys" is the reason why.

Hopefully this helps everyone else out there with this issue.
Note: this is after I wrote a startup application to check the numlock, capslock, and scroll lock states and set them (on, off, off).

FINALLY!