Why an RDP connection suddenly stopped working
After Microsoft’s 2018 CredSSP security updates, some Remote Desktop connections failed with an authentication error mentioning encryption oracle remediation. CredSSP is involved in delegating credentials during authentication.
Update the client and the server
A mismatch between patched systems and security policy could prevent the connection. The preferred resolution is to bring both the client and destination into a supported, appropriately updated state and review their policies together.
Microsoft documents the issue in its CredSSP security update guidance and RDP troubleshooting article. These explain the compatibility settings and their security consequences.
Why the old workaround isn’t the default fix
The original May 2018 post described setting AllowEncryptionOracle to 2, or choosing Vulnerable under the Encryption Oracle Remediation policy. That weakened protection to allow a connection to an incompatible system. It wasn’t a repair of the underlying vulnerability.
Don’t leave a workstation in that state as a permanent solution. If an administrator uses a temporary compatibility exception during recovery, it needs a defined purpose and removal after the endpoints are updated.
For managed systems
Ask the responsible IT team to check update levels, policy inheritance, and approved recovery access. Changing a local setting may be overwritten by domain policy and can weaken other connections made by the same client.
This article explains a historical 2018 issue. It does not mean every modern RDP authentication error has the same cause.
