How do I fix remote desktop connection error?

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 wasnt 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

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:

1. Go to the Start Menu, search for Remote Desktop Connection, and open it up.
2. Click on Show Options to unveil all the settings.
3. Switch to the Experience tab and then make sure Reconnect if the connection is dropped box is checked.
   
   Changing RDP Settings
4. 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. Heres how to do it:

1. Press Windows Key + I to open Settings.
2. Navigate to Accounts and then switch to the Access work or school tab.
   
   Account Settings
3. Select the domain you have connected your system to and then click Disconnect.
4. Click Yes when prompted to confirm.
   
   Confirming to Remove Domain
5. Disconnect your system and then restart your computer as prompted.
6. Once you have restarted your system, you can join the domain again if you wish to.
7. 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. Heres how to do it:

1. To change your MTU value, you will have to download a tool called TCP Optimizer. You can download it from here.
2. Once downloaded, open up TCP Optimizer as an administrator.
3. At the bottom, select Custom in front of Choose settings.
4. Change the MTU value to 1458.
   
   Changing the MTU Size
5. Click Apply Changes and then exit the program.
6. 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. Heres how to do it:

1. Go to the Start Menu, search for Local Group Policy and open up Edit group policy.
2. Navigate to the following directory:
3. Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Security
4. On the right-hand side, locate the Require use of specific security layer for remote (RDP) connections and double-click it to edit it.
5. If it is set to Not configured, select Enabled and then in front of Security Layer, choose RDP.
   
   Editing RDP Security Policy
6. Click Apply and then hit OK.
7. Restart your system so that the changes take effect.
8. 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, heres 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, un-tick the Allow connections only from computers running Remote Desktop with Network Level Authentication box.
   
   Disabling Network Level Authentication
4. Click Apply and then hit OK.
5. 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:

1. Press Windows + R to open Run prompt.
2. Type in services.msc and press Enter.
   
   Running Services.msc
3. Double click on Remote Desktop Service and click on Stop.
   
4. Click on Start after waiting for at least 5 seconds.
5. Check to see if the issue persists.

Solution 7: Disable VPN Connection

It is possible that your computer might be configured to use a proxy or a VPN connection due to which its internet connection might be routed through another server and this might be preventing it from being able to properly establish a connection. Therefore in this step, we will be disabling the internet explorers proxy settings and you also have to make sure to disable any VPNs running on your computer.

1. Press Windows + R key on your keyboard simultaneously.
2. A run dialog box will appear on your screen, type MSConfig in the empty box, and press OK.
   
   msconfig
3. Select the boot option from the system configuration window and then check the Safe Boot option.
4. Click apply and press OK.
5. Restart your PC now to boot into the safe mode.
6. Again, press the same Windows + R keys simultaneously and type inetcpl.cpl in the Run dialog box and press Enter to execute it.
   
   Run inetcpl.cpl
7. An internet properties dialog box would appear on your screen, select the Connections tab from there.
8. Uncheck the Use a proxy server for your LAN box and then click OK.
   
   Disable the use of Proxy Servers
9. Open MSConfig again now and this time uncheck the safe boot option save your changes and restart your computer.
10. Check to see if the error message persists.

Solution 8: Reconfigure Local Security Policy

This is another way to fix the issue in which you should use the Local Security Policy utility. You can do it by proceeding with the following steps:

1. Press Windows + R to open the Run prompt.
2. Type in Secpol.msc and press Enter to launch the Local Security Policy Utility.
3. In the local security policy Utility, click on the Local Policies option, and then select the SecurityOption from the left pane.
   
   Navigate to Windows Settings > Security Settings > Local Policies > Security Options
4. In the right pane, scroll and click on the System Cryptography option and
5. In the right pane scroll to find the System cryptography: Use FIPS 140 compliant cryptographic algorithms, including encryption, hashing and signing algorithms option.
6. Double click on this option and then check the Enabled button on the next window.
   
   Clicking on the Enabled option
7. Click on Apply to save your changes and then on OK to close out of the window.
8. Check to see if doing so fixes the issue on your computer.

Solution 10: Allowing Remote Connections

It is possible that Remote Connections arent allowed on your computer according to some system configurations due to which this error is being shown while trying to use RDP. Therefore, in this step, we will be reconfiguring this setting from the Control Panel and then we will check to see if doing so fixes this issue on our computer. In order to do that:

1. Press Windows + R to launch the Run prompt.
2. Type in Control Panel and press Enter to launch the classical control panel interface.
   
   Accessing the Classic Control Panel interface
3. In the Control Panel, click on the System and Security option and then select the System button.
4. In the system settings, click on the Advanced System Settings from the left pane.
   
5. In the advanced system settings, click on the Remote tab and make sure that the Allow Remote Assistance Connections to this Computer option is checked.
6. In addition to that, make sure that the Allow Remote Connections to this Computer tab below it is also checked.
   
   Allow remote connections to this computer
7. Click on Apply to save your changes and then on OK to exit out of the window.
8. Check to see if doing so fixes this issue on your computer.

Solution 11: Changing the Startup of Service

It is possible that the Remote Desktop service has been configured in such a way that it isnt allowed to start up automatically. Therefore, in this step, we will be changing this configuration and we will allow the service to be started automatically. In order to do this, follow the guide below.

1. Press Windows + R to launch the Run prompt.
2. Type in Services.msc and press Enter to launch the service management window.
   
   Run dialog: services.msc
3. In the service management window, double click on the Remote Desktop Services option and then click on the Stop button.
4. Click on the Startup Type option and select the Automatic option.
   
   Selecting Automatic in the Startup type
5. Closeout of this window and return to the desktop.
6. After doing so, restart your computer and check to see if the issue persists.

Solution 12: Enable Persistent Bitmap Caching

Another possible reason behind the occurrence of this issue is the Persistent Bitmap Caching feature being disabled from the RDP settings. Therefore, in this step, we will launch the Remote Desktop Connections app and then change this setting from its experience panel. In order to do this, follow the guide below.

1. Press Windows + S on your keyboard and type in Remote Desktop Connection in the search bar.
   
   Typing in Remote Desktop Connections in the search bar
2. Click on the Show Options button and then click on the Experience tab.
3. In the experience tab, check the Persistent Bitmap Caching option and save your changes.
4. Try to make the Remote Desktop connection and then check to see if the issue still persists.

Solution 13: Disabling Static IP on Computer

It is possible that this issue is being triggered on your computer because you have configured your network adapter to use a static IP and it is not aligning with the Remote Desktop Connection properly. Therefore, in this step, we will be disabling the Static IP on our computer through the network configuration settings and then check if the issue is fixed by doing so. For that:

1. Press Windows + R to launch the Run prompt.
2. Type in ncpa.cpl and press Enter to launch the network configuration panel.
   
   Run this in the Run dialog box
3. In the network configuration panel, right-click on your network adapter and select Properties.
4. Double-click on the Internet Protocol Version 4 (TCP/IPV4) option and then click on the General tab.
   
   Accessing the Internet Protocol Version 4 settings
5. Check the Obtain IP Address automatically option and save your changes.
6. Click on OK to exit out of the window and check to see if the issue still persists.

Solution 14: Reconfiguring SonicWall VPN

If you are using the SonicWall VPN client on your computer and are using the default configurations with that application, this error might spring up while trying to use the Remote Desktop Connection application. Therefore, in this step, we will be changing some settings from within the VPN. For that:

1. Launch Sonicwall on your computer.
2. Click on VPN and then select the Settings option.
3. Look for WAN under the VPN policies list.
4. Click on the Configure option to the right and then select the Client tab.
5. Click on the Virtual Adapter Settings dropdown and select the DHCP Lease option.
   
   Selecting the option from the dropdown
6. Check to see if doing so fixes the issue.
7. If this issue still isnt fixed, we will have to remove the current DHCP lease from the VPN.
8. Navigate to the VPN option and then select the DHCP overVPN button.
9. Delete the already existing DHCP lease and restart the connection
10. Check to see if the issue persists after doing this.

Solution 15: Diagnosing Connection through Command Prompt

It is possible that the computer that you are trying to connect to using the Remote Desktop Connection might not be available for connection due to which this issue is being triggered. Therefore, we will have to diagnose whether the computer is available for connection or not.

For this purpose, we will be using the command prompt to first identify the IP address of the computer and then we will use the command prompt on our computer to try and ping it. If the ping is successful, the connection can be made, if it isnt that means that the computer that you are trying to connect to is at fault and not your settings. For this purpose:

1. Gain access to the computer you want to connect to locally and press the Windows + R keys on its keyboard to launch the run prompt.
2. Type in Cmd and press Enter to launch the command prompt.
   
   Type cmd into the Run dialog
3. In the command prompt, type in the following command and press Enter to display the IP information for the computer.
4. Note the IP address listed under the Default Gateway heading which should be in the 192.xxx.x.xx or a similar format.
   
   The Default Gateway listed in the results
5. Once you have acquired the IP address of the computer that you are trying to connect to, you can come back to your own computer for further testing.
6. On your personal computer, press Windows + R to launch the Run prompt and type in Cmd to open the command prompt.
7. Type in the following command in the command prompt and press enter to execute it.
   ping (IP ADDRESS of the computer that we want to connect to)
8. Wait for the command prompt to finish the pinging of the IP address and note down the results.
9. If the ping is successful, it means that the IP address is accessible.
10. Now we will be testing the telnet capability of the computer by checking if telnet is possible over the IP address.
11. For that, press Windows + R and type in Cmd to open the command prompt.
12. Type in the following command to check if telnet is possible on the port which is required to be open by the RDP client.telnet <IP address> 3389
13. You should be seeing a black screen if this telnet is successful, if it isnt it means that the port is being blocked on your computer.

If the black screen isnt returned, it means that the port might not be opened on your computer due to which this issue is being shown while trying to telnet on the port. Therefore, in this step, we will be reconfiguring the Windows Firewall to open the specific port on our computer. For that:

1. Press Windows + I to open settings and click on Update & Security.
   
   Selecting the Update & Security Option
2. Select the Windows Security tab from the left pane and click on the Firewall and Network Security option.
   
   Accessing the Firewall & network protection settings
3. Select the Advanced Settings button from the list.
4. A new window will open up, Click on the Inbound Rules option, and select New Rule.
   
   Clicking on Inbound Rule and select New Rule
5. Select Port and click on Next.
   
   Selecting Port and clicking on Next
6. Click on TCP and select the Specified Local Ports option.
   
   Clicking on TCP and checking the Specified Local Ports option
7. Enter in 3389 into the port number.
8. Click on Next and select Allow the Connection.
   
   Selecting the Allow the connection option
9. Select Next and make sure all three options are checked.
   
   Checking All options
10. Again, click on Next and write a Name for the new rule.
11. Select Next after writing a name and click on Finish.
12. Similarly, go back to the 4th step that we have listed and select Outbound Rules this time and repeat the whole process to create an Outbound Rule for this process as well.
13. After creating both an inbound and an Outbound rule, check to see if the issue persists.

Solution 16: Turn off UDP on Client

It is possible to fix this issue by simply changing a setting inside the registry or from the group policy. If you are using Windows Home version, you can try going about this solution using the registry method, and otherwise, you can implement the group policy method from the guide below.

Registry Method:

1. Press Windows + R to launch the run prompt.
2. Type in regedit and press Enter to launch the Registry.
   
   regedit.exe
3. Inside the registry, navigate through the following options.HKLM\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services\Client
4. Inside this folder, set the fClientDisableUDP option to 1.
5. Save your changes and exit out of the registry.
6. Check to see if adding this value to the registry fixes this issue on your computer.

Group Policy Method

1. Press Windows + R buttons on your keyboard to launch the run prompt.
2. Type in Gpedit.msc and press Enter to launch the Group Policy Manager.
   
   Type gpedit.msc into the Run dialog and press Enter
3. In the Group Policy Manager, double click on the Computer Configuration option and then open the Administrative Templates option.
4. Double click on Windows Components and then double click on the Remote Desktop Services option.
5. Double click on the Remote Desktop Connection Client and then double click on the Turn off UDP on Client option.
6. Check the Enabled button and save your changes.
   
   Checking the Enabled option
7. Exit out of the Group Policy manager and then check to see if the issue persists.

Using PowerShell Command

If for some reason you are unable to add the registry value as indicated above, we can also implement this change using the Windows Powershell utility. For that purpose:

1. Press Windows + X on your keyboard and select the Powershell (Admin) option.
   
   Running PowerShell as an administrator
2. Type in the following command inside the PowerShell window and press Enter to execute it.New-ItemProperty 'HKLM:\SOFTWARE\Microsoft\Terminal Server Client' -Name UseURCP -PropertyType DWord -Value 0
3. After the command is executed on your computer, check to see if the issue still persists.

Final Solution:

Most people that were facing this issue noticed that it arises after a recent Windows Update. According to our sources, the issue is caused if either your Remote client or your Windows itself has been updated to the 1809 version of Windows. Therefore, as a final solution, it is recommended to go back to the previous version of Windows or wait for a more stable version of the operating system to be released.