Try the following methods in order to resolve the connection error.
The error code 0x904 might not be widely documented, but Remote Desktop errors often relate to:
If this error happens frequently, you can adjust the Group Policy settings on the remote computer to manage how console sessions are handled. i remote desktop connection error code 0x904 install
If you are encountering 0x904 specifically while trying to install software remotely or via a scripted RDP session:
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. Try the following methods in order to resolve
Temporary fix (to test):
Permanent fix: Use Autoruns from Microsoft Sysinternals to disable all non-Microsoft shell extensions. If you are encountering 0x904 specifically while trying
Error code 0x904 is frustrating but rarely dangerous. It simply means the remote computer is reserving your user profile for a session that is already active. By ensuring the previous session is fully signed out (either physically or via the command line), you should be able to establish your Remote Desktop connection immediately.
If you continue to experience issues, ensure your Windows OS is fully updated, as Microsoft occasionally releases patches for RDP bugs.
Important Note: The error code
0x904is relatively rare and is not a standard Microsoft RDP client error (like 0x4, 0x7, 0x104, etc.). In Windows core networking,0x904is often interpreted asERROR_WRITE_PROTECT(The media is write protected) or a derived RDP-specific internal session error. In the context of "install" and "RDP," it typically points to a prerequisite installation failure (e.g., RDP 8.0/8.1 update, licensing component, or a graphics stack update) that then prevents RDP connections.
When an RDP session attempts to negotiate licensing and the local license store (%WinDir%\System32\MSLicensing) is missing or write-protected, Windows tries to "install" the licensing module on the fly. Failure to write MSLicensing.reg or mslicensing.dll triggers 0x904.