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

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:

1. In Quick Connect and Ribbon Search, does the regular “.” key (not the numpad one) work?
2. 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?
3. 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,

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

Hello rodtormente,

Thank you for your patience and for the thorough testing and details you provided. This information clearly shows the behavior is isolated to the Quick Connect field and the Ribbon Search bar, which helps us narrow down the cause.

We are currently investigating this internally. Once we have an update, a workaround, or a fix recommendation, we will get back to you.

Best regards,

Hello rodtormente,

Thank you for your patience.

Our development team tested internally with a Portuguese (Brazilian ABNT2) keyboard and was unable to reproduce the issue on their end. To help us narrow down what is different in your environment, could you please confirm whether the problem still occurs after updating to Remote Desktop Manager 2026.1.15.0?

If you can test 2026.1.15.0, please verify specifically:

• Whether the numpad “.” still does not work in the Quick Connect field and the Ribbon Search bar
• Whether it continues to work normally in other text fields within the application
• 
  

This will help us determine if the issue was resolved in a later build or if we need to investigate further with additional environment-specific factors.

We appreciate your collaboration!

Best regards,