There seems to be no official documented mechanism for reporting bugs in Sysinternals stuff, so... Verified on RDCMan 3.1 (x64) exe build dated June 18th 2025, as well as earlier versions: If RDCMan is in the foreground, and or monitor sleep/power save mode happens (possibly screen saver) -- not lock screen! -- when the monitor powers back on, RDCMan no longer paints/redraws the session. You have to minimise then restore RDCMan for it to begin drawing again. This is 100% reproducible. Help > About > the hyperlink that leads to the Sysinternals website -- when clicking it, an application exception occurs. This is 100% reproducible. Stack trace for the 2nd item shows that this is an application/code bug, where for some reason the underlying code tries to actually execute a program named the website URL rather than launch registered web browser with said URL. Doing something like start {websiteurl} works just fine from Command Prompt, and other application built-in hyperlinks work fine, so this is definitely a bug in RDCMan. Edit: I tried to include a stack trace but the forum software rejected my post when attempting to do so. Great.

RDCMan: where to report bugs?

Jeremy Chadwick 0

There seems to be no official documented mechanism for reporting bugs in Sysinternals stuff, so...

Verified on RDCMan 3.1 (x64) exe build dated June 18th 2025, as well as earlier versions:

If RDCMan is in the foreground, and or monitor sleep/power save mode happens (possibly screen saver) -- not lock screen! -- when the monitor powers back on, RDCMan no longer paints/redraws the session. You have to minimise then restore RDCMan for it to begin drawing again. This is 100% reproducible.
Help > About > the hyperlink that leads to the Sysinternals website -- when clicking it, an application exception occurs. This is 100% reproducible.

Stack trace for the 2nd item shows that this is an application/code bug, where for some reason the underlying code tries to actually execute a program named the website URL rather than launch registered web browser with said URL. Doing something like start {websiteurl} works just fine from Command Prompt, and other application built-in hyperlinks work fine, so this is definitely a bug in RDCMan. Edit: I tried to include a stack trace but the forum software rejected my post when attempting to do so. Great.

Share via

RDCMan: where to report bugs?

Your answer