Fix: “An Internel Error Occurred” Connecting to RDP

The “Remote Desktop Connection: An Internal Error has Occurred” message while attempting to connect to a desktop or laptop through the Remote Desktop Connection, users typically experience an immediate disconnection attempt or failure to establish the remote connection entirely.

Fix- Remote Desktop Connection ‘An Internal Error has Occurred’
Fix- Remote Desktop Connection ‘An Internal Error has Occurred’

This error indicates a problem within the Remote Desktop Protocol (RDP) service, often due to misconfigurations or conflicting settings. The most common cause of this issue is a discrepancy in the Security layer settings between the client and the server.

Other potential causes include issues with the Remote Desktop service itself or network-related problems such as VPN conflicts or firewall restrictions.

Now that we know the details and causes of this particular issue, let’s proceed with resolving this error.

1. Change RDP Security Settings

Restrictive and incompatible group policy configurations can sometimes interfere with Remote Desktop connections.

Specifically, setting the “Require use of specific security layer for remote (RDP) connections” policy to Enabled and selecting RDP as the security layer mitigates conflicts that can arise from the default or improperly configured settings.

  1. Open the Group Policy Editor by pressing Windows key + R and typing gpedit.msc.
    Opening Run Window
    Opening Run Window
  2. Navigate to the following path:
    Computer Configuration -> Administrative Templates -> Windows Components -> Remote Desktop Services -> Remote Desktop Session Host -> Security
  3. Enable the policy “Require use of specific security layer for remote (RDP) connections” and set the Security Layer to RDP.
    Enabling RDP Security Layer Settings
    Enabling RDP Security Layer Settings
  4. Restart your computer, then try reconnecting to see if the error has been resolved.

2. Allow Remote Connections

If the ‘Allow Remote connection’ option is not enabled, Windows will block external connections as a security precaution. Enabling this option ensures that the system can accept remote desktop requests, which is often a necessary change to resolve related errors.

  1. Press the Windows key and type View Advanced System Settings.
    Opening Advance System Settings
    Opening Advance System Settings
  2. Hit Enter to open System Settings.
  3. Click on the Remote tab.
  4. Choose the option Allow Remote Connections to This Computer.
  5. Click Apply, then OK.
    Allowing Remote Connection
    Allowing Remote Connection
  6. Attempt a Remote Desktop connection to see if the error has been resolved.

3. Enable “Reconnect If Connection Drops” Option

The Remote Desktop Connection client includes an option that allows users to automatically reconnect upon an unexpected disconnection.

When this option is activated, the RDP client automatically attempts to re-establish a session without user intervention should the connection momentarily drop.

This could potentially bypass temporary network glitches that could otherwise result in an internal error notification.

  1. Press the Windows key and type Remote Desktop Connection.
  2. Click Show Options.
    Click Show Options
    Click Show Options
  3. Select the Experience tab and check Reconnect If the Connection Is Dropped.
    Enabling Reconnect If The Connection Is Dropped
    Enabling Reconnect If The Connection Is Dropped
  4. Try connecting to a Windows system to see if the issue has been resolved.

4. Delete MachineKeys

MachineKeys are important for creating secure communication channels between systems, such as when utilizing Remote Desktop.

If these keys become corrupted, the secure channel may fail to establish, prompting the internal error.

Removing the corrupt MachineKeys and forces the system to regenerate new, better ones, that may resolve the problem.

  1. Navigate to the following path using File Explorer:
    C:\ProgramData\Microsoft\Crypto\RSA\MachineKeys
  2. Right-click on the f686… file and select Delete.
    Deleting Machine Key File
    Deleting Machine Key File
  3. If an error occurs, access the file properties by right-clicking and selecting Properties.
  4. Go to the Security tab and click Advanced.
    Opening Advanced Folder Settings
    Opening Advanced Folder Settings
  5. Click Change and enter your local account username.
    Click Change
    Click Change
  6. Then click Check Names and select OK.
    Entering Microsoft Local Account Name
    Entering Microsoft Local Account Name
  7. Click Add, then Select A Principal.
    Clicking Add Button
    Clicking Add Button
  8. Type the username again, then click Check Names, followed by OK.
  9. Grant all permissions under Basic Permissions.
    Taking Full Access to the File
    Taking Full Access to the File
  10. Click OK, then Apply, and again OK.
  11. Select OK again to close the window.
  12. Attempt to delete the file once more to see if the error is resolved.

5. Restart Remote Desktop Service

The Remote Desktop Service is essential for all RDP related processes. If it’s not functioning correctly, it could cause the error.

Sometimes, this service might encounter issues or bugs that prevent it from operating correctly. Restarting the service can re-establish RDP connections that may resolve the problem.

  1. Press the Win key and type Services into the Start Menu.
    Opening Services App
    Opening Services App
  2. Open the Services window and locate Remote Desktop Services.
  3. Right-click the service and select Properties.
    Opening Service Properties
    Opening Service Properties
  4. Set the startup type to Automatic.
  5. Click Apply and, if the service is stopped, click the Start button.
    Restarting RDP Service
    Restarting RDP Service
  6. Check if restarting the service resolves the issue.

6. Disable VPN

VPN(s) modify your network routing, which can create conflicts or restrictions in connecting to remote systems. Therefore, you must disable your VPN if you want to connect to another computer through RDP succesfully.

  1. Press the Windows key, type Appwiz.CPL, and click OK.
    Opening Programs And Features
    Opening Programs And Features
  2. Select the VPN application and choose Uninstall.
    Uninstalling VPN Program
    Uninstalling VPN Program
  3. To deactivate the proxy, refer to the first method mentioned in this article.
  4. After completing these steps, verify if the issue has been resolved.
ABOUT THE AUTHOR

Kevin Arrows


Kevin Arrows is a highly experienced and knowledgeable technology specialist with over a decade of industry experience. He holds a Microsoft Certified Technology Specialist (MCTS) certification and has a deep passion for staying up-to-date on the latest tech developments. Kevin has written extensively on a wide range of tech-related topics, showcasing his expertise and knowledge in areas such as software development, cybersecurity, and cloud computing. His contributions to the tech field have been widely recognized and respected by his peers, and he is highly regarded for his ability to explain complex technical concepts in a clear and concise manner.

Comments

20
    DM
    Daniel Milisic Sep 23, 2019

    Solution 0:Run the Certificates MMC as Local Machine
    Find your Remote Desktop certificate
    Delete it
    Restart the Remote Desktop ServiceYou should advise readers disabling NLA is a bad idea, and doing so makes their machine less secure.Cheers,
    D.

    Reply
      MM
      Michael Maertzdorf Dec 6, 2019

      Under wich of the cert stores is this one located at?

      CS
      CHIDI UGOCHUKWU SAMUEL Apr 17, 2020

      This was helpful

      DL
      David Levin Jul 29, 2020

      This did the trick for me.

      EK
      Ekke Jun 2, 2021

      In my case, this was part of the problem. Thank you for pointing me in the correct direction.
      After deleting the RDP certificate, I also had file permission problems on the c:ProgramDataMicrosoftCryptoRSAMachineKeysf686aace…. file for some unknown reason.

      Event ViewerSystem gave this error: “The RD Session Host Server has failed to create a new self signed certificate to be used for RD Session Host Server authentication on SSL connections. The relevant status code was Object already exists.”

      After taking ownership and deleting the file, RDP recreated the certificate and all was fine again.

      Reply
    SW
    Shane Warren Author Sep 24, 2019

    Thank you for sharing your solution, the article will be edited shortly

    SD
    Snuff Daddy Dec 10, 2019

    Daniel Milisic is exactly right, I’ve had to do this twice over the years on a Win2008 server. If the error starts happening out of the blue, I’d bet dollars to donuts this is the cause. Here is a more detailed procedure:* Win+R : mmc.exe
    * Ctrl+M to add snap-in
    * choose “Certificates”, click “Add >”
    * Computer account, Local Computer
    * The self-signed certificate should be under Remote DesktopCertificates
    * delete all but one of the certificates that has the same expiration date, it is unknown if you can simply delete them all
    * possibly unnecessary: restart the Remote Desktop/Terminal Services service – and make sure it is set to auto-start

    Reply
    MG
    Michael Gauthier May 11, 2020

    I have two identical virtual machines at Godaddy that I connect to regularly. Tonight one connection worked consistently, the second failed every time with the internal error. This would suggest that the second machine might be at fault, however (as directed above) I opened the Show Options on the connection window and although the “reconnect…” was already checked, I tried to connect again and it worked. Go figure.

    JS
    Jordan Starks Jul 11, 2020

    In my case I had to change RDP security from Negotiate to RDP in Terminal Services. When left on Negotiate it was using TLS 1.0 which is not authorized for use.

    Reply
      SE
      Senthilkumar Jul 18, 2020

      Thanks much Jordan, your statement helped me to resolve the long pending issue for me 🙂 Changing the values of the “MinEncryptionLevel” in Regedit fixed my issue.
      HKEY_LOCAL_MACHINESystemCurrentControlSetControlTerminal ServerWinStationsRDP-TcpMinEncryptionLevel

      Reply
    LP
    Lukáš Pekař Jul 17, 2020

    Thank you. For me it was solution 5.

    Reply
    ᴅʀ
    ᴅʀᴀʏᴢᴇɴ Jul 21, 2020

    Thanks Kevin,
    Setting the RDP Security Layer fixed it for me.
    Very strange how this happened for no apparent reason when I’d not had any updates, go figure..

    Reply
    DL
    David Levin Aug 19, 2020

    Alternate Solution:
    Repeatedly click “Connect” when viewing your Remote Desktop Connection. Hint: You can use the enter key to close the error message.
    Repeat if unsuccessful up to 20 times. Eventually, I was able to get in without needing to change any other settings. Sometimes, the faster I click “connect” the higher my chance of getting in. Hope this works for others.This is clearly a major bug in Windows 10!

      SF
      Sabino Flores Sep 9, 2020

      so i do hahahaha

      MK
      Mohammed Khambaty Jan 25, 2021

      How did you fix this problem?

    SL
    Scott Landry Dec 10, 2020

    Y’all are most likely under attack via brute force.
    check your event viewer, you may notice a ton of audit failures.

    Use VPN to RDP and close external ports.

    Reply
    MK
    murat KIZIL Jan 21, 2021

    hi,

    “Server 2008 r2” was using more users and using less resources. Since Server 2012 (especially in 2016), the same number of RDP users started using more resources. In other words, we could not run as many users on the same server in 2016 server as before. What is your comment, solution on this issue?

    GM
    Gilton Mkumbwa Feb 22, 2021

    Solution number 4 worked for me thank you

    ᴅʀ
    ᴅʀᴀʏᴢᴇɴ Feb 28, 2021

    I was advised by my server host that the reason I was getting this error is something not listed above, and probably should be done by everyone using RDP to improve security.
    Change the default RDP Port.
    https://docs.microsoft.com/en-us/windows-server/remote/remote-desktop-services/clients/change-listening-port
    *** Make sure to create new TCP & UDP Firewall rules for your new port number before rebooting. You can look at the default ones for their configuration.

    Reply
    AR
    Artur Jun 2, 2021

    In my case this was a solution:
    Solution 4: Changing Security of RDP in Group Policy Editor
    And
    Solution 10: Allowing Remote Connections
    rdp works if I used both solutions at the same time
    THANK YOU 🙂

    Reply