I just updated my RDM installation to 2025.2.13.1 and since then RDM crashes when using SSH-sessions.
I always get this message in the eventviewer:
Name der fehlerhaften Anwendung: RemoteDesktopManager.exe, Version: 2025.2.13.1, Zeitstempel: 0x67fe0000 Name des fehlerhaften Moduls: ntdll.dll, Version: 10.0.22621.5262, Zeitstempel: 0x3b213567 Ausnahmecode: 0xc0000374 Fehleroffset: 0x000000000010d539 ID des fehlerhaften Prozesses: 0x0x64D4 Startzeit der fehlerhaften Anwendung: 0x0x1DBD702C52717FF Pfad der fehlerhaften Anwendung: C:\Program Files\Devolutions\Remote Desktop Manager\RemoteDesktopManager.exe Pfad des fehlerhaften Moduls: C:\WINDOWS\SYSTEM32\ntdll.dll Berichtskennung: 8668dcfc-02fe-4471-87a1-ea8980588979 Vollständiger Name des fehlerhaften Pakets: Anwendungs-ID, die relativ zum fehlerhaften Paket ist:
Recommended Answer
@hoelle666
I found a bug and I'm pretty sure it is the cause for your problem. I have made a fix and it will be available in our next release: 2025.2.14.0
Regards
Denis Vincent
Hello,
Thank you for contacting Devolutions Support.
As per the crash logs, you have provided us, this issue is caused by a Faulting module in Windows:
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Per the information we have gathered on that matter, this issue is tied to Windows and not RDM itself.
For this reason, the only thing we can suggest is to run the following tools:
1-Run the .Net Framework Repair Tool: https://www.microsoft.com/en-ca/download/details.aspx?id=30135
2-Run SFC Scannow - https://support.microsoft.com/en-us/kb/929833
For more information on that matter, please refer to this external link:
https://answers.microsoft.com/en-us/windows/forum/all/app-crash-with-ntdlldll/9aa59f80-99a1-4f3c-b2f0-7eb72df05b2a
Best regards,
Samuel Dery
Hi,
I experience the exact same problem after upgrade to 2025.2.13.1 with ssh connections.
Faulting application name: RemoteDesktopManager.exe, version: 2025.2.13.1, time stamp: 0x67fe0000 Faulting module name: ntdll.dll, version: 10.0.22621.5262, time stamp: 0x3b213567 Exception code: 0xc0000374 Fault offset: 0x000000000010d539 Faulting process id: 0x0xB78 Faulting application start time: 0x0x1DBD8BF2F4C426C Faulting application path: C:\Program Files\Devolutions\Remote Desktop Manager\RemoteDesktopManager.exe Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll Report Id: 713f6d37-5d10-4ebd-8936-e925f0f6b550 Faulting package full name: Faulting package-relative application ID:
Error code 0xC0000374 indicates a STATUS_HEAP_CORRUPTION.
My .NET version reported by RDM About page is 9.0.5, if this is of any relevance.
Hi,
I would need some information about your SSH sessions: are they using GSSAPI or SSPI authentication? are they using Smartcard authentication in either CAPI or PKCS11 mode? Are you using an SSH agent? If yes, is the agent Pagent or OpenSSH, and is it provided by RDM or externally?
This would help me target more precisely my investigations into this problem.
Regards
Denis Vincent
In my case:
Regards
@hoelle666 Thanks for the info. It does narrow my research.
Sorry for the inconvenience.
Regards
Denis Vincent
@hoelle666
I found a bug and I'm pretty sure it is the cause for your problem. I have made a fix and it will be available in our next release: 2025.2.14.0
Regards
Denis Vincent
OK, just for the record: I'm also using agent authentication. But as an agent I'm running KeePass with a plugin.
@eiben Thanks for the info. Since the KeePass agent is a Putty compatible agent, it does point to the same bug.
Let us know if the next release does not fix the issue.
Regards
Denis Vincent
@Denis Vincent I can confirm that the problem is fixed with 2025.2.14.0.
Thank you.
@Denis Vincent: I can also confirm, that a first test didn't crash RDM anymore.
Thanks for the good news, I'm glad I could help.
Regards
Denis Vincent