Numeric keypad problem

OK, I think I’ve dealt with this long enough. I am having persistent problems with version 2024 not recognizing input from the numeric keypad. It does not matter whether it’s a PC and Pro or anything else and the free version. What the hell is going on here?

Num lock?

We have done some numeric keypad fixes. It would be worth checking if you’re up to date. The version your profile says you are using isn’t the latest version.

In the past I’ve had issues like this whilst using SU (even if it was set to English) on a French language OS (Windows in French) & I have to go deep into windows settings somewhere to change the decimal separator from , to . & since windows is a soup, i can never remember how to get deep enough into the settings to access that option - back in older windows versions it was under Language & regional settings & quite easy to find, since w10 & 11 it’s a hassle.
But this may be not @JamesClark s case at all…

When I check for updates, it tells me I have the latest version installed.

Not only is that not the problem, but even the numbers on the keyboard won’t register at times.

I used window’s native layout creator to make a specific French layout. In my layout, the decimal key of the numpad is an actual comma, not a decimal key anymore.
it fixed everything on my end. I’m now using French (custom)

have you tried a different keyboard ? to rule out hardware defect ?

2 Likes

The first time I ran into this was when I was teaching a class on the free version. We were all using laptops. I was having no problem, but both of the students could not enter numbers using their numeric keypads. I tried using their laptops, but could not enter any numbers, unless I used the numbers on the keyboard. I have since been running into this problem on my workstation. The problem gets worse when I try to enter a number from the keypad, only to be unable to enter any numbers for keyboard also. I have never seen this problem until the 2024 upgrade.

I have not stumbled on it for years, but Windows used to have features for the disabled that could be turned on by pushing some arcane key combination. One of these features was “sticky keys” that replaced key combinations with the same keys pressed in sequence, so that when you pressed Alt or Ctrl, Windows went on to wait for the rest of the key combination - forever if a combination with a function was not reached. A physically stuck modifier key would also induce similar behaviour.

thanks for the idea, I’ll look into that !