RDM 2026.3.12.0 crashes when using embedded browser sessions
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:
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
RDM 2026.3.12.0 crashes when using embedded browser sessions
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
Remote Desktop Manager stopped working after today's Devolutions Cloud update
Hello,
I need urgent assistance because after today's update my entire Remote Desktop Manager environment stopped working.
Prior to today's update everything was working correctly. My data source was configured as an online Devolutions Hub / Devolutions Cloud data source and I was able to access all entries, launch RDP sessions, view documentation, attachments, and manage my environment normally.
Today I updated to the new Devolutions Cloud version. During the update, the Devolutions Password Manager application was also installed.
After the update:
I can successfully log in to Devolutions Cloud.
I can access the web interface.
I can see all my vaults.
I can see all folders and entries.
I can see documentation.
I can see attachments.
All my data appears to be present and intact.
However, I am no longer able to launch any connections from Remote Desktop Manager.
When I attempt to open a Remote Desktop entry from Devolutions Cloud, Remote Desktop Manager starts but immediately reports:
"Unable to connect to the data source. Would you like to switch to offline mode?"
I then tried the following troubleshooting steps:
Recreated the Devolutions Cloud data source.
Verified the host URL.
Verified my credentials.
Reinstalled Remote Desktop Manager.
Created a completely new configuration.
Added the Devolutions Cloud data source again from scratch.
The connection test succeeds successfully and reports that the connection has been established.
However, when Remote Desktop Manager actually attempts to open the data source, it fails every time.
I also collected the detailed error log. The relevant part shows:
HTTP 403 Forbidden
and the stack trace points to:
HubClient.GetVaultV3(Guid vaultId)
This suggests that authentication succeeds, but access to the vault is denied when Remote Desktop Manager attempts to load it.
Additionally, Remote Desktop Manager reports that no shared vaults are available.
What is confusing is that I can still log in through the web interface and I can see all of my data, documents, attachments, and entries without any issue.
It appears that something changed during today's migration/update and Remote Desktop Manager is no longer able to access the vault even though the account itself is working correctly.
Has anyone experienced the same issue after today's update?
Could someone please explain what changed and what steps are required to restore Remote Desktop Manager functionality?
Any assistance would be greatly appreciated as I currently cannot use any of my remote connections.
Thank you.