How to Fix the “Internal Error Has Occurred” Remote Desktop Connection Error in Windows 10 & 11

Get back onto Remote Desktop with these fixes for the "internal error has occurred" issue.

Many users utilize the Remote Desktop Connection app included with Windows to connect with remote PCs. However, some users have reported a Remote Desktop Connection error message that says, “An internal error has occurred.” Consequently, they can’t connect to remote PCs with RDC when that error occurs.

This error means RDC’s Remote Desktop Protocol can’t establish a server connection with the remote PC selected. Does the “internal error has occurred” error message pop up when you try to connect to another computer with Remote Desktop Connection? If it does, this is how you can resolve that RDP issue in Windows 10 and 11.

First, check the basic settings required for remote connections are enabled. The Allow the remote connection setting needs to be enabled on the host computer (the remote one you’re trying to connect to). This is how you can select the Allow remote connection setting in Windows 10 and 11:

If you don’t see the Allow connections only from computers option, that probably means the Windows platform isn’t a Pro or Enterprise edition. You can only enable remote connections on host computers with Windows Pro and Enterprise. However, you can still connect to host PCs with Windows Home client PCs.

There’s an Allow connections only from computers running Remote Desktop with Network Level Authentication setting just below the Allow Remote connection radio button. Selecting that option implements tighter Network Layer Authentication security for remote connections. However, some users confirm that disabling NLA by unticking that checkbox can fix the “internal error has occurred” error. So, deselect that option if you’ve got it selected.

Remote Desktop Services is a service needed for connecting to remote PCs. So, it could be the case you need to fix the “internal error has occurred” error because that service isn’t enabled on your PC. This is how you can start the Remote Desktop Services in Windows 11/10:

Some Remote Desktop Connection users have confirmed that selecting a Reconnect if the connection is dropped setting in that app can resolve this error. That simple potential resolution is certainly worth a try. You can select that Reconnect setting like this:

If you’ve set a specific DNS server on your PC, change to an automatic DNS server instead. There could be an issue with the DNS server you’ve set. You can set an automatic DNS server like this:

Group Policy includes a Require use of specific security layer policy setting. Enabling an RDP security layer with that policy might fix the “internal error has occurred” error for some users. To do so, set the Require use of specific security layer policy setting as follows:

Users have also confirmed they fixed the “internal error has occurred” issue by enabling a Turn off UDP on Client policy setting. This is how you can enable that policy setting.

Is your PC connected with a domain (work or school) account? If so, that domain account could be causing the remote connection issue. Try disconnecting a domain account like this:

VPNs that route connections to different servers can also cause the “internal error has occurred” issue to arise. If you’re utilizing a VPN, at least try temporarily disabling it. This is how you can turn off a VPN in Settings:

Those potential fixes for the “internal error has occurred” issue will probably re-establish remote PC access in most cases. The issue is often caused by RDP security, network, or remote connection setting configurations that many of the above solutions will address. So, those potential resolutions are certainly worth a try.

Jack has been a freelance tech journalist for more than a decade. He has covered Windows Vista, 7, 10, and 11 topics within a multitude of guides for MakeUseOf and numerous other websites.