Solidify when Remote Desktop is connected with Secure Client 5.x

[Translator]

Updated from AnyConnect 4.10 to Secure Client 5.1.8.105.

The installation itself succeeds without any problems, but after the version upgrade, when attempting a Remote Desktop (RDP) connection, the destination freezes and becomes unresponsive immediately after the RDP connection is established after connecting to the VPN.

The local logon to the destination works correctly, so the destination is not fixed. Also, there are no problems with communication other than RDP. Some devices, not all, are experiencing an incident, and this mainly occurs on thin client devices. OS is Windows 10 or 11.

Assuming any bugs since the issue resolves when reverting to the old version. If anyone here has encountered a similar incident and/or has already solved it, appreciate it if you could share your insights.

It would be helpful if you could provide guidance on any logs or commands that should be collected when requesting Cisco TAC to open a case

[AViftrup]

Always collect DART logs from your Secure Client when creating a TAC case on this matter.

Based on this post information, I cannot determine a root-cause.

DART can be installed with your setup of Secure Client as a module.

[Translator]

RDP on Windows may solve the problem by making a TCP connection.
Why don't you try it?

[Translator]

Thank you for posting.

I didn't know that there was a way to limit it to TCP. I'd like to try to eliminate it or not.