Fix 0xC00A0028: Remote Desktop Reconnect Console Error

Why you're seeing this error

This error pops up when you try to reconnect a Remote Desktop session that was previously connected to the console (the physical screen/keyboard/mouse of the machine) using mstsc /admin or mstsc /console, and that session got disconnected. Windows won't let you just pick it back up — it sees the old session as still attached to the console and says "sorry, can't do that."

You'll see this most often on Windows Server (2012 R2 through 2022) or Windows 10/11 Pro if you use the /admin switch to connect directly to the console session (session 0). Real-world trigger: you RDP'd into a server using mstsc /admin, your internet dropped, and when you reconnect you get this error instead of your old desktop.

Fix #1: Use mstsc /admin again (the quick fix)

This is the first thing to try because it works 90% of the time. The trick is that you must use the exact same connection method you originally used. If you connected via /admin before, you need to connect with /admin again.

1. Close any open RDP windows on your machine.
2. Press Windows Key + R, type mstsc /admin, and hit Enter.
3. In the Remote Desktop Connection window, type the computer name or IP address of the machine you're trying to reach.
4. Click Connect.
5. When prompted, enter your credentials. After you click OK, you should see your disconnected session restored — you'll get back to the same desktop with all your apps still running.

If this doesn't work, you'll get the same 0xC00A0028 error. Move on to Fix #2.

Fix #2: Kill the stale session from another admin session

When the /admin trick fails, it usually means the disconnected session is stuck in a weird state. You need to manually kill it from another RDP session. You'll need admin rights to do this.

1. Open a new Remote Desktop connection without the /admin flag. Connect to the machine using a normal RDP session (just mstsc). If you can't connect because all sessions are full, skip to Fix #3.
2. Once you're in, open Command Prompt as administrator. Right-click the Start button and pick Command Prompt (Admin) or Windows PowerShell (Admin).
3. Type query session and press Enter. You'll see a list of all active sessions. Look for the one with a state of "Disc" (disconnected) and a session name of "console" or "rdp-tcp#0". Note the session ID number in the left column.
4. Now type logoff [session ID] (replace [session ID] with the number you saw). For example: logoff 1. Press Enter.
5. You should see "The session has been logged off." No confirmation box — it just happens. That session is now gone.
6. Close the RDP window. Now open a new connection using mstsc /admin (Fix #1 steps). This time it should connect fresh, and you won't get the error.

Fix #3: Restart the Remote Desktop Services (when you can't get any session in)

If you can't even establish a normal RDP session because all available sessions are filled with disconnected console sessions (common on servers with only 2 admin sessions), you need to restart the service remotely. You'll need local admin access to the machine — either physical access or a management tool like iDRAC, iLO, or IPMI.

1. Log in locally (physically at the machine) or through your management console (Dell iDRAC, HP iLO, etc.).
2. Open Services (press Windows Key + R, type services.msc, hit Enter).
3. Scroll down to Remote Desktop Services (it's sometimes called Terminal Services on older systems). Right-click it and select Restart.
4. You'll see a warning that all current RDP sessions will be terminated. Click Yes to proceed.
5. After the service restarts (takes about 10-15 seconds), close the Services window.
6. Now go back to your remote machine, open mstsc /admin, and connect. You should get a clean login screen with no error.

Heads-up: This kills all active RDP sessions for everyone. Only do this if you're sure no one else is working on the machine, or if you have permission to bump them.

Quick-Reference Summary Table

That's it. The error 0xC00A0028 is annoying but it's not a deep problem — it's just Windows being picky about how you reconnect to a console session. Stick with Fix #1 first, and if that doesn't cut it, go after the session directly. You'll be back on your desktop before you know it.