Execution of entry via command line creates a new remotedesktopmanager.exe process which never exits
Execution of entry via command line creates a new remotedesktopmanager.exe process which never exits
It seems like in the Newer versions of RDM (sometime between November 2024 and January 2025) the handling of entry execution via the command line has been changed.
Command example:
cmd.exe /C "C:\Program Files\Devolutions\Remote Desktop Manager\RemoteDesktopManager.exe" /DataSource:<DataSourceGUID> /Repository:00000000-0000-0000-0000-000000000000 /Session:<SessionGUID>
Before:
I would use the command line and it would launch a RemoteDesktopManager.exe instance, and then exit.
Now:
I use the command line and launches a RemoteDesktopManager.exe instance which never exits, it permanently uses about 130MB ram. Even closing all visible RDM windows does not kill the RemoteDesktopManager.exe instance which was created when executing via command line. When I'm in this state (I have an instance of RemoteDesktopManager.exe leftover from the command line execution and I've closed the main RDM window) I am unable to open a new RDM window via the start menu (or shortcut). The only way to open a new RDM window is by opening task manager and forcing all the leftover RemoteDesktopManager.exe instances to 'end task'. At this point I can launch a new RDM window normally by running it from the start menu
All Comments (9)
Hello,
Thank you for reaching out to us regarding this,
Could you please specify the version of RDM you are currently using?
What type of data source are you using?
Additionally, I would like to confirm if RDM is perhaps minimized in your Windows taskbar? If you go under "File" -> "Settings" -> "User Interface" -> "Taskbar/Trayicon" is the option "Reduce to trayicon/taskbar on close currently enabled?
Enabling the "Allow Multiple instances" option under "File" -> "Settings" -> "Advanced" may help with this issue by allowing you to start another instance of RDM without fully closing the previous instance.
Let me know,
Best regards,
Samuel Dery
Hello! Thanks for your time in investigating this post.
Currently my version is 2025.1.31.0, but for sure it’s also an issue with 2025.1.30.0.
data source is sql lite
the reduce to trayicon/taskbar setting is not enabled
FYI,
Under topic 44574 I reported a similar behavior and where I have a remote support session planned this afternoon with Patrick Ouimet (Devolutions) for analysis.
A report is here generated via cmd-line/prompt, where previously (version 2024 to reproduce) after generating the report output/file the RDM process was closed neatly, while now (client version 2025) after generation the Windows process remains active (in the background).
Option indicated enabled then a 2nd RDM session will actually be opened and active which will also (as intended for this option) remain active, previously the cmd was executed in the already present/active RDM session and only a background RDM process was started and finished after executing.
Yes it seems like the same issue, let me know the results of your session!
Behavior in a teams shared and analyzed, issue will be passed on to development team for fix/solution.
Behavior in a teams shared and analyzed, issue will be passed on to development team for fix/solution.
Any update from that team?
I expect they will give another message that they have applied a fix, when I test the version released yesterday (2025.1.34.0) I see that it works on my side as before.
No new background processes remain present :-)
Thanks! looks like its working on my end as well!
This report can be closed
Hello,
Thank you for the follow-up.
I’ll go ahead and mark this topic as resolved. Please feel free to reply here if the issue arises again.
Best regards,
Jacob Lafrenière