Fix ERROR_CTX_WINSTATION_BUSY (0X00001B70) RDP

Quick Answer

Open Remote Desktop Services Manager (tsadmin.msc), find idle sessions, right-click and select Log Off. If that's not enough, raise the connection limit via Group Policy or registry.

Why This Happens

Windows Server limits concurrent RDP connections — default's 2 on most SKUs (plus the console session). The culprit here is almost always someone's locked session sitting there idle for hours. Could be an admin who walked off, a scheduled task that didn't close cleanly, or a service account holding a session. The error code 0X00001B70 maps to ERROR_CTX_WINSTATION_BUSY, which is Windows telling you: "No more seats at the table." You'll see this most often on Windows Server 2019 or 2022 in a lab, dev box, or a lightly managed production server where nobody's watching session counts.

Step-by-Step Fix

Check active sessions — Run qwinsta from an elevated command prompt. Lists all sessions, their IDs, and state (Active, Disc, etc.). Disc means disconnected but still consuming a license.
Kill idle sessions — In the same command prompt, type rwinsta for each session marked Disc. Replace with the session number from the qwinsta output. This force-logs them off instantly.
Or use the GUI — Open tsadmin.msc (Remote Desktop Services Manager). Expand your server, click Sessions, right-click the idle session, choose Log Off. Same result, easier for point-and-click types.
Increase the connection limit — If you keep hitting the ceiling, bump it. Run gpedit.msc, go to Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Connections. Enable Restrict Remote Desktop Services users to a single Remote Desktop Services session (if you want one session per user), and set Limit number of connections to something higher — 5 or 10, depending on your needs. Group Policy refresh takes a reboot or gpupdate /force.
Registry shortcut — No Group Policy? Edit HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp, set MaxInstanceCount to a DWORD value of 10 (decimal). Reboot or restart the Remote Desktop Services service (net stop TermService && net start TermService).

Alternative Fixes if the Main One Fails

Restart the TermService — Yes, it's the nuclear option. From an admin prompt: net stop TermService && net start TermService. Kills all sessions. Do this only if you're sure nobody's doing critical work over RDP.
Check for stale sessions via PowerShell — Run Get-WmiObject -Class Win32_TerminalService | Select-Object -Property *. Rarely needed, but useful if qwinsta returns nothing useful (broken WMI). I've seen this on Server 2012 R2 after failed updates.
Verify the port isn't conflicting — If you changed the RDP port (3389 default), make sure another service isn't squatting on the new port. Run netstat -ano | findstr :3389 (replace with your port). If the PID isn't TermService, that's your problem. Kill the rogue process or change the RDP port back.

Prevention Tip

Set a Group Policy to automatically disconnect idle sessions after 15 minutes. Go to Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Session Time Limits. Enable Set time limit for disconnected sessions and set it to 15 minutes. Also enable Set time limit for active but idle Remote Desktop Services sessions — 1 hour is generous. This cuts down the "session full" calls by 90%. Don't bother with third-party session management tools unless you're running a multi-user RDS farm — for a handful of admins, native tools work fine.