J. P. Gilliver (John) wrote:

VanguardLH WROTE:

Same happen when you move the keyboard to a different computer?

Laptop.

Laptops don't have room for a number pad, so they overlay the numpad
keys atop the alphanumeric keys at the right end. Look at:

https://www.replacementlaptopkeys.co...yboard_key.jpg
(click to enlarge)

Notice the 0 (zero) key at the top row has 3 characters possible: 0
(zero), right parens, and / (divide). I don't remember how it is done
but there is some way to turn on the numpad characters for those keys.
However, if that were the case, I would think you would get / (slash)
for each press on Shift+0 that doesn't appear to do anything. I would
find out what toggles the numpad and toggle it a couple times and then
once more, if needed, to turn off the numpad to make sure the toggle
state didn't get confused for those keys.

Have you yet cold booted the laptop? I don't mean shutdown into
low-power or hibernate mode but completely powered off. For a cold
boot, the CPU sends a reset signal to all hardware to make sure it
starts in a known state. I've had hardware that got confused to what
state it should be, and a cold boot gave it the reset to start at a
known initial state.

Do you have Sticky Keys enabled in Windows? You may not have
deliberately enable it but did so accidentally. Pressing Shift 5 times
in rapid succession will turn on Stick Keys. I've done that a couple
time when ****ed at something and ended up hitting the Shift more than 5
times and wondering what that beep was for.

You press Shift+0 but don't get a right parenthesis character. The
question is if there is a hardware fault where the keypress is not
registered; i.e., no scan code for the keypress is sent. The other
possibility is that some software has usurped that key combo. Keyboards
generate 2 scan codes per keypress: keydown and keyup. That way,
software can see if you pressed a key or released it. It has too long
since I used a key scan code tool to remember what I've used. I
remember running it and then I'd press and hold down a key to see what
the tool said was that scan code. Then I'd release the key to see what
different scan code got generated for that action. I wasn't using it to
find missing scan codes but to define some key remapping. Keyboard
keyboard remapping software is also a possibility for the missing scan
code for downpress+0 issuing the scan code for that key combo.

I'd first boot Windows into its safe mode to see the problem still
exists. If so, I'd try a keyboard scan code reporting tool that showed
me both downpress and release of keys for their scan codes.