CredSSP encryption oracle remediation Windows Origin: Platform & cloud Last updated 15 Oct 2026

Remote Desktop: An authentication error has occurred. The function requested is not supported. This could be due to CredSSP encryption oracle remediation

The RDP client and server disagree on CredSSP security updates — one side is patched and enforcing, the other isn’t.

Exact message you may see CredSSP encryption oracle remediationAn authentication error has occurred. The function requested is not supportedThis could be due to CredSSP encryption oracle remediation
Seen on: Windows

Meaning

After the CVE-2018-0886 updates, patched clients refuse to connect to unpatched servers (and vice versa depending on policy). The real fix is updating the server; a temporary client policy can relax it.

Common causes

  • Server missing CredSSP security updates
  • Client policy set to Force Updated Clients
  • NLA/CredSSP misconfiguration

⚡ Quick fix

  1. Install current Windows updates on the server
  2. Temporarily set Encryption Oracle Remediation to Vulnerable on the client (then revert)
  3. Use the console/Hyper-V/Azure serial console to patch the server

Detailed fix by platform

Windows

  1. reg add HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\CredSSP\Parameters /v AllowEncryptionOracle /t REG_DWORD /d 2 /f # temporary; revert after patching

How to diagnose

  1. Patches — Server patch level
  2. Policy — Encryption Oracle Remediation setting on both sides

🔧 Still not fixed?

Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:

Where this error sits

Origin: Platform & cloud. Errors that are often confused with or caused by this one (click to open):

0x80070005 — Windows Error 0x80070005 (E_ACCESSDENIED): Access is denied (Windows)0x800700050x800704EC — 0x800704EC: This program is blocked by group policy (Windows Defender) (Windows)0x800704EC403 Forbidden wp-admin — WordPress: 403 Forbidden on wp-admin, wp-login.php or admin-ajax.php (WordPress)403 Forbidden wp-adminAADSTS50053 — AADSTS50053: Your account is locked (Smart Lockout) / sign-in blocked due to suspicious activity (Azure)AADSTS50053antiforgery token could not be decrypted — ASP.NET Core: The antiforgery token could not be decrypted / The required antiforgery cookie is not present (400 Bad Request) (.NET)antiforgery token cou…invalid algorithm — JWT error: invalid algorithm / The specified alg value is not allowed / jwt signature is required (Authentication)invalid algorithminvalid csrf token — ForbiddenError: invalid csrf token (EBADCSRFTOKEN) (Authentication)invalid csrf tokenis damaged and can’t be opened — macOS: “App” is damaged and can’t be opened. You should move it to the Trash. (macOS)is damaged and can’t …CredSSP e…

Explore the map of this error Full error map →

🧠 Still stuck? Analyze your error

Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.

💬 What worked for others

No tips yet — did something else fix this for you?

Share what worked for you

Tips are checked by an editor before they appear. Links are removed.