About RDP client behavior after MS update

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements

Welcome Idira to LIVEcommunity!

Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.

Meet Idira

About RDP client behavior after MS update

L4 Transporter

Hello,

Due to new MS updates on workstations, the RDP client behavior has changed and is now more security-sensitive, resulting in an interactive popup for anyone using PAM.

The screen is as follows:Field_Content_versions_oct20__068Vy00001Mq2AcIAJ.pngFrom what I've seen, the point is that if the publisher isn't signed, the RDP client now asks for confirmation. I've already tried a few steps, including following this KB: Sign the RDP file | CyberArk Docs

Basically, you create a certificate for the PVWAs, specifying it in the web config and portal options.

 

I've gotten a warning that the publisher is signed. I've also checked the .rdp files generated by the PVWAs, and the signature is OK.

Field_Content_versions_oct20__068Vy00001Mr6JtIAJ.png 

Despite this, the warning doesn't go away, even adding a new certificate to the PSMs with the balanced address.

Even changing the intended purposes of the certificates doesn't fix it. From what I understand, PVWAs require a "code signing" certificate to sign the RDPs, and PSMs require a "server authentication and remote desktop auth" certificate. However, I'm not finding precise details on how the certificates should be generated and configured.

 

Could you help me.

 

Thanks in advance

 

Regards

Simona

6 REPLIES 6

L4 Transporter

Hello,

If code signing is a required enhanced key usage, then the issuing CA must also include the code signing EKU.

Normally the intended purposes of a certificate cannot be changed after issuance, plus there are dependencies on what the certificate is capable of based on the issuing CA capabilities. So even if the end entity certificate intended purposes is manually modified, it might not work due to restrictions of the issuing CA.

 

I previously asked the community and opened a case to determine certificate requirements for each CyberArk component. The replies were only for PTA and documentation could not be provided for remaining components.

For example, the PVWA documentation should describe if certificates require Client Authentication, Server Authentication, or Code Signing, depending on what capabilities are being configured.

Note - If forced to use the Digicert Software Trust Program to sign files, then another route is needed for on the fly signing as they require files to be scanned before signing.

 

L5 Sessionator

L1 Bithead

This doesn't fix your issue but if you need to revert to the previous dialog behavior you can change a registry key documents in the link below towards the bottom of the page.

 

https://learn.microsoft.com/en-us/windows-server/remote/remote-desktop-services/remotepc/understanding-security-warnings

 

L1 Bithead

I also found where another post said they made some registry changes after signing and it fixed their issue, see the below post.

https://community.cyberark.com/s/question/0D5Vy00002Ru95bKAB/signed-cyberark-psm-rdp-files-still-prompt-verify-the-publisher-after-windows-11-kb5082052

 

Hi simonavittori,

Starting with the April 2026 security update, the Remote Desktop Connection app shows new security warnings by default when you open RDP files.

 

If the update causes temporary disruptions in your environment, you can revert to the previous dialogue behaviour by setting a registry value.

 

Select Start, type Registry Editor, and then open it.

 

Go to and modify the key (add it if not present):

HKLM\Software\Policies\Microsoft\Windows NT\Terminal Services\Client

 

with the following values:

 

Name: RedirectionWarningDialogVersion

Type: REG_DWORD

Data: 1

 

L4 Transporter

Hi @simona vittori​ 

Several community members have shared answers to your question. Could you let us know if any of these resolved your issue?

If so, please mark the appropriate answer as “Select as Best” to help other members find the solution easily.

If the issue remains unresolved, I recommend submitting a ticket with our support team for further assistance.

Thank you,

Shaked

  • 321 Views
  • 6 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!