Remote Desktop Connection Error Code - 0x904 Extended Error Code 0x7 Best [patched]

Remote Desktop error 0x904 (Extended error 0x7) typically indicates a network instability or a security handshake failure, such as expired certificates or mismatched encryption settings. This error is common on modern Windows 10/11 and Windows Server (2016-2022) environments. Quick Fixes

Switch to IP Address: Attempt to connect using the remote computer's IP address instead of its hostname to bypass potential DNS resolution issues.

Restart RDP Services: On the remote machine, open a Command Prompt as Administrator and run:net stop termservice then net start termservice.

Check VPN/Network: If you are using a VPN, disconnect and reconnect. Slow or high-latency VPN connections are a primary cause of this specific error code. Detailed Troubleshooting Guide 1. Fix Expired RDP Certificates (Server Side)

Expired self-signed certificates are a frequent "hidden" cause for 0x904 errors on specific servers.

On the remote server, press Win + R, type certlm.msc, and press Enter. Navigate to Remote Desktop > Certificates.

Check if the certificate is expired. If it is, right-click and delete it.

Restart the Remote Desktop Services (as shown in Quick Fixes) to force Windows to generate a new valid certificate. 2. Adjust Security Layer Settings (GPO)

If the client and server have mismatched encryption ciphers, forcing a specific security layer can resolve the handshake failure.

Open the Group Policy Editor (gpedit.msc) on the remote server.

Go to: Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Security.

Require use of specific security layer for remote (RDP) connections: Set to Enabled and choose RDP from the dropdown.

Require user authentication... using Network Level Authentication (NLA): Set to Disabled for testing, then restart the server. 3. Firewall & Antivirus Exceptions

Third-party security software (like Bitdefender) often blocks RDP after Windows updates.

Ensure mstsc.exe is added to the exception list in your antivirus.

Verify Windows Firewall allows both Remote Desktop and Remote Desktop (WebSocket) for Private and Public networks on both machines. 4. Registry Modification (Client Side)

Adding a specific transport key can help the client handle modern RDP gateway connections better. Unable to RDP into some Windows Servers - Error code: 0x904

The Remote Desktop error code 0x904 (extended error 0x7) typically indicates a network-level connection failure caused by unstable network conditions, expired security certificates, or firewall blocks. It is most common when using a VPN or after upgrading to Windows 11. Top Recommended Solutions

Renew Expired RDP CertificatesExpired self-signed certificates often prevent certain servers from accepting connections while others on the same network work fine.

Action: Log into the affected server locally. Open Certificates MMC (certlm.msc), navigate to Remote Desktop > Certificates, and delete the expired certificate.

Restart: Open Command Prompt as admin and run restart-service termserv -force to let Windows generate a fresh certificate.

Verify Network and VPN StabilityThis error is frequently triggered by packet loss, insufficient bandwidth, or slow VPN response times.

Action: Reconnect your VPN or test the connection speed. If the connection is sluggish, try switching to a different ISP or network.

Adjust Firewall and Antivirus ExceptionsThird-party security software (like Bitdefender Security) can abruptly block RDP traffic. Action: Add mstsc.exe as an exception in your firewall.

Rule: Ensure both Remote Desktop and Remote Desktop (WebSocket) are allowed for both Private and Public networks.

Connect via IP Instead of HostnameDNS resolution issues can sometimes present as a 0x904 error.

Action: Try establishing the connection using the server’s static IP address rather than its Friendly Domain Name (FQDN).

Azure VM Special Fix: MachineKeys CorruptionIf the error occurs on an Azure Virtual Machine, it often stems from a corrupt certificate store.

Action: In the Azure Portal, use the Run Command feature to execute a PowerShell script renaming the folder: Rename-Item -path "C:\ProgramData\Microsoft\Crypto\RSA\MachineKeys" -NewName "MachineKeys_old". Reboot the VM afterward.

Force RDP Security LayerMismatched encryption ciphers or Network Level Authentication (NLA) failures can cause immediate disconnects.

Action: Use the Group Policy Editor (gpedit.msc) on the server. Navigate to Computer Configuration > Admin Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Security.

Setting: Enable Require use of specific security layer and select RDP. Fixed: Remote Desktop 0x904 Error [2 Solutions] - AnyViewer

The Remote Desktop Connection error 0x904 (Extended Code 0x7)

typically indicates a network instability or a security handshake failure

, often caused by expired certificates, firewall blocks, or compatibility issues with newer Windows versions like Windows 11. Step 1: Fix Expired RDP Certificates

This is the most common cause when a connection suddenly fails while others on the same network work fine.

Log into the remote server (via console or alternative access). certlm.msc , and hit Enter to open the Certificates MMC snap-in. Navigate to Remote Desktop > Certificates (or Personal > Certificates).

Look for the certificate issued to the computer name. Check its expiration date. If it is expired or corrupt, right-click and Delete Open Command Prompt as Administrator and run: restart-service termserv -force (or simply restart the server).

Windows will automatically generate a fresh self-signed certificate upon service restart. www.remoteaccesspcdesktop.com Step 2: Windows 11 Compatibility Workarounds Remote Desktop error 0x904 (Extended error 0x7) typically

Windows 11 (builds 22H2 and later) has known bugs with RDP hostname resolution and specific cipher suites. www.remoteaccesspcdesktop.com Connect via IP Address : Instead of typing the computer name (e.g., ), use the target's internal IP address (e.g., 192.168.1.100 Use the Microsoft Store App : Users have reported success using the Remote Desktop app from the Microsoft Store instead of the built-in Spiceworks Community Step 3: Check Firewall and Security Software

Even if RDP is "Allowed," specific security layers may still block the connection. www.remoteaccesspcdesktop.com Allow MSTSC explicitly "Allow an app through Windows Firewall" Ensure both Remote Desktop Remote Desktop (WebSocket) are checked for Private and Public. Allow another app , browse to C:\Windows\System32\mstsc.exe , and add it with full permissions. Third-Party Antivirus : Apps like Bitdefender have been known to block RDP. Add to their exception lists. Spiceworks Community Step 4: Azure VM Special Case

If the target is an Azure Virtual Machine, a corrupt certificate store is a frequent culprit. www.remoteaccesspcdesktop.com Azure Portal , go to your VM and select Run command > RunPowerShellScript Run this command to rename the key folder:

Rename-Item -path "C:\ProgramData\Microsoft\Crypto\RSA\MachineKeys" -NewName "MachineKeys_old" the server. www.remoteaccesspcdesktop.com Step 5: Adjust Security Layer (Last Resort) Unable to RDP into some Windows Servers - Error code: 0x904 24 Apr 2025 —

Fixing Remote Desktop Error Code 0x904 (Extended Code 0x7) Remote Desktop Connection (RDP) error code 0x904 with extended error code 0x7 is a common connection failure that often occurs after Windows updates (especially Windows 11 upgrades) or when network conditions are unstable. It typically signifies that the client is unable to establish a secure, stable handshake with the remote host. Core Causes

Unstable Network/VPN: Insufficient bandwidth, high packet loss, or slow VPN connections.

Expired RDP Certificates: Self-signed certificates on the host machine may have expired and failed to auto-renew.

Encryption Mismatches: A failure in TLS/SSL negotiation where the client and server do not support the same cipher suites.

Firewall Blockage: Antivirus software or Windows Defender Firewall may be blocking the connection on either the source or destination.

OS Compatibility: Frequent issues reported when connecting from Windows 11 to older Windows Server versions. Step-by-Step Solutions 1. Renew Expired RDP Certificates

Expired self-signed certificates are a primary cause of this error on servers that haven't been rebooted in a while.

Log into the remote server locally or via a different remote access tool.

Press Win + R, type certlm.msc, and press Enter to open the Certificates console. Navigate to Remote Desktop > Certificates.

Check the expiration date. If expired, delete the old certificate.

Open an elevated Command Prompt and restart the term service to generate a new certificate:restart-service termserv -force.

It looks like there's no response available for this search. Try asking something else. Unable to RDP into some Windows Servers - Error code: 0x904

The Remote Desktop error code (Extended Error ) typically signals a network-level disconnect or a security handshake failure. It often surfaces during unstable connections, when VPN speeds drop, or due to expired RDP certificates.

Below are the most effective solutions for resolving this error: 1. Fix Expired or Corrupt RDP Certificates

Often, the self-signed certificate used for RDP has expired or become corrupted, which explains why some servers work while others on the same network fail. For Windows Servers: Open the Certificates MMC snap-in ( certlm.msc Navigate to Remote Desktop > Certificates Delete the expired certificate. Open Command Prompt as Administrator and run: restart-service termserv -force to automatically generate a new one. For Azure VMs: Users often resolve this by renaming the MachineKeys folder via the Azure Portal's "Run Command" feature:

Rename-Item -path "C:\ProgramData\Microsoft\Crypto\RSA\MachineKeys" -NewName "MachineKeys_old" then reboot the server. 2. Bypass DNS with IP Address

If there is a DNS resolution issue or a bug in a specific Windows 11 update, hostnames may fail to resolve correctly. Try connecting directly using the IP address of the remote computer instead of its hostname. Flush your DNS cache on the client machine by running ipconfig /flushdns in Command Prompt. 3. Adjust Security & NLA Settings

Compatibility issues with Network Level Authentication (NLA) or mismatched encryption cyphers frequently trigger this error. Disable NLA temporarily to test the connection:

Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Security

Require use of specific security layer for remote (RDP) connections and select as the Security Layer.

Require user authentication for remote connections by using Network Level Authentication 4. Verify Firewall & Antivirus Exceptions

Remote Desktop error 0x904 (Extended Error Code 0x7) typically indicates a general connectivity failure often caused by expired self-signed RDP certificates, network instability, or firewall interference. This error is common after Windows 11 upgrades or when connecting via VPN. Primary Fix: Renew RDP Certificates

Most IT professionals find that an expired or corrupt self-signed certificate on the host machine is the root cause.

Access the host computer locally or through another remote method.

Open Certificates MMC: Press Win + R, type certlm.msc, and press Enter.

Delete Expired Certificate: Navigate to Remote Desktop > Certificates. Identify the certificate, check the expiration date, and delete it if it has passed.

Restart RDP Services: Open Command Prompt as an administrator and run:restart-service termserv -force.Windows will automatically generate a new, valid self-signed certificate.. Secondary Solutions

If renewing the certificate does not resolve the issue, try these targeted workarounds:

Connect via IP Address: Windows 11 may have hostname resolution bugs causing 0x904. Try connecting using the server's internal IP address (e.g., 192.168.1.100) instead of its computer name.

Disable UDP on Client: Some connections stabilize when forced to use TCP only. Open Group Policy Editor (gpedit.msc).

Navigate to Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Connection Client. Set Turn off UDP on client to Enabled.

Firewall & Antivirus Exceptions: Ensure mstsc.exe (Remote Desktop Connection) is allowed through the firewall on both the client and host. Users from Spiceworks Community specifically noted that third-party security software like Bitdefender can block these connections.

Use the Microsoft Store App: The "Remote Desktop" app available in the Microsoft Store uses a different networking stack and often bypasses the 0x904 error found in the built-in mstsc.exe client. Azure VM Specific Fix

If you are encountering this on an Azure Virtual Machine, it may be due to a corrupt MachineKeys folder. Close all RDP sessions Open Regedit Navigate to:

Use the Run command feature in the Azure Portal to execute:Rename-Item -path "C:\ProgramData\Microsoft\Crypto\RSA\MachineKeys" -NewName "MachineKeys_old".

Reboot the server to let Windows recreate a clean certificate store. After Windows 11 Upgrade RDP Error 0x904 extended error 0x7

Remote Desktop error 0x904 (Extended Error 0x7) is a general connectivity failure usually triggered by expired self-signed certificates, network instability, or firewall blocks. Top Fixes for Error 0x904 / 0x7

Renew Expired RDP CertificatesRDP relies on a self-signed certificate that may not auto-renew. If this certificate expires, the connection will fail instantly.

Log into the host machine locally or via an alternative tool. Run certlm.msc to open the certificate manager. Navigate to Remote Desktop > Certificates. If the certificate is expired, Delete it.

Restart the Remote Desktop Services (termserv) via the Services app or PowerShell (restart-service termserv -force) to trigger the generation of a new certificate.

Fix Corrupt Certificate Store (Azure VMs)If you are using an Azure Virtual Machine, a corrupt MachineKeys folder can prevent RDP from functioning.

Use the Run Command feature in the Azure Portal to execute this PowerShell command:Rename-Item -path "C:\ProgramData\Microsoft\Crypto\RSA\MachineKeys" -NewName "MachineKeys_old". Reboot the VM to allow Windows to rebuild the folder.

Verify Firewall and Port 3389Firewalls may block RDP traffic even if the service is enabled.

Use PowerShell to test connectivity: Test-NetConnection [Remote_IP] -Port 3389.

On the host machine, ensure Remote Desktop and Remote Desktop (WebSocket) are allowed for both Public and Private networks in the Windows Firewall.

Adjust Security LayersMismatched encryption settings between the client and host can cause 0x904. On the host, open gpedit.msc.

Go to Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Security.

Set Require use of specific security layer for remote (RDP) connections to Enabled and select RDP from the dropdown.

Disable Require user authentication... using Network Level Authentication (NLA) as a test to see if the connection establishes. Summary of Likely Causes Unable to RDP into some Windows Servers - Error code: 0x904

Remote Desktop error 0x904 (extended error 0x7) typically indicates a general network connection failure, often triggered by expired RDP certificates firewall blocks unstable network/VPN conditions www.remoteaccesspcdesktop.com Core Troubleshooting Steps Renew Expired RDP Certificates: On the remote server, open certlm.msc , navigate to Remote Desktop > Certificates , and delete expired certificates. Restart Remote Desktop Services to generate a new one. Use IP Address:

Bypass DNS issues by connecting using the server’s internal IP address instead of its hostname. Verify Firewall Settings: Remote Desktop

is allowed in Windows Firewall for both Private/Public networks. Add exceptions for in third-party security software if necessary. Use Microsoft Store App: Try using the alternative Microsoft Remote Desktop app for better compatibility. Fix Certificate Store (Azure): If using Azure VMs, rename C:\ProgramData\Microsoft\Crypto\RSA\MachineKeys to address potential corruption. Spiceworks Community Additional Solutions Restart Remote Host: Reboot the server to resolve service issues. Check VPN: Ensure your connection is stable. Disable NLA: If needed, disable Network Level Authentication (NLA) on the host for testing. Spiceworks Community Are you connecting to a local server cloud-hosted machine like an Azure VM? After Windows 11 Upgrade RDP Error 0x904 extended error 0x7 30 Jun 2021 —

The Remote Desktop connection error 0x904 (Extended Error Code: 0x7) is a common RDP issue that typically indicates a network connection failure security certificate problem

. It often occurs after Windows updates (especially Windows 11) or when using a VPN

Here is a summary of the best troubleshooting steps compiled from expert blog posts and technical forums: 1. Fix Expired RDP Certificates (Most Common Solution)

If you can connect to some servers but not others, an expired self-signed certificate on the host machine is a likely culprit : Log in to the host machine locally or via another tool. Certificates (Local Computer) by running certlm.msc Navigate to Remote Desktop > Certificates Find the expired certificate, right-click, and Restart the Remote Desktop Services ) via Command Prompt as Administrator: restart-service termserv -force . Windows will automatically generate a fresh certificate 2. Rename Corrupt MachineKeys (For Azure VMs)

If you are using an Azure Virtual Machine, a corrupt certificate store may prevent RDP from creating new certificates : Use the Azure Portal's Run Command feature to execute a PowerShell script:

Rename-Item -path "C:\ProgramData\Microsoft\Crypto\RSA\MachineKeys" -NewName "MachineKeys_old" : Reboot the server 3. Adjust Firewall & Antivirus Settings Security software like Bitdefender or the native Windows Firewall may block the connection Remote Desktop (WebSocket)

are allowed through the firewall for both Private and Public networks

: Try temporarily disabling third-party antivirus to see if the connection is restored 4. Network & Connection Quick Fixes

The Remote Desktop error 0x904 (Extended Code 0x7) is a common connection failure that typically stems from network instability, firewall misconfigurations, or expired security certificates. This error often appears on Windows 10/11 and Windows Server 2016/2019/2022, especially after system updates. www.remoteaccesspcdesktop.com Primary Causes Network Instability:

Insufficient bandwidth, high packet loss, or slow VPN connections. Certificate Issues:

Expired self-signed RDP certificates or corrupt certificate stores (common on Azure VMs). Firewall Blocks: Misconfigured rules on either the client or host machine. Compatibility: Known quirks in Windows 11 hostname resolution. Spiceworks Community Best Fixes & Troubleshooting Steps 1. Fix Expired RDP Certificates (Recommended)

This is the most common resolution for persistent 0x904 errors on physical servers. www.remoteaccesspcdesktop.com

Access the host server locally or via an alternative method. Open the Certificates snap-in: Press certlm.msc , and hit Enter. Navigate to Remote Desktop > Certificates Check for an expired certificate. If it is past its date, right-click and delete Open Command Prompt as Administrator and run: restart-service termserv -force . Windows will automatically generate a new certificate. www.remoteaccesspcdesktop.com 2. Use IP Address Instead of Hostname

Windows 11 sometimes fails to resolve hostnames correctly for RDP, triggering 0x904. www.remoteaccesspcdesktop.com In the Remote Desktop Connection window, enter the IP address 192.168.1.50 ) instead of the computer name. TheITBros.com 3. Configure Firewall Rules Ensure the correct RDP services are allowed through the Windows Defender Firewall on both machines.

Search for "Allow an app through Windows Firewall" in the Start menu. Change settings Ensure both Remote Desktop Remote Desktop (WebSocket) are checked for both C:\Windows\System32\mstsc.exe manually if it is not in the list. www.remoteaccesspcdesktop.com 4. Fix Azure VM Certificate Corruption If the error occurs on an Azure Virtual Machine Azure Portal to reset the certificate store. www.remoteaccesspcdesktop.com In the Azure Portal, go to your VM's Run command RunPowerShellScript and execute:

Rename-Item -path "C:\ProgramData\Microsoft\Crypto\RSA\MachineKeys" -NewName "MachineKeys_old" the server. www.remoteaccesspcdesktop.com 5. Adjust Security Layers (Legacy Support)

If connecting from an older client to a newer host, the security layer might be too high. TheITBros.com On the host, open Local Group Policy Editor gpedit.msc Navigate to:

Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Security

Require use of specific security layer for remote (RDP) connections and set it to Microsoft Learn Are you connecting over a local network , and which version of is the host machine running? After Windows 11 Upgrade RDP Error 0x904 extended error 0x7

1. Clear the RDP client license cache (most common fix for 0x904 + 0x7)

  • Close all RDP sessions
  • Open Regedit
  • Navigate to: 
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSLicensing
  • Delete the entire MSLicensing key (back it up first if you prefer)
  • Restart your computer
  • Try connecting again — Windows will recreate the license store

The Quick Workaround (Use the Web Client)

If you need immediate access and cannot troubleshoot right now, try using the Web Client instead of the desktop app. If you want

  • Go to the Azure Virtual Desktop web client (or your specific cloud provider’s web portal).
  • Log in there and try to connect. This often bypasses the token issues present in the local RDP app.

4. Configure Firewall and Security Software

  • On the remote computer:
    • Go to Windows Defender Firewall (or your third-party firewall software).
    • Create a new rule to allow incoming connections on TCP port 3389.
  • Temporarily disable security software to test if it's interfering with RDC.

Part 6: Preventing Future Occurrences of 0x904 Extended 0x7

Once you resolve the error, implement these best practices to ensure it never returns:

  • Regularly clear RDP cache using a scheduled task: del /q %USERPROFILE%\Documents\Default.rdp
  • Update your RDP client – Use the latest version of Microsoft Remote Desktop from the Store, not the legacy mstsc.exe if possible.
  • Stable network conditions – Ensure jitter is below 15ms and packet loss is 0%. Error 0x7 thrives on unstable connections.
  • Use RDP Gateway – Instead of direct RDP, route through a Remote Desktop Gateway to stabilize authentication.

Best fixes (try in order)

Fix #2: Update the RDP Client (Version Mismatch)

Error 0x904 often occurs when there is a mismatch between the client version and the security protocols required by the host PC. This is common if you are using the built-in "Microsoft Remote Desktop" app from the Windows Store.

  1. Open the Microsoft Store.
  2. Click the Library icon in the bottom left.
  3. Click Get Updates.
  4. If an update for Microsoft Remote Desktop is available, install it.
  5. Restart the app and try again.

If you are using the built-in Windows RDP client (mstsc.exe), ensure your Windows OS is fully updated via Windows Update.

5. Additional Troubleshooting Steps

  • Restart both the client and remote computers.
  • Ensure the remote computer is turned on and connected to the internet.
  • Try connecting using a different RDC client or an alternative remote access tool.

Conclusion

By following these steps, you should be able to resolve the Remote Desktop Connection error code 0x904 with extended error code 0x7. If the issue persists, consider seeking additional help from your network administrator or a professional technician. Do you have any questions or would you like to add any additional troubleshooting steps?

Remote Desktop error 0x904 (Extended Error 0x7) typically indicates a general network connectivity failure. It most commonly occurs due to unstable network conditions, expired RDP certificates, or firewall blocks. Phase 1: Network & VPN Stability

This error is frequently triggered by insufficient bandwidth or packet loss.

Reconnect VPN: If you are using a VPN, disconnect and reconnect to refresh the tunnel.

Use IP Address: Try connecting using the remote computer's IP address instead of its hostname to rule out DNS resolution issues.

Test Ping: Run a ping -t [remote-ip] to check for high latency or dropped packets. Phase 2: Fix Expired RDP Certificates

A common cause in server environments is an expired self-signed RDP certificate that fails to renew automatically.

Log into the target server (locally or via an alternative remote tool).

Press Win + R, type certlm.msc, and hit Enter to open the Certificate Manager. Navigate to Remote Desktop > Certificates.

Locate the expired certificate, right-click it, and select Delete.

Restart the Remote Desktop Service to generate a new certificate by running this command in an administrator Command Prompt:restart-service termserv -force. Phase 3: Firewall & Security Software

Security suites like Bitdefender or Windows Firewall may block the specific RDP process.

Allow mstsc.exe: Ensure Remote Desktop and Remote Desktop (WebSocket) are allowed through the firewall on both the source and destination computers.

Add Exception: Add C:\Windows\System32\mstsc.exe to your antivirus/firewall exclusion list. Phase 4: Azure VM Specific Fix

If the error occurs on an Azure Virtual Machine, the certificate store may be corrupt. Access the VM via the Azure Portal. Use the Run command feature and select RunPowerShellScript.

Execute the following to rename the corrupt key folder:Rename-Item -path "C:\ProgramData\Microsoft\Crypto\RSA\MachineKeys" -NewName "MachineKeys_old". Reboot the server.

Are you connecting over a local network or a wide-area network/VPN? Unable to RDP into some Windows Servers - Error code: 0x904

Title: Fixing Remote Desktop Connection Error 0x904 (Extended Error 0x7)

Having trouble connecting via Remote Desktop? Error 0x904 with extended error code 0x7 typically indicates an authentication or TLS/credSSP issue between client and server. Try the steps below in order until the connection succeeds.

  1. Quick checks
  • Confirm both machines are powered on and reachable (ping or try another service/port).
  • Ensure RDP is enabled on the target (System > Remote settings).
  • Verify correct username, hostname/IP, and port (default 3389).
  1. Update Windows and RDP clients
  • Install all pending Windows updates on both client and server.
  • If using a third-party RDP client, update it to the latest version.
  1. Check network/firewall
  • Allow inbound TCP 3389 on the server firewall.
  • Ensure no middlebox (VPN, proxy, appliance) is intercepting TLS for RDP.
  • If using NAT, verify port forwarding rules.
  1. Credential & authentication fixes
  • Clear saved credentials on the client (Windows Credential Manager) and re-enter credentials.
  • Try connecting with a different user account that has Remote Desktop rights.
  • On the server, confirm the user is in the Remote Desktop Users group or is an administrator.
  1. TLS / CredSSP and encryption issues
  • On both client and server, ensure Group Policy for Credential Delegation and Encryption Oracle Remediation are compatible:
    • Run gpedit.msc → Computer Configuration → Administrative Templates → System → Credentials Delegation → Encryption Oracle Remediation. Set to “Mitigated” or “Vulnerable” temporarily to test (prefer Mitigated).
    • Reboot or run gpupdate /force.
  • If recent updates changed CredSSP behavior, install corresponding updates on both sides or revert the policy temporarily while deploying fixes.
  1. RDP listener and certificate
  • Check the RDP listener: run (on server) qwinsta to confirm listener status.
  • In Event Viewer look for TLS/Creds issues under Windows Logs → System and Applications and Services Logs → Microsoft → Windows → TerminalServices or RemoteDesktopServices.
  • If certificate problems appear, regenerate or rebind an appropriate certificate for RDP.
  1. Services and remote desktop host checks
  • Ensure Remote Desktop Services and Remote Desktop Services UserMode Port Redirector are running.
  • Restart those services or reboot the server if safe.
  1. Test with Network Level Authentication (NLA)
  • Temporarily disable NLA to isolate the issue: System Properties → Remote → uncheck “Allow connections only from computers running Remote Desktop with Network Level Authentication.”
  • If this fixes it, troubleshoot NLA/credentials rather than leaving it disabled.
  1. Logs and advanced diagnostics
  • Collect Event Viewer errors around the connection time and Google specific event IDs.
  • Use Microsoft’s Remote Desktop client logs (on Windows: Event Viewer and %localappdata%\Packages\Microsoft.RemoteDesktop_*\LocalState) and network captures (WireShark) if needed.
  1. Workarounds
  • Connect via an alternative remote method (PowerShell Remoting / WinRM, third-party remote tools) while resolving RDP.
  • Ensure strong security: re-enable NLA and correct CredSSP/TLS settings once fixed.

If you want, share the exact Windows versions (client/server), recent updates applied, and key Event Viewer error messages and I’ll provide targeted commands or registry edits.

Troubleshooting Remote Desktop Error 0x904 (Extended Code 0x7)

The Remote Desktop connection error 0x904 with extended error code 0x7 is a common Windows error that typically indicates a network connectivity issue. It often occurs when the network connection is unstable, bandwidth is insufficient, or there is a mismatch in encryption settings between the client and the host. Quick Summary of Causes

Unstable Network: Slow VPN speeds, packet loss, or low bandwidth.

Security Software Interference: Firewalls or antivirus (like Bitdefender) blocking rdp.exe.

Expired Certificates: Corrupt or expired self-signed RDP certificates on the remote server.

NLA Conflicts: Network Level Authentication (NLA) issues, especially after a Windows 11 upgrade. Step-by-Step Solutions 1. Verify and Allow RDP Through Firewall

A single misconfigured firewall setting can trigger this error. Ensure RDP traffic is allowed on both the source and destination computers.

Press Win + S and type "Allow an app through Windows Firewall". Click Change settings.

Check both Remote Desktop and Remote Desktop (WebSocket) for both Private and Public networks.

If it’s missing, click Allow another app, browse to C:\Windows\System32\mstsc.exe, and add it.

Confirm that TCP port 3389 is open using PowerShell: Test-NetConnection [server_name] -Port 3389. 2. Renew Expired RDP Certificates

If the server's self-signed certificate is invalid, open the Certificates MMC snap-in (certlm.msc), navigate to Remote Desktop > Certificates, delete expired ones, and restart the Remote Desktop Services (restart-service termserv -force) to generate a new one. 3. Adjust Network Level Authentication (NLA)

Modify NLA settings via the Group Policy Editor (gpedit.msc) under Computer Configuration settings for Remote Desktop Services if compatibility issues are suspected. Unable to RDP into some Windows Servers - Error code: 0x904

Here’s a helpful post you can use or share regarding the Remote Desktop error code 0x904 with extended error code 0x7.

Fix 1: Clear the Local RDP License Cache (Most Effective for Error 0x7)

Since extended error 0x7 often means "cannot store the license," deleting the corrupted cache forces a fresh license negotiation.

  1. Close all RDP sessions.
  2. Press Win + R, type %windir%\system32\mstsc.exe (do not open via Start menu yet).
  3. Navigate to the cache folder:
    • Open File Explorer and go to: %localappdata%\Microsoft\Terminal Server Client\Cache
    • Alternatively: C:\Users\YourUsername\AppData\Local\Microsoft\Terminal Server Client\Cache
  4. Delete all files inside the Cache folder (files like cache.bin, bcache.bin).
  5. Also delete Default.rdp in the parent folder (...\Terminal Server Client\).
  6. Restart your computer and try connecting again.

Leave a Reply