About this article: This article is reviewed against the cited sources. This is source research, not lab validation. Check the stated versions and your own requirements before making changes.
Remote Desktop Connection stops with:
An authentication error has occurred. The function requested is not supported. Remote computer: name This could be due to CredSSP encryption oracle remediation.
The tempting fix is to set a policy to Vulnerable on the client. Microsoft's own warning is that this exposes the remote server to attack. The proper fix is to find which end of the connection is missing the CredSSP update, or has it installed but has not been restarted, and fix that end.
What you see
- The message above, or "The token supplied to the function is invalid", both listed by Microsoft as errors from a blocked CredSSP pairing (Microsoft support, CredSSP updates for CVE-2018-0886).
- On the client computer, event ID 6041 in the System log, source LSA (LsaSrv): "A CredSSP authentication to <hostname> failed to negotiate a common protocol version. The remote host offered version <Protocol Version> which is not permitted by Encryption Oracle Remediation."
- The same client may reach other servers, or other clients may reach the same server. Comparing them points to the end that differs.
Why it happens
CredSSP is an authentication provider that processes sign-in requests for other applications, including Remote Desktop Connection. In March 2018 Microsoft fixed a flaw in it (CVE-2018-0886) where an attacker could relay user credentials to run code on the target system. The update added a policy, Encryption Oracle Remediation, with three settings (Microsoft support, KB 4093492):
| Setting | Registry value | As a client | As a server |
|---|---|---|---|
| Force updated clients | 0 | Will not fall back to the insecure version | Will not accept unpatched clients |
| Mitigated | 1 | Will not fall back to the insecure version | Accepts unpatched clients |
| Vulnerable | 2 | Falls back, exposing remote servers to attack | Accepts unpatched clients |
A May 2018 update changed the default from Vulnerable to Mitigated. Microsoft's Remote Desktop troubleshooting page sums up the result: clients that have the updates cannot connect to servers that do not have them, or to updated servers that have not been restarted (Microsoft Learn, User can't authenticate or must authenticate twice).
Microsoft's matrix shows two blocked pairings:
- An updated client (Force updated clients or Mitigated) connecting to an unpatched server. Microsoft's Azure article calls this the most common scenario (Microsoft Learn, CredSSP encryption oracle remediation on an Azure VM).
- An unpatched client connecting to a server set to Force updated clients.
Microsoft also says third-party Remote Desktop clients and servers must use the latest CredSSP version, so an older third-party product on either end can cause the same block.
How to prove the cause
1. Read event 6041 on the client. It confirms the block is CredSSP negotiation and names the remote host.
2. Check whether the server has the update. Microsoft's Azure article gives the check: the update history, or the version of TSpkg.dll in %systemroot%\system32. Its table lists the first patched versions; for Windows Server 2016 that is 10.0.14393.2248 (KB 4103723).
3. Check whether the server has been restarted since updating. Microsoft notes that an updated server that has not been restarted is blocked as well, and that any change to the policy also needs a restart.
4. Check the policy on both ends. The setting is in Computer Configuration > Administrative Templates > System > Credentials Delegation > Encryption Oracle Remediation, stored in the registry value AllowEncryptionOracle under HKLM\Software\Microsoft\Windows\CurrentVersion\Policies\System\CredSSP\Parameters. Run gpresult /H on each end to see which policy sets it. A server at 0 (Force updated clients) refuses unpatched clients.
5. Note any third-party client or server in the connection and check with its vendor that it supports the current CredSSP version.
The fix
Microsoft's resolution is to update and restart all systems: install the CredSSP updates on both client and server so the connection is secure (Microsoft Learn, User can't authenticate or must authenticate twice).
- Server missing the update: install the CredSSP update for that Windows version and restart. Microsoft lists the update numbers per version in KB 4093492 and on the CVE-2018-0886 page. If updates will not install, fix the update fault first.
- Server updated but not restarted: restart it.
- Unpatched client refused by a Force updated clients server: update the client. Microsoft's guidance for Force updated clients is not to deploy it until every client supports the new version.
- Third-party product: update it to a version its vendor says supports the current CredSSP.
Microsoft recommends setting the policy to Force updated clients or Mitigated on clients and servers.
Temporary workaround, only while updates are in progress
Microsoft lists a workaround for an updated client that must reach an unpatched server: set the client's Encryption Oracle Remediation policy to Enabled with Protection Level: Vulnerable, or set the registry value from an elevated prompt:
REG ADD HKLM\Software\Microsoft\Windows\CurrentVersion\Policies\System\CredSSP\Parameters\ /v AllowEncryptionOracle /t REG_DWORD /d 2
Microsoft's warning: after this change an insecure connection is allowed that exposes the remote server to attacks. Use it only until the server is updated, then set the policy back to Mitigated (1) or Force updated clients (0) and restart the client.
How to confirm the fix
- The Remote Desktop connection completes from the client that failed.
- No new event 6041 on that client.
AllowEncryptionOracleon the client is 0 or 1, not 2, or the policy is not set at all (Mitigated is the default after the May 2018 update).
What to watch afterwards
- Workarounds left in place. A client set to Vulnerable stays exposed after the server is fixed. Find and reverse every one.
- Servers that update but do not restart, which Microsoft names as a cause in their own right.
- Older or unsupported systems and third-party Remote Desktop products. These follow from Microsoft's matrix as the remaining ways to hit a blocked pairing.
Read next
Related articles you may want next.
- TroubleshootingRemote Desktop "An internal error has occurred": certificate, security layer and service checksA direct Remote Desktop connection fails with "An internal error has occurred" before or after you enter credentials. Rule out the network, test the security negotiation, then check the server's Remote Desktop certificate, key permissions and listener.Read article
- TroubleshootingRD Gateway Connection Failures: Certificate, CAP, RAP and Transport ChecksFind why RD Gateway connections fail: check the certificate name, read Gateway events 200/201/300/301/304, test CAP and RAP logic, central NPS timeouts, and TCP 443 / UDP 3391.Read article
- TroubleshootingWindows Cumulative Update Fails: DISM and SFC DiagnosisCumulative update failing with 0x800f0831 or 0x80073712? Read CBS.log, run DISM and SFC scans that do not repair, then choose a repair source that matches.Read article
Risks and limits
- Setting a client to Vulnerable exposes the servers it connects to. Microsoft's other temporary option, forcing the RDP security layer and turning off Network Level Authentication on the server, also reduces security; Microsoft recommends using either only temporarily, if at all.
- Every change to this policy needs a restart.
- Microsoft notes that a server can be set to fall back to TLS for authentication, so results can differ from the matrix, which describes CredSSP behaviour only.
- The Azure article's scripts download and install the 2018 update files; they are written for Azure VMs and are not repeated here.
Sources
- Microsoft Learn, "User can't authenticate or must authenticate twice", applies to supported Windows Server versions, last updated 12 February 2026: https://learn.microsoft.com/en-us/troubleshoot/windows-server/remote/cannot-authenticate-must-authenticate-twice
- Microsoft support, "CredSSP updates for CVE-2018-0886" (KB 4093492), page dated 2 August 2024: https://support.microsoft.com/en-us/help/4093492
- Microsoft Learn, "Error when you try to RDP to a Windows VM in Azure: CredSSP encryption oracle remediation" (KB 4295591), last updated 25 August 2023: https://learn.microsoft.com/en-us/troubleshoot/azure/virtual-machines/windows/credssp-encryption-oracle-remediation
Next step
Lowering the policy makes the error go away and leaves the server exposed. NetLeverage has looked after business servers since 2002. If you are seeing the CredSSP message, talk to us through managed support with event 6041 from the client and the update history of the server it is trying to reach.
This article was originally published on .