mstsc.exe not foud since upgrade to version 2022.3.15

mstsc.exe not foud since upgrade to version 2022.3.15

avatar

Since the upgrade to version 2022.3.15, rmd is unable to find the mstsc.exe. Following error is mentioned in the application log: System.ArgumentException: Illegal characters in path.
I checked the Windows path and evrythibg is fine. mstsc.exe can be started from anywhere within a cmd window.
Any idea ?
Thanks

All Comments (11)

avatar

Same problem

avatar

Hello,

can you please verify the option in File => Options => Path => Configure installation path => Microsoft Remote Desktop Client

Regards,
Min

avatar

The default path is c:\windows\system32.

br,

Stefan

avatar

Hello Stefan,

alright this is fine - when do you exactly get the entry in the RDM application log? If you try to open an External RDP session?

Do you also receive an error message or just the entry in the app log?

Thanks!

Regards,
Min

avatar

The error occurs only with external display; if the display parameter is set to embedded, it is working fine.
Here is the complete error message in the log file:

System.ArgumentException: Illegal characters in path.
at System.IO.Path.CheckInvalidPathChars(String path, Boolean checkAdditional)
at System.IO.Path.Combine(String path1, String path2)
at Devolutions.RemoteDesktopManager.Business.Connectors.RemoteDesktopConnector.Connect(Connection connection, OpenConnectionMode openConnectionMode)

avatar

The error displayed within the application is "Unable to find mstsc.exe, Microsoft Remote Desktop Client must be installed."

avatar

Hi Stefan,

Would you mind telling me the exact name of the entry you're trying to open?

When we create the log file, we use the entry's name, so this could be where the invalid characters come from.

Thank you!

Jonathan Del Signore

avatar

Hi Jonathan,

This is the entry: KORTRIJK | Windows Server - OCI IDtech
I replaced the pipe | with another character, and it is working.
Thanks for the tip !

Stefan

avatar

Alright thanks for testing, we'll open a ticket to protect this issue from happening in the future.

Regards

Jonathan Del Signore

avatar

Hello,

We've fixed this issue internally. It will be included in the next version 2022.3.16.0.

Regards

Jonathan Del Signore

avatar

Thanks for your quick support!