Frequent application crashes since upgrade to 2026.3.15.0 - .Net runrtime event ID 1026
This has been happening for few weeks now but today has happened a half dozen times which is becoming somewhat frustrating.
About 10 days ago I followed all steps outlined in this guide: https://docs.devolutions.net/rdm/knowledge-base/troubleshooting-articles/remote-desktop-manager-crashes-in-versions-2024.1-to-2024.3
Dot net and Windows EdgeView2 are up to date, I, running latest version of RDM and have reset the app by renaming appdata profile RDM folder name.
Still getting crashes.
Found these logs ref the crash in EventViewer.
Event ID 1026 .Net Runtime followed by Event ID 1000 Application Error
Application: RemoteDesktopManager.exe
CoreCLR Version: 10.0.1426.52326
.NET Version: 10.0.14
Description: The process was terminated due to an unhandled exception.
Exception Info: System.InvalidOperationException: Handle is not initialized.
at System.WeakReference`1.SetTarget(T target)
at System.Windows.Forms.ToolStrip.Dispose(Boolean disposing)
at System.ComponentModel.Component.Dispose()
at Devolutions.Protocols.Xterm.Dispose(Boolean disposing)
at Devolutions.Protocols.XtermSsh.Dispose(Boolean disposing)
at System.ComponentModel.Component.Finalize()
at System.GC.RunFinalizers()
Faulting application name: RemoteDesktopManager.exe, version: 2026.3.15.0, time stamp: 0x6ac20000
Faulting module name: KERNELBASE.dll, version: 10.0.26100.9549, time stamp: 0x4370855d
Exception code: 0xe0434352
Fault offset: 0x00000000000c483a
Faulting process id: 0x57B0
Faulting application start time: 0x1DD661F3274C426
Faulting application path: C:\Program Files\Devolutions\Remote Desktop Manager\RemoteDesktopManager.exe
Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll
Report Id: 50417f8d-ae42-468c-b2f3-f4df14480d66
Faulting package full name:
Faulting package-relative application ID:
Any suggestions please on what else to try here?
Forgot to add - we are using Microsoft SQL back end on the teams edition and are also connecting to Pleasant Password Server for authentication.
Vault has 250 folders and 1945 sessions with 9 synchronizers
Just seen another post on here ref high RAM on version 2026.3.15 and wondering if that as same thing here - RAM maxing out.
I've since upgraded to 2026.3.16.0 and since then, admittedly only a day, its been OK.
Hello,
Thanks for the post.
Indeed, we would need to wait the release of RDM 2026.3.16.0. Unfortunately, I cannot provide an ETA at this time for the release of that version.
However, when this version will be available, we will post here.
Best regards,
Jeff Dagenais
Im running the newest version 2026.3.16.0 already? It was available for update to me from within the app on Wednesday 28Oct. Having said that it crashed again just now while trying to type on a newly opened SSH session to a linux VM. Only 3 machines open in total.
Faulting application name: RemoteDesktopManager.exe, version: 2026.3.16.0, time stamp: 0x6ada0000
Faulting module name: KERNELBASE.dll, version: 10.0.26100.9711, time stamp: 0xfb9071fb
Exception code: 0xe0434352
Fault offset: 0x00000000000c408a
Faulting process id: 0x651C
Faulting application start time: 0x1DD683C75437C26
Faulting application path: C:\Program Files\Devolutions\Remote Desktop Manager\RemoteDesktopManager.exe
Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll
Report Id: ac44f1d0-41d7-4d77-b7f6-2a329c217db1
Faulting package full name:
Faulting package-relative application ID:
Hello,
Thank you for contacting us on that matter,
The entry you sent (exception code 0xe0434352) tells us RDM hit an unhandled .NET exception, but the stack trace that shows the actual cause is in a separate event. Could you send us the following:
The .NET Runtime event: In Event Viewer > Windows Logs > Application, look for an entry with source .NET Runtime (Event ID 1026) at the same time as the crash. Please copy its full text, or export it.
RDM’s application log: In RDM, go to Help > Application Logs and send us the entries from around the time of the crash.
A few details:Does this happen with any SSH entry, or only with this Linux VM?
Does it crash on the first keystroke, or after some typing? Is it tied to particular keys (paste, special characters, accented characters)?
Which keyboard layout or input language is active in Windows?
Are the sessions embedded (tabbed) or undocked/detached?
As a test, could you also try opening the same SSH entry in an external window, if that option is available for the entry, and see whether it still crashes?
Once we have the .NET Runtime event, we should be able to pinpoint the cause.
Best regards,
Tommy Sanders