RDM crashes on embedded websession (webview2) since update to version 2026.3.X
Hi Everyone,
since I have updated to version 2026.3.X my RDM crashes after a while when a website-session is active. So far I can tell that it happens always when I change focus back to RDM.
First the window freezes and after a view seconds RDM closes completely.
In the eventlog I can see three entries:
The first is an WebView2Controller.MoveFocus error:
The two entries after this error have the same content:
The part "F107AF84049F3D11396FD71955F555198DEEB8C7E0C992FF24C0CFCE20E3AA2CD__InterfaceImplementation.global::Avalonia.Controls.Win.WebView2.Interop.ICoreWebView2Controller.MoveFocus(COREWEBVIEW2_MOVE_FOCUS_REASON reason)"
looks for me more as a webview2 problem. But I've only been having this problem since the update to version 2026.3.X.
And I also reinstalled .Net Runtime and webview2.
Is there anyone facing the same problem?
e08d9e80-b6c0-4689-9ee5-96033684cf8b.png
984109ae-4983-40a1-be54-6867a4211f32.png
44ff76a0-f2d7-4d04-8069-2ce8884a19d8.png
Hello,
Thank you for the report and the event log details.
This is a known issue in Remote Desktop Manager 2026.3, and our development team is working on it.
When the RDM window gets focus back, the embedded browser can return an error that RDM does not handle, so the application closes.
Repairing or reinstalling WebView2 or .NET does not change this.
Unfortunately, we don't have any workaround for now.
We will post an update here as soon as a version with the fix is available.
Best regards,
Alexis Beauparlant
Hello,
Thank you for the report and the event log details.
This is a known issue in Remote Desktop Manager 2026.3, and our development team is working on it.
When the RDM window gets focus back, the embedded browser can return an error that RDM does not handle, so the application closes.
Repairing or reinstalling WebView2 or .NET does not change this.
Unfortunately, we don't have any workaround for now.
We will post an update here as soon as a version with the fix is available.
Best regards,
@Alexis Beauparlant
Hi Alexis,
Thank you very much for your reply and explanation.
I'll look forward to the fix in one of the upcoming versions!
Best regards,
Arne