Remote Desktop Services is currently busy: how to fix it on Windows Server
The server received your connection but could not give you a session. Start at the console, check for the September 2026 Windows update and its fix, clear stuck sessions, then find what keeps causing it.
Key takeaways
- Start at the console. Microsoft's first test is a sign-in through the server's console, which does not use Remote Desktop and keeps working when every Remote Desktop sign-in is refused.
- Check for the September 2026 update. It made Remote Desktop Services unstable. The fix is the out-of-band update of 14 September 2026 or any later cumulative update, and you do not have to uninstall the September update first.
- Clear stuck sessions with
quserandlogoff <ID>, then restart the service withRestart-Service -Name TermService -Force. Users are disconnected, but their sessions are kept. - If it keeps coming back, look for a leak, often from third-party security software, or a hardening Group Policy.
- On a RyzenRDP server, RDP Rescue fixes this error for $39, invoiced only once you can sign in again.
On this page
- Short answer
- Quick checklist
- What does "Remote Desktop Services is currently busy" mean?
- Can you still reach the server? Start with the console
- Did a Windows update break Remote Desktop? The September 2026 updates
- How do I clear stuck sessions?
- Which services and logs should I check?
- Why does it keep coming back?
- Can someone fix it for me for a fixed price?
- Your own Windows server
Short answer
"Remote Desktop Services is currently busy" means the server received your connection, but its Remote Desktop
service could not start or reconnect a session for you. If it began after a September 2026 Windows security update,
Microsoft has confirmed the cause: install the matching out-of-band update of 14 September 2026, or any later
cumulative update. Otherwise, sign in through the server's console, sign out stuck sessions with quser and
logoff, and restart the Remote Desktop Services service (TermService).
Quick checklist
- Sign in through the console, not Remote Desktop: the physical screen, or for a virtual server a view of its screen from your hosting provider, where it offers one. This is Microsoft's own first test.
- Check for the September 2026 update. If it is installed and its fix is not, install the latest cumulative update or the matching out-of-band update from the table below.
- Clear stuck sessions: run
quser, thenlogoffwith the ID of a stuck session. - Restart the service:
Restart-Service -Name TermService -Force. Users are disconnected, but their sessions are kept. - Still failing? Restart the server, then read the Remote Desktop event logs.
- Keeps coming back? Look at third-party software, security software first, and at hardening Group Policy.
What does "Remote Desktop Services is currently busy" mean?
The full message reads: "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." It comes from the server, so the IP address, the port and the network path are working. The connection arrived; the Remote Desktop service could not hand you a session. That makes it a different problem from a connection that times out or drops, which our Remote Desktop timeout guide covers.
| Likely cause | What points to it | What to do |
|---|---|---|
| The September 2026 Windows security update | It started after that update. Sign-in hangs at Welcome or at "Please wait for the Remote Desktop Configuration", or File Explorer, MMC or the Windows Update page stop responding | Install the out-of-band update or a later cumulative update |
| A stuck session | One user cannot get back into their session while others can sign in | Sign that session out with logoff |
| A memory, session or token leak | A restart fixes it for a while, then it returns | Find the software that leaks; Microsoft names security software as a common cause |
| A hardening Group Policy | It started after a policy change, for example to User Rights Assignment | Remove the policy to test, and read the GroupPolicy log |
| A wider problem on the server | Signing in at the console is slow or shows another error too | Fix that problem first |
Can you still reach the server? Start with the console
Microsoft's first troubleshooting step is a sign-in through the console: the physical screen, or for a virtual machine, the hypervisor's console. The console does not use Remote Desktop, so the busy message does not appear there. The test shows whether something else is wrong with sign-in itself, such as a different error or a very slow sign-in. If the console has problems too, Microsoft advises fixing those first.
On a virtual private server, the console is a view of the server's screen that your hosting provider may give you in the browser. Where you have one, it keeps working when every Remote Desktop sign-in is refused, and you can run every command in this guide from it. If you run Hyper-V yourself, use a Basic session: Microsoft notes that an Enhanced session runs over Remote Desktop and can show the same message.
While you are at the console, rule out client sign-ins that were switched off for maintenance:
change logon /query
chglogon /query does the same: chglogon is the older command that change logon replaced. If it reports that
logons are disabled, change logon /enable turns logons from client sessions back on. A restart turns them back on
as well.
On a RyzenRDP server, the RyzenRDP console is your account: servers, invoices and tickets. It does not show the server's screen, but it keeps working while Remote Desktop is down. Open a ticket of the type "Technical support" there with the error message and when it started. We tell you on the ticket whether the fix is free or $39 and ask for your OK. Once you agree, we can reach the server's screen without Remote Desktop.
Did a Windows update break Remote Desktop? The September 2026 updates
After the security updates of 8 September 2026, Microsoft confirmed that Remote Desktop Services can become unstable. The symptoms on its list:
- this message, or "This computer can't connect to the remote computer";
- "A licensing error occurred while the client was attempting to connect (licensing timed out)";
- connections that stay at Connecting, sign-ins that stay at Welcome, or a server that stays at Please wait for the Remote Desktop Configuration;
- MMC, the RDS Licensing Diagnoser, File Explorer or the Windows Update page no longer responding.
In the Remote Desktop window this often shows as a connection stuck at "Configuring remote session".
Microsoft fixed it in out-of-band (OOB) updates released on 14 September 2026, and later cumulative updates include the fix. For Windows Server:
| Windows Server | Affected September 2026 update | Out-of-band fix (14 September 2026) |
|---|---|---|
| Windows Server 2025 | KB5122871 | KB5129235 |
| Windows Server 2022 | KB5122882 | KB5129237 |
| Windows Server 2019 | KB5122876 | KB5129238 |
| Windows Server 2016 | KB5123099 | KB5129239 |
Microsoft's article also lists the updates for Windows 10, Windows 11 and Windows Server 2012 and 2012 R2. Check your version and both updates in PowerShell. This example is for Windows Server 2022; use the numbers from your row:
Get-ComputerInfo | Select-Object WindowsProductName, WindowsVersion, OsBuildNumber
Get-HotFix -Id KB5122882,KB5129237
If Get-HotFix does not list a KB, Microsoft's fallback looks in the installed packages:
Get-WindowsPackage -Online | Where-Object PackageName -Match '5122882|5129237' | Select-Object PackageName, PackageState, ReleaseType, InstallTime
Both checks look only for those two numbers. A later cumulative update also contains the fix, and on a server that
has one, the September numbers may not be listed at all. An error saying Get-HotFix cannot find a KB only means
that KB is not listed, not that the fix is missing. To see the most recently installed update, use the example from
Microsoft's Get-HotFix reference:
(Get-HotFix | Sort-Object -Property InstalledOn)[-1]
If that KB number is a cumulative update for your version released after 14 September 2026, the fix is already in it. Check the release date of the KB itself, not the day it was installed.
To fix it:
- Install the latest cumulative update for your version, which is Microsoft's first recommendation, or the out-of-band update from the table if your update policy calls for that one.
- You do not have to uninstall the September update first. Microsoft says to install the fix directly.
- If the Windows Update page hangs, download the standalone package for your version from the Microsoft Update Catalog and install it on the server. Our guide to installing Windows updates with PowerShell covers the command line.
- Restart if the update asks for it. Then check that new Remote Desktop connections work, that you can sign in and out, and that File Explorer, MMC and the Windows Update page respond.
Microsoft mentions removing the September update only as a temporary recovery step, for a server where the out-of-band update cannot be installed.
Some answers point to Microsoft article 2661332. That hotfix lists Windows Server 2008 R2 only, so it does not apply to current Windows Server versions.
On Windows Server 2016, extended support ends on 12 January 2027. Our page on Windows Server 2016 end of support explains the options.
How do I clear stuck sessions?
Open Command Prompt or PowerShell as Administrator on the server, from the console if Remote Desktop refuses you.
-
List the sessions:
quserquseris the same command asquery user. For each session it shows the user name, the session name, the session ID, the state (active or disconnected), the idle time and the sign-in time. Look for old disconnected sessions and for the session of the user who cannot get in. The output contains user names, so Microsoft advises removing them before you share it in a ticket or a forum. -
Sign out a stuck session by its ID:
logoff 3This ends every program in that session and deletes it, so unsaved work in it is lost. If the user is still around, warn them first with the
msgcommand.logoffcannot sign out the console session. -
Reset a session that will not end:
reset session 3Microsoft keeps this for a session that malfunctions or has stopped responding. Unsaved work in it is lost too.
-
Restart the Remote Desktop Services service:
Restart-Service -Name TermService -ForceMicrosoft's article says this disconnects every user connected over Remote Desktop, but the sessions are kept, and users might be able to reconnect to them. Run it from the console: inside a Remote Desktop session, yours drops too. If the restart clears the error, watch how much memory the service uses over the following days, because steady growth points to a leak.
-
Restart the server if the service will not restart or the error returns straight away. Microsoft lists a restart as the first step for memory problems.
Which services and logs should I check?
Get-Service -Name TermService,SessionEnv,UmRdpService
TermService is Remote Desktop Services itself; SessionEnv and UmRdpService are the two services Microsoft
checks alongside it, and the output gives each one's display name and status. After a fix, Microsoft expects all
three to be running where the server's role needs them.
Then read these event logs in Event Viewer, under Applications and Services Logs > Microsoft > Windows unless noted, and look for errors and warnings at the time the message appeared:
- TerminalServices-LocalSessionManager > Operational
- TerminalServices-RemoteConnectionManager > Operational
- RemoteDesktopServices-RdpCoreTS > Operational
- GroupPolicy > Operational, for policies that fail to apply
- Windows Logs > System and Windows Logs > Application
The same logs from PowerShell, newest event first:
Get-WinEvent -LogName 'Microsoft-Windows-TerminalServices-LocalSessionManager/Operational' -MaxEvents 50
Swap in Microsoft-Windows-TerminalServices-RemoteConnectionManager/Operational or
Microsoft-Windows-RemoteDesktopServices-RdpCoreTS/Operational for the other two.
Why does it keep coming back?
- A restart fixes it for a while. Microsoft reads that pattern as a leak of memory, sessions or tokens. Watch Task Manager for a process whose memory keeps growing between restarts. A session leak often shows nothing in Task Manager, Microsoft notes, so a clean Task Manager does not rule it out: test by uninstalling suspect software instead.
- Third-party software. Microsoft says leaks are often caused by non-Microsoft software, and session leaks very often by security software such as antivirus or endpoint protection that interacts with user sessions. Keep all third-party software updated. To test a suspect, uninstall it rather than stop it: a stopped program can still have modules loaded.
- Hardening Group Policy. Policies that harden the server, for example changes to User Rights Assignment, can cause it. Where it is safe to do so, remove them to test, and check the GroupPolicy log for policies that fail or for problems with the Group Policy Client service.
- Still unexplained. Microsoft's TSS tool (the
UEX_RDSSrvscenario on the server) records traces for a support case with Microsoft.
Can someone fix it for me for a fixed price?
Everything in this guide is free to do yourself if you can reach the server, through a second Remote Desktop session or a console that shows the server's screen. You also need the Administrator password, and the Microsoft articles in the sources below cover every step. On a RyzenRDP server where every Remote Desktop sign-in is refused, open a ticket.
If your server is with RyzenRDP and you would rather hand it over:
- RDP Rescue has "Remote Desktop Services is currently busy" on its fix list. For this error we clear the stuck sessions, restart the service and deal with the Windows update that caused it. Tracking down a leak in other software, or changing your hardening policies, is admin time. One fix costs $39, and we raise the invoice only once you can sign in again. If we cannot fix it, there is no invoice. A fault on our side, in the host, the network or the Windows installation we delivered, is fixed free. RDP Rescue covers RyzenRDP servers only.
- Care for Windows, $29 a month, installs Windows updates in a monthly window you pick and holds back updates known to break Remote Desktop, with 30 minutes of admin time each month.
- Other work inside Windows is admin time at $29 per 30 minutes, prepaid.
Your own Windows server
A RyzenRDP Windows VPS is your own Windows Server with full Administrator access, and your RyzenRDP account console, where you open tickets, keeps working when Remote Desktop does not. Windows Server is installed for you but not activated: the Windows Server license is not included in the plan price, and you license and activate it yourself. The FAQ covers licensing and how many people can sign in at once.
FAQ
Will restarting Remote Desktop Services sign everyone out?
No, it disconnects them. Microsoft says restarting the Remote Desktop Services service (TermService) disconnects every user connected over Remote Desktop, but their sessions are kept, and they might be able to reconnect to them. Signing a user out with logoff is different, because it ends that session and every program in it.
Do I need to uninstall the September 2026 update to fix it?
No. Microsoft says to install the matching out-of-band update of 14 September 2026, or any later cumulative update, directly, without uninstalling the September update first. On Windows Server 2022, for example, the affected update is KB5122882 and the out-of-band fix is KB5129237. Microsoft mentions removing the September update only as a temporary recovery step when the fix cannot be installed.
How can I fix it if I cannot connect with Remote Desktop at all?
Sign in through the server's console, which does not use Remote Desktop. That is the physical screen, or for a virtual server the hypervisor's console or a view of the server's screen that your hosting provider gives you, where it offers one. From there, run quser and logoff to clear stuck sessions, restart the service with Restart-Service -Name TermService -Force, and install the update that fixes the September 2026 issue. Another administrator who still has a working Remote Desktop session can run the same commands. On a RyzenRDP server, the RyzenRDP console is your account, not a view of the server's screen, so open a ticket there. Once you agree on the ticket, we can reach the server's screen without Remote Desktop.
Why do some users get the message and others do not?
When one user cannot get in while others can, that user's own session can be stuck. As an older example, on Windows Server 2008 R2 Microsoft traced one case (article 2661332) to a deadlock with apps such as Excel, where a user could not reconnect to a disconnected session. Find the session with quser and sign it out with logoff. When every user gets the message, the Remote Desktop service itself is in trouble, so check for the September 2026 update and restart TermService.
Does a reboot fix it for good?
Often not. Microsoft notes that when a restart fixes the error only for a while, the cause is likely a leak of memory, sessions or tokens, often from non-Microsoft software such as antivirus or endpoint protection. If the September 2026 security update is the cause, the lasting fix is the out-of-band update or a later cumulative update.
How many people can sign in to a Windows VPS at the same time?
Without the Remote Desktop Session Host role, Windows Server allows the two connections for administration that need no RDS CALs. More users need the Remote Desktop Session Host role, a Remote Desktop Licensing server and an RDS CAL for each user or device, which you license yourself. On RyzenRDP, the Windows Server license itself is not included in the plan price. Windows Server is installed but not activated, and you license and activate it yourself, as the licensing answer in our FAQ explains.
Can you fix it for me, and what does it cost?
On a RyzenRDP server, yes. "Remote Desktop Services is currently busy" is on the RDP Rescue fix list. For this error we clear the stuck sessions, restart the service and deal with the Windows update that caused it; tracking down a leak in other software, or changing your hardening policies, is admin time. We tell you on the ticket whether the fix is free or paid and ask for your OK before we start. One fix costs $39, and the invoice is raised only once you can sign in again; if we cannot fix it, there is no invoice. A fault on our side, in the host, the network or the Windows installation we delivered, is fixed free. RDP Rescue covers RyzenRDP servers only.
Sources
- Microsoft Learn: Troubleshoot Remote Desktop Services instability after September 2026 Windows security updates (symptoms, the affected and out-of-band updates, checks and event logs; updated 28 September 2026)
- Microsoft Learn: Remote Desktop Service is currently busy message on connecting (the console test, restarting the service, leaks, Group Policy; updated 12 February 2026)
- Microsoft Learn: Resolved issues in Windows Server 2025 (Remote Desktop Services might stop responding after the September 2026 security update; resolved by KB5129235)
- Microsoft Learn: command references for quser, logoff, reset session and change logon
- Microsoft Learn: PowerShell Restart-Service, Get-WinEvent and Get-HotFix (Example 4: the most recent hotfix)
- Microsoft Support: KB 2661332, You cannot reestablish a Remote Desktop Services session to a Windows Server 2008 R2-based server (the full message text; a Windows Server 2008 R2 hotfix only)
- Microsoft Learn: Troubleshoot Remote desktop disconnected errors (two connections for administration without RDS CALs) and License Remote Desktop Services with client access licenses (CALs) (the Remote Desktop Licensing server, per user and per device CALs)