Navigate to: Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Security .
Here’s a systematic plan to resolve the 0x904 error. The key is to change only one thing at a time and test your connection after each step.
If the above solutions do not resolve the issue, try:
Restart Remote Desktop Services via Command Prompt (Admin): restart-service termserv -force to trigger a new auto-generated certificate. i remote desktop connection error code 0x904 better
Always try the CredSSP AllowEncryptionOracle = 2 registry fix first. It works for 80% of users. If not, move to Group Policy, and as a last resort, downgrade to RDP Security Layer.
NLA provides an extra layer of security by authenticating users before establishing a full session. However, older client machines or differing domain policies can trigger error 0x904 during this pre-authentication phase.
Try connecting using the (e.g., 192.168.1.50 ) instead of the computer name. This is a proven workaround for Windows 11 RDP bugs. 3. Repair Azure VM Certificate Stores If the above solutions do not resolve the
: If your target is an Azure Virtual Machine, the certificate store might be corrupt. In the Azure Portal, use the Run Command tool to run this PowerShell script:
Error code 0x904 is not a hardware failure or a simple network glitch. It’s a , and fixing it requires targeted changes to CredSSP, Group Policy, or the RDP security layer.
Unstable VPN connections or incorrect hostname resolution. 1. The Quickest Fixes (Try These First) If not, move to Group Policy, and as
The client machine may have a corrupted license cache.
These steps rarely fix because this error is deeper in the OS stack. The better solution involves modifying security policies, registry keys, or Group Policy Objects (GPOs) while understanding the security trade-offs.