Hello,
after the update to version 2026.1.10.0 our jump host doenst work anymore.
Agent is not connecting.
Error log
[06.03.2026 09:21:38] RDMJump: 2112198948928
[06.03.2026 09:21:40] Ungültige Serialisierungsassembly: der erforderliche Typ Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializerContract ist nicht in der generierten Assembly 'RemoteDesktopManager.Core.XmlSerializers, Version=2026.1.10.0, Culture=neutral, PublicKeyToken=null' vorhanden.
[06.03.2026 09:21:40] bei System.Xml.Serialization.TempAssembly.GetTypeFromAssembly(Assembly assembly, String typeName)
bei System.Xml.Serialization.TempAssembly.LoadGeneratedAssembly(Type type, String defaultNamespace, XmlSerializerImplementation& contract)
bei System.Xml.Serialization.XmlSerializer..ctor(Type type, String defaultNamespace)
bei Devolutions.RemoteDesktopManager.Managers.VirtualChannelManager.GetSerializer(Type type, String nameSpace)
bei Devolutions.RemoteDesktopManager.Managers.VirtualChannelManager.SaveObjectToBytes(Object value)
bei Devolutions.RemoteDesktopManager.Managers.VirtualChannelManager.SendMessage(JumpMessage message)
[06.03.2026 09:21:47] RDMJump: Acknowledge timeout
[06.03.2026 09:21:47] Started
[06.03.2026 09:34:13] RDMJump: 2082568376496
[06.03.2026 09:34:14] Ungültige Serialisierungsassembly: der erforderliche Typ Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializerContract ist nicht in der generierten Assembly 'RemoteDesktopManager.Core.XmlSerializers, Version=2026.1.10.0, Culture=neutral, PublicKeyToken=null' vorhanden.
[06.03.2026 09:34:15] bei System.Xml.Serialization.TempAssembly.GetTypeFromAssembly(Assembly assembly, String typeName)
bei System.Xml.Serialization.TempAssembly.LoadGeneratedAssembly(Type type, String defaultNamespace, XmlSerializerImplementation& contract)
bei System.Xml.Serialization.XmlSerializer..ctor(Type type, String defaultNamespace)
bei Devolutions.RemoteDesktopManager.Managers.VirtualChannelManager.GetSerializer(Type type, String nameSpace)
bei Devolutions.RemoteDesktopManager.Managers.VirtualChannelManager.SaveObjectToBytes(Object value)
bei Devolutions.RemoteDesktopManager.Managers.VirtualChannelManager.SendMessage(JumpMessage message)
[06.03.2026 09:34:21] RDMJump: Acknowledge timeout
[06.03.2026 09:34:21] Started
[06.03.2026 09:38:20] RDMJump: 2557481874784
[06.03.2026 09:38:20] Ungültige Serialisierungsassembly: der erforderliche Typ Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializerContract ist nicht in der generierten Assembly 'RemoteDesktopManager.Core.XmlSerializers, Version=2026.1.10.0, Culture=neutral, PublicKeyToken=null' vorhanden.
[06.03.2026 09:38:20] bei System.Xml.Serialization.TempAssembly.GetTypeFromAssembly(Assembly assembly, String typeName)
bei System.Xml.Serialization.TempAssembly.LoadGeneratedAssembly(Type type, String defaultNamespace, XmlSerializerImplementation& contract)
bei System.Xml.Serialization.XmlSerializer..ctor(Type type, String defaultNamespace)
bei Devolutions.RemoteDesktopManager.Managers.VirtualChannelManager.GetSerializer(Type type, String nameSpace)
bei Devolutions.RemoteDesktopManager.Managers.VirtualChannelManager.SaveObjectToBytes(Object value)
bei Devolutions.RemoteDesktopManager.Managers.VirtualChannelManager.SendMessage(JumpMessage message)
[06.03.2026 09:38:26] RDMJump: Acknowledge timeout
[06.03.2026 09:38:26] Started
I Have already reinstalled cleanly everything nothing helps here.
Also switching the rmd jup to legacy doenst help.
I Updated also everything from .net no help
I Downgraded jump host to 2025 version an it works again. (Client still 2026)
Hello,
Thank you for reaching out regarding this matter.
This is a currently known issue that our team is actively working to resolve.
Once a fix is included in a future update, I will be sure to keep you informed.
Best regards,
Jacob Lafrenière
Hello
I wrote the same in the other thread, but for visibility this should be fixed in 2026.1.11 (which should be released soon).
Thanks for your patience and sorry for the inconvenience
Kind regards,
Richard Markievicz
Hello,
Thank you for being so patient!
I'm pleased to inform you that a new version of RDM (2026.1.11.0) has been released, featuring the fix for your issue.
Latest Version: Download RDM
Please let us know if this works or if you encounter any issues.
Best regards,
Maxim Robert