Windows Server 2016 Remote Desktop not working after reboot
"I have recently set up a number of new Remote Desktop Servers on my Windows Server 2016. 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 what can I do?"
3 solutions for “Windows Server 2016 Remote Desktop not working after reboot”
To fix Remote Desktop not working after reboot on Win 11/10 or Windows server 2016 or 2012 R2, here we have 2 workarounds to help you easily get rid of the trouble.”
- Check the network connections and whether 2 PCs are on the same LAN. If 2 PCs are not on the same LAN or there's something wrong with the network, then the connections won't be accomplished.
- Log in to Windows Server 2016 with an administrator account and try to RDP to the server to see if this error occurs still.
If the workarounds do not work for you, try the following solutions.
Method 1. Reset Remote Desktop Connection Broker Properties
It is said that resetting Remote Desktop Connection Broker Properties can fix Windows Server 2016, 2012, Windows 10 Remote Desktop not working after reboot. Therefore we can have as try.
Step 1. Press Win + R to open the dialog box and enter "services.msc", hit "OK".
Step 2. Locate Connection Broker, edit “Properties”.
Step 3. In the “General” tab, switch “Automatic” in Startup type. And please also ensure the relevant services in the “Dependencies” tab are listed in the startup.
Method 2. Create a new DWORD Value
If the services drop or crash, we can fix the issue "Windows Server 2016, 2012 Remote Desktop not working after reboot by increasing the service startup time in Registry Editor.
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 3. Run Disk Cleanup to free up disk space
Disk Cleanup can free up space on your hard disk, creating improved system performance, which may address the issue "Remote Desktop not working after reboot", including Windows 10.
Step 1. Search "cmd" in the search box, and run as administrator to open Command Prompt.
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. If the issue remains and you don't want to take too much time on fixing the issue, you can use a free & easy-operated 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.
Ready to work:
- Be sure that the local device and the remote device are wake and connected to the Internet.
- Download and install AnyViewer on both PCs.
Step 1. Sign up for an AnyViewer account and sign in to the two computers. The device will be assigned to the account once logged in.
Step 2. On the main interface of AnyViewer in your current computer, go to "Device" and locate the remote PC. Click it and choose "One-click control" to access an unattended computer with one click.
Step 3. Then you can remote into the computer over the internet for free and you can see the screen of the remote computer and run apps on it.
We know the ways how to access an unattended computer with one click via AnyViewer. The utility also allows you to access your friend’s computer for one time by sending a control request. Get it and have a try.
Solutions for “Windows Server 2016 Remote Desktop not working after reboot” are shown in 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.