Error 0x204 means the RDP connection is not reaching a usable Remote Desktop endpoint, so test port 3389 first and then repair either the host listener or the network/firewall path based on the result.
1. Test connectivity from the client
On the PC initiating RDP, open PowerShell and run:
$hostName = "REMOTE-PC-IP"
Test-NetConnection $hostName -Port 3389 -InformationLevel Detailed
mstsc /v:$hostName
# On the remote PC's console:
qwinsta
Get-NetFirewallRule -DisplayGroup "Remote Desktop"
Replace REMOTE-PC-IP with the workgroup PC’s IPv4 address. Using the IP avoids a workgroup name-resolution problem.
Interpret the results:
-
TcpTestSucceeded : False— port 3389 is blocked, the RDP listener is not running, or the address is wrong. -
TcpTestSucceeded : True— the network path works; investigate the listener, permissions, or authentication. - In
qwinsta, the expected result includesrdp-tcpwith stateListen. Microsoft documents these checks in its RDP connection troubleshooting procedure.^1^
2. If port 3389 is unreachable
Use local/console access to the remote Windows 11 PC:
- Open Settings → System → Remote Desktop.
- Turn on Remote Desktop.
- Under Remote Desktop users, ensure the required local workgroup user is permitted. Local administrators already have access.
- Prevent the PC from sleeping while remote access is required.
- Open Windows Defender Firewall → Allow an app or feature through Windows Defender Firewall → Change settings.
- Enable Remote Desktop for the active network profile.^2^
Then open PowerShell as administrator on the remote PC and re-enable the built-in RDP firewall rules:
Get-NetFirewallRule -DisplayGroup "Remote Desktop" |
Set-NetFirewallRule -Enabled True
Get-Service TermService,UmRdpService
Start-Service TermService
qwinsta
Do not leave Windows Firewall disabled as a workaround. If a third-party firewall or security product is installed, verify that it permits inbound TCP 3389 instead.
If using a custom RDP port, test that port and connect as IP-address:port; the default Remote Desktop firewall rules might not cover a custom port.^3^
3. If port 3389 is reachable but RDP still fails
On the remote PC:
- Run
services.msc. - Confirm these services are running:
- Remote Desktop Services
- Remote Desktop Services UserMode Port Redirector
- Run:
netstat -anob | findstr 3389 tasklist /svc | findstr TermService - Confirm the PID listening on 3389 belongs to
TermService. - Connect using the IP address rather than the computer name.
If the sign-in screen appears, connectivity is fixed. In a workgroup, use an account that exists on the remote PC, entered as:
REMOTE-PC-NAME\localuser
The account must have a password and belong to Administrators or Remote Desktop Users.
4. Check whether the update-specific issue actually applies
Microsoft documented a separate Windows 11 24H2 update issue where sessions either:
- froze shortly after connecting, or
- disconnected unexpectedly—commonly after about 65 seconds when a Windows 11 24H2 client connected over UDP to Windows Server 2016 or earlier.
That does not match a connection that immediately fails with 0x204. The freeze was resolved by the April 8, 2025 update, and the disconnect issue was addressed by the March 27, 2025 update or later.^4^
If the actual symptom is freezing or disconnecting rather than immediate 0x204 failure, install the latest cumulative update on the affected Windows 11 device and restart it. Otherwise, continue with the listener and port checks above rather than uninstalling security updates.
If the problem remains, record winver, the installed KB number, TcpTestSucceeded, and the qwinsta output. Those results identify whether escalation should focus on Windows servicing, the RDP listener, or the network path.
References