Home › Remote Desktop Services › 0x607

Remote Desktop Services · 0x607 · Windows 10 / Windows 11 / Windows Server 2019 / 2022

RDS Error 0x607: CredSSP Oracle Remediation Fix for Win10/11/Server

Error 0x607 occurs due to mismatched CredSSP patch levels post-CVE-2018-0886. Patch the server or temporarily set client policy to Vulnerable.

Error Details

FactValueSourceNote
Exact error stringAn authentication error has occurred. The function requested is not supportedmstsc.exe dialog boxError code 0x607
Affected OS Build RangeWindows 10/11, Server 2019/2022 (Post-May 2018 updates)Microsoft Security AdvisoryCVE-2018-0886
Registry Key for WorkaroundHKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\CredSSP\ParametersRegistry EditorDWORD AllowEncryptionOracle=2
Relevant Service/EndpointRemote Desktop Services (RDP)Windows ServicesPort 3389
Log Line SignatureEvent ID 6041 or Schannel Event 36888/36874Windows Event Viewer > SystemCredSSP authentication failure

Log Files to Check

What This Error Actually Means

The error code 0x607, often accompanied by the message "An authentication error has occurred. The function requested is not supported," is a specific failure within the Remote Desktop Services (RDS) authentication pipeline. It is not a generic network connectivity issue, nor is it typically a credential mismatch in the traditional sense. Instead, this error signifies a cryptographic handshake failure at the CredSSP (Credential Security Support Provider) layer. Specifically, it indicates that the client and server cannot agree on the security level required to mitigate the "Encryption Oracle" vulnerability (CVE-2018-0886). When Microsoft released the patch for this vulnerability in May 2018, they changed the default behavior of CredSSP from allowing vulnerable connections to blocking them by default. If a client machine has been patched and is configured to enforce strict security standards, but the target server remains unpatched or is configured to allow vulnerable encryption modes, the client will abruptly terminate the connection attempt with error 0x607. This mechanism is designed to prevent man-in-the-middle attacks that exploit weaknesses in the CredSSP protocol's encryption negotiation process.

Affected Versions and Scope

This issue affects any Windows environment where there is a version disparity between the client initiating the Remote Desktop Protocol (RDP) connection and the server accepting it. The scope includes Windows 10, Windows 11, Windows Server 2019, and Windows Server 2022. Crucially, this error manifests when a client running a post-May 2018 security update (such as KB4103723 or later cumulative updates) attempts to connect to a server that has not received the corresponding CredSSP patch. The "Affected OS Build Range" is effectively any build that has installed the mitigation for CVE-2018-0886. Conversely, systems that have never been updated since their initial deployment prior to May 2018 may not exhibit this error when connecting to each other, but they are vulnerable to exploitation. In modern enterprise environments managed via Microsoft Endpoint Manager (Intune) or Group Policy, the scope is determined by the "Encryption Oracle Remediation" policy setting. If the policy is set to "Mitigated" or "Force Updated Clients" on the client side, and the server does not support these modes, the connection fails. This is particularly common in hybrid environments where legacy servers are excluded from automatic Windows Update policies.

Where To Look First: Logs and Event IDs

To diagnose this issue accurately, you must inspect the event logs on both the client and the server, though the client-side logs are often more immediate. On the client machine, navigate to C:\Windows\System32\winevt\Logs\System.evtx. Look for Event ID 6041, which specifically denotes a CredSSP authentication failure. The log entry will typically state that the encryption oracle remediation policy blocked the connection. Additionally, check for Schannel errors, specifically Event IDs 36888 and 36874, which indicate SSL/TLS handshake failures related to certificate or protocol mismatches. On the server side, examine C:\Windows\System32\winevt\Logs\Security.evtx for audit failures, although these may be less specific regarding the CredSSP layer. To quickly extract relevant events using PowerShell, run the following command on the client: Get-WinEvent -FilterHashtable @{LogName='System'; ID=6041} -MaxEvents 5 | Format-List. This will display the most recent CredSSP failures, allowing you to correlate the timestamp with your connection attempt. If you need to verify the current policy state via logs, check the Application log for any warnings from the Microsoft-Windows-TerminalServices-RemoteConnectionManager operational log.

Root Causes

Cause 1: Unpatched Server with Mitigated Client Policy

The most common cause is a server that has not been updated with the May 2018 CredSSP security patch (KB4103723 or equivalent). The client, being up-to-date and running default policies, attempts to negotiate a secure connection. When the server responds with an older, vulnerable encryption mode, the client rejects it. You can tell this apart by checking the server's installed updates; if KB4103723 is missing, this is the root cause.

Cause 2: Group Policy Mismatch (Force Updated Clients)

An administrator may have explicitly configured the client's Group Policy to "Force Updated Clients." This setting requires the server to also be patched and configured to accept only updated clients. If the server is not patched, or if its policy is set to "Vulnerable," the connection is blocked. Distinguish this by checking the client's registry at HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\CredSSP\Parameters. If the value AllowEncryptionOracle is set to 0, the policy is forcing updated clients.

Cause 3: Intune Configuration Profile Misalignment

In cloud-managed environments, an OMA-URI configuration profile in Intune may be pushing a strict CredSSP policy to clients. If this profile is applied to devices connecting to on-premises servers that are not managed by the same update rings, a mismatch occurs. Verify this by checking the device compliance status in the Intune admin center.

Fix Procedure

  1. Patch the Server (Preferred): The only secure and permanent fix is to update the target server. Run Windows Update on the server to install the latest cumulative update, which includes the CredSSP patch. Reboot the server after installation.
  2. Verify Client Policy via PowerShell: On the client, check the current state of the CredSSP policy using PowerShell: Get-ItemProperty -Path "HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\CredSSP\Parameters" -Name "AllowEncryptionOracle" -ErrorAction SilentlyContinue. If this returns a value, note it. A value of 2 means "Vulnerable" (workaround), 1 means "Mitigated," and 0 means "Force Updated Clients."
  3. Apply Temporary Workaround (If Server Cannot Be Patched Immediately): If the server cannot be patched immediately, you must lower the client's security posture. Create the registry key if it does not exist: New-Item -Path "HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\CredSSP\Parameters" -Force. Then set the value to allow vulnerable connections: Set-ItemProperty -Path "HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\CredSSP\Parameters" -Name "AllowEncryptionOracle" -Value 2 -Type DWord.
  4. Configure via Intune (For Managed Clients): If managing via Intune, create a new Configuration Profile. Navigate to Intune admin center > Devices > Configuration profiles > Create profile. Select Platform: Windows 10 and later, Profile type: Templates, Template: Custom. Add the OMA-URI setting: ./Device/Vendor/MSFT/Policy/ConfigOperations/CredSSP/AllowEncryptionOracle with Data Type as Integer and Value as 2. Assign this to the affected device group.
  5. Revert Workaround: Once the server is patched, remove the registry key or update the Intune profile to revert to "Mitigated" (Value 1) or delete the policy to use defaults. Use Remove-ItemProperty -Path "HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\CredSSP\Parameters" -Name "AllowEncryptionOracle" on local machines.
Warning: Setting AllowEncryptionOracle to 2 (Vulnerable) exposes the client to potential man-in-the-middle attacks. This should only be used as a temporary emergency measure for critical business continuity and must be reverted immediately after the server is patched. Never leave this setting in production environments long-term.

Error Code Variants

Error Code Description Distinguishing Feature
0x607 CredSSP Authentication Failure Specifically related to Encryption Oracle remediation mismatch. Occurs during initial authentication handshake.
0x112f Remote Desktop Connection Broker Error Related to load balancing or session redirection, not CredSSP encryption. Check RD Connection Broker logs.
0x5 Access Denied Generic permission error. Usually indicates the user account is disabled, locked out, or lacks RDP permissions.
0x104f Certificate Error Related to SSL certificate validation failures, not CredSSP protocol negotiation. Check server certificate trust chain.

Verification

To verify the fix, attempt to reconnect using mstsc.exe. A successful connection will result in a standard RDP session without any error dialogs. To confirm programmatically, check the System log on the client again for Event ID 6041. If the fix is successful, no new 6041 events should appear after your connection attempt. You can also verify the server's patch level by running Get-HotFix | Where-Object {$_.HotFixID -like "KB4103723"} on the server (or the relevant cumulative update ID for newer builds). In Intune, navigate to Intune admin center > Devices > Monitor and check the device's compliance status to ensure it meets the security baseline requirements. Additionally, use dsregcmd /status on the client to ensure domain join status is healthy, as authentication issues can sometimes be compounded by directory service connectivity problems.

Prevention

To prevent recurrence, implement a strict patch management policy that ensures all RDS servers are updated within the same maintenance window as clients. Use Microsoft Endpoint Configuration Manager (MECM) or Intune to enforce Windows Update for Business policies. Create a baseline configuration profile in Intune that monitors the presence of the CredSSP patch on servers and alerts if it is missing. Navigate to Intune admin center > Devices > Compliance policies and create a policy that checks for specific update IDs on server operating systems. Furthermore, standardize the "Encryption Oracle Remediation" setting across all devices via Group Policy or Intune Configuration Profiles to "Mitigated" (Value 1) rather than leaving it at default or "Vulnerable." This ensures that while connections are secure, they do not unnecessarily block unpatched servers unless explicitly forced. Regularly audit your RDS infrastructure using PowerShell scripts that query the patch status of all terminal servers and compare it against the client fleet's policy settings.

Tip: Use the Test-NetConnection cmdlet with the -Port 3389 parameter to verify basic connectivity before diving into CredSSP logs. If port 3389 is blocked, you will not see a CredSSP error but rather a network timeout. This quick check saves time by ruling out firewall issues first.

Sources & References

Get new error code fixes by email

Product-specific solutions for Intune, Autopilot, SCCM and Entra ID — straight to your inbox. No spam.