By Vivian / Last Updated October 22, 2021

Windows Server 2016 Remote Desktop not working after reboot

I have recently set up a number of new Server 2016 Remote Desktop Servers. However, it runs slowly when I remotely access another PC and seems to crash nearly, so I reboot it. However, the Windows Server 2016 Remote Desktop is not working after reboot. I totally have no idea about it now. Anyone can suggest to me that what can I do?

4 solutions for “Windows Server 2016 Remote Desktop not working after reboot”

Because there are many reasons for the problem, so let’s check something first to help you quickly find the root of the problem and address it quickly if you ever meet with the situation like “Remote Desktop not working after reboot on Win 11/10 or Windows server 2016 or 2012 R2.”

  • Please try to use the Remote Desktop of other clients (such as Windows 10) to connect to Windows 2016 to test whether the same problem occurs.
  • Whether the client in question and Windows 2016 are in a local area network, and whether there are other intermediate devices (such as routers, etc.) connected.
  • Is your network environment a domain or a work domain? Please log in to Windows 2000 with an administrator account and try remote desktop to see if this error occurs.

Now, follow me and read some solutions to fix the issue.

Method 1. Disable the third-party services

Step 1. Press Control + Alt +Delete to open Task Manager.

Step 2. Click on " Startup" tab.

Step 3. Disable third-party service and leave MS only.



Method 2. Setting Remote Desktop Connection Broker

Step 1. Press Win + R to run box and enter services.msc.

Step 2. Locate Connection Broker, edit “Properties”.

Step 3. In “General” tab, switch “Automatic” in Startup type. And please also ensure the relevant services in “Dependencies” tab are listed in startup.


Method 3. Create a new DWORD Value

Step 1. Press Win + R to run box and then enter “regedit”.


Step 2. Navigation: HKEY_LOCAL_MACHINE> SYSTEM>Current Control Set> Control

Step 3. Copy “ServicesPipeTimeout” and right-click it, then select “New” and choose DWORD Value, and then paste as the name.


Step 4. Double click the new DWORD Value, and then tick “Decimal”, change the value to 60000. Finally restart.


Method 4. Run Disk cleanup to free up disk space

Step 1. Search CMD in the search box, run as administrator to open CMD 


Step 2. Type “cleanmgr.exe” and press the “Enter” key.


Step 3. Select the drive you want to clean up.

Note: Disk Cleanup won't remove files that your computer needs, making it a safe way to free up a bit of space on your PC.

Software to replace Remote Desktop for Windows Server

After trying the above methods, maybe you already have an answer for “Windows Server 2016 Remote Desktop not working after reboot. Or you can use easy-to-use remote access software, AnyViewer. It’s workable for all editions of Windows Server 2022/2019/2016/2012 R2 (64bit and 32bit) and Windows 11/10/8.1/8/7. Whether you reboot the computer or not, AnyViewer can always give you a better experience. Now, follow me to know how to operate:

Ready to work:

  • Be sure that the local device and the remote device are wake and connected to the Internet.
  • Download and install AnyViewer.
Download Freeware Windows 2022/2019/2016/2012 R2
Secure Download

Step 1. Open and run AnyViewer, then you can see the device ID, temporary security code, Settings and so on.


Step 2. Input the device ID of the remote computer on the local PC, and then choose “Connect”.


Step 3. Send a control request to the remote computer.


Step 4. There will be a pop-up request on the remote computer, click on “allow” and then you can access successfully to the remote computer.


Note: If you are willing to access unattended computer, you are allowed to use “Input security code” connection method in AnyViewer.


Solutions for “Windows Server 2016 Remote Desktop not working after reboot” are shown on this post. What’s more, a better solution to remote access like AnyViewer is also recommended, which can easily help you out of the problem.