Hello,
Remote Desktop Manager 2026.3.12.0 repeatedly crashes and closes completely during normal use. I have to restart the application each time.
RDM runs directly on Windows 11 Pro, build 26300. The Windows event log records an unhandled exception in the embedded WebView2 component when focus returns to the RDM window:
System.IO.FileNotFoundException: The specified module could not be found. (0x8007007E)
The stack trace includes:
Avalonia.Controls.Win.WebView2.Interop.ICoreWebView2Controller.MoveFocus
Avalonia.Controls.Win.WebView2.WebView2BaseAdapter.SafeCallController
Environment:
Remote Desktop Manager 2026.3.12.0 64-bit (PreJIT)
Środowisko wykonawcze: .NET 10.0.12
Platforma: Microsoft Windows 10.0.26300
Źródło danych: RDMDev
Przydzielona pamięć: 699 MB
I completed an online repair of WebView2, but the crashes continue with the same exception. The latest verified occurrence was on October 7, 2026, at 11:58, Warsaw local time. Windows recorded events 1026 and 1000, with exception codes 0xe0434352 and 0xc000041d.
I found a similar report on your forum:
https://forum.devolutions.net/topics/56661/rdm-crashes-on-embedded-websession-webview2-since-update-to-version-20
Embedded browser sessions are an essential part of my workflow. Switching these sessions to an external browser would require substantial changes, so I would prefer a solution that preserves the embedded browser functionality.
Could you please confirm whether this is a known issue and whether a fix or a workaround that retains embedded browser sessions is available? Please let me know which additional logs or crash dumps you need.
Best regards,
Daniel Mańczyk
@danielmanczyk
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.
No need to send more logs or crash dumps for now, we are able to reproduce the issue with the same results.
As for the workaround, we don't have any for now unfortunately.
We will post an update here as soon as a version with the fix is available.
Best regards,
Alexis Beauparlant