RDCMAN v3.21: Remote Desktop Connection Manager Bug List

Lee Wilmott 30 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.

6 answers

Sort by: Newest
Most helpful Newest Oldest
  1. Seng, Matthew McCutcheon 1 Reputation point
    2026-10-02T22:59:35.4033333+00:00

    Today I updated from 2.90 to 3.21 and ran into lots of credential and cert issues that I never had in 2.90.

    I spent basically all day troubleshooting with copilot and eventually narrowed it down to the fact that freshly-created servers worked fine (though wouldn't use my saved credentials), while servers loaded from an RDG file threw cert errors (specifically "server name doesn't match name in cert", and "cert auth not trusted"). Everything pointed to some change in the RDP stack, which happened to be applied to RDG-loaded servers, but not freshly-created servers for some reason.

    I went looking to see if there happened to be a newer version, or a changelog or something. Took me forever poking through various blogs and doc sites to find this forum.

    Anyway, after reading this thread I tried the -mstsc flag and it instantly fixed all my problems. Admittedly I am not well versed in this stuff, but what exactly happened here? Why the tectonic shift? And why would freshly-created servers be treated differently than RDG-loaded servers? That discrepancy alone was an insane goose chase.

    P.S. Another issue I noticed is that when not using -mstsc there is no longer a Log off server option in the context menu for servers. Is that intentional?

    Was this answer helpful?

    0 comments
  2. Iain Marshall 5 Reputation points
    2026-09-17T08:03:28.5766667+00:00

    The mouse cursor disappears every time I move it over a text box

    Was this answer helpful?

    1 person found this answer helpful.
  3. 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
  4. 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
  5. Adri fo 10 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?

    3 people found 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.