The remote desktop ‘an internal error has occurred’ error is often caused by RDP settings or local group policy security. There are some reports that users are unable to use the Remote Desktop Connection Client to connect to another system. Reportedly, this problem came out of the blue and was not caused by a specific action. After clicking Connect, the Remote Desktop Connection Client freezes and the error appears after a few seconds. If you see the message "an error has occurred Windows 10", then your spirits will surely rise. Since the remote desktop connection is used by many users for business or personal purposes, this bug can prove to be very painful. However, don’t worry as you can fix the problem 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 exact cause is unknown, but it can be caused by one of the following factors –
- Remote desktop connection settings: For some users, the error was caused by remote desktop connection client settings.
- RDP security: In some cases, the error may occur due to the security of the Remote Desktop Protocol, in which case you need to change the security layer.
- The computer’s domain: another thing that can cause the error to occur can be the domain your system is connected to. In this case, removing the domain and rejoining fixes the problem.
Now, before you apply the solutions listed below, please make sure that you are using an administrator account. We also recommend that you follow the solutions given in the same order as indicated, so that you can isolate your problem quickly.
Solution 1: Change Remote Desktop Connection settings
To start with, we will try to isolate the problem by changing the RDP settings a bit. Some users have reported that their problem was fixed after checking the "Reconnect if the connection is dropped" checkbox. You can do this by following the steps given:
1.Go to Start menu, search for Remote Desktop Connection and open it.
2.Click Show Options to view all settings.
3.switch to the Experience tab and then make sure that the "Reconnect if the connection is dropped" checkbox is selected.
4. try to connect again.
Solution 2: Re-enter the domain
The error message is sometimes generated due to the domain you have connected your system to. In such cases, removing the domain and rejoining it will fix your problem. Here is how to do it:
1.Press the Windows key + I to open the settings.
2.Navigate to Accounts and then go to the Access Work or School tab.
3. Select the domain you have connected your system to, and then click Disconnect.
4.Click Yes when prompted for confirmation.
5. Disconnect the system and restart the computer when prompted.
6. after you reboot your system, you can join the domain again if you want to.
7. try again with RDP.
Solution 3: Change the MTU value
Another way to fix the problem is to change your MTU value. Maximum Transmission Unit is the largest size of a packet that can be sent on a network. Lowering the MTU value may help to fix the problem. Here’s how to do it:
1.To change your MTU value, you need to download a tool called TCP Optimizer. You can download it here.
2. after downloading TCP Optimizer, open it as administrator.
3. select Custom below before selecting Settings.
4. Change the MTU value to 1458.
5.Click Apply changes and then exit the program.
6. Check if this will fix the problem.
Solution 4: Change the security of RDP in the Group Policy Editor
In some cases, the error message is displayed due to your RDP security layer in Windows Group Policies. In such scenarios you need to force it to use the RDP security layer. Here is how to do it:
1. go to the Start menu, search for local group policies and open "Edit group policy.
2. navigate to the following directory: Computer Configuration> Administrative Templates> Windows Components> 4.Remote Desktop Services> Remote
3.Desktop Session Host> Security On the right side you will find the option ‘Use a specific
4.’Remote connection security layer (RDP) required’ and double-click it to edit it.
5. if set to ‘Not Configured’, select Enabled and then select RDP before security layer.
6. click Apply and then click OK.
7.Restart your system for the changes to take effect.
try to connect again.
Solution 5: Disable network level authentication
You can also try to fix your problem by disabling network-level authentication or NLA. The problem can sometimes occur if your or the target system is configured to allow only remote connections running Remote Desktop with NLA. Disabling it will fix the problem, here is how to do it:
1. Go to your desktop, right-click on this PC and select Properties.
2. Click on remote settings.
3.Under Remote Desktop, uncheck the "Allow connections only from computers running Remote