Ensure client connects using the exact hostname on the certificate:
Error code 0x904 is rarely a sign of a catastrophic hardware failure; it is almost always a navigation issue. Your computer is essentially "lost" on the network. By verifying the IP address, flushing your DNS cache, and ensuring Network Discovery is enabled, you can quickly resolve this error and restore your remote workflow.
If none of these steps work, contact your network administrator to check if the target machine is online and reachable on the network.
Remote Desktop Connection Error Code 0x904 (often accompanied by extended error code 0x7) is a generic connection failure that typically stems from network instability, expired security certificates, or firewall blocks. It is most common in modern Windows 10/11 environments and Windows Server setups. Core Causes & Fixes 1. Expired RDP Certificates (Most Common)
The error often triggers when a server's self-signed RDP certificate expires, as they do not always renew automatically.
Fix: Log into the affected server locally. Open the Certificates MMC snap-in (certlm.msc), navigate to Remote Desktop > Certificates, and delete any expired certificates. Restart the Remote Desktop Services (TermService) to force Windows to generate a new certificate. 2. Network & VPN Instability
Insufficient bandwidth, high packet loss, or slow VPN speeds frequently cause 0x904.
Fix: Verify your internet speed on both ends. If using a VPN, try reconnecting or switching to a more stable ISP. 3. Firewall & Antivirus Obstruction
Security software may block mstsc.exe even if Remote Desktop is technically "enabled".
Fix: Access Allow an app through Windows Firewall and ensure both Remote Desktop and Remote Desktop (WebSocket) are checked for both Private and Public networks. Some users find that adding rdp.exe or mstsc.exe as an exception in third-party antivirus (like Bitdefender) resolves the issue. 4. Windows 11 Compatibility Bugs
Users have reported this error specifically after Windows 11 updates.
Workaround: Try connecting via the IP address of the remote machine instead of its hostname. Alternatively, download the Microsoft Store version of the Remote Desktop app, which often bypasses bugs found in the standard legacy client. Fixed: Remote Desktop 0x904 Error [2 Solutions] - AnyViewer
Remote Desktop error code (often accompanied by extended error code 0x7)
typically indicates a network connection issue, such as insufficient bandwidth, packet loss, or a mismatch in encryption ciphers
. It frequently occurs after Windows 11 updates or when connecting over a VPN. Core Troubleshooting Steps Connect via IP Address
: Instead of using the computer's hostname, try entering its direct IP address in the Remote Desktop Connection box. This bypasses potential DNS resolution bugs. Use the Microsoft Store App : The modern Microsoft Remote Desktop app from the Microsoft Store
uses different networking code than the built-in legacy client ( ) and often bypasses the 0x904 error. Renew Expired RDP Certificates
: One of the most common "hidden" causes is an expired self-signed certificate on the host machine. On the host, press certlm.msc , and navigate to Remote Desktop > Certificates
Check the expiration date; if expired, delete the certificate. Restart the Remote Desktop Services services.msc to force Windows to generate a new one. Fix Azure VM Certificate Corruption
: If using an Azure Virtual Machine, certificate store corruption is a known cause. Use the Azure Portal's "Run Command" to rename the MachineKeys folder with the following PowerShell:
Rename-Item -path "C:\ProgramData\Microsoft\Crypto\RSA\MachineKeys" -NewName "MachineKeys_old" Then reboot the server. www.remoteaccesspcdesktop.com Advanced Network & Registry Fixes Unable to RDP into some Windows Servers - Error code: 0x904
Understanding and Resolving Remote Desktop Connection Error Code 0x904 i remote desktop connection error code 0x904 better
Introduction
Remote Desktop Connection (RDC) is a vital tool for many professionals, allowing them to access and control a remote computer from another location. However, users often encounter errors that hinder their ability to establish a successful connection. One such error is the RDC error code 0x904. This paper aims to provide an in-depth analysis of the error code 0x904, its causes, and effective solutions to resolve the issue.
What is Remote Desktop Connection Error Code 0x904?
The Remote Desktop Connection error code 0x904 is a specific error that occurs when a user attempts to connect to a remote desktop, but the connection fails. The error message typically reads: "The remote computer disconnected. The error code is 0x904." This error can be frustrating, especially for users who rely on RDC for work or personal purposes.
Causes of Remote Desktop Connection Error Code 0x904
Several factors contribute to the occurrence of error code 0x904. Understanding these causes is crucial to resolving the issue:
Solutions to Resolve Remote Desktop Connection Error Code 0x904
To resolve error code 0x904, try the following solutions:
Advanced Troubleshooting Steps
If the above solutions do not resolve the issue, try:
Conclusion
Remote Desktop Connection error code 0x904 can be a challenging issue to resolve, but by understanding its causes and applying the solutions outlined in this paper, users can successfully troubleshoot and resolve the error. Regular maintenance, such as updating software and verifying remote desktop settings, can also help prevent error code 0x904 from occurring in the future. By following these guidelines, users can ensure a seamless and efficient remote desktop connection experience.
Recommendations
Future Research Directions
By continuing to research and understand RDC error codes like 0x904, we can improve the overall remote desktop connection experience and enhance the productivity of users worldwide.
Remote Desktop error code is often a result of expired or corrupt certificates unstable network connections Windows 11 compatibility bugs www.remoteaccesspcdesktop.com Most Effective Fixes Renew RDP Certificates (Primary Solution)
: This error is frequently caused by expired self-signed certificates on the target server. Log into the target server directly. Open the Certificates MMC snap-in ( certlm.msc Remote Desktop Certificates the expired certificate. Restart the service via Command Prompt (Admin): restart-service termserv -force . Windows will automatically generate a fresh certificate. Fix Certificate Corruption (Azure VMs)
: 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:
Rename-Item -path "C:\ProgramData\Microsoft\Crypto\RSA\MachineKeys" -NewName "MachineKeys_old" the server to reset the store. Windows 11 Workarounds : Windows 11 (builds 22H2 and later) has known RDP bugs. Use the IP Address : Instead of using the computer's hostname (e.g., ), type in its direct IP address (e.g., 192.168.1.50 Switch Apps Remote Desktop app from the Microsoft Store instead of the built-in "Remote Desktop Connection" (
), as it uses a different networking stack that often bypasses this error. Network and Firewall Stability is open on the target computer's firewall.
If using a VPN, a slow or unstable connection can trigger 0x904. Reconnect to your VPN or try a more stable internet source. www.remoteaccesspcdesktop.com Are you connecting to a local office computer Azure Virtual Machine Fix Remote Desktop Error Code 0x904: 4 Working Solutions Ensure client connects using the exact hostname on
Troubleshooting Remote Desktop Connection Error Code 0x904: A Comprehensive Guide
Are you frustrated with the Remote Desktop Connection error code 0x904? You're not alone! Many users have reported encountering this issue while trying to establish a remote desktop connection. In this blog post, we'll explore the possible causes of error code 0x904 and provide you with practical solutions to resolve it.
What is Error Code 0x904?
Error code 0x904 is a common issue that occurs when trying to establish a Remote Desktop Connection (RDC) to a Windows machine. The error message typically reads: "The remote computer disconnected. The error code is 0x904." This error can occur due to various reasons, including network connectivity issues, incorrect configuration, or problems with the remote desktop software.
Causes of Error Code 0x904
After analyzing various user reports and technical forums, we've identified some common causes of error code 0x904:
Solutions to Resolve Error Code 0x904
Don't worry; we've got you covered! Here are some step-by-step solutions to help you resolve error code 0x904:
Solution 1: Check Network Connectivity
Solution 2: Verify RDC Configuration
Solution 3: Update Remote Desktop Software
Solution 4: Disable Firewall or Antivirus Software
Solution 5: Check Event Logs
Conclusion
Error code 0x904 can be frustrating, but with these solutions, you should be able to resolve the issue and establish a successful Remote Desktop Connection. If you're still experiencing problems, feel free to leave a comment below, and we'll do our best to help you troubleshoot the issue.
Additional Tips
By following these solutions and tips, you should be able to overcome error code 0x904 and enjoy a seamless remote desktop experience.
Remote Desktop Connection error 0x904 (often accompanied by extended error code 0x7) is a common issue typically caused by network instability, expired RDP certificates, or Windows 11 compatibility bugs. Most Effective Fixes for Error 0x904
Renew Expired RDP Certificates: The most common root cause is an expired self-signed certificate on the remote server.
On the remote server, press Win + R, type certlm.msc, and hit Enter to open Local Computer Certificates. Navigate to Remote Desktop > Certificates.
Check the expiration date of the certificate. If it has expired, delete it. Solutions to Resolve Remote Desktop Connection Error Code
Restart the Remote Desktop Services by running restart-service termserv -force in PowerShell as an Administrator. Windows will automatically generate a fresh certificate.
Use the IP Address Instead of Hostname: Many users on Windows 11 (specifically builds 22H2 and later) encounter 0x904 due to a bug in hostname resolution.
Instead of entering the computer's name (e.g., "Office-PC"), enter its internal IP address (e.g., 192.168.1.50) in the Remote Desktop Connection window.
Switch to the Microsoft Store RDP App: If the built-in mstsc.exe client continues to fail, the Microsoft Remote Desktop app available in the Microsoft Store often works because it uses a different networking stack that bypasses these specific bugs.
Fix Azure VM Certificate Corruption: If you are using an Azure Virtual Machine, the 0x904 error frequently stems from a corrupt MachineKeys folder.
Access the VM via the Azure Portal and use the Run Command feature to execute the following PowerShell script:Rename-Item -path "C:\ProgramData\Microsoft\Crypto\RSA\MachineKeys" -NewName "MachineKeys_old".
Reboot the VM; Windows will recreate a healthy folder and fresh certificates.
Grant Private Key Permissions: In advanced environments like CyberArk PSM, the error may occur if the NETWORK SERVICE account lacks read access to the RDP certificate's private key.
In the Certificates MMC snap-in, right-click your certificate > All Tasks > Manage Private Keys, and ensure NETWORK SERVICE has Read permissions. Quick Connectivity Checklist
Check Firewall: Ensure "Remote Desktop" and "Remote Desktop (WebSocket)" are allowed through the Windows Defender Firewall on both the client and host.
Verify RDP Port: Use PowerShell to test if port 3389 is open: Test-NetConnection [TargetIP] -Port 3389.
Network Stability: If connecting over a VPN, ensure you have sufficient bandwidth; high packet loss can trigger this code.
Are you trying to connect to an office PC?
| Error | Layer | Cause | |-------|-------|-------| | 0x904 | TLS | Certificate validation failure | | 0x907 | CredSSP | Encryption oracle remediation (CVE-2018-0886) | | 0x516 | Network | TCP timeout / firewall | | 0x104 | Licensing | No RDS CAL available | | 0x80090302 | Security | Unsupported security protocol (e.g., server requires TLS 1.2, client only 1.0) |
Many guides stop at restarting TermService. Go further:
LsaSrv or TermServLicensing errors.Better because: Licensing issues often persist unless the licensing service is reset along with RDP.
This error typically occurs when trying to connect to a remote Windows machine via Microsoft Remote Desktop (RDP), often on Windows 10/11 Pro, Enterprise, or Server editions. It's commonly associated with licensing or authentication failures.
If the IP address works but the hostname consistently fails, you can manually map the name to the IP.
Use this checklist to rule out simple, one-click issues. Even advanced users skip these steps sometimes.
| Step | Action | Expected Result | |------|--------|------------------| | 1 | Can you ping the remote PC by hostname and IP? | Full reply from both | | 2 | Is Remote Desktop enabled on the host? | Settings > System > Remote Desktop = ON | | 3 | Does the user account have permission? | User is in “Remote Desktop Users” group | | 4 | Is the remote PC awake (not in sleep/hibernate)? | Network activity or WoL configured | | 5 | Is the local date/time correct? | Within 5 minutes of the remote machine |
If all above checks pass, error 0x904 is almost certainly a security layer mismatch. Proceed to the advanced fixes.