"Remote Desktop Services Is Currently Busy": How to Fix It

The "Remote Desktop Services is currently busy" message means the server accepted your connection but could not create or hand over a session in time. The usual culprits are a hung or leaked user session, a process slowly eating memory, security software that hooks into RDP, or a Group Policy hardening change. In most cases, resetting the stuck session or restarting the Remote Desktop Services service clears it, and finding the leaking software stops it coming back.

The full wording users see is usually: "The task you are trying to do can't be completed because Remote Desktop Services is currently busy. Please try again in a few minutes. Other users should still be able to log on." This guide works through the causes in the order an administrator should check them.

What Causes "Remote Desktop Services Is Currently Busy"?

The error is caused by the server running out of the resources it needs to build a new session, not by a problem on your own PC. Microsoft's troubleshooting article for this message groups the causes into three families, and in practice a fourth (connection limits) catches many small offices out.

A memory leak is when a program keeps asking Windows for memory and never gives it back. Over days, that starves the session manager, so new logons stall even though the server looks healthy. A session leak is similar: sessions that should have closed stay half-alive in the background, and each one holds resources that new connections need.

How Do I Fix a Hung Remote Desktop Session?

You fix a hung session by listing all sessions on the server and resetting the one that is stuck. This is the quickest fix when only one user is affected, and it doesn't disturb anyone else.

1. Sign in to the server another way: an administrator RDP session that still works, the physical console, or your hypervisor's console.
2. Open Command Prompt or PowerShell as administrator.
3. Run query session (or the short form qwinsta) to list every session with its ID and state. Add /server:SERVERNAME to run it against a remote server.
4. Find the affected user. A session in a Disc (disconnected) state, or one that stays in a connecting state, is the likely culprit.
5. Run reset session <ID> (or rwinsta <ID>), replacing <ID> with the session number. Unsaved work in that session is lost.
6. Ask the user to connect again.

If you prefer a graphical route, open Task Manager → Users on the server, right-click the stuck user and choose Sign off. On a full RDS deployment, Server Manager → Remote Desktop Services → Collections also lets you log off sessions.

Should I Restart the Remote Desktop Services Service?

Yes, restarting the Remote Desktop Services service is a sensible workaround when several users get the error and a full reboot isn't convenient. Microsoft notes that this disconnects everyone currently connected over RDP, but their sessions are kept and they can reconnect to them.

1. On the server, press Win + R, type services.msc and press Enter.
2. Find Remote Desktop Services in the list.
3. Before restarting, open Task Manager → Details and note how much memory the svchost process hosting it is using. Unusually high use points to a leak.
4. Right-click Remote Desktop Services and select Restart. Accept the prompt to restart dependent services.
5. Test a new RDP connection.

Do this from the console, not over RDP, or you will cut off your own connection. If you manage the server as a Hyper-V virtual machine, use a Basic session in the VM console. An Enhanced session uses RDP itself, so it can show the same busy message.

Why Does the Error Keep Coming Back After a Reboot?

The error returns after a reboot when something is leaking memory or sessions. The reboot clears the build-up, then the same software slowly fills it again. You need to find that software, not just restart more often.

1. Open Task Manager → Details and add the Memory (active private working set) and Handles columns if they aren't visible.
2. Check again over several hours or days. A process whose memory or handle count only ever goes up is the suspect.
3. List software that interacts with RDP sessions: antivirus and endpoint protection, monitoring agents, printer redirection tools, remote support tools and session recorders.
4. Update those products first. If the problem continues, remove them one at a time and watch whether the error stops.

Microsoft points out that stopping a product's service isn't the same as uninstalling it. Drivers and hooks can stay loaded, so a proper test means uninstalling, rebooting and observing. If you still can't find the cause, the same article explains how to collect traces with Microsoft's TSS tool for a support case.

Can Group Policy Cause "Remote Desktop Server Is Currently Busy"?

Yes. Security hardening applied through Group Policy, especially changes to User Rights Assignment, can stop sessions from initialising and produce this message. Problems with the Group Policy Client service itself can have the same effect.

1. Open Event Viewer → Applications and Services Logs → Microsoft → Windows → GroupPolicy → Operational and look for errors around the time of failed logons.
2. Run gpresult /h C:\gp.html as administrator and review which policies apply to the server.
3. If your security team allows it, temporarily move the server out of the hardening policy, run gpupdate /force and test.
4. If the error stops, reintroduce the settings one by one to find the one responsible.

While you are in Group Policy, check two settings under Computer Configuration → Administrative Templates → Windows Components → Remote Desktop Services → Remote Desktop Session Host → Connections: Limit number of connections and Restrict Remote Desktop Services users to a single Remote Desktop Services session. A low connection limit blocks extra users; the single-session rule reconnects users to their old session, which helps if old sessions are piling up.

Do RDS Licensing and Session Limits Play a Part?

Licensing is rarely the direct cause of the "busy" message, but session limits often explain why a server refuses extra users. A Windows Server without the RD Session Host role allows only two concurrent remote connections, intended for administration, and those two don't need client access licences.

For more users at once, you need the RD Session Host role, an RD Licensing server and Remote Desktop Services CALs (client access licences). According to Microsoft's RDS CAL documentation, there is a 120-day grace period; after it ends, clients must have a valid CAL issued by the licence server before they can sign in. CALs come per user or per device, and a CAL works with its own Windows Server version or earlier, but not with a newer one.

If you are planning a multi-user server, Windows Server 2022 Standard pairs with our Server 2022 RDS Device CALs, and our guide on how to apply and activate RDS CALs on Windows Server walks through installing them on the licence server.

A Common Mistake We See

A frequent pattern is a small business that installs Windows Server, lets three or four staff connect over Remote Desktop, and then hits errors once a third person tries to log in. The server was never given the RD Session Host role, so it is still in two-session administrative mode. Buying CALs alone doesn't change that: the role and the licence server have to be deployed and configured first, and the CAL type (user or device) must match the licensing mode you set. Plan the role, the licensing mode and the CAL count together before staff start relying on the server.

Frequently Asked Questions

Is "Remote Desktop Services currently busy" a problem with my PC?

Rarely. The message comes from the server you are connecting to, which can't build a session for you at that moment. Trying again from a different PC usually gives the same result. The fix happens on the server: resetting a stuck session, restarting the service, or removing the software that leaks resources.

How do I fix "Remote Desktop is currently busy" without rebooting the server?

Sign in through the console or a working admin session, run query session to find the affected user, then reset session with that session ID. If several users are affected, restart the Remote Desktop Services service from services.msc. Users are disconnected briefly but can reconnect to their saved sessions.

Why does only one user get the busy error?

When other people can still log on, the affected user usually has an orphaned or hung session that Windows keeps trying to reconnect them to. Resetting that one session normally fixes it. If the same user is hit repeatedly, check their logon scripts, profile and any software that loads in their session.

Can antivirus cause "Remote Desktop server is currently busy"?

Yes. Microsoft lists security software and endpoint protection among the products most likely to cause session leaks, because they hook into each new session. Update the product first. If the error persists, uninstall it temporarily, reboot and test, because simply stopping its service can leave drivers loaded.

Do I need RDS CALs to fix this error?

Not usually. CALs don't cure leaks or hung sessions. They matter when you need more than two simultaneous users, which requires the RD Session Host role and RDS CALs once the 120-day grace period ends. Licensing faults normally produce their own licensing messages rather than the busy error.

How long should I wait before trying again?

The message suggests a few minutes, and a brief spike can clear on its own. If it is still there after five to ten minutes, it won't fix itself; something on the server is stuck. Move on to checking sessions and memory use rather than retrying repeatedly.

Conclusion

"Remote Desktop Services is currently busy" is a server-side resource problem: reset hung sessions, restart the service as a workaround, then track down the software or policy that keeps causing it. If your server also needs to support more than two users at once, deploy the RD Session Host role with the right CALs from our Windows Server 2022 collection.

Useful Links