Save 10%Pay yearly on any plan. 6% half-yearly, 3% quarterly. Help centreWhatsAppTelegram TeamsOpen a ticket

Fix: 'An Internal Error Has Occurred' in Remote Desktop Connection

The Remote Desktop message "An internal error has occurred" has several causes. Seven fixes, from the simplest on your PC to the settings on the server.

3 min readBy Daniel

Reviewed by the AmazingRDP technical team

Fixing the Remote Desktop internal error

A remote desktop with support that answers. See our RDP plans. See Cheap RDP from $4.99

"An internal error has occurred" is one of the least helpful messages Remote Desktop has. It means the client and the server began to talk and could not agree on how to continue; it does not say why. The causes fall into three groups: something on your PC, something on the path between, and something on the server. Work from the top; the early fixes are quick.

1. Rule out the simple things

  • Check the address and port. If your provider gave you an address with a port, such as 203.0.113.10:4489, the port must be typed with it. A wrong port on a machine that answers gives exactly this error.
  • Try again in a minute. A server that is restarting or installing updates answers like this for a short while.
  • Try another network, for example your phone's hotspot. If it works there, the cause is on your network or VPN.
  • Try another client, for example the Remote Desktop app on your phone. If that connects, the cause is on your PC.

2. Change two client settings

  1. Start Remote Desktop Connection and click Show Options.
  2. On the Experience tab, untick Persistent bitmap caching and Reconnect if the connection is dropped.
  3. On the Advanced tab, set If server authentication fails to Connect and don't warn me for this test.
  4. Connect.

If you connect through a saved .rdp file, test once without it; a damaged file causes the same message.

3. Switch off UDP on the client

Remote Desktop tries a faster UDP connection beside the normal one. Some routers and VPNs break it, and the session fails or drops. Tell the client to use TCP only. In a Command Prompt as administrator on your PC:

reg add "HKLM\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services\Client" /v fClientDisableUDP /t REG_DWORD /d 1 /f

Restart the PC and try again. To undo it, run the same line with /d 0.

4. Leave the VPN, or fix its packet size

Through a VPN, large packets are sometimes dropped silently. Test without the VPN. If that cures it, lower the VPN's MTU setting, or keep UDP off as in fix 3.

5. On the server: restart Remote Desktop Services

The following fixes need administrator rights on the server and a way in that is not Remote Desktop: the console in your provider's control panel. In PowerShell as administrator:

Restart-Service TermService -Force

This ends all Remote Desktop sessions on the server and clears a stuck service.

6. On the server: renew the Remote Desktop certificate

The server identifies itself with a certificate it created for itself. If that is damaged or its private key is unreadable, connections fail with the internal error.

  1. Press Win + R, run certlm.msc.
  2. Open Remote Desktop, Certificates.
  3. Delete the certificate named after the server.
  4. Restart the service as in fix 5. Windows creates a new certificate.

The first connection afterwards shows a certificate warning, because the certificate is new. That is expected.

7. On the server: set the security layer

  1. Run gpedit.msc.
  2. Go to Computer Configuration, Administrative Templates, Windows Components, Remote Desktop Services, Remote Desktop Session Host, Security.
  3. Open Require use of specific security layer for remote (RDP) connections, choose Enabled, and set the layer to Negotiate. If the error stays, try RDP as a test.
  4. Run gpupdate /force and restart the service.

The RDP layer is the old, weaker one. It is useful to find the cause; if only it works, the real problem is the certificate or TLS settings on the server, and those should be repaired.

Also worth checking on the server

CauseSign and fix
Many failed logins from the internetThe Security log is full of event 4625. Bots guessing passwords can exhaust the service. Limit the port to your addresses or change it: see RDP on a different port and securing RDP
Updates half installedFinish them and restart
Memory or disk fullThe server cannot create a session. Free space; check Task Manager
Very old client or serverThey share no common encryption any more. Update the older side

On a shared remote desktop

You have no access to the server's settings, and you do not need it: do fixes 1 to 4. If the error stays, the cause is on the server side. Open a ticket and say what you tried and from which network; that saves a round of questions.

Related: how to connect to RDP and what Remote Desktop can do. Our RDP plans come with support for exactly this kind of problem.

Questions

What causes 'An internal error has occurred' in Remote Desktop?

A wrong port, a blocked UDP connection, a VPN, a damaged server certificate, a stuck Remote Desktop service or mismatched security settings.

How do I fix the RDP internal error quickly?

Check the address and port, test from another network, untick bitmap caching and reconnect in the client, and switch off UDP on the client.

How do I restart Remote Desktop Services?

On the server, run Restart-Service TermService -Force in PowerShell as administrator.

What if I cannot access the server settings?

On a shared remote desktop, do the client-side fixes and then open a ticket with your provider.