RDM 2026.2.1.2 freeze on loading connection after upgrade from 2026.1.12.6 on MacOsX Ventura 13.7.8

RDM not RDP!

Hello,

Sorry for the late reply.

Which version of Devolutions Server are you running?

Do you get the same behavior using RDM Windows 2026.2.8.0?

Best regards,

I have exactly the same issue (same versions of RDM, same version of macOS). This is what I've done:

• I tried the .cfg rename with 2026.2.1.2, it didn't help.
• I downloaded the latest version of RDM - on the web page it told me it would be 2026.2.8.0, but instead what downloaded was 2026.2.1.5, filename "Devolutions.RemoteDesktopManager.Mac.2026.2.1.5.dmg". 2.8.0 seems to be Windows, I can't test that.
• I deleted 2026.2.1.2 by dragging the app to Trash
• 2026.2.1.5 also hangs on startup, "Loading..." is displayed.
• my connections are cloud based
• I deleted 2026.2.1.5 by dragging app to Trash, and additionally deleting folder ~/Library/Application Support/com.devolutions.remotedesktopmanager
• Started 2026.2.1.5 again, it asked me to login for the cloud to allow me to connect to my existing connections. Then it got stuck on "Loading..."; Force Quit, delete app and ~/Library/Application Support/com.devolutions.remotedesktopmanager folder again
• Downloaded old version 1.12.6, installed and was successfully able to connect to my cloud connections

I have also tried it with 2026.2.1.5 on macOS 26.5.1. Infinite "Loading ..." , "Loading connections..." cycle.
I also deleted all my cloud connections, re-imported them as CSV instead of RDM format ... it didn't help.

Exported cloud connections to local RDM file.

Seems like 2026.2.1.x is broken.

Next I deleted the folder com.devolutions.remotedesktopmanager, and started 2.1.5 again, this time not logging into my Devolutions account but setting up a local XML store. It seemed to create the store OK, but then got back into the endless "Loading...".

Deleted folder, reinstalled 2026.1.12.6, tried to setup XML store ... started to import RDM file .. it took a long time loading connections ... and finally I have something which works again (macOS Ventura 13.7.8).

Clean install of 2026.2.1.5 on macOS 26.5.1 ... I exported the RDM from the Ventura machine, and imported to Tahoe machine as a local XML store. Worked OK.

Back to the Ventura 13.7.8 machine ... installed 2026.2.1.5 (without deleting the folder or app). Now it fails to load the XML store, sitting in "Loading connections...". Removed 2026.2.1.5, deleted folder, then clean-installed 2026.1.12.6 - it now loads the XML store again and is working.

I have exactly the same issue (same versions of RDM, same version of macOS). This is what I've done:

• I tried the .cfg rename with 2026.2.1.2, it didn't help.
• I downloaded the latest version of RDM - on the web page it told me it would be 2026.2.8.0, but instead what downloaded was 2026.2.1.5, filename "Devolutions.RemoteDesktopManager.Mac.2026.2.1.5.dmg". 2.8.0 seems to be Windows, I can't test that.
• I deleted 2026.2.1.2 by dragging the app to Trash
• 2026.2.1.5 also hangs on startup, "Loading..." is displayed.
• my connections are cloud based
• I deleted 2026.2.1.5 by dragging app to Trash, and additionally deleting folder ~/Library/Application Support/com.devolutions.remotedesktopmanager
• Started 2026.2.1.5 again, it asked me to login for the cloud to allow me to connect to my existing connections. Then it got stuck on "Loading..."; Force Quit, delete app and ~/Library/Application Support/com.devolutions.remotedesktopmanager folder again
• Downloaded old version 1.12.6, installed and was successfully able to connect to my cloud connections

I have also tried it with 2026.2.1.5 on macOS 26.5.1. Infinite "Loading ..." , "Loading connections..." cycle.
I also deleted all my cloud connections, re-imported them as CSV instead of RDM format ... it didn't help.

Exported cloud connections to local RDM file.

Seems like 2026.2.1.x is broken.

Next I deleted the folder com.devolutions.remotedesktopmanager, and started 2.1.5 again, this time not logging into my Devolutions account but setting up a local XML store. It seemed to create the store OK, but then got back into the endless "Loading...".

Deleted folder, reinstalled 2026.1.12.6, tried to setup XML store ... started to import RDM file .. it took a long time loading connections ... and finally I have something which works again (macOS Ventura 13.7.8).

Clean install of 2026.2.1.5 on macOS 26.5.1 ... I exported the RDM from the Ventura machine, and imported to Tahoe machine as a local XML store. Worked OK.

Back to the Ventura 13.7.8 machine ... installed 2026.2.1.5 (without deleting the folder or app). Now it fails to load the XML store, sitting in "Loading connections...". Removed 2026.2.1.5, deleted folder, then clean-installed 2026.1.12.6 - it now loads the XML store again and is working.

@devolutions80
where can I download 2026.1.12.6? I don't think that this is offered at Devolution's website.

I have exactly the same issue (same versions of RDM, same version of macOS). This is what I've done:

• I tried the .cfg rename with 2026.2.1.2, it didn't help.
• I downloaded the latest version of RDM - on the web page it told me it would be 2026.2.8.0, but instead what downloaded was 2026.2.1.5, filename "Devolutions.RemoteDesktopManager.Mac.2026.2.1.5.dmg". 2.8.0 seems to be Windows, I can't test that.
• I deleted 2026.2.1.2 by dragging the app to Trash
• 2026.2.1.5 also hangs on startup, "Loading..." is displayed.
• my connections are cloud based
• I deleted 2026.2.1.5 by dragging app to Trash, and additionally deleting folder ~/Library/Application Support/com.devolutions.remotedesktopmanager
• Started 2026.2.1.5 again, it asked me to login for the cloud to allow me to connect to my existing connections. Then it got stuck on "Loading..."; Force Quit, delete app and ~/Library/Application Support/com.devolutions.remotedesktopmanager folder again
• Downloaded old version 1.12.6, installed and was successfully able to connect to my cloud connections

I have also tried it with 2026.2.1.5 on macOS 26.5.1. Infinite "Loading ..." , "Loading connections..." cycle.
I also deleted all my cloud connections, re-imported them as CSV instead of RDM format ... it didn't help.

Exported cloud connections to local RDM file.

Seems like 2026.2.1.x is broken.

Next I deleted the folder com.devolutions.remotedesktopmanager, and started 2.1.5 again, this time not logging into my Devolutions account but setting up a local XML store. It seemed to create the store OK, but then got back into the endless "Loading...".

Deleted folder, reinstalled 2026.1.12.6, tried to setup XML store ... started to import RDM file .. it took a long time loading connections ... and finally I have something which works again (macOS Ventura 13.7.8).

Clean install of 2026.2.1.5 on macOS 26.5.1 ... I exported the RDM from the Ventura machine, and imported to Tahoe machine as a local XML store. Worked OK.

Back to the Ventura 13.7.8 machine ... installed 2026.2.1.5 (without deleting the folder or app). Now it fails to load the XML store, sitting in "Loading connections...". Removed 2026.2.1.5, deleted folder, then clean-installed 2026.1.12.6 - it now loads the XML store again and is working.



@devolutions80
where can I download 2026.1.12.6? I don't think that this is offered at Devolution's website.

@mharding42
does this mean that RDM 2026.2.1.5 has a bug?

I have exactly the same issue (same versions of RDM, same version of macOS). This is what I've done:

• I tried the .cfg rename with 2026.2.1.2, it didn't help.
• I downloaded the latest version of RDM - on the web page it told me it would be 2026.2.8.0, but instead what downloaded was 2026.2.1.5, filename "Devolutions.RemoteDesktopManager.Mac.2026.2.1.5.dmg". 2.8.0 seems to be Windows, I can't test that.
• I deleted 2026.2.1.2 by dragging the app to Trash
• 2026.2.1.5 also hangs on startup, "Loading..." is displayed.
• my connections are cloud based
• I deleted 2026.2.1.5 by dragging app to Trash, and additionally deleting folder ~/Library/Application Support/com.devolutions.remotedesktopmanager
• Started 2026.2.1.5 again, it asked me to login for the cloud to allow me to connect to my existing connections. Then it got stuck on "Loading..."; Force Quit, delete app and ~/Library/Application Support/com.devolutions.remotedesktopmanager folder again
• Downloaded old version 1.12.6, installed and was successfully able to connect to my cloud connections

I have also tried it with 2026.2.1.5 on macOS 26.5.1. Infinite "Loading ..." , "Loading connections..." cycle.
I also deleted all my cloud connections, re-imported them as CSV instead of RDM format ... it didn't help.

Exported cloud connections to local RDM file.

Seems like 2026.2.1.x is broken.

Next I deleted the folder com.devolutions.remotedesktopmanager, and started 2.1.5 again, this time not logging into my Devolutions account but setting up a local XML store. It seemed to create the store OK, but then got back into the endless "Loading...".

Deleted folder, reinstalled 2026.1.12.6, tried to setup XML store ... started to import RDM file .. it took a long time loading connections ... and finally I have something which works again (macOS Ventura 13.7.8).

Clean install of 2026.2.1.5 on macOS 26.5.1 ... I exported the RDM from the Ventura machine, and imported to Tahoe machine as a local XML store. Worked OK.

Back to the Ventura 13.7.8 machine ... installed 2026.2.1.5 (without deleting the folder or app). Now it fails to load the XML store, sitting in "Loading connections...". Removed 2026.2.1.5, deleted folder, then clean-installed 2026.1.12.6 - it now loads the XML store again and is working.



@devolutions80
where can I download 2026.1.12.6? I don't think that this is offered at Devolution's website.

@mharding42
never mind, I found the URL: https://devolutions.net/remote-desktop-manager/previous-versions/

Hello
after updating RDP latest build on a old macbook with Ventura 13.7.8, it freeze during loadin connection from devolution server.
Rollback to previous version work. Try the cfg rename but unsussesfully.
Any ideas?
Thanks

@Maran Michele - FactorySolver srl
I assume you have RDM 2026.2.1.5. Go to this URL: https://devolutions.net/remote-desktop-manager/previous-versions/ and download version 2026.1.12.6. Then remove RDM 2026.2.1.5 and install RDM 2026.1.12.6. Then it should work.

Hello,

Sorry for the late reply.

Which version of Devolutions Server are you running?

Do you get the same behavior using RDM Windows 2026.2.8.0?

Best regards,

@Jeff Dagenais
Hello Jeff

Were you able to identify the problem or we must remain on old version ?

Thanks

Hello,

Thank you for your patience.

Could you please confirm the version of your Devolutions Server? You may be attempting to connect using incompatible versions. For reference, please see the following article:
https://docs.devolutions.net/resources/other-resources/prevent-issues-by-matching-major-and-minor-versions

I look forward to your response.

Best regards,

In my case, I don’t have a self hosted server. I am using Devolutions hub

I have exactly the same issue (same versions of RDM, same version of macOS). This is what I've done:

• I tried the .cfg rename with 2026.2.1.2, it didn't help.
• I downloaded the latest version of RDM - on the web page it told me it would be 2026.2.8.0, but instead what downloaded was 2026.2.1.5, filename "Devolutions.RemoteDesktopManager.Mac.2026.2.1.5.dmg". 2.8.0 seems to be Windows, I can't test that.
• I deleted 2026.2.1.2 by dragging the app to Trash
• 2026.2.1.5 also hangs on startup, "Loading..." is displayed.
• my connections are cloud based
• I deleted 2026.2.1.5 by dragging app to Trash, and additionally deleting folder ~/Library/Application Support/com.devolutions.remotedesktopmanager
• Started 2026.2.1.5 again, it asked me to login for the cloud to allow me to connect to my existing connections. Then it got stuck on "Loading..."; Force Quit, delete app and ~/Library/Application Support/com.devolutions.remotedesktopmanager folder again
• Downloaded old version 1.12.6, installed and was successfully able to connect to my cloud connections

I have also tried it with 2026.2.1.5 on macOS 26.5.1. Infinite "Loading ..." , "Loading connections..." cycle.
I also deleted all my cloud connections, re-imported them as CSV instead of RDM format ... it didn't help.

Exported cloud connections to local RDM file.

Seems like 2026.2.1.x is broken.

Next I deleted the folder com.devolutions.remotedesktopmanager, and started 2.1.5 again, this time not logging into my Devolutions account but setting up a local XML store. It seemed to create the store OK, but then got back into the endless "Loading...".

Deleted folder, reinstalled 2026.1.12.6, tried to setup XML store ... started to import RDM file .. it took a long time loading connections ... and finally I have something which works again (macOS Ventura 13.7.8).

Clean install of 2026.2.1.5 on macOS 26.5.1 ... I exported the RDM from the Ventura machine, and imported to Tahoe machine as a local XML store. Worked OK.

Back to the Ventura 13.7.8 machine ... installed 2026.2.1.5 (without deleting the folder or app). Now it fails to load the XML store, sitting in "Loading connections...". Removed 2026.2.1.5, deleted folder, then clean-installed 2026.1.12.6 - it now loads the XML store again and is working.



@devolutions80
where can I download 2026.1.12.6? I don't think that this is offered at Devolution's website.

@mharding42
Here is the URL for previous versions: https://devolutions.net/remote-desktop-manager/previous-versions/#linux

Hello
after updating RDP latest build on a old macbook with Ventura 13.7.8, it freeze during loadin connection from devolution server.
Rollback to previous version work. Try the cfg rename but unsussesfully.
Any ideas?
Thanks

@Maran Michele - FactorySolver srl
I assume you have RDM 2026.2.1.5. Go to this URL: https://devolutions.net/remote-desktop-manager/previous-versions/ and download version 2026.1.12.6. Then remove RDM 2026.2.1.5 and install RDM 2026.1.12.6. Then it should work.

@mharding42
thank you. the older version fixed it

Hi... I noticed the same problem on my mac after updating it to the latest version of RDM as well. I will roll it back, but will this issue be fixed in future versions?