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. Show
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 SettingsTo 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:
Solution 2: Rejoining DomainThe 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:
Solution 3: Changing MTU ValueAnother 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:
Solution 4: Changing Security of RDP in Group Policy EditorIn 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:
Solution 5: Disabling Network Level AuthenticationYou 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:
Solution 6: Restarting Remote Desktop ServiceIn some cases, restarting the Remote Desktop Service does the trick, therefore, in this step, we will be manually restarting it. For that:
Solution 7: Disable VPN ConnectionIt 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.
Solution 8: Reconfigure Local Security PolicyThis 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:
Solution 10: Allowing Remote ConnectionsIt 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:
Solution 11: Changing the Startup of ServiceIt 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.
Solution 12: Enable Persistent Bitmap CachingAnother 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.
Solution 13: Disabling Static IP on ComputerIt 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:
Solution 14: Reconfiguring SonicWall VPNIf 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:
Solution 15: Diagnosing Connection through Command PromptIt 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:
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:
Solution 16: Turn off UDP on ClientIt 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:
Group Policy Method
Using PowerShell CommandIf 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:
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. |