Jump Host - Devolutions Agent not available

Hello

We're tracking a few customer issues with Devolutions Agent and Jump after the 2026.3 update.

Just to try something really low-hanging and try to unblock you quickly, can you please try going to File > Settings > Performance, and under "Entry Images" uncheck "Show favicon cache".

Restart RDM and then try the session - does it work now?

Let me know if that helps

Kind regards,

The setting didn't resolve the issue.

And no worry about unblocking me. I'm testing the new version in our testing environment.

Hello

Ok, thanks; it was worth checking.

What would concretely help me find and fix the issue(s) faster would be the following diagnostics:

• On the RDM client side, go to Help > Troubleshooting > Performance Profiling
  • Set the Level to "131" and leave the window open
• Reproduce the "Devolutions Agent is not available on the jump host" issue
• Send me the output from the profiler window by PM. You could export it to a file, .zip it and attach it to a PM, that's probably the best workflow
• At the same time, if you are able, please send the corresponding logs from the Agent side. You can .zip both of these folders and attach them also if possible:
  • %programdata%\Devolutions\Agent
  • %appdata%\Devolutions\Session

Please let me know if you have some questions and thank you for your patience

Thanks and kind regards,

PM send.

Hi Richard,
we are experiencing the same issue since updating to RDM 2026.3 and the new Devolutions Agent.
In our environment, the issue seems to occur especially after an RDP session to the jump host has been closed using the X button instead of logging off from Windows.
The Windows session therefore remains active/disconnected on the jump host. When trying to establish another connection through the jump host afterwards, RDM reports that the “Devolutions Agent is not available on the jump host.”
This behavior only started after the 2026.3 update.
Maybe this detail helps with reproducing and narrowing down the issue.

Regards
Sebastian

Hi Sebastien

Thanks for chiming in here, and I'm sorry for the inconvenience.

We've a number of users experiencing instability with this. I'm working currently on what I hope will be a comprehensive fix to make negotiation between RDM and the Agent completely robust. It should be ready within the next couple of minor RDM releases. I will update this thread with more information.

Thank you for your patience; and don't hesitate with other questions or comments in the meantime

Kind regards,

After upgrading to 2026.3.13.0 on all servers running RDM, we have the same issue. Our Bastion is now running the new agent service, but I can't make it work. I get 'Devolutions Agent is not available on the jump host'.

Our workaround is to logoff the user and using the Agent is an once in session-time opportunity. If you reconnect to the same RDP session then you can not use the Agent connection once more.
Also the Agent status is shown as red x.
I hope Richard is working on that problem.