NoMachine enabling “Mouse Keys” on Windows remote host

[hartacus]

I’m connecting from one Windows computer (Windows 11) to another Windows computer (Windows 10) on my LAN with NoMachine. After connecting, the remote host always has the “Mouse Keys” accessibility feature enabled, which makes the numpad control the mouse cursor.

I can’t disable “Mouse Keys” when the NoMachine session is active. I can disable “Mouse Keys” only after I have ended the NoMachine session, but I have to manually do this. However, next time I connect, “Mouse Keys” is enabled again.

I don’t have any of the mouse-related settings in the NoMachine player enabled, nor in the active session. I can’t find any info on NoMachine controlling “Mouse Keys”, so thought I would ask here.

As a workaround, I have changed the “Mouse Keys” setting regarding NumLock so that it works when NumLock is off instead of when NumLock is on, and I keep NumLock on. This means I can continue to use the numpad when connected via NoMachine and afterwards. However, “Mouse Keys” is still enabled when I don’t need it to be.

NoMachine server and player both running 9.6.3

[Britgirl]

Hi, NoMachine turns on Mouse Keys when it detects that no mouse is attached to the server. We know that this is not ideal, but it’s the only way for NoMachine to be able to show the cursor. In fact, the OS sets an invisible cursor when there is no mouse attached, unless Mouse Keys is enabled. If you don’t have a mouse attached to the server, you could try attaching one.

[mohsin]

I think this is controlled by Windows itself, not NoMachine.

On the remote Windows host, try going into Accessibility settings and enabling Mouse Keys there. Sometimes it does not kick in unless it is turned on directly in the system settings.

If it still does not respond in the session, it might be a permission issue. I have seen cases where accessibility features only work properly when the remote session is running with admin level access.

Also worth checking if other accessibility options behave the same way. That can help figure out if it is a NoMachine limitation or just Windows not applying the setting correctly.

[Author]

Posts