Windows 11 22H2+ PSM-RDP Issues

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

PAM SaaS Articles
4 min read
L0 Member
No ratings

Impacts

PCloud + PSM + RDP Proxy + Windows 11 22H2 and newer Workstations

PCloud Component Versions 14.6 and 14.7

 

Related to

Known Issue: https://community.cyberark.com/s/article/KI00019661

Related Error: https://community.cyberark.com/s/article/Error-The-remote-session-was-disconnected-because-license-s...

 

Issue

PSM RDP connections fail with the following error:

ka3Vy00000AOy5JIAT__eid=ka3Vy00000AOy5J&feoid=00N2J000009R3kl&refid=0EMVy00000eTalq.png

 

Cause

This issue occurs because the Remote Desktop Connection client (mstsc.exe) on Windows 11 22H2 and newer requires elevated privileges to create the necessary license store in the registry (specifically under HKEY_CURRENT_USER\Software\Microsoft\MSLicensing) when it's not already present. This store is a local repository used to manage Client Access Licenses (CALs) for RDP sessions. If the license store hasn't been created when the PSM-RDP connection is launched from the PVWA, the connection attempt fails with the "remote desktop needs to be run with elevated privileges" error (often accompanied by details about license store creation failing due to access denied).

Steps

Workaround

According to https://windowsforum.com/threads/fixing-windows-11-remote-desktop-issues-after-24h2-update.352977/ a group policy change is required.

 

Step-by-Step Instructions:​

  1. Open Local Group Policy Editor:
    1. Click on the Start menu, type "Edit group policy", and launch the application.
  2. Navigate Through the Policy Hierarchy:
    1. In the left panel, expand Local Computer Policy > Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Connections.
  3. Modify the Network Detection Policy:
    1. In the right-side pane, locate and double-click "Select network detection on the server."
    2. Change the policy setting to Enabled.
  4. Configure Detection Options:
    1. Once enabled, you will see options for "Select Network Detect Level."
    2. Change the setting to "Turn off Connect Time Detect and Continuous Network Detect."

(Note: Some users have found that simply disabling Continuous Network Detect might suffice. Feel free to experiment with which configuration works best for your environment.)

  1. Apply Changes and Update Policies:
    1. Click Apply and OK to confirm your changes.
  2. Open a Command Prompt window (you might need administrator privileges) and run the command:

gpupdate /force

  1. Relaunch RDP connection from the PVWA.

 

Solution

Running mstsc.exe as Administrator once (even to any arbitrary remote host) creates the required registry entries with the necessary permissions. After that, non-elevated launches, like those triggered by PSM-RDP, can successfully access and use the existing store without encountering the error. Thank Microsoft for this added "feature."

 

Idira recommends the registry permissions be adjusted on HKEY_LOCAL_MACHINE\Software\Microsoft\MSLicensing. Ensure that the current user, Administrators, and "All Application Packages" have Full Control.

 

To apply this setting using a GPO, here are the steps:

On the DC, create or edit a GPO and ensure the GPO is linked to the OU containing the domain-joined workstations.

  1. In the Group Policy Management Editor, navigate to: Computer Configuration > Policies > Windows Settings > Security Settings > Registry.
  2. Right-click the Registry node and select Add Key.
  3. In the dialog box, manually enter the registry path:

MACHINE\Software\Microsoft\MSLicensing

  1. Click OK.
  2. In the Database Security for MACHINE\Software\Microsoft\MSLicensing window, click Add to specify the accounts or groups. Add the desired security principals, such as:
    1. Administrators
    2. Authenticated Users (or a specific group like Domain Users)
    3. All Application Packages (if needed for compatibility with modern apps or services)
  3. For each added principal, check Full Control (ensures read, write, and modify permissions).
  4. Ensure Allow inheritable permissions from parent to propagate is checked unless you have a specific reason to disable it.
  5. Click Advanced to verify or fine-tune permissions if needed (e.g., ensure permissions apply to "This key and subkeys").
  6. Finally, click OK to save the permissions settings.

 

Next, apply the GPO a limited group of computers or a test group for initial rollout.

If that works, then roll out the GPO org wide.

 

Verify the GPO has Been Applied

  1. Open regedit on a test workstation
  2. Navigate to HKEY_LOCAL_MACHINE\Software\Microsoft\MSLicensing
  3. Right-click the key, select Permissions, and confirm that the specified accounts (e.g., Authenticated Users, Administrators, All Application Packages) have Full Control.

 

Related Documentation

KB5051987 causes Windows 11 RDP Session to get Stuck at Login:

https://learn.microsoft.com/en-us/answers/questions/2169684/kb5051987-causes-windows-11-rdp-session-...

1.3.9 Connect-Time and Continuous Network Characteristics Detection:

https://learn.microsoft.com/en-us/openspecs/windows_protocols/ms-rdpbcgr/dc672839-4f4e-40b1-a71c-cd6...

1.3.1.1 RDP Connection Sequence

https://learn.microsoft.com/en-us/openspecs/windows_protocols/ms-rdpbcgr/023f1e69-cfe8-4ee6-9ee0-7e7...

 

1. Optional Connect-Time Auto-Detection: During the Optional Connect-Time Auto-Detection phase, the goal is to determine characteristics of the network, such as the round-trip latency time and the bandwidth of the link between the server and client. This is accomplished by exchanging a collection of PDUs (specified in section 2.2.14) over a predetermined period of time with enough data to ensure that the results are statistically relevant.

 

These links and documentation from Microsoft show the workaround setting has to do with RDP connection quality, not security; thus, no vulnerability is created by applying the suggested policies.

Rate this article:
  • 1578 Views
  • 0 comments
  • 0 Likes
Article Dashboard
Version history
Last Updated:
‎11-05-2026 11:47 AM
Updated by: