Here's the full error message in RDM
COMException - Catastrophic failure (Exception from HRESULT: 0x8000FFFF (E_UNEXPECTED))
at Devolutions.RemoteDesktopManager.Managers.EmbeddedViewManager.c05a4a169bb1ade915a9f6f7b6339eeac(FreEmbeddedView c60a5c3d79f5c9d8ce9ed13393ea1eab7, Connection c6aea3d31dfb3fea36c5f53f7fe93584c, Boolean c483b2477d7bfce4f8b55bb662eb78b4e, Boolean ca6a22d3f25c975ff31a01aa94e590fe7, OpenConnectionMode c602973c05c2f5870e41c508b048b13c5, Image cab3b489b5921f9edda008f021b9c5ea9)
at Devolutions.RemoteDesktopManager.Managers.EmbeddedViewManager.Open(Connection connection, FreEmbeddedView frame, Boolean isConnected, OpenConnectionMode openConnectionMode, Boolean undocked, Image image)
at Devolutions.RemoteDesktopManager.Business.Connectors.EmbeddedConnector.Connect(Connection connection, OpenConnectionMode openConnectionMode)
at Devolutions.RemoteDesktopManager.Managers.ConnectionManager.OpenConnection(Connection connection, OpenConnectionParameter parameter)
at Devolutions.RemoteDesktopManager.Managers.ConnectionManager.OpenConnections(Connection connectionList, OpenConnectionParameter parameter)
at Devolutions.RemoteDesktopManager.Managers.ActionManager.c2d3a897d165d9e56a0d53f388986ac51(Connection cfabc0254f46d7d8ae5a71db9e5a0b5b5, OpenConnectionMode c602973c05c2f5870e41c508b048b13c5, IConnectionSource c5b7a41272702648f46cf77ee6b3a92cb)
at Devolutions.RemoteDesktopManager.Managers.ActionManager.OpenConnections(Connection currentConnections, OpenConnectionMode openConnectionMode, IConnectionSource source, Boolean checkOpenedConnection)
at Devolutions.RemoteDesktopManager.Frames.ConnectionViews.FreBaseConnectionView.OpenConnection(Connection currentConnections, OpenConnectionMode openConnectionMode)
at Devolutions.RemoteDesktopManager.Frames.ConnectionViews.FreConnectionTreeListView.cbad026f0443b4db7579b28d004e7ca8d(Boolean ce86b9cea9309620f2c628f54915f70f5)
at Devolutions.RemoteDesktopManager.Managers.ThreadManager.caa310ce107ed0c993f3d034df6d00336(Object c19f185fd70cefc696ba148af1c4faf54, EventArgs cf1018bb83ec7debd818319fd3cb4844e)
at System.Windows.Forms.Timer.OnTick(EventArgs e)
at System.Windows.Forms.Timer.TimerNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
Please note that this same error is also present in Microsoft RDC Manager. RDM and RDC Manager use the same Microsoft ActiveX to establish the RDP connection in embedded mode. You can download RDC Manager to confirm that you have the same error in that application https://www.microsoft.com/en-us/download/confirmation.aspx?id=44989
The workaround that we propose is to change the RDP engine to use FreeRDP. To do so, go in File -> Options -> Types -> RDP and change the RDP engine for FreeRDP.
Hope that Microsoft will resolve this issue in their next update.
I asked to all users who sent us an error report to confirmed me their OS and as of now, they all confirmed that they we're on the latest Windows 10 Insider Preview build, which is 10.0.17728 Build 17728.
The issue really seems to be related to that specific OS.
One of our customers sent us an email today and has he mentioned, the lastest Insider Preview resolve the issue.
That being said, if you upgrade your Windows 10 Insider Preview to the latest release, this should resolve the catastrophic failure error message.
Thanks for keeping us all up to date on this thread, Jeff. I can confirm, I was running build 17728 and have since upgraded to 17730 and the issue went away.
I can also confirm that I was running build 17728 and just upgraded to 17741 and no longer experience the issue.