2026.3.x - Terminal Services console no longer works

A fix for this issue has been implemented in version 2026.3.13.0

2026.3.x - Terminal Services console no longer works

avatar

Hi all

I use the "Terminal Services console" tool under the "System administration" category very frequently to manage and, if necessary, log off users logged into a server.
Since upgrading to version 2026.3.x (currently 2026.3.9.0), I receive the following error message when launching the tool:
"Unable to retrieve Terminal sessions; verify your credentials."
In the properties of the host object, under Management tools -> Tools -> Credentials, I have enabled "Use session credentials". I have also tried using "Username and password" with the credentials of a Domain Administrator. Unfortunately, without success.
A simple RDP connection works without any issues.

I am running the application with a user who also has administrator privileges on the target host.

What can I do to fix this?

All Comments (4)

avatar

Hello Michael,

Thank you for the detailed report.

We were able to reproduce the issue with the Terminal Services console in RDM 2026.3 on our side.
This confirms it is a problem in the application, not with your credentials or your setup.

We have forwarded it to our QA team, and it is now under investigation.

Since you use the tool to log off users, these workarounds should help in the meantime:

  • Use the Windows commands below, run from the same account:

quser /server:<host>

logoff <session ID> /server:<host>


  • Run the portable version of RDM 2026.2.19.0 next to your current install, only for this tool. Another customer confirmed that the tool still works in that version.


We will let you know as soon as a fix is available.

Best regards,

Alexis Beauparlant

avatar

Hello Alexis,

Thanks for your answer. I'll be using the portable version 2026.2.19.0 in the meantime until a fix is released.

Best regards,
MIchael

avatar

Hello,

Thank you for your patience while our team looked into the issue you reported.

I'm happy to let you know that the latest version of Remote Desktop Manager (2026.3.13.0) includes a fix for this problem. You can download it from our website here:
https://devolutions.net/remote-desktop-manager/download/

Once you have installed the update, could you please test it in your environment and confirm that everything now works as expected? If the issue persists or if you notice anything unusual related to the same original problem, just reply to this message with a few details, and we will be glad to look into it further.

Thank you for your collaboration.

Best regards,

Érica Poirier

avatar
Hello,

Thank you for your patience while our team looked into the issue you reported.

I'm happy to let you know that the latest version of Remote Desktop Manager (2026.3.13.0) includes a fix for this problem. You can download it from our website here:
https://devolutions.net/remote-desktop-manager/download/

Once you have installed the update, could you please test it in your environment and confirm that everything now works as expected? If the issue persists, or if you notice anything unusual related to the same original problem, just reply to this email with a few details, and we will be glad to look into it further.

Thank you for your collaboration.

Best regards,


@Erica Poirier
Hello there
for me it's fixed

A fix for this issue has been implemented in version 2026.3.13.0