The remote desktop error ‘An internal error has occurred’ is often caused by RDP settings or its local group policy security. There have been quite a few reports which state that users are not able to use the Remote Desktop Connection client to connect to another system. According to reports, this issue occurred out of the blue and wasn’t caused by any particular action.
Upon clicking Connect, the Remote Desktop Connection client freezes and then the error pops up after a few seconds. Since Remote Desktop Connection is used by many users for their business or personal purposes, this error can turn out to be quite the pain. However, do not worry as you will able to fix the issue by going through this article.
What causes the ‘An Internal Error has Occurred’ Error on Windows 10?
Since the error appears out of the blue, its specific cause is not known, however, it can occur due to one of the following factors —
- Remote Desktop Connection settings: For some users, the error was caused by their Remote Desktop Connection client settings.
- RDP Security: In some cases, the error can appear due to the Security of the Remote Desktop Protocol in which case you will have to change the security layer.
- Computer’s domain: Another thing that can cause the error to appear can be the domain to which your system is connected. In such a case, removing the domain and then joining it again will fix the issue.
Now, before you apply the solutions that are provided down below, please make sure that you are using an administrator account. Also, we recommend following the given solutions in the same order as provided so that you can isolate your issue quickly.
Solution 1: Change Remote Desktop Connection Settings
To start off, we will try to isolate the issue by changing the RDP settings a little bit. Some users have reported that their issue was resolved once they checked the ‘Reconnect if the connection is dropped’ box. You can do this by following the given steps:
- Go to the Start Menu, search for Remote Desktop Connection and open it up.
- Click on Show Options to unveil all the settings.
- Switch to the Experience tab and then make sure ‘Reconnect if the connection is dropped’ box is checked.
- Try connecting again.
Solution 2: Rejoining Domain
The error message is sometimes generated due to the domain you have connected your system to. In such cases, removing the domain and then joining it again will fix your issue. Here’s how to do it:
- Press Windows Key + I to open Settings.
- Navigate to Accounts and then switch to the Access work or school tab.
- Select the domain you have connected your system to and then click Disconnect.
- Click Yes when prompted to confirm.
- Disconnect your system and then restart your computer as prompted.
- Once you have restarted your system, you can join the domain again if you wish to.
- Try using RDP again.
Solution 3: Changing MTU Value
Another way of fixing the issue would be to change your MTU value. Maximum Transmission Unit is the largest size of a packet that can be sent in a network. Dropping the MTU value can help in fixing the issue. Here’s how to do it:
- To change your MTU value, you will have to download a tool called TCP Optimizer. You can download it from here.
- Once downloaded, open up TCP Optimizer as an administrator.
- At the bottom, select Custom in front of Choose settings.
- Change the MTU value to 1458.
- Click Apply Changes and then exit the program.
- Check if it fixes the issue.
Solution 4: Changing Security of RDP in Group Policy Editor
In some cases, the error message pops up due to your RDP security layer in the Windows group policies. In such scenarios, you will have to force it to use the RDP Security layer. Here’s how to do it:
- Go to the Start Menu, search for Local Group Policy and open up ‘Edit group policy’.
- Navigate to the following directory:
- Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Security
- On the right-hand side, locate the ‘Require use of specific security layer for remote (RDP) connections’ and double-click it to edit it.
- If it is set to ‘Not configured’, select Enabled and then in front of Security Layer, choose RDP.
- Click Apply and then hit OK.
- Restart your system so that the changes take effect.
- Try connecting again.
Solution 5: Disabling Network Level Authentication
You can also try to fix your issue by disabling Network Level Authentication or NLA. The issue can, at times, be caused if you or the target system is configured to only allow remote connections that are running Remote Desktop with NLA. Disabling it will fix the issue, here’s how to do it:
- Go to your Desktop, right-click on This PC and select Properties.
- Click on Remote Settings.
- Under Remote Desktop, un-tick the ‘Allow connections only from computers running Remote Desktop with Network Level Authentication’ box.
- Click Apply and then hit OK.
- See if it isolates the issue.
Solution 6: Restarting Remote Desktop Service
In some cases, restarting the Remote Desktop Service does the trick, therefore, in this step, we will be manually restarting it. For that:
- Press “Windows” + “R” to open Run prompt.
- Type in “services.msc” and press “Enter“.
- Double click on “Remote Desktop Service” and click on “Stop”.
- Click on “Start” after waiting for at least 5 seconds.
- Check to see if the issue persists.