Windows 10 Updated Can't Connected Your RDP

[blue Snow]

This morning going to check my staking POS on my RDP (remote desktop connection), I received this error while opening.



The problem happen after updating windows 10,
how to fix it?. here you go..

1. go to keyboard tab (windows+r) and write gpedit.msc

2. click administrative Templates - click system and - click credential delegation



3. double click Encryption oracle remediation



4. enabling Encryption oracle remediation and select vulnerable, Press ok



Now, I am able to control my RDP.

source: https://sysally.com/blog/how-to-fix-credssp-authentication-error-in-rdp/


Another reason to follow this instruction

Edit: ah nevermind, looks like I'm wrong https://support.microsoft.com/en-gb/help/4295591/credssp-encryption-oracle-remediation-error-when-to-rdp-to-azure-vm

CVE-2018-0886

[jackg]

This concerns me greatly...

I'm pretty sure when talking about using vulnerable connections and there being a problem witb authentication this means you've stopped using keys to connect to the remote desktop.

Your remote desktop really shouldn't accept non encrypted connections to start with but if it does you should quickly change that or take it down if you don't want it to be overrun by a random stranger at some point. Can you not just redownload a config file or authentication file (I don't use anything other than ssh to access remote spaces so can't help with the technicals). But please stop sending unencrypted communications if that is what you're doing.

Edit: ah nevermind, looks like I'm wrong https://support.microsoft.com/en-gb/help/4295591/credssp-encryption-oracle-remediation-error-when-to-rdp-to-azure-vm

[joniboini]

Isn't updating both the client and server a better solution so there's no need to change the level to vulnerable?

At least that's what I see from the matrix. Also,

To resolve the issue, install CredSSP updates for both client and server so that RDP can be established in a secure manner. For more information, see CVE-2018-0886 | CredSSP Remote Code Execution Vulnerability.

Source: https://support.microsoft.com/en-gb/help/4295591/credssp-encryption-oracle-remediation-error-when-to-rdp-to-azure-vm

CVE-2018-0886

[jackg]

Isn't updating both the client and server a better solution so there's no need to change the level to vulnerable?

At least that's what I see from the matrix. Also,

Yeah I see it now and agree with that, you're better off updating them both.

There's a reason Microsoft chose the word "vulnerable"...

At least run the same version of both - if you don't want to update the client.