Connecting to a remote workstation or Windows server via Remote Desktop Connection (mstsc.exe) only to be stopped by the critical dialogue: “An authentication error has occurred. The function requested is not supported. Remote computer: <hostname>. This could be due to CredSSP encryption oracle remediation” prevents remote administration. The connection aborts before reaching the remote desktop login screen. This error is triggered by Credential Security Support Provider protocol (CredSSP) policy enforcement. When Microsoft patched the CVE-2018-0886 vulnerability, Windows began blocking unpatched or misaligned RDP connections where client and server encryption oracle remediation settings mismatch. This guide explains how to resolve CredSSP and Network Level Authentication (NLA) conflicts safely in Windows 11.
What Causes the Remote Desktop CredSSP Authentication Error?
Remote Desktop uses CredSSP to pre-authenticate user credentials securely prior to establishing the RDP session tunnel. The authentication failure occurs due to:
- CredSSP Encryption Oracle Remediation Policy: The client workstation enforcing “Force Updated Clients” or “Mitigated” while the target remote server lacks the required cumulative security update.
- Network Level Authentication (NLA) Mismatches: The remote host demanding NLA verification while the client’s security provider cannot establish a compatible TLS handshake.
- Clock and Time Skew Drift: Time discrepancies greater than 5 minutes between the client and remote domain controller causing Kerberos ticket rejection.
- Corrupted Remote Desktop Credentials: Stale RDP credentials stored in Windows Credential Manager attempting authentication with outdated NTLM tokens.
Step 1: Configure Encryption Oracle Remediation via Group Policy
On Windows 11 Pro and Enterprise editions, configuring the local CredSSP policy allows secure fallback connections while the remote server is being updated.
- Press Win + R, type
gpedit.msc, and press Enter to launch the Local Group Policy Editor. - Navigate through the policy tree:
Computer Configuration > Administrative Templates > System > Credentials Delegation - In the right-hand panel, double-click the policy named:
Encryption Oracle Remediation - Select the radio button for Enabled.
- In the Protection Level dropdown box that appears under Options, change the setting to:
- Vulnerable (allows connection to unpatched hosts) or Mitigated.
- Click Apply and OK.
- Open Command Prompt as administrator and refresh system policies:
gpupdate /force - Relaunch Remote Desktop Connection and connect to the remote host.
Step 2: Configure the CredSSP Policy via the Windows Registry (Home & Pro)
If you are running Windows 11 Home (which lacks gpedit.msc), apply the policy directly through the Windows Registry.
- Press Win + R, type
regedit, and press Enter. - Navigate to the following registry path:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System - Right-click on the
Systemfolder, select New > Key, and name it:CredSSP - Right-click on the new
CredSSPkey, select New > Key, and name it:Parameters - Select the
Parameterskey. In the right panel, right-click, choose New > DWORD (32-bit) Value, and name it:AllowEncryptionOracle - Double-click
AllowEncryptionOracle, set its Value data to 2 (which corresponds to Vulnerable / Fallback), and click OK. - Close the Registry Editor and retry your RDP session.
Step 3: Temporarily Disable Network Level Authentication (NLA) on the Remote Host
If you have administrative access to the remote machine (via console or alternative management tools), disabling NLA allows the session to connect.
- On the remote host, press Win + R, type
sysdm.cpl, and press Enter. - Navigate to the Remote tab.
- Under the Remote Desktop section, untick the checkbox for:
“Require computers to use Network Level Authentication to connect (recommended)”. - Click Apply and OK.
- Alternatively, execute this PowerShell command with administrative privileges on the remote server:
(Get-WmiObject -class "Win32_TSGeneralSetting" -Namespace root\cimv2\terminalservices -Filter "TerminalName='RDP-Tcp'").SetUserAuthenticationRequired(0) - Security note: Once you log in and install the latest Windows cumulative updates on the remote server, re-enable NLA to maintain enterprise security standards.
Step 4: Synchronise System Time and Clear Stale RDP Credentials
Kerberos authentication fails if the client and server clocks drift apart by more than 300 seconds.
- Right-click the clock in the bottom-right corner of the taskbar and select Adjust date and time.
- Click the Sync now button under Additional settings.
- Next, press Win + S, type
Credential Manager, and open it. - Click Windows Credentials, scroll down to Generic Credentials, and find any entries starting with
TERMSRV/<hostname>. - Click the arrow and select Remove to eliminate cached, corrupted passwords.
Troubleshooting Summary for Remote Desktop Authentication Error
| Remediation Level | System Setting | Value / Action |
|---|---|---|
| Group Policy (Pro/Ent) | Encryption Oracle Remediation |
Set to “Enabled” with Protection Level “Vulnerable” |
| Windows Registry (Home) | AllowEncryptionOracle DWORD |
Set Value data to 2 under CredSSP\Parameters |
| Remote Host Configuration | Network Level Authentication (NLA) | Untick NLA requirement under System Properties > Remote |
| Credential Management | Windows Credential Manager | Delete outdated TERMSRV/ records and sync time via w32tm |
By aligning CredSSP encryption remediation policies and resolving NLA discrepancies, you eliminate RDP authentication blocks and restore secure remote management in Windows 11.