High CPU usage since update to Version

We will update to Version 2025.1.26 tonight

Hello,

Thank you for contacting us on that matter!

We will wait for you to update and see if the problem persists. If it does, please let us know.

In the meantime, If you have any other questions, feel free to let us know.

Best regards,

Dear Maxim,

the update doesn´t help and we are not happy at all now ... Any idea ?

BR

Sascha

Hello Sascha,

Thank you for your response! I am sorry for any inconvenience this is causing.

Could you please let me know if each user has a unique application data folder (roaming profiles or similar technologies)?

When using RDM in a Remote Desktop Services environment, it may be necessary to adjust the RDP entry settings to minimize resource usage and enhance the application's startup performance. Could you please follow the steps in Solution 3 of this helpful topic and see if it improves performance?

https://docs.devolutions.net/rdm/kb/troubleshooting-articles/startup-performance/#solution-3-prevent-internet-access

You can also limit the memory consumption of RDP entries. Please see the link below.

https://docs.devolutions.net/rdm/kb/knowledge-base/rdp-session-entry/memory-tuning-rdp-sessions/

Thank you for your patience. If you have any other questions, feel free to let us know.

Best regards,

Dear Maxim,

so far, no good news. We Update to 2025.1.29.0 and still high CPU usage ...

A plain application is consumming 13.2 % CPU, even with an empty Local Data Source and max. performance configuration.

Any other idea. The tool is more or less unusable ...

BR

Sascha

Hi,

We upgraded from 2024.3.10.0 to 2025.1.29.0 and are experiencing the same issue after upgrade on one of our terminal servers.

RemoteDesktopManager consumes about 12% CPU per user.

Server is is flatlining at 100% CPU use in total.

We use RDM on two more servers. On these servers CPU use is 0-1% per user.

Kr,

Kyron

Hello

The description of the issue implies something specific to the environment (we've not had many reports like this, and Kyron reports that just one server is affected).

The QA and support team will undoubtedly try to reproduce the problem, but without more data it will be hard to diagnose. RDM has some profiling tools but nothing that can capture runaway CPU when the application is effectively idle as seems to be the case here.

If you don't mind helping with some advanced troubleshooting, the following steps might help us to identify the problem:

• Download procdump from Microsoft / SysInternals

• Extract the download to a location on disk

• From an administrative command prompt, `cd` to the extracted procdump directory

• Run RDM (if it's not running already) and let it idle. We want it to be already running so we're capturing the idle state, not the startup cost.

• Back in the command prompt run `procdump64.exe RemoteDesktopManager.exe -c 10 -s 5 -n 10`. You may need to accept the license agreement which pops up.

This will instruct procdump to generate a minidump from RDM every time processor utilization exceeds 10% for 5 seconds, exiting after capture 10 minidumps. The command prompt will give some feedback as it generates the mini dumps. Based on your screenshots above I believe this should be an appropriate configuration.

procdump will write the dump files to the current directory and they'll be named like "RemoteDesktopManager.exe_{date}_{time}.dmp".

Once you've gathered these files please let us know and the support team can provide you an avenue to upload them to us. Do not post them here on the public forum. I encourage you to read the security disclaimer around dump files.

Please, let me know if you have any questions and I apologize for the inconvenience.

Kind regards,

Dear Richard,

I create the file and can upload it. Please provide a link ...

And I read the disclaimer

BR

Sascha

Hi Sascha

Thanks a lot for the follow up. I've sent you a PM with some instructions. Please let me know if you have any question or you don't receive the PM.

Kind regards,

Hi Richard,

file is uploaded as requested.

BR

Sascha

Hello Sascha

Thanks again for sending the files. I believe I've hit up what the issue is and I'm working on that.

In the meantime, Kyron can you tell me the exact OS and build number of the affected server in your case? You can get the information by running `winver` from the Start Menu or run dialog.

Best regards,

Hi Richard,

Microsoft Windows Server Version 1607 (OS Build 14393.7876)

BR

Sascha