How to Fix the “Internal Error Has Occurred” Remote Desktop Connection Error in Windows 10 & 11
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.
1. Select the “Allow Remote Connections” Setting
First, check the basic settings required for remote connections are enabled. TheAllow the remote connectionsetting needs to be enabled on the host computer (the remote one you’re trying to connect to). This is how you can select theAllow remote connectionsetting in Windows 10 and 11:
If you don’t see theAllow connections only from computersoption, 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.
2. Disable Network Layer Authentication
There’s anAllow connections only from computers running Remote Desktop with Network Level Authenticationsetting just below theAllow Remote connectionradio 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.
3. Start or Restart the Remote Desktop Connection Service
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:
4. Select the “Reconnect if the Connection Is Dropped” Setting
Some Remote Desktop Connection users have confirmed that selecting aReconnect if the connection is droppedsetting in that app can resolve this error. That simple potential resolution is certainly worth a try. you may select thatReconnectsetting like this:
5. Set an Automatic DNS Server
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:
6. Enable the “Require Use of Specific Security Layer” Group Policy Setting
Group Policy includes aRequire use of specific security layer policysetting. Enabling an RDP security layer with that policy might fix the “internal error has occurred” error for some users. To do so, set theRequire use of specific security layerpolicy setting as follows:
7. Turn Off UDP on the Client via Group Policy
Users have also confirmed they fixed the “internal error has occurred” issue by enabling aTurn off UDPon Clientpolicy setting. This is how you’re able to enable that policy setting.
8. Disconnect a Domain Account
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:
9. Turn Off Any Active VPNs
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:
Re-establish Remote PC Access on Windows
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.
Can’t connect remotely to your Windows PC? Are you encountering the 0x104 error? Here’s how to solve it.
Not Linux, not Windows. Something better.
My foolproof plan is to use Windows 10 until 2030, with the latest security updates.
Every squeak is your PC’s way of crying for help.
This small feature makes a massive difference.
Anyone with more than a passing interest in motorsports must see these films.
