Devolutions ForumDevolutions Forum

Unable to start RDM

Unable to start RDM

avatar
mcsida

Hi!

We are using RDM 13.0.6.0 and have 5 licenses.

Starting from today, I noticed that I can't start RDM anymore - it nearly instantly switches to "Not Responding".

I tried to "delete" the configuration by renaming the folder "C:\Users\USER\AppData\Local\Devolutions\RemoteDesktopManager" and when starting, I get to enter license information, as expected. If I cancel this window, it's "Not Responding" again. If I enter the correct license information, I get the following error message after a while:

Devolutions.RemoteDesktopManager.Business.TryGoOfflineException: The remote name could not be resolved: 'crm.devolutions.net' ---> System.Net.WebException: The remote name could not be resolved: 'crm.devolutions.net'
    at System.Net.HttpWebRequest.GetResponse()
    at Devolutions.RemoteDesktopManager.Managers.RDMOManager.SendRegistrationEnterprise(RDMOCreateAccountInfo accountInfo, String serial)
    --- End of inner exception stack trace ---

We are using many customer connections in a MSSQL database. Does this error message mean that we can't use RDM at all when crm.devolutions.net isn't reachable? Our internet connection is fine otherwise.

After a while there is also a message with "Web Browser" title, saying "Stop running this script? A script on this page is causing your web browser to run slowly. If it continues to run, your computer might become unresponsive". Also my colleague that had RDM already running over night received this message, but he didn't restart RDM, so he is the only one now that can connect to our customers with RDM. All other colleagues experience the same issue as described above when trying to start RDM.

Any help? Is this a temporary issue?

Thanks!

All Comments (4)

avatar
Maxim Robert

Hello,

Thank you for reaching out and for the detailed information.

Based on the behaviour you’re describing, the issue is very likely related to the version of Remote Desktop Manager you are currently using. Version 13.0.6.0 is significantly outdated and is no longer supported by Devolutions.

There are two important implications here:

  • This version no longer receives updates, meaning any issues, especially those related to connectivity (such as resolving crm.devolutions.net), cannot be resolved.


  • Older versions of RDM rely on services and endpoints that may have changed, been deprecated, or are no longer fully compatible with the current infrastructure. This can result in exactly the type of startup freeze and “Not Responding” behaviour you're seeing.


We strongly recommend upgrading to the latest version of Remote Desktop Manager. Newer versions:

  • Are actively maintained and supported.


  • Include fixes for connectivity and performance issues.


  • Address important security concerns present in older builds.


If you have any further questions, please don't hesitate to let us know.

Best regards,

Maxim Robert

avatar
Carl Marien

Hello,

To add to maxim post it is also possible that your current Windows version is contributing to the issue. RDM 13 dates back to around 2017, when Windows 7 was still widely supported. Modern environments (such as Windows 10/11) may no longer fully support components or dependencies used by that version. Conversely, newer versions of RDM (2023+) have dropped support for older operating systems like Windows 7.

We strongly recommend upgrading to the latest version of Remote Desktop Manager. Newer versions are actively maintained, include important fixes for connectivity and performance, and ensure compatibility with current operating systems and infrastructure.

If you have any constraints preventing an upgrade, please let us know and we can help explore possible workarounds.

Best regards,

Carl Marien

avatar
mcsida

We are all on Windows 11 Pro (25H2).

I asked another who normally uses it and it's working fine on his machine (he only got the "Web Browser" window, which he simply closed).
So we have 2 users with the described behavior, one where it works normally and one that doesn't want to restart because of the risk that it doesn't work anymore.

Nothing changed on our machines and we were able to use RDM normally last week.

While I understand that you suggest an update (also something that I wanted to suggest for a while now already), could you please tell us what the error message means? Is this happening because crm.devolutions.net can't be reached?

Thanks!

avatar
mcsida

Can we use our MSSQL database that we're currently using (for RDM 13) when we switch to the latest version?
We have a lot of things in this MSSQL database - logins, rdp, vnc, files, links, etc.