nsapop.blogg.se - Allmänt

Windows server 2016 remote desktop services device

If the PID we need corresponds to the csrss.exe process, kill the process by clicking End task in the context menu or by entering the following command in the command prompt: taskkill /F /PID 5140ĭo it for each (4) user if there are some of them. Now, open the Task Manager, go to the Details tab and find the PID and the process from the previous step. Now, display the list of the running process in the session ID we received earlier: C:\>query process /id 2įind the csrss.exe process (check the IMAGE column) and its PID. We must kill the csrss.exe process that is working in this session. There are 3 columns we need in the output: SESSIONNAME, USERNAME and ID.įind the (4) user and the corresponding ID, in this example, it is ID 2. It will show all users and their remote sessions on the RDS host. SESSIONNAME USERNAME ID STATE TYPE DEVICE So let us try to solve the problem without rebooting the host.įirst, run the elevated command prompt and execute the command: C:\>query session If it does not help, it is better to reboot the server.īut this is often not possible, as it will affect other users’ sessions on the RDS host. To start with, try to reset all hung (4) RDS sessions in the Task Manager.

Windows Logon Application (winlogon.exe).

Client-Server Runtime Process (csrss.exe).

As a rule, there will be 4 processes in a hung RDS user session: But sometimes we can find multiple hung sessions with the name (4) instead of a username in the Task Manager. In most cases, it is enough to solve the problem. Reset Stuck Client Remote Desktop Session on RDSįirst of all, try to find and reset a session of the user who cannot logon to the RDS server.įind a user in the Users tab of the Task Manager and click Log off in the context menu. Also, view the event log to see if there are any critical errors related to RDS. Make sure that we have enough server resources since the problem may occur due to the lack of RAM or disk space.Ĭheck the RAM load and how much free space is left on the disk with the operating system installed (there must be at least 1GB).

How to fix the error remote desktop services is currently busy? Let us now look at the possible methods to fix this error.

Lack of RAM or disk space on the RDSH server.An issue with a user profile or profsvc service.An error in the operation of the Remote Desktop Services.The error may appear for a number of reasons as given below:

Sometimes users cannot connect to RDS Windows Server using the built-in RDP client (mstsc.exe) with the following error: What causes the error remote desktop services is currently busy? Let us today discuss the possible causes and fixes for this error. Users often receive the error message “remote desktop services is currently busy” while connecting to a Windows server using RDP.Īs a part of our Server Management Services, we help our Customers with Windows related errors regularly.