High RAM ussage

High RAM ussage

avatar
martin25

Hi everyone,
I have a desktop PC running Windows 11 25H2, fully up to date, with RDM version 2026.3.12.0 installed. If I leave RDM running for a week, it gradually consumes all available memory, even though it is mostly idle and I only connect to remote sessions occasionally.
The only solution is to restart the entire system, after which everything works fine again. This issue has been occurring across several consecutive RDM versions.
Interestingly, when I connect to the desktop via RDP, the RAM usage starts to decrease gradually. When I started writing this post, RDM was consuming 17 GB of RAM. After approximately 10–15 minutes of being connected via RDP, its memory usage had dropped to just 2 GB and was still decreasing.
On my other laptop, RDM uses only around 390 MB of RAM.
The desktop has the following specifications:

  • CPU: Intel(R) Core(TM) i7-7700
  • RAM: 32 GB
  • Storage: 2 TB SSD

Has anyone experienced

This is how RAM was used after the first login:
Remote Desktop Manager 2026.3.12.0 64-bit (PreJIT)
Runtime: .NET 10.0.12
Platform: Microsoft Windows 10.0.26200
Allocated memory: 17390 MB

...after 10-15min
11a0e552-1849-4f0f-84d0-d36b59b4a6ff
now after 30min it is still using 1.2GB RAM

11a0e552-1849-4f0f-84d0-d36b59b4a6ff.png

RDM.png

All Comments (1)

avatar
Alexis Beauparlant

@martin25 Hello,

Thank you for the detailed report and the memory figures.

Let's first rule out the local configuration by starting RDM with a fresh one.

  1. Close RDM.
  2. Open the C:\Users\Username\AppData\Local\Devolutions folder.
  3. Rename the RemoteDesktopManager folder to RemoteDesktopManager.old.
  4. Start RDM again, which creates a new, clean configuration.

https://docs.devolutions.net/rdm/knowledge-base/how-to-articles/reset-remote-desktop-manager-to-default-settings/

Nothing is deleted, since your old settings stay in the RemoteDesktopManager.old folder.

If you use a local workspace, you will need to import your entries back from the Connections.db file in that old folder. To import it, simply copy "Connections.db" from RemoteDesktopManager.old and paste it into the new folder created in step 4.
If you use external workspaces, you will need to connect to them again.

Once done, leave RDM running as usual for a few days and let us know if the memory still climbs.

Best regards,

Alexis Beauparlant