Strategies to Counteract Internal Error with Remote Desktop

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 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 theAllow remote connection setting in Windows 10 and 11:

1. Click the search box or button (the magnifying glass icon) that’s on the Windows taskbar.
2. Typeadvanced system settings inside the search box.
3. SelectView advanced system settings to bring a System Properties window.
4. Click the System Properties window’sRemote tab.
5. Enable remote assistance by selecting theAllow Remote Assistance checkbox.
6. Select theAllow Remote connections to this computer radio button if that feature is not enabled.
   
7. ClickApply andOK to save the new remote connection settings.

If you don’t see theAllow 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.

2. Disable Network Layer Authentication

There’s an Allow connections only from computers running Remote Desktop with Network Level Authentication setting just below theAllow 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.

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:

1. Open the search utility for finding files and apps in Windows 11/10.
2. EnterServices within Windows’ search box and select to open that app from there.
3. Double-clickRemote Desktop Services to access some configuration settings for that service.
   
4. If disabled, selectAutomatic on theStartup drop-down menu for Remote Desktop Services.
5. ClickStart (inside the properties window) to run Remote Desktop Services.
   
6. SelectApply to set the new service options.
7. Then you can exit the window by clickingOK orX .
8. If Remote Desktop Services is already running, you can try restarting it instead. Right-clickRemote Desktop Services to view its context menu and selectRestart from there.

Click here

Some Remote Desktop Connection users have confirmed that selecting aReconnect 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 thatReconnect setting like this:

1. Start the RDC app with a method in our how-to open Remote Desktop Connection guide .
2. ClickShow Options to view RDC’s settings.
   
3. Select theExperience tab.
   
4. Then select theReconnect if the connection is dropped checkbox.
5. Press theConnect button.

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:

1. Open Run (press theWin + R hotkey or see how to open Windows Run ) and enterncpa.cpl in that command box.
2. ClickOK to view the Network Connections applet.
3. Right-click the internet connection to select itsProperties context menu option.
   OtsAV Radio Webcaster
4. SelectInternet Protocol Version 4 and clickProperties .
5. Then clickObtain DNS server automatically radio button.
   Glarysoft File Recovery Pro Annually - Helps to recover your lost file/data, even permanently deleted data.
6. Also, clickObtain an IP address automatically if that option isn’t selected.
7. SelectOK to confirm the new DNS and IP address settings.

6. Enable the “Require Use of Specific Security Layer” Group Policy Setting

Group Policy includes aRequire 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 theRequire use of specific security layer policy setting as follows:

1. Open Local Group Policy Editor with a method in our guide on how to launch gpedit.msc guide. If you’re using Windows Home, be sure to check out how to access Group Policy Editor on Windows Home first.
2. Next, you’ll need to double-clickComputer Configuration >Administrative Templates in the Group Policy’s sidebar.
3. Double-clickWindows Components >Remote Desktop Services >Remote Desktop Session Host in the console tree.
4. ClickSecurity to view its policy settings.
5. Double-click the Require use of specific security layer for remote (RDP) connections policy.
   
6. Select theEnabled radio button for that policy.
7. ChooseRDP in theSecurity Layer drop-down menu.
   
8. ClickApply >OK inside theRequire use of specific security layer for remote (RDP) connections policy window.
9. Restart Windows and then open the Remote Desktop Connection app to check if that fixes the issue.

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 UDP on Client policy setting. This is how you can enable that policy setting.

1. Start Group Policy Editor and go to this policy setting location:
   Computer Configuration\Admin Templates\Windows Components\Remote Desktop Services\Remote Desktop Connection Client
2. Then double-clickTurn off UDP on Client on the right side of Group Policy Editor.
   
3. Select that policy’sEnabled option.
   
4. ClickApply to set the newTurn off UDP on Client policy.
5. SelectOK in theTurn off UDP on Client window and exit Group Policy Editor.

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:

1. PressWin + I to open Settings.
2. Then select theAccounts tab or category.
3. ClickAccess work or school to view connected domain accounts.
   
4. SelectDisconnect for a domain account.
5. Press your Start menu’sRestart button.
6. Then try connecting to the remote computer with RDC again.

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:

1. Open the Windows Settings app to selectNetwork & internet .
2. Click theVPN navigation option or tab.
   
3. Select your VPN’sDisconnect option.
   
   EmEditor is a fast, lightweight, yet extensible, easy-to-use text editor, code editor, CSV editor, and large file viewer for Windows. Both native 64-bit and 32-bit builds are available, and moreover, the 64-bit includes separate builds for SSE2 (128-bit), AVX-2 (256-bit), and AVX-512 (512-bit) instruction sets. New versions support AI-assisted writing.

PearlMountain Image Converter

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.