Fix Remote Desktop Services Is Currently Busy in Windows 11

When you see “Remote Desktop Services is currently busy” in Windows 11, it usually means the Remote Desktop host has hit its connection limit or a stale session is blocking new logins. The fix is to free up sessions or restart the Remote Desktop services, and this article walks you through both approaches step by step.

Why This Error Appears

Remote Desktop Protocol (RDP) allows Windows 11 Pro, Enterprise, and Education editions to accept multiple simultaneous connections, but the free Remote Desktop Host on Windows 11 only permits one active session at a time. The “currently busy” message appears when:

Another user is already logged on and you try to connect with a different account.
A previous session was disconnected but not logged off, so it still counts as active.
The Remote Desktop Services service is hung or the listener is stuck.
Group Policy or registry settings limit the number of connections to 1.

Windows 11 Home does not include Remote Desktop Host at all, so this error only applies to Pro, Enterprise, or Education editions.

Quick Fix: Log Off the Stale Session

The most common cause is an orphaned session left behind after a network drop or abrupt shutdown. To clear it:

Open the Remote Desktop Connection client on your local machine.
Type the host computer’s IP or name and connect.
You may see a prompt that the user is already logged on. Choose “No” to disconnect the other session.
If you cannot connect at all, use the host’s physical console (or another admin connection) to press Ctrl+Alt+Delete and select “Sign out” for the stale user.

If you don’t have physical access, you can use PowerShell from another admin session on the host:

query session

This lists all sessions. Note the session ID for the stuck user, then run:

logoff <sessionID>

That forcibly ends the session and frees the connection slot.

Restart the Remote Desktop Services

If no session appears stuck, the service itself may have stopped responding. Restart it from an elevated command prompt or PowerShell on the host:

net stop TermService
net start TermService

Alternatively, open Services.msc, find Remote Desktop Services, right-click and choose Restart. This disconnects all active sessions, so do it during a maintenance window if others are using the machine.

Also check that the Remote Desktop Services UserMode Port Redirector and Remote Desktop Configuration services are running. If they are stopped, set them to Automatic and start them.

Check Group Policy and Registry Limits

Windows 11 Pro allows only one remote session by default, but administrators can raise that limit via Group Policy or registry. To see if a policy is forcing the busy state:

Press Win+R, type gpedit.msc (Pro/Enterprise only) and press Enter.
Navigate to Computer Configuration > Administrative Templates > Windows Components &strong> Remote Desktop Services > Remote Desktop Session Host > Connections.
Double-click Limit number of connections. If it is Enabled, the value is the maximum concurrent sessions. Setting it to 1 will cause the busy error for a second user.

If you don’t have Group Policy, check the registry:

HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services

Look for a DWORD named MaxInstanceCount. If it exists and is 1, that’s the culprit. Change it to a higher number (like 2 or 3) or delete it to use the default. You must restart the Remote Desktop Services for the change to take effect.

Network and Firewall Considerations

Sometimes the error is misleading and the real issue is the network. If the host’s IP changed or the port (3389) is blocked, Windows may show a generic “busy” message. Verify that:

The host is reachable via ping.
Port 3389 is open in Windows Defender Firewall for both TCP and UDP.
Your router forwards port 3389 if you are connecting from outside the local network.

To test the port, run from your local machine:

Test-NetConnection <hostIP> -Port 3389

If TcpTestSucceeded is False, the port is blocked. Add a firewall rule on the host: Windows Defender Firewall > Advanced Settings > Inbound Rules > New Rule, select Port, enter 3389, and allow the connection.

Alternatives to Native RDP

If the busy error persists and you need a reliable remote connection, consider these alternatives:

Quick Assist – Built into Windows 11, allows someone to view or control the PC without RDP. It is session-based and does not conflict with RDP.
Third-party remote tools – Many free and paid options exist that run as a service and do not use the RDP listener. They often bypass the single-session limit.
Windows 365 or Azure Virtual Desktop – Cloud-based solutions that give each user a separate virtual machine, eliminating the busy error entirely.

These options are especially useful if you only need occasional remote help and want to avoid managing RDP sessions.

Frequently Asked Questions

Why does the error happen even when I am the only user?

If you are the only user but still get the busy message, the most likely cause is a disconnected session that the system still considers active. Check with query session and log off any stale sessions. Also, verify that the Remote Desktop Services service is actually running and not hung.

Can I increase the number of simultaneous RDP connections on Windows 11?

Yes, but only on Pro, Enterprise, or Education editions. You can modify the Group Policy “Limit number of connections” or the registry MaxInstanceCount value. However, Microsoft’s licensing terms technically require a Remote Desktop Services license for multiple concurrent users, so for more than one active session you should use a proper RDS deployment.

Does Windows 11 Home support Remote Desktop?

No. Windows 11 Home can use the Remote Desktop client to connect to other machines, but it cannot act as a Remote Desktop host. The “Remote Desktop Services is currently busy” error will not appear on Home because the feature is not available.

Will restarting the Remote Desktop Services disconnect all users?

Yes. Restarting the TermService service will drop all active RDP sessions. Make sure you warn any other users or schedule the restart during off-peak hours.

What should I do if the error appears after a Windows update?

Windows updates can sometimes reset service settings or firewall rules. Re-check that the Remote Desktop Services is set to Automatic and running, and that port 3389 is not blocked. If the issue persists, use System Restore to roll back the update temporarily.

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.

More in this bed

The whole Tech How-To bed →