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.
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 explorer’s proxy settings and you also have to make sure to disable any VPNs running on your computer.
- Press Windows + R key on your keyboard simultaneously.
- A run dialog box will appear on your screen, type “MSConfig” in the empty box, and press OK.
- Select the boot option from the system configuration window and then check the “Safe Boot” option.
- Click apply and press OK.
- Restart your PC now to boot into the safe mode.
- Again, press the same “Windows” + “R” keys simultaneously and type “inetcpl.cpl” in the Run dialog box and press “Enter” to execute it.
- An internet properties dialog box would appear on your screen, select the “Connections” tab from there.
- Uncheck the “Use a proxy server for your LAN” box and then click OK.
- Open MSConfig again now and this time uncheck the safe boot option save your changes and restart your computer.
- 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:
- Press “Windows” + “R” to open the Run prompt.
- Type in “Secpol.msc” and press “Enter” to launch the Local Security Policy Utility.
- In the local security policy Utility, click on the “Local Policies” option, and then select the “Security Option” from the left pane.
- In the right pane, scroll and click on the “System Cryptography” option and
- In the right pane scroll to find the “System cryptography: Use FIPS 140 compliant cryptographic algorithms, including encryption, hashing and signing algorithms” option.
- Double click on this option and then check the “Enabled” button on the next window.
- Click on “Apply” to save your changes and then on “OK” to close out of the window.
- Check to see if doing so fixes the issue on your computer.
Solution 10: Allowing Remote Connections
It is possible that Remote Connections aren’t 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:
- Press “Windows” + “R” to launch the Run prompt.
- Type in “Control Panel” and press “Enter” to launch the classical control panel interface.
- In the Control Panel, click on the “System and Security” option and then select the “System” button.
- In the system settings, click on the “Advanced System Settings” from the left pane.
- 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.
- In addition to that, make sure that the “Allow Remote Connections to this Computer” tab below it is also checked.
- Click on “Apply” to save your changes and then on “OK” to exit out of the window.
- 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 isn’t 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.
- Press “Windows” + “R” to launch the Run prompt.
- Type in “Services.msc” and press “Enter” to launch the service management window.
- In the service management window, double click on the “Remote Desktop Services” option and then click on the “Stop” button.
- Click on the “Startup Type” option and select the “Automatic” option.
- Closeout of this window and return to the desktop.
- 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.
- Press “Windows” + “S” on your keyboard and type in “Remote Desktop Connection” in the search bar.
- Click on the “Show Options” button and then click on the “Experience” tab.
- In the experience tab, check the “Persistent Bitmap Caching” option and save your changes.
- 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:
- Press “Windows” + “R” to launch the Run prompt.
- Type in “ncpa.cpl” and press “Enter” to launch the network configuration panel.
- In the network configuration panel, right-click on your network adapter and select “Properties”.
- Double-click on the “Internet Protocol Version 4 (TCP/IPV4)” option and then click on the “General” tab.
- Check the “Obtain IP Address automatically” option and save your changes.
- 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:
- Launch Sonicwall on your computer.
- Click on “VPN” and then select the “Settings” option.
- Look for “WAN” under the VPN policies list.
- Click on the “Configure” option to the right and then select the “Client” tab.
- Click on the “Virtual Adapter Settings” dropdown and select the “DHCP Lease” option.
- Check to see if doing so fixes the issue.
- If this issue still isn’t fixed, we will have to remove the current DHCP lease from the VPN.
- Navigate to the “VPN” option and then select the “DHCP over VPN” button.
- Delete the already existing DHCP lease and restart the connection
- 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 isn’t that means that the computer that you are trying to connect to is at fault and not your settings. For this purpose:
- 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.
- Type in “Cmd” and press “Enter” to launch the command prompt.
- In the command prompt, type in the following command and press “Enter” to display the IP information for the computer.
- Note the IP address listed under the “Default Gateway” heading which should be in the “192.xxx.x.xx” or a similar format.
- 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.
- On your personal computer, press “Windows” + “R” to launch the Run prompt and type in “Cmd” to open the command prompt.
- 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)
- Wait for the command prompt to finish the pinging of the IP address and note down the results.
- If the ping is successful, it means that the IP address is accessible.
- Now we will be testing the “telnet” capability of the computer by checking if telnet is possible over the IP address.
- For that, press “Windows” + “R” and type in “Cmd” to open the command prompt.
- 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
- You should be seeing a black screen if this telnet is successful, if it isn’t it means that the port is being blocked on your computer.
If the black screen isn’t 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:
- Press “Windows” + “I” to open settings and click on “Update & Security”.
- Select the “Windows Security” tab from the left pane and click on the “Firewall and Network Security” option.
- Select the “Advanced Settings” button from the list.
- A new window will open up, Click on the “Inbound Rules” option, and select “New Rule“.
- Select “Port” and click on “Next”.
- Click on “TCP” and select the “Specified Local Ports” option.
- Enter in “3389” into the port number.
- Click on “Next” and select “Allow the Connection“.
- Select “Next” and make sure all three options are checked.
- Again, click on “Next” and write a “Name” for the new rule.
- Select “Next” after writing a name and click on “Finish“.
- 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.
- 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.
- Press “Windows” + “R” to launch the run prompt.
- Type in “regedit” and press “Enter” to launch the Registry.
- Inside the registry, navigate through the following options.
HKLM\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services\Client
- Inside this folder, set the fClientDisableUDP option to “1”.
- Save your changes and exit out of the registry.
- Check to see if adding this value to the registry fixes this issue on your computer.
Group Policy Method
- Press “Windows” + “R” buttons on your keyboard to launch the run prompt.
- Type in “Gpedit.msc” and press “Enter” to launch the Group Policy Manager.
- In the Group Policy Manager, double click on the “Computer Configuration” option and then open the “Administrative Templates” option.
- Double click on “Windows Components” and then double click on the “Remote Desktop Services” option.
- Double click on the “Remote Desktop Connection Client” and then double click on the “Turn off UDP on Client” option.
- Check the “Enabled” button and save your changes.
- 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:
- Press “Windows” + “X” on your keyboard and select the “Powershell (Admin)” option.
- 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
- After the command is executed on your computer, check to see if the issue still persists.
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.