RDCMAN v3.21: Remote Desktop Connection Manager Bug List

Lee Wilmott 20 Reputation points
2026-08-25T13:03:17.6766667+00:00

RDCMAN v3.21

A list of known bugs in RDCMan v3.21...

  • "Recent" Built-in group doesn't work.
  • Connects using the credentials for the RD Gateway (rather than the credentials configured for the server). (It appears that if the Gateway credentials aren't valid for the remote server then the credentials for the remote server are used).
  • "Connect Server As..." is ignored! This might be due to the above!
  • The hotkeys are not passed through to the Remote Desktop Server (for example, if the Remote Desktop has focus and I press the "Windows" key then my workstation shows the Start Menu - rather than my Remote Desktop showing the Start Menu).
  • If you are Full Screen mode and press "escape" within your Remote Desktop then you are exited out of Full Screen mode (rather than passing the Escape keypress to the remote session). Might be related to the above!
  • Clicking the URL in the About Box doesn't work.

I am staying on version v3.12 for now. Sadly the last two releases have been very poor.

Personally I think it's worth pulling this release until it's been fixed.

I hope to see these issues fixed because this application is REALLY useful!

Many thanks!

Posting in hope that it is seen by the developers! Fingers crossed!

This message has been posted here: https://techcommunity.microsoft.com/blog/sysinternals-blog/process-monitor-v4-1-zoomit-12-3-for-macos-rdcman-v3-21-and-zoomit-v12-21/4548264

Sysinternals
Sysinternals

Advanced system utilities to manage, troubleshoot, and diagnose Windows and Linux systems and applications.

4 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Adri fo 0 Reputation points
    2026-08-31T09:50:18.7833333+00:00

    Hi,

    I am experiencing an issue with version 3.21. When connected to a server and running ssms.exe, the mouse cursor disappears inside the central panel of SSMS.

    I tested running standard MSTSC directly (mstsc.exe) and it works fine, but the problem occurs in version 3.21.

    Could you please check if version 3.22 resolves this issue?

    Thank you,

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  2. E Mor Ajpf 0 Reputation points
    2026-09-10T09:55:02.9066667+00:00

    Connect to console does not have any effect either on v3.21, whereas on 3.12 it does work.

    Was this answer helpful?

    0 comments
  3. Schindler Christian 26 Reputation points
    2026-09-03T08:24:47.7033333+00:00

    I'm experiencing the following:

    Connecting through a RDP Gateway is extremly slow and only shows a blank screen.

    Switching back to previous version fixes this. Also stored credentials get corrupted with this version.

    Was this answer helpful?

    0 comments
  4. Alex Mihaiuc 261 Reputation points Microsoft Employee
    2026-08-26T09:49:26.5866667+00:00

    Hey Lee,

    Thank you for the heads-up! Would you be willing to try v3.22?

    You can switch to the "old" RDCMan by launching it with the "-mstsc" option, but it's just a stopgap.

    I currently claim about the upcoming version that:

    • I fixed Recent.
    • I added 2 separate credentials workflows for remote desktop gateways. Any combination of <gateway credentials>, <server credentials> and <offered>, <not offered> should be treated in a deterministic manner now.
    • For the hotkeys to work, the control needs to be full screen. It's a limitation of the new h264 / h265 based remote desktop engine, and an update will arrive. That's why Esc is special, as well.
    • Didn't know about the website invocation from Help! Fixing.

    I also quoted you in the internal discussion about the new engine.

    Cheers,
    Alex

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.