It is a pity to see the Oracle CredSSP Encryption recovery error when trying to connect to a Windows computer via RDP. I had the same problem when I tried to set up a remote desktop connection to my virtual private server with Windows Server 2012 R2. After taking some time to solve the problem, I learned the reason why my Windows 10 computer reported an error after a recent Windows update. Later I found alternatives to repair the CredSSP by making different settings in the Group Policy Editor or in the Register. Let me tell you about this vulnerability to bypass Oracle CredSSP’s CredSSP Remediation Error.
What does CredSSP Encryption Oracle Remediation mean?
The actual error you see when connecting to an RDP connection is
An authentication error has occurred.
The requested function is not supported.
Remote computer: 192.168.1.1
This may be due to the encryption of the CredSSP Oracle.
More information is available at https://go.microsoft.com/fwlink/?linkid=866660.
Before you know the actual patch, it is useful to know why you received such a message when you are logged on to an RDP connection.
In my case I usually use an older version of the Windows operating system on my VPS. When I connect to a VPS from my PC with Windows 10 Pro, this error usually occurs for data security reasons. The authentication error is due to the compatibility/support of the operating system. If the target computer you are connecting to is updated, you will never see this encoding error.
We are now working around this limitation by enabling a few options, or you can upgrade the client computer to the latest version of Windows. That’s easy to do. That’s the task ahead of us!
Oracle CredSSP Encryption solution with group policy
If you have access to the Group Policy Editor, you can use this method. This works well if you try to connect to an AWS, a VM Azure or any other VPS machine via Windows 10 1803, 7, 8.1, 2008, 2016, etc..
One step: Use the Windows or Cortana search to find the group policy editor (gpedit.msc).
2 Step : If you have the editor, click on Administrative Templates, then click on System and select Account Delegation.
Step three: Now select Change policy settings, then select Enable and change the protection level to Vulnerable.
Step four: Finally, apply the settings and then try to connect via RDP.
Learn how to solve Oracle CredSSP encryption cleanup by changing the configuration settings in the Group Policy. If you do not have a Group Policy Editor, check the second method.
CredSSP corrected via RegEditdevice
This permission works well if you are using Windows 10 Edition, where some basic features are not available to users. So let’s see how we can disable this bug.
One step: Regedit search for Cortana.
2 Step : Now develop HKEY_LOCAL_MACHINE, then Software, then Microsoft, then Windows, then CurrentVersion, then Policies, then System.
Step three: You have to make a new key here. Right-click on the System folder, then select New Key and name the CredSSP. Again, create another key within the CredSSP called Options. It looks exactly like the picture below.
Step four: In the parameters you must create a new DWORD value and call it AllowEncryptionOracle. Finally, change the value of DWORD to 2 and the base to decimal.
I mean, this. You can now try to connect to the RDP network from any version of Windows that receives an error for the Oracle CredSSP Encryption Sanitization solution.
this could be due to credssp encryption oracle remediation windows server 2012 r2,encryption oracle remediation missing in windows 7,an authentication error has occurred the function requested is not supported,linkid=86660 remote desktop