Fix STATUS_USER_SESSION_DELETED (0XC0000203) Fast

When does this error show up?

You're working over Remote Desktop (RDP) on a Windows 10 or Windows Server machine. Maybe you're in the middle of copying a file, or you stepped away for coffee. Suddenly the connection drops. When you try to reconnect, you get a message box with STATUS_USER_SESSION_DELETED (0XC0000203). The text says something like "The remote user session has been deleted."

This can also happen if you have multiple RDP sessions to the same server and one of them gets killed by another admin (or by a script). Or maybe the server's RDP service restarted while you were connected.

Root cause

Every RDP session on a Windows machine gets an ID and a handle. When the session is ended on the server side—maybe the user logged off, or the session timed out, or an admin ran logoff or reset session—the server marks that session as deleted. But your client computer still remembers the old session handle and tries to talk to it. The server responds with STATUS_USER_SESSION_DELETED, which basically means: "You're holding a ticket to a room that no longer exists."

The fix is simple: tell your client to forget that old session and start a new one. But sometimes the server also has a ghost session sitting there, and you need to clean that up too.

Fix 1: The fast reboot (client side only)

1. Close the RDP client window if it's still open.
2. Open Task Manager (Ctrl+Shift+Esc).
3. Look for any mstsc.exe process running. Right-click it and select End task. This kills any leftover RDP client connections.
4. Now open a new RDP connection. You should be able to log in fresh. If this works, you're done.

Fix 2: Kill the orphaned session on the server

If the reboot didn't work, the server still has a ghost session that is confusing things. You need to remove it.

1. On the server (or get another admin to do this), open Command Prompt as administrator. To do that, press Win + X, then choose Command Prompt (Admin) or Windows PowerShell (Admin).
2. Type query session and press Enter. You'll see a list of all user sessions, like this:
   

    SESSIONNAME       USERNAME                 ID  STATE   TYPE        DEVICE
    services                                    0  Disc
    console                                     1  Conn
    rdp-tcp#0         jdoe                      2  Active
    rdp-tcp#1         jdoe                      3  Disc

3. Look for a session with a Disc (disconnected) state or an Active state that belongs to you. Note the ID number (e.g., 2 or 3).
4. Type logoff ID where ID is the session number. For example, if your session ID is 2, type:
   logoff 2
   Then press Enter. This logs off that session completely.
5. Now try connecting again. The error should be gone.

Fix 3: Reset the network adapter (if you can't get to the server)

Sometimes you can't access the server directly. In that case, reset the network connection on your client machine.

1. On your local Windows machine, go to Settings > Network & Internet > Status.
2. Click Network reset at the bottom.
3. Click Reset now. Your PC will reboot.
4. After the reboot, try the RDP connection again. This clears any cached session info on your network stack.

Fix 4: Restart the Remote Desktop Services on the server

If none of that worked, the RDP service itself might be in a bad state. You need admin access to the server.

1. On the server, open Services.msc (press Win + R, type services.msc, hit Enter).
2. Scroll down to Remote Desktop Services (the display name is often just "Remote Desktop Services" or "TermService").
3. Right-click it and choose Restart. This will disconnect all active RDP sessions for a moment, so warn other users if it's a shared server.
4. Wait 10 seconds, then try connecting again.

Still failing? Here's what else to check

• Check the server's RDP listener port. Make sure nothing else is using port 3389. Run netstat -aon | findstr :3389 on the server. If another app has that port, you'll need to change the RDP port or kill the conflicting process.
• Look for corrupted user profiles. If the error keeps happening for one specific user, their profile might be damaged. Create a new test user and see if the same error occurs.
• Check for group policy restrictions. Some policies limit the number of concurrent RDP sessions. If you hit the limit, new connections get refused. Check gpedit.msc under Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Connections. The setting "Restrict Remote Desktop Services users to a single Remote Desktop Services session" can cause this.
• Firewall or network issues. A firewall rule that resets idle connections can cause the session to drop on the server side. Check for any network equipment that has a "TCP idle timeout" setting lower than 30 minutes.

In my experience, Fix 2 (logoff the session) solves 90% of these errors. Fix 4 (restart the service) gets the rest. If you're still stuck, it's almost always a group policy or firewall issue. Good luck.