RDP v2026.3.15.0 - keyboard shortcuts for tab navigion (previous, next) sometimes are not functional

Hello Ales,

Thank you for reaching out!

Each Remote Desktop Manager shortcut has a Mode, shown in File > Settings > Keyboard (Keyboard shortcuts customization). Select previous tab, and Select next tab use "When not in session" by default. In that mode, the shortcut works while focus is on the Remote Desktop Manager interface, but it is ignored once you click inside a session tab.

To narrow it down, could you tell us:

• Which Mode is set for Select previous tab and Select next tab (Default, When not in session or Global hotkey)

• Whether the shortcut fails only after you have clicked inside a session, and which session type that was

If the Mode is "When not in session", try setting both to Default, click Save, and restart Remote Desktop Manager, then let us know if it still happens.

Thank you in advance!

Best regards,

Hello.

Both keyboard shortcuts are in Default Mode.

It does not matter if I'm in inside session windows and it does not matter if it is SSH sessin terminal window or RDP session window.

When I close RDM application and execute it again sometimes it repair keyboard shortcuts tab navigation trouble.

Thank you,

Best regards,

Ales

Hello Ales,

Thank you for the details. Shortcuts set to Default mode only work while the keyboard grab icon (the magnet) in the status bar at the bottom right of Remote Desktop Manager is enabled. When it is turned off, every Default mode shortcut stops working, both inside and outside sessions. This setting is saved, so it stays off after a restart until the icon is clicked again.

Next time the tab shortcuts stop working, could you check the following before restarting Remote Desktop Manager:

• Is the magnet icon in the status bar enabled? When it is off, hovering over it shows "Click to grab the keyboard". If so, click it once and try the shortcuts again.

• If it is enabled, do other shortcuts still work with the focus on the Remote Desktop Manager interface, for example Ctrl+Shift+L to go to the Dashboard?

Thank you in advance!

Best regards,

Hello.

• yes, the magnet icon is enabled

• no - nor another keyboard shortcuts like CTRL+SHIFT+L are not working

Thank you very much.

Best regards

Ales

Hello Ales,

Thank you for confirming. Since Ctrl+Shift+L stops working as well, Remote Desktop Manager stops handling all of its shortcuts at once.

The next time it happens, could you try the following before restarting:

• Click once on any entry in the navigation pane, then press Ctrl+Shift+L.

• If nothing happens, press and release Alt, Ctrl and Shift once each, then press Ctrl+Shift+L again.

Please let us know which step brought the shortcuts back, if any. It would also help to know what you were doing just before it stopped, for example waking the PC from sleep, unlocking it, switching windows with Alt+Tab, or if Remote Desktop Manager froze for a moment.

Thank you in advance!

Best regards,

Hello.

• CTRL+SHIFT+L do nothing in navigation panel

• ALT, CTRL, SHIFT (once each) and then CTRL+SHIFT+L also do nothing

I have no functional solution for brought the shortcuts back another then restart application or computer. Now I restarted RDM application for example 5 times without success shortcuts functional.

Thank you very much.

Best regards,

Ales

Hello Ales,

Thank you for testing these steps!

Your results tell us a few things. All of Remote Desktop Manager’s shortcuts stop at the same time, even with the keyboard grab enabled. Restarting the application does not fix it, but restarting Windows sometimes does. So the problem is not the shortcut configuration. Remote Desktop Manager has stopped receiving the keys, and that state outlasts the application itself.

The steps below will help us find out why.

1. If the shortcuts are not working right now, please check these first:

• Leftover process: Close Remote Desktop Manager, open Task Manager, go to the Details tab and check whether RemoteDesktopManager.exe is still running. If it is, end it, reopen Remote Desktop Manager and test Ctrl+Shift+L. A process left running in the background would explain why restarting the application does not help but restarting Windows does.

• Other applications: Test whether shortcuts work in other applications. If they also fail, the cause is on the Windows side rather than in Remote Desktop Manager.

2. Then restart Windows, and set up the following so we capture the next occurrence:

• Disable API hooking: Go to File – Settings – Entry types – Sessions – Remote Desktop (RDP) – Advanced and set Enable API hooking to Disabled. We are aware of an issue in versions 2026.3.14 and 2026.3.15 where keyboard input can break in embedded RDP sessions after using Alt+Tab, and a fix is planned for an upcoming version. If the shortcuts keep working with this setting disabled, that confirms your issue is related. Please do not change this setting if you connect through Devolutions Gateway.

With this information, we can either confirm the cause or at least we will have everything we need to reproduce it.

Thank you in advance!

Best regards,

Hello Ales,

Thank you for testing these steps!

Your results tell us a few things. All of Remote Desktop Manager’s shortcuts stop at the same time, even with the keyboard grab enabled. Restarting the application does not fix it, but restarting Windows sometimes does. So the problem is not the shortcut configuration. Remote Desktop Manager has stopped receiving the keys, and that state outlasts the application itself.

The steps below will help us find out why.

1. If the shortcuts are not working right now, please check these first:

• Leftover process: Close Remote Desktop Manager, open Task Manager, go to the Details tab and check whether RemoteDesktopManager.exe is still running. If it is, end it, reopen Remote Desktop Manager and test Ctrl+Shift+L. A process left running in the background would explain why restarting the application does not help but restarting Windows does.

• Other applications: Test whether shortcuts work in other applications. If they also fail, the cause is on the Windows side rather than in Remote Desktop Manager.

2. Then restart Windows, and set up the following so we capture the next occurrence:

• Disable API hooking: Go to File – Settings – Entry types – Sessions – Remote Desktop (RDP) – Advanced and set Enable API hooking to Disabled. We are aware of an issue in versions 2026.3.14 and 2026.3.15 where keyboard input can break in embedded RDP sessions after using Alt+Tab, and a fix is planned for an upcoming version. If the shortcuts keep working with this setting disabled, that confirms your issue is related. Please do not change this setting if you connect through Devolutions Gateway.

With this information, we can either confirm the cause or at least we will have everything we need to reproduce it.

Thank you in advance!

Best regards,

@Sam Moynihan

Hello Sam.

ad 1) I executed RDM, keyboard shortcuts without success. I closed RDM and check process manager - no process RemoteDesktopManager.exe. I executed RDM again and I tested keyboard shortcuts - without success (two SSH terminal session), but I thing that keyboard shortcuts are catched by SSH terminal session (because cursor moves or some chars are typed to terminal console) and not by RDM.

If I pressed CTRL+SHIFT+L (dashboard) - terminal screen is reseting

If I pressed CTRL+ALT+PAGEUP (previous tab) - current terminal line moves down about one line

If I pressed CTRL+ALT+PAGEDOWN (next tab) - current terminal line moves up about one line

ad 2) I checked settings of Enable API hooking, but I had already to Disabled.

Thank you very much for your help.

Best regards,

Ales

Hello Ales,

Thank you for testing these steps!

Your results tell us a few things. All of Remote Desktop Manager’s shortcuts stop at the same time, even with the keyboard grab enabled. Restarting the application does not fix it, but restarting Windows sometimes does. So the problem is not the shortcut configuration. Remote Desktop Manager has stopped receiving the keys, and that state outlasts the application itself.

The steps below will help us find out why.

1. If the shortcuts are not working right now, please check these first:

• Leftover process: Close Remote Desktop Manager, open Task Manager, go to the Details tab and check whether RemoteDesktopManager.exe is still running. If it is, end it, reopen Remote Desktop Manager and test Ctrl+Shift+L. A process left running in the background would explain why restarting the application does not help but restarting Windows does.

• Other applications: Test whether shortcuts work in other applications. If they also fail, the cause is on the Windows side rather than in Remote Desktop Manager.

2. Then restart Windows, and set up the following so we capture the next occurrence:

• Disable API hooking: Go to File – Settings – Entry types – Sessions – Remote Desktop (RDP) – Advanced and set Enable API hooking to Disabled. We are aware of an issue in versions 2026.3.14 and 2026.3.15 where keyboard input can break in embedded RDP sessions after using Alt+Tab, and a fix is planned for an upcoming version. If the shortcuts keep working with this setting disabled, that confirms your issue is related. Please do not change this setting if you connect through Devolutions Gateway.

With this information, we can either confirm the cause or at least we will have everything we need to reproduce it.

Thank you in advance!

Best regards,

@Sam Moynihan

Hello Sam.

ad 1) I executed RDM, keyboard shortcuts without success. I closed RDM and check process manager - no process RemoteDesktopManager.exe. I executed RDM again and I tested keyboard shortcuts - without success (two SSH terminal session), but I thing that keyboard shortcuts are catched by SSH terminal session (because cursor moves or some chars are typed to terminal console) and not by RDM.

If I pressed CTRL+SHIFT+L (dashboard) - terminal screen is reseting

If I pressed CTRL+ALT+PAGEUP (previous tab) - current terminal line moves down about one line

If I pressed CTRL+ALT+PAGEDOWN (next tab) - current terminal line moves up about one line

ad 2) I checked settings of Enable API hooking, but I had already to Disabled.

Thank you very much for your help.

Best regards,

Ales

@aleskomarek

I closed RDM second time and I executed RDM again and keyboard shortcuts are ok. It is strange.

Shortcuts in other applications has no troubles.

Hello Ales,

Thank you for the update, and for testing so carefully. It is useful that the shortcuts came back after the second restart, because it tells us the problem is not in the shortcut configuration itself.

To narrow it down, could you tell us:

1. What type of entry are the two "terminal" sessions (for example SSH Shell, PuTTY, PowerShell or Windows Terminal)?

2. When it happens, is there any session open at all? Does it also happen right after starting RDM, before opening any session?

3. What keyboard layout do you use? Do you have other keyboard software running (AutoHotkey, a keyboard or mouse utility, another remote tool)?

4. Does it tend to start after something specific, such as locking or unlocking the PC, waking it from sleep, or switching windows with Alt+Tab?

The next time it happens, please do not restart RDM first. Open Help > Troubleshooting > Application logs, and send us what you see there from that moment.

As a test, you could also change the two tab shortcuts to a combination without Alt, for example Ctrl+Shift+PageUp and Ctrl+Shift+PageDown.

Please let us know whether the behavior is the same.

Thank you in advance!

Best regards,

Hello Ales,

Thank you for the update, and for testing so carefully. It is useful that the shortcuts came back after the second restart, because it tells us the problem is not in the shortcut configuration itself.

To narrow it down, could you tell us:

1. What type of entry are the two "terminal" sessions (for example SSH Shell, PuTTY, PowerShell or Windows Terminal)?

2. When it happens, is there any session open at all? Does it also happen right after starting RDM, before opening any session?

3. What keyboard layout do you use? Do you have other keyboard software running (AutoHotkey, a keyboard or mouse utility, another remote tool)?

4. Does it tend to start after something specific, such as locking or unlocking the PC, waking it from sleep, or switching windows with Alt+Tab?

The next time it happens, please do not restart RDM first. Open Help > Troubleshooting > Application logs, and send us what you see there from that moment.

As a test, you could also change the two tab shortcuts to a combination without Alt, for example Ctrl+Shift+PageUp and Ctrl+Shift+PageDown.

Please let us know whether the behavior is the same.

Thank you in advance!

Best regards,

@Sam Moynihan

Hello Sam.

• SSH terminal session

• It does not matter - I tested with no other session opened.

• Yes - I user AutoHotKey. But then it occurred to me that this might actually be the problem, so I ran tests without this application. Without success.

• No other special actions.

BUT I described my observation in a ticket: "RDP v2026.3.15.0 - inactive focus to SSH terminal window when switching tabs":

I see the difference between your tests and my tests. I open whole folder with sessions with CTRL + ENTER. Goal is this:

- You are moving between session by clicking on tab and it is functional.

- BUT I moving between tabs by keyboard shortcuts. I switch from first tab to next tab by keyboard shortcut CTRL+ALT+PGDOWN (next tab navigation) and the cursor in second session is inactive and from now are keyboard shortcuts between tab navigation not functional.

I hope that it helps.

Thank You very much.

Best regards,

Ales

I'm not sure if this is the same issue that I have. My issue is: when I open several SSH sessions, I am able to switch between them using CTRL+TAB, or CTRL+SHIFT+TAB. This is what I expect.

But when I press CTRL+TAB when the rightmost session is active (or CTRL+SHIFT+TAB when the leftmost session is active), it switches to the Dashboard, and then it is stuck at Dashboard - those above keys don't work anymore. I'd like to be able to just switch away from the Dashboard to the session next to it by pressing CTRL+TAB, and it should be the default behavior.

This is currently 3.15, but I think it was the same in 3.16.

Thanks in advance.

@RDMTinkerer

Hello.

First move to next tab is functional. But on the next tab is not focused cursor in the ssh terminal session (like your screenshot). And then is not functional moving to next tabs.

Thank you.

Best regards.

Ales

No no, it's the opposite. It does work for me when in SSH session, but stops working on the Dashboard tab.

Hello Ales,

Thank you for the additional details.

Our team reproduced the issue you described: when sessions are opened together with Ctrl+Enter, the next tab has an inactive terminal cursor, and the tab shortcuts stop working. Our developer team has a fix for it, planned for an upcoming update. We will let you know as soon as it is available. Until then, clicking each tab once after opening the folder keeps the shortcuts working.

Once you have installed the update, could you test both cases and let us know the result?

• Opening the folder with Ctrl+Enter and moving between tabs with your shortcuts.

• Using the shortcuts after RDM locks and you unlock it with your PIN.

Thank you in advance!

Best regards,

Hello Ales,

Thank you for the additional details.

Our team reproduced the issue you described: when sessions are opened together with Ctrl+Enter, the next tab has an inactive terminal cursor, and the tab shortcuts stop working. Our developer team has a fix for it, planned for an upcoming update. We will let you know as soon as it is available. Until then, clicking each tab once after opening the folder keeps the shortcuts working.

Once you have installed the update, could you test both cases and let us know the result?

• Opening the folder with Ctrl+Enter and moving between tabs with your shortcuts.

• Using the shortcuts after RDM locks and you unlock it with your PIN.

Thank you in advance!

Best regards,

@Sam Moynihan

Hello Sam.

Great news. I will test new version as soon as possible.

Thank you very much for your help.

Best regards,

Ales

Hello,

Thank you for your patience while our team looked into the issue you reported.

I'm happy to let you know that the latest version of Remote Desktop Manager (2026.3.17.0) includes a fix for this problem. You can download it from our website here:

https://devolutions.net/remote-desktop-manager/download/

Once you have installed the update, could you please test it in your environment and confirm that everything now works as expected? If the issue persists or if you notice anything unusual related to the same original problem, just reply to this message with a few details, and we will be glad to look into it further.

Thank you for your collaboration.

Best regards,

Hello,

Thank you for your patience while our team looked into the issue you reported.

I'm happy to let you know that the latest version of Remote Desktop Manager (2026.3.17.0) includes a fix for this problem. You can download it from our website here:

https://devolutions.net/remote-desktop-manager/download/

Once you have installed the update, could you please test it in your environment and confirm that everything now works as expected? If the issue persists or if you notice anything unusual related to the same original problem, just reply to this message with a few details, and we will be glad to look into it further.

Thank you for your collaboration.

Best regards,

@Maxim Robert

Hello Robert.

Great news.

I tested new version of RDM and I can't simulate previous problems.

Now it seems that the troubles are fixed.

Thank you very much.

Best regards,

Ales

Hello,

Thank you for your feedback. We're pleased to hear that everything is now working as expected.

Please don't hesitate to create a new thread if you need any further assistance.

Best regards,