I Remote Desktop Connection Error Code 0x904 Install

The Ghost in the Machine: Dissecting Remote Desktop Error 0x904

In the architecture of modern remote work, the Remote Desktop Protocol (RDP) serves as a critical bridge between user and machine. When that bridge collapses into a specific alphanumeric code—0x904—immediately following an installation or update, the frustration is palpable. Unlike generic network timeouts, this error signals a deeper, more insidious conflict: a fundamental disagreement between the RDP client, the operating system’s licensing mechanism, and recently altered security protocols.

Error 0x904 typically manifests not as a connection rejection, but as a pre-connection abort. The user enters credentials, the client attempts to negotiate encryption, and then the session dies, often returning a message about licensing or internal protocol errors. The context of “install” is paramount here. This error rarely appears on a clean, unchanged system. Instead, it surfaces after a Windows update, a new Remote Desktop Services (RDS) role installation, or a security patch that modifies CredSSP (Credential Security Support Provider) settings.

Solution 4: Perform a Fresh Install of the Remote Desktop Client (For Windows Store Version)

If you are using the Microsoft Store Remote Desktop client (Universal Windows Platform app) rather than the classic mstsc.exe, the 0x904 error indicates a corrupted AppX package.

How to reinstall the Store version:

1. Open Settings > Apps > Installed apps.
2. Search for "Remote Desktop".
3. Click the three dots and select Uninstall.
4. Open PowerShell as Administrator.
5. To ensure complete removal, run:

   Get-AppxPackage *RemoteDesktop* | Remove-AppxPackage -AllUsers
   

6. Reboot your PC.
7. Open the Microsoft Store, search for "Microsoft Remote Desktop" (version 10.x), and click Install.

Step 5 – Manual extraction workaround

Download the RDP 8.1 update (KB2923545 for Win7/8) or RDP 10.0 CAB from Microsoft Update Catalog, then:

expand -r *.cab C:\RDPExtract
regsvr32 C:\RDPExtract\mstscax.dll

Method 3: Modify Local Group Policy (Prevention)

If this error happens frequently, you can adjust the Group Policy settings on the remote computer to manage how console sessions are handled.

1. Connect to the remote computer physically or via a different admin account.
2. Press Windows Key + R, type gpedit.msc, and press Enter.
3. Navigate to the following path: Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Connections
4. Look for a policy named "Restrict Remote Desktop Services users to a single Remote Desktop Services session".
5. Set this to Enabled (which forces the old session to disconnect when a new one starts) or Disabled depending on your specific usage needs.
   • Note for Windows 10/11: Enabling this often resolves the 0x904 error by automatically kicking the "stuck" session so the new one can connect.

Steps to Resolve:

1. Open the Remote Desktop Gateway Manager on the Gateway server.
2. Navigate to Policies.
3. Check the Resource Authorization Policies (RAPs).
   • Ensure that the user group trying to connect is allowed to connect to the target resource (the PC you are trying to install on).
4. Check the Connection Authorization Policies (CAPs).
   • Verify that the authentication method (Password/Smartcard) matches what the client is providing.

The Registry Fix (Client-Side): Sometimes the client fails to negotiate the gateway connection properly. You can force the client to bypass specific gateway checks (useful for testing installs): i remote desktop connection error code 0x904 install

1. Open regedit.
2. Navigate to: HKEY_CURRENT_USER\Software\Microsoft\Terminal Server Client
3. Look for a DWORD named RDGClientTransport. If it doesn't exist, create it.
4. Set the value to 1.
   • 0 = Negotiate (Default)
   • 1 = Use RPC over HTTP (often fixes 0x904)
   • 2 = Use RPC over HTTPS

Restart your connection and attempt the install again.

Solution 5: Disable Third-Party Shell Extensions (Explorer Crash Fix)

Because mstsc.exe runs as a child process of explorer.exe, a buggy shell extension can cause the RDP client to fail with code 0x904. The primary culprits are NVIDIA Display Container LS and Intel Graphics Shell Extension.

Temporary fix (to test):

1. Kill Explorer: Press Ctrl + Shift + Esc to open Task Manager.
2. Find Windows Explorer, right-click it, and select End task. Your taskbar and desktop will disappear.
3. In Task Manager, click File > Run new task.
4. Type mstsc.exe and check "Create this task with administrative privileges".
5. The RDP client should open without the 0x904 error. If it works, a shell extension is the cause.

Permanent fix: Use Autoruns from Microsoft Sysinternals to disable all non-Microsoft shell extensions.

Troubleshooting Steps

7. Prevention

• Do not use write-protected volumes (e.g., UWF-enabled drives, SD cards) as system drives for RDP hosts.
• Avoid setting HKLM\SOFTWARE\Microsoft\Terminal Server Client as read-only via Group Policy.
• Ensure Remote Desktop Services Client feature is installed before stripping down Windows with tools like NTLite.

When to contact support

• Include: exact error code (0x904), Windows version/build, whether client or server install, recent changes (updates/AV installs), relevant Event Viewer error messages, and installer log output.

If you want, tell me your Windows version (e.g., Windows 10 22H2, Windows Server 2019) and whether this is the client or host install — I’ll give exact commands and tailored steps.

(Invoking related search suggestions.)