Fix Remote Desktop“An Internal Error Has Occurred” Server 2016

Are you depressed by Remote Desktop “an internal error has occurred” Server 2016? This post illustrates related reasons and 5 useful solutions to fix the problem.


By Ellie / Updated on November 24, 2022

Share this: instagram reddit

Remote Desktop error: An internal error has occurred in Server 2016

"Recently, I have had trouble connecting to my Server 2016 with RDP. I always get a message “ An internal error has occurred” each time. I totally have no idea about the issue. Any suggestions that can help me to fix the issue?"

Internal Error

The reasons for Remote Desktop An internal error has occurred for Server 2016

RDP An internal error as occurred on Server 2012, Server 2016 is an error that it’s difficult to find the causes. Usually, we can take misconfigured Server Settings, the denial of the service that attacks port 3389, firewall Settings, and weak networks into consideration. Furthermore, it also has something to do with the security of RDP. We need to change the security layer to fix the issue.

How to fix RDP error: An internal error has occurred in Server 2016

After knowing the root of the problem, let’s clarify the solutions to fix the issue "Remote Desktop Connection An internal error has occurred".

Method 1. Verify Remote Desktop Connection Settings

Step 1. Search “Remote Desktop Connection” in the search box and open it.

Step 2. Click on the Show options, and then locate on the “Experience” tab.


Step 3. Check or tick “Reconnect if the connection is dropped”.


Method 2. Disabling Network Level Authentication

Step 1. Click on “This PC” on your desktop, and then click on Properties in the left upper.

PC Computer  Properties

Step 2. Choose remote settings, locate the “ Remote” tab and finally uncheck and untick “ Allow connections only from computers running Remote Desktop with Network Level Authentication”.

Uncheck Identity Verification

Note: You can also solve the problem by clicking on “Allow remote connections to this computer”.

Method 3. Restart Remote Desktop Service

Step 1. Press Win + R to run the box, and then input “ services. msc” and then press “ Enter”.


Step 2. Double click “ Remote Desktop Services”.

Remote Desktop Services

Step 3. Now you can see the information in the following picture. Locate “Service status” and then click on “Stop” and hit OK.

Stop Service Status

Step 4. Wait nearly 6 seconds and then click on “Start”.

Start Service Status

Method 4. Change Security of RDP in Group Policy Editor

Step 1. Press Win + R and enter "gpedit.msc"  to open  Edit Group Policy.

Run Box Gpedit

Step 2. Navigation:

Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Security

Step 3. Locate “ Require use of specific security layer for remote connections” and double click it.

Open the Security Layer

Step 4. After “double click”, Choose “enabled” and select “RDP” in the security layer.

Security Layer

Step 5. Finally hit OK.

Method 5. Allow 3389 port in Defender Firewall

Step 1. Press Win + R to run the box, type “Control Panel” and press the “Enter” key to open the Control Panel.

Run Box Control Panel

Step 2. Click the “System and Security” and then select “Windows Firewall.” Choose “Advanced Settings.”

Advanced Settings

Step 3. Click the “Inbound Rules” option on the left of the Windows Firewall window and then click the “New Rule” option under the “Actions”.

Inbound Rule Firewall

Step 4. Click the “Port” option and then click “Next.”


Step 5. Click “TCP” for the port type and then click “Specific local ports.” Type in 3389 to the textbox next to “Specific local ports” and then click “Next.” 

3389 Port

Step 6. Click “Allow the connection” and then click “Next.”

Allow the Connection

Step 7. Select all options for connection types, then click “Next” again

Confirm Check

Step 8. Type in a name for the rule such as "TCP 3389," then click “Finish” to allow the 3389 port in Windows Firewall.

TCP 3389

A free alternative to RDP for Windows Server 2016: AnyViewer

Is there any way above already solve the Remote Desktop An internal error has occurred on Server 2016? If the answer is Yes, congratulations! If the answer is no, it is recommended to resort to a free RDP alternative: AnyViewer. It’s a stable and high-effective remote access software, which is applicable for Windows Server 2022/2019/2016/2012 R2 and Windows 11/10/8.1/8/7. Read the following instructions and get to know how to operate: 


  • Make sure both computers are connected to the Internet.
  • Download and install AnyViewer.
Download Freeware Win Servers & PCs
Secure Download

Step 1. On the PC that you want to control from another computer (the host computer), install and run AnyViewer; click "Log in" and click "Sign up".

Sign Up

Step 2.  Filling all necessary information to create an AnyViewer account and then you'll be logged in to AnyViewer.  If you have already signed up an account from its official website, you can sign in directly. 

Note:  The device will be assigned to the account automatically be assigned to the account you've logged in to. 

Free Edition

Step 3. On your local PC, log in to the same account as the remote PC and then go to "Device". Locate the distant computer, click it and choose "One-click control" to take full control of the PC. 


If you want to control a remote computer without signing in to the same account, you can go to "Connect",  type in the device ID of the remote PC, and get remote access via sending remote control or inputting a security code. 



5 methods to fix Remote Desktop An internal error has occurred in Server 2016 are shown in this post. Or you can simply resort to third-party free & secure remote access freeware-- AnyViewer, which can give you a better experience.