By Ellie / Last Updated November 4, 2021

Remote Desktop services is currently busy

“I recently upgraded to Windows 10, and it runs smoothly. But today I've run across a problem. When I try to use Windows Remote Desktop, I received this: The task you are trying to do can’t be completed because Remote Desktop Services is currently busy.”

Remote Desktop Service Busy

If you ever see this error when you’re trying to log on to a Remote Desktop Server, it means that you are unable to connect to RDS Servers running Windows Server using the built-in RDP client. This happens due to a number of reasons, including an error in the operation of the Remote Desktop Services, a bug in the csrss.exe process, etc.

How to fix the error “Remote Desktop Services is currently busy”?

Here in this post, we’ll introduce three solutions to help you troubleshoot this problem. See the detailed steps listed in the following.

Solution 1. Reset stuck client Remote Desktop session

Step 1. Press Win + R, then type in “cmd” and press OK to open up the Command Prompt window.  

Run Box CMD

Step 2. Open a command prompt and type in “query session”. Then the command prompt returns a session name and ID for the affected user. In this case, we will assume “system” is having the issue. Take note of the user’s session ID, in this case it is Session 2.

Query Session

Step 3. Type in “query process /id 2” in the command prompt. Then there will display the list of running process in the session ID you noted earlier. Find the csrss.exe process and its PID. In my case, the PID is 5140. You need to end this process.

Query Process ID

 Step 4. Press Ctrl + Shift + Esc to open the Task Manager. Go to the Details tab and find the PID and the process we mentioned in the last step. Right-click it and then click End task.

End csrss.exe Process

In addition to csrss.exe, any processes operating within the stale session ID must be terminated. Generally, csrss.exe, winlogon.exe, dwm.exe, and LogonUI.exe should all be terminated. The procedures for terminating the other three processes are identical to those for terminating csrss.exe. To end the other three processes, simply repeat the procedures above.

Solution 2. Reset an RDS user session

Step 1. Press Windows key + R to invoke the Run dialog box. Type in “cmd” and press OK. Type in “query process” in the command prompt. Copy the session name of the problem user. In this case, we will assume “system” is having the issue, then the session name is “rdp-tcp#5”.

Session Name

Step 2. Then type in “reset session ”. Replace the SESSIONNAME with “rdp-tcp#5”. Then you may try to log on and a problem should not occur again.

Reset Session

Solution 3. Set Remote Desktop Drain mode

You need to make sure that the Drain mode preventing users from creating new RDP connections is disabled.

Step 1. Open Command Prompt and type in “chglogon.exe /QUERY” in the command prompt.

Query Drain Mode

If the command returns “Session logins are currently ENABLED”, then the problem not lies in here, you can stop here.

Step 2. If the command returns “New user logons are DISABLED, but reconnections to existing sessions are ENABLED”, then you need to disable Drain mode by typing in “chglogon.exe /enable”.

Disable Drain Mode

The easiest option: choose third-party remote control software

Then how to effectively avoid problems like “Remote Desktop Services is currently busy”? Here we provide you with the easiest option. You can use AnyViewer, the free yet professional third-party remote control software for Windows Servers, including Windows Server 2022/2019/2016/2012 R2, which can perfectly help you avoid RDP problems like name of remote access server did not resolve, the remote session was disconnected License Servers, your credentials did not work on Remote Desktop on Windows Server 2016.

AnyViewer has two connection methods: one is to send a control request, and the other is to connect input a security code. The following will introduce the operation steps of the two methods respectively. You can choose according to your own situation.

Preparation work:

  • Connect the client computer (the controller computer) and the host computer (the controlled computer) to the Internet.
  • Download and install AnyViewer on the client computer and the host computer respectively.
Download Freeware Win PCs & Servers
Secure Download

 Methods 1. Send a control request to realize Windows Server remote connection

Step 1. Run AnyViewer on both computers. On the client computer, input the device ID of the host computer in the Partner ID box, and then click Connect.

Temporary Code

Step 2. Then there will be a pop-up window, choose Send a control request to your partner. And then click OK.

Send a Control Request to Your Partner

Step 3. The host computer will receive a pop-up request. People sitting in front of the host computer need to click the green button to make the connection successful.

Request to Control Your Device

Methods 2. Input security code to realize Windows Server remote connection

There are two types of security codes:

  • A permanent security code is set by you in advance.
  • A temporary security code is automatically generated and will change every time.

Step 1. First, you need to set up a permanent security code on the host computer. Click Settings and then Recipient. Tick the third option. Then set the security code you want in the box. Then click OK to finish the set-up process. 

Accept Remote Control

Step 2. Return to the main interface of AnyViewer on the host computer, you could see the Temporary Security Code.

Copy the Temporary Security Code

Step 3. On the client computer, input the device ID of the host computer and click Connect. Choose Input security code, then enter either the permanent security code or the temporary security code of the host computer and click OK.

Security Code

Conclusion

Three solutions to the error “Remote Desktop Services is currently busy” on Windows 10 are introduced in this post. Furthermore, we propose the simplest method for remotely controlling computers, AnyViewer, which will free you from multiple RDP problems.