0x904 Extended Error Code 0x7 Full ^new^ — Remote Desktop Connection Error Code

This is a common cause for servers that were working but suddenly stopped. Log into the target server locally or via another tool. certlm.msc , and hit Enter to open local certificates. Navigate to Remote Desktop > Certificates Check for an expired certificate. If found,

: In a pinch, they skip the DNS name and connect directly via the IP address , bypassing potential resolution issues that can sometimes trigger the same error. This is a common cause for servers that

If you administer the RD Gateway server: Navigate to Remote Desktop > Certificates Check for

At its core, error 0x904 occurs when the Remote Desktop Protocol (RDP) client cannot establish or maintain a stable connection to the destination. The "Extended Error 0x7" specifically flags that while the network route might exist, the session was terminated prematurely during the initialization phase. This is common in environments utilizing VPNs, where latency or packet loss can cause the sensitive RDP handshake to time out. Primary Causes The "Extended Error 0x7" specifically flags that while

If the server cannot generate new certificates, the key store might be corrupt. : This requires an administrative reboot. Rename the folder C:\ProgramData\Microsoft\Crypto\RSA\MachineKeys MachineKeys_old and restart the server to rebuild the key store. Spiceworks Community PowerShell commands to verify if your RDP port (3389) is open on the network? Unable to RDP into some Windows Servers - Error code: 0x904 24 Apr 2025 —

Over the years, Microsoft has patched critical vulnerabilities in the Credential Security Support Provider (CredSSP). If a client is fully patched (e.g., enforcing "Encryption Oracle Remediation" to "Protected") while the server is outdated, the security negotiation fails. The server, receiving a request it cannot safely process, terminates the session with a peer reset (0x7) before the licensing stage even completes, which Windows then logs generically as 0x904.

The is intimidating, but it almost always points to a certificate or transport mismatch between the RDP client and the RD Gateway.