- An Authentication Error Has Occurred Windows 10
- Authentication Error Has Occurred Remote Desktop Windows 10
- Authentication Error Has Occurred Credssp Rdp
- Remote Desktop Authentication Error 0x80004005
In March 2018, Microsoft released a security update that fixes a vulnerability in the Credential Security Support Provider Protocol (CredSSP). This vulnerability (CVE-2018–0886) allows an attacker to remotely execute arbitrary code on a vulnerable Windows host with an open RDP port (TCP/3389). In May 2018, an update “2018-05 Security only/Monthly Rollup” was released. It blocks the connection to computers with an affected version of CredSSP.
Good Article Mohamed! I will strongly suggest to read the article and in detail CVE-2018-0886.When I found that issue few weeks ago after the CVE article I've decided to patch immediately few servers, the main reason is that 'Any change to Encryption Oracle Remediation requires a reboot.' So I preferred to apply the hotfix instead of applying a regkey or create a group policy that should apply. Obviously, it's never a good idea to expose remote desktop publicly, in this setup the firewall was doing incoming connection filtering based on clients' public IP address. The issue only affected the PC that was not in the domain. I found a couple of ways to resolve the issue: Use a different user account to connect to the non-domain PC. A) A windows 7 machine hosting Remote Desktop: A client Windows 7 PC had no problem connecting to it, but the same user connecting from a Windows 10 machine failed. B) If the client is not patched while the server is updated, RDP can still work.
When you try to connect to a remote computer with a vulnerable CredSSP from Windows 10/Windows Server 2016, you receive the Remote Desktop Connection error:
An authentication error has occurred.
The function is not supported.
Remote Computer: hostname
This could be due to CredSSP encryption oracle remediation.
For more information, see link.
On Windows 7, the CredSSP error looks like this:
An authentication error has occurred.
The function requested is not supported.
- An authentication error has occurred (Code: 0x607) Remote Computer: RDSHost.domain.local. A 0x607 error is caused by using an invalid security certificate for authentication. Certificate validation is picky, for good reason. While the error points to a failed certificate, it doesn’t share any information about which certificate failed or how it failed.
- May 06, 2020 The following error appeared on a Windows 7 based computer, when I tried to connect to a Server 2012 via the Remote Desktop Connection app: 'An authentication error has occurred. The Function Requested is not Supported.' At the same time, the Remote Desktop connection is successful from Windows 10 based PCs.
Remote computer: hostnname
To fix This could be due to credssp encryption oracle remediation error, you need to install the latest Windows security update on the remote computer. You can install the latest Cumulative Update for your Windows version. You can download the update manually via Microsoft Update Catalog or install it via Windows Update or WSUS.
Hint. CredSSP authentication error appears only when you try to connect via RDP from a computer on which the latest security updates are installed to a non-updated computer (for example, a computer that never gets updates, or a clean installed device with a Windows 10/Windows Server 2016 build that was released before March 2018).
An Authentication Error Has Occurred Windows 10
Hint. There is a workaround allowing you to connect to a computer with a vulnerable version of CredSSP. To do this, you need to configure a special Group Policy parameter named Encryption Oracle Remediation on your computer from which you are establishing the Remote Desktop connection.
- Press Win+R, type gpedit.msc, and press Enter;
- Go to the following section of the Local Group Policy Editor: Computer Configuration > Administrative Templates > System > Credentials Delegation;
- Open the policy setting Encryption Oracle Remediation;
- Change its state to Enabled, and set Vulnerable in the Protection Level field;
- Update the Group Policy settings using:
Hint. You can also allow your computer to connect to vulnerable versions of CredSSP through the registry. Run the following command through elevated command prompt:
Now you can connect to the remote host via RDP and install the updates. After upgrading, don’t forget to disable the policy or reset the AllowEncryptionOracle registry value to its original value:
There are 3 options in the “Encryption Oracle Remediation” policy:
- Vulnerable — the client can connect to vulnerable computers;
- Mitigated — the client cannot connect to vulnerable servers, but the servers can allow vulnerable clients to connect;
- Force Updated Clients — secure RDP CredSPP interoperability layer.
How to Configure DHCP Conflict Resolution?If from a computer that doesn’t have the CredSPP security update installed you can’t connect to an updated RDP/RDS host with the “Force updated clients” option enabled, you can allow the server to accept connections with an affected version of CredSPP. To do this, you need to enable the policy with the Mitigated value on the server. In this way, to make changes to the server you can remotely connect to it via PowerShell under admin credentials:
And allow the connection:
In all cases, Microsoft always recommends installing the latest Windows updates on both the RDP server and the client.
AuthorAuthentication Error Has Occurred Remote Desktop Windows 10
Recent Posts
Cyril KardashevskyI enjoy technology and developing websites. Since 2012 I'm running a few of my own websites, and share useful content on gadgets, PC administration and website promotion.Latest posts by Cyril Kardashevsky (see all)