Hello Support, Hello @Richard Markiewicz (pinging you as requested),
we are facing a problem that whenever we reconnect our jumphost (in order for example to resize the window), our Main RDM loses connection to the agent and doesn't allow new connections. The current open Session/s is/are locked as well.
We are running the following versions:
Remote Desktop Manager (Main + Jumphost): 2026.1.24.0 Extended maintenance from June 29, 2026
Remote Desktop Agent: 2026.2.4.0
Steps to reproduce the error (Screenshots are from LAB Machines and therefore not sensible data)
1.) Connect to the jumphost or any server through the jumphost
Sidenote:
Here the Agent Status when after connecting
And Devolutions Agent is running
2.) Right Mouse Button on the Jumphost Tab and click Reconnect
3.) Try open any other Jump or entry that goes through that jumphost. You will get the waiting window for the Devolutions Agent and afterwards the error that Devolutions Agent is not available

Devolutions Agent is still running on the Jumphost but connection to the main RDM is lost

Workaround: What fixes the problem, would be to disconnect from the jumphost and reconnect with it close. But that does bring the problem, that it always opens as a tab again and moving just this window to smaller monitor becomes (wihtout changing the entry settings) impossible. And what the reconnect doesn't fix, is the next step.
4.) Now about the locked session that I mentioned. In result of the lost agent connection, when you either close or log off the session on the Jumphost, main RDM still recognizes it as connected. Even after closing the Jump Host completely
a.) Close the session
b.) Session still showing opened
c.) Close or log off Jumphost
d.) Confirm to close all opened sessions
e.)
Jump Host closed, but previously connected session still shows as open
Workaround: You could still right-click and select reconnect on the entry to connect again, but it still keeps the session locked. Only way to release the session from this connection lock is to close RDM and open it again.
Hope this helps. Wanted to send a debug report, but for some reason it didn't record. If not reproducible by your side, I can create the Debug Report.
Thanks in advance and BR
Mauricio
6a8f2684-c21c-4249-ba4d-09f4e6c5694c.png
51d933ba-4beb-4a00-85da-40cf69c83910.png
d4403f5e-72a0-429f-b95e-bc05b2a92eaa.png
189d83b2-74fb-4ff1-80a7-645c5d0530a6.png
128e2138-5427-4e0b-a3dc-81005b274c7a.png
41076848-263f-4367-8937-6b2100ba591d.png
b8ce6059-b0b4-4381-b958-47bd6c024c15.png
afe6be2f-8aa5-4418-9717-5022739cc1ec.png
13af31d0-e694-41ff-8fd1-76e155be81e7.png
88c12f51-541e-4303-8b52-230954b0a82e.png
9b2d44db-8024-48ac-a452-29336cb67fcf.png
4115a6c2-88e3-4fe5-8c2f-16a2faa4ebe5.png
Hello Mauricio
Thanks a lot for the detailed reporting. I am sorry for the inconvenience.
So you are currently on the 2026.1 extended maintenance. Both issues you report appear to be bugs in 2026.1 but I cannot reproduce either condition in 2026.2.
It's unlikely that we can get a new extended maintenance release to back port these fixes; typically such a release is reserved for critical or extremely high impact bugs or security issues and I'm not sure this falls into either category. To balance it further, 2026.1 is the extended maintenance version until 2026.3 is released (which will be in just a few weeks), and at that time 2026.2 becomes the extended maintenance version.
Unfortunately if you want to stay on 2026.1 for now my recommendation to avoid these issues would be stick with RDM Jump as the jump host approach. 2026.1 warns you of the upcoming deprecation, and 2026.2 makes the deprecation notice "hard" but it's not actually removed until 2026.3. If the waning dialog while using RDM Jump is a problem on your side, I can share a mechanism to disable that for your users.
I am sorry for the inconvenience. Please let me know if you have other questions, or something isn't clear.
Kind regards,
Richard Markievicz