NumPad Decimal key (Numpad .) not working in Quick Connect/Ribbon Search

NumPad Decimal key (Numpad .) not working in Quick Connect/Ribbon Search - Version 2026.1.12.0

Published 5 days ago

Since updating to version 2026.1.12.0 (64-bit), the decimal key on the numeric keypad has stopped working specifically in the Quick Connect field and the Ribbon Search bar.
My Keyboard Layout is Brazilian ABNT2.
The ‘.’ (dot) key on the numpad does not input any character, but all other keys work correctly, including the /, *, -, +, and , keys.
To troubleshoot the issue, I have already disabled hardware acceleration, toggled software rendering mode, reset keyboard shortcuts and layout, and changed the keyboard hook settings in the RDP properties

All Comments (2)

Eduard Sepúlveda López

Published 4 days ago

Hello rodtormente,

Thank you for the details. Since this started after upgrading to 2026.1.12.0 (64-bit) and only occurs in the Quick Connect field and the Ribbon Search bar, this points to a UI input-handling issue in those specific controls rather than an RDP session keyboard setting.

Also, the “Keyboard Hook” option you changed applies to RDP session entries, so it typically affects input inside the RDP session window, not application UI fields like Quick Connect or Ribbon Search.

To isolate this quickly, could you please confirm:

In Quick Connect and Ribbon Search, does the regular “.” key (not the numpad one) work?
Does the numpad decimal key work in other RDM text fields (for example: editing an entry name, Notes, or Description), or is it only those two fields?
What is your Windows regional decimal symbol set to (comma or dot), and does switching it (temporarily) change the behavior after restarting RDM?

If you can include your Windows version/build, that will help us correlate with any OS-level input changes.

Thanks in advance!

Best regards,

Eduard Sepulveda Lopez

rodtormente

Published 3 days ago

Yes, the regular “.” key (next to the “M”) works, and Alt+46 also works.

In other fields within the application, the numpad “.” works normally. The issue only occurs in the Quick Connect field and the Ribbon Search bar.

I changed the RDP settings because it didn’t make sense for the “.” to stop working, so I tried adjusting any keyboard-related option I could find.

When switching to the US English keyboard layout, the numpad “.” stops working everywhere, including in Windows itself. This is not unexpected, since on the US layout that key typically behaves differently (as a decimal key tied to the system’s regional settings).

I am using Microsoft Windows 10 Pro (10.0.19045). I am aware it is out of support, but I also tested on a Windows 10 machine upgraded to Windows 11, and the behavior is the same.

Thanks in advance for your help