SSH connections using key agent crashes RDM

More info from the event logs:

Application: RemoteDesktopManager.exe
CoreCLR Version: 9.0.825.36511
.NET Version: 9.0.8
Description: The process was terminated due to an unhandled exception.
Exception Info: System.NullReferenceException: Object reference not set to an instance of an object.
at System.Windows.Forms.NativeWindow.WindowClass.Callback(HWND hWnd, MessageId msg, WPARAM wparam, LPARAM lparam)




Faulting application name: RemoteDesktopManager.exe, version: 2025.2.27.0, time stamp: 0x68760000
Faulting module name: KERNELBASE.dll, version: 10.0.20348.3932, time stamp: 0x4c7b412e
Exception code: 0xe0434352
Fault offset: 0x000000000003f46c
Faulting process id: 0x54c0
Faulting application start time: 0x01dc18330251a508
Faulting application path: C:\Program Files\Devolutions\Remote Desktop Manager\RemoteDesktopManager.exe
Faulting module path: C:\Windows\System32\KERNELBASE.dll
Report Id: 1f625346-8ea5-4963-93f7-27f1a60e1733
Faulting package full name:
Faulting package-relative application ID:




** I have tried reinstalling/repairing .NET 9 on my system -- did not help (still crashing)

Hello,

Thank you for reaching out to Devolutions Support.

We recently pushed a few fixes in the latest updates that may have affected older keys. Could you confirm if the issue appeared after an update? If so, please try removing the old keys and check if the problem persists.

If the issue continues, please follow the steps in the documentation to reset RDM to its default settings:
https://docs.devolutions.net/rdm/kb/how-to-articles/reset-rdm-to-default-settings/

If the problem is related to the RDM installation, this reset should resolve it. If not, please let us know and we will investigate further.

Best regards,

Hello,

One last thing.

The logs suggest there may be an issue with a problematic DLL. Could you please try running the following command as an administrator and let us know if anything is detected or repaired?

sfc /scannow

Best regards,

Hi,

Have the same issue after upgrade to 2025.2.27.0. Resetting RDM to default settings, does not resolve the problem.

Hi,
Have the same issue after upgrade to 2025.2.27.0
if I stop SSH KeyAgent that is automatically started with RDM, main window of RDM and SSH key agent stop responding. i need to kill RDM from task manager because it not responding to the close command.

If I disable RDM agent and use pagent with the same keys I don't have any problem.

Update: I started RDM with administrative privileges, then started Key Agent. I tried connecting to the Linux server via SSH and key authentication, and the connection was successful. Then I tried stopping Key Agent, and when I clicked "Stop" RDM and the Key Agent windows froze for about 30 seconds, then all windows closed.

Hello,

Thank you for your response.

I have opened a case to further investigate the issue. I will send you a confirmation email shortly and will also conduct testing on my end.

Best regards,

Version 2025.2.28.0 has the same problem.

Version 2025.2.28.0 has the same problem.

@marcingarski

I confirm it.

Hello,

Thank you for your response.

Unfortunately, the fix has not been released yet. I will keep you informed as soon as it becomes available.

Best regards,

I found new pattern. Start RDM, start PuTTY, open session in PuTTY. PuTTY hangs for a while, RDM is closing, PuTTY opens session.

Hello,

Thank you for your response.

Just to confirm, is PuTTY opening when RDM is closing?

Do you see any error messages? Additionally, could you please check if there are any application logs available under the Help tab?

I’ll share this pattern with the developers who are currently investigating the issue.

Best regards,

Hello,

Can't reproduce issue with PuTTY anymore on 2025.3.15.0. Application logs are clear, but still original issue occurs.

Hello,

Thank you for your response.

Could you please confirm the original issue that occurred on your end?

Best regards,

I just updated from .2.30 to 2025.3.16 and I confirm that the ssh agent no longer works, it crashes for me too

Hello,

This issue has been elusive so far, as we haven't been able to replicate it reliably. However, we've fix some structural issues with the SSH Key agent, which will reach live with version 2025.3.17. This could potentially fix the issue you've been describing so far. Please let us know if you are still experiencing the problem once the version is released.

Regards,

This issue is affecting me too on Win 11. I upgraded to 2025.3.16.0 and now any interaction with the ssh-agent hangs RDM.

I removed 3.16 and installed 2.26 and is able to connect using ssh-agent again.

Hello,

As specified in my last response, please let us know if the 2025.3.17 version works for you when it comes out.

Regards,

Hello,

The issue that you encountered is now fixed in the latest version of Remote Desktop Manager. Could you update and let us know if everything works for you?
https://devolutions.net/remote-desktop-manager/downloadenterprise/

Best Regards,

Testes on 2025.3.17 and sadly nothing changes, still the RDM crashes. I am not sure if this is relevant but in release notes I can't find any information about SSH Key agent fixes.

I can connect with version 2025.3.17 and the Agent active.
So it works now.
When I start the software, the SSH agent automatically activates as before.
However, if I go to Tools - SSH Key Agent and try to stop the service, the software crashes.

I am also experiencing issues trying to connect with ssh keys. I was using 3.16 and updated to 3.17 but the issue persists. I tired removing the key from the agent and readding it but no help. I was able to stop and start the agent but now it crashes RDM.

I am getting these events:
Application: RemoteDesktopManager.exe
CoreCLR Version: 9.0.925.41916
.NET Version: 9.0.9
Description: The application requested process termination through System.Environment.FailFast.
Message: A callback was made on a garbage collected delegate of type 'Devolutions.Protocols!Devolutions.Protocols.Core.PageantManager+WndProcDelegate::Invoke'.
Stack:
at Devolutions.Protocols.Core.PageantManager.DestroyWindow(IntPtr)
at Devolutions.Protocols.Core.PageantManager.DestroyWindow(IntPtr)
at Devolutions.Protocols.Core.PageantManager.MessageLoopThread()
at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)


Faulting application name: RemoteDesktopManager.exe, version: 2025.3.17.0, time stamp: 0x68a40000
Faulting module name: coreclr.dll, version: 9.0.925.41916, time stamp: 0x68a4f589
Exception code: 0x80131623
Fault offset: 0x000000000024480e
Faulting process id: 0x0x10B8
Faulting application start time: 0x0x1DC42A29AFB7030
Faulting application path: C:\Program Files\Devolutions\Remote Desktop Manager\RemoteDesktopManager.exe
Faulting module path: C:\Program Files\dotnet\shared\Microsoft.NETCore.App\9.0.9\coreclr.dll
Report Id: 9f1a289c-827c-4b51-8266-093de43b15b2
Faulting package full name:
Faulting package-relative application ID:

@toddmackenzie Thanks for the info, it will be helpful.

I am currently working on this problem, I can't say when the solution will be ready, but it is my top priority.

Regards

Hello,

Denis has a potential fix which will be included in our upcoming version of RDM (2025.3.18.0).

Best Regards,

Tried today 2025.3.20.0 version with "Potential fix for issue with SSH key agent crashing" and no crashes yet now. Thanks for fixing this annoying bug.

Hello,

That's great to hear. Thanks for letting us know.

If the issue happens again then do not hesitate to let us know on this thread

Best Regards,

2025.3.20.0 is working for me as well.

Thanks for the quick turn around.