Windows OS Hub
  • Windows Server
    • Windows Server 2016
    • Windows Server 2012 R2
    • Windows Server 2012
    • Windows Server 2008 R2
    • SCCM
  • Active Directory
    • Group Policies
  • Windows Clients
    • Windows 10
    • Windows 8
    • Windows 7
    • MS Office
    • Outlook
  • Virtualization
    • VMWare
    • Hyper-V
  • PowerShell
  • Exchange
  • Home
  • About

Windows OS Hub

  • Windows Server
    • Windows Server 2016
    • Windows Server 2012 R2
    • Windows Server 2012
    • Windows Server 2008 R2
    • SCCM
  • Active Directory
    • Group Policies
  • Windows Clients
    • Windows 10
    • Windows 8
    • Windows 7
    • MS Office
    • Outlook
  • Virtualization
    • VMWare
    • Hyper-V
  • PowerShell
  • Exchange

 Windows OS Hub / Windows 10 / An Internal Error has Occurred: Remote Desktop Connection Error

May 13, 2020 Windows 10Windows Server 2012 R2

An Internal Error has Occurred: Remote Desktop Connection Error

I saw a strange message “An internal error has occurred” when trying to connect from Windows 10 to a recently deployed RDSH server running Windows Server 2012 R2 using RDP. As lately as yesterday, the Remote Desktop connection to the server worked fine, but after the installation and configuration of RemoteApps and server restart, I was not able to connect to its desktop. Obviously, the Remote Desktop Services seems to be working, since a user is prompted for a password when connecting.

As I have understood, the RDP console message “An internal error has occurred” may appear in different cases and be caused by both Remote Desktop server and client issues. In this article I tried to describe all the ways to solve the problem and the scenario that had helped me.

windows 10 remote desktop connection error An internal error has occurred

First of all, make sure that the RDP port 3389 accepts connection on your RDS server, and that the connection is not blocked by the firewall (Test-NetConnection your_rdp_server –port 3389).

Having studied the RDP connection logs on the RDS server, I did not see any errors. The Microsoft-Windows-RemoteDesktopServices-RdpCoreTS/Operational log showed that the RDP session was created:

The server accepted a new TCP connection from client 192.168.1.60:64379.
Connection RDP-Tcp#4 created

However, the RDP session was terminated later without any error:

The server has terminated main RDP connection with the client.
The disconnect reason is 0

The server has terminated main RDP connection with the client: Microsoft-Windows-RemoteDesktopServices-RdpCoreTS

Check the status of the Remote Desktop Services on your remote server and restart the service. You can do it remotely through the Services.msc console (use the “Connect to another computer” option), but it is easier to check a service status and restart it using PowerShell:

(Get-Service TermService -ComputerName ny-rds1).status

The service is running, let’s restart it:

Get-Service TermService -ComputerName ny-rds1| Restart-Service –force –verbose

restart TermService powershell

But this did not solve the problem.

Here are some other ways to solve it I have managed to find in the Web:

  • If you see the EventID 1057 in the TerminalServices-RemoteConnectionManager event log (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), go to the folder C:\ProgramData\Microsoft\Crypto\RSA, rename the Machinekeys folder into Machinekeys_bak and restart the TermService;
  • I have also found that the RDP problem “An internal error has occurred” happened in Windows 10 1809 if the Configure H.264/AVC hardware encoding for Remote Desktop connections policy is enabled on the remote computer (it is located in the following GPO section: Computer Configuration -> Administrative Templates -> Windows Components -> Remote Desktop Services -> Remote Desktop Session Host -> Remote Session Environment). To solve the problem, you just need to disable the UDP protocol for RDP by creating the fClientDisableUDP parameter with the value 1 in the registry key HKLM\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services\Client;
  • If the error appears immediately after clicking connect (the connection attempt seem to be immediately rejected by remote desktop server), try to increase the maximum outstanding RDP connections limit. On Windows 10 the SKUs by default is set to 100, but on Windows Server is 3000. Run the regedit.exe and create the DWORD registry parameter MaxOutstandingConnections with the value 10000 in the reg key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\. (The special RDP counter takes into account not quite correct RDP logins, and upon reaching the specified MaxOutstandingConnections value, the RDP access is blocked.)

Neither of the scenarios described above was applicable in my case. Occasionally, I found that other computers did not experience any problems when connecting to this RDS server. It meant that there was an issue with my computer, not with the Remote Desktop server.

I cleared the RDP connection history in the registry key HKEY_CURRENT_USER\Software\Microsoft\Terminal Server Client\Servers and reset the RDP cache in C:\Users\%Username%\AppData\Local\Microsoft\Terminal Server Client\Cache (prior to doing it, close all running mstsc.exe sessions):

del "C:\Users\%Username%\AppData\Local\Microsoft\Terminal Server Client\cache"

clean rdp cache cmd

Then I restarted my computer, and the RDP connection error disappeared!

5 comments
4
Facebook Twitter Google + Pinterest
previous post
How to Refresh AD Groups Membership without Reboot/Logoff?
next post
Configuring Windows Firewall Rules with PowerShell

Related Reading

How to Disable NetBIOS and LLMNR Protocols in...

April 9, 2021

Enable Windows Lock Screen after Inactivity via GPO

April 8, 2021

Can’t Copy and Paste via Remote Desktop (RDP)...

March 31, 2021

UAC: This App Has Been Blocked for Your...

March 30, 2021

How to Unlock a File Locked by Any...

March 29, 2021

5 comments

Serg May 13, 2020 - 10:13 am

I have this error then perform RDP connect frow Win10 to Win7. The problem is RD client from Windows 10 automatic use TLS 1.2 (default Security Protocol) negotiation, but Windows 7 only support TLS 1.0

Reply
infofree May 15, 2020 - 12:41 am

google is your friend., its not only 10>7 its old 7 to Updated 7, its also Digital Key Checking, the solution is out there if you look for it. use your Event ID from the log,and the error message you get and the OS vers

Reply
infofree May 15, 2020 - 12:42 am

Its actually an added FEATURE, not a BUG, thru updates to 7,it also broke the same thing, Admins had a nightmare if they didn’t have remote patch and Updates capable enterprise wide. 1 user fixing it on 1 station is EASY.

Reply
Den June 5, 2020 - 11:43 am

The following was help for me to fix this rdp bug:
Run the Certificates MMC as Local Machine -> find your Remote Desktop certificate -> Delete it -> and restart Remote Desktop Service (TermService )

Reply
Terry Grigg July 15, 2020 - 2:13 am

I found running the remote connection as administrator I could connect

Reply

Leave a Comment Cancel Reply

Categories

  • Active Directory
  • Group Policies
  • Exchange
  • Windows 10
  • Windows 8
  • Windows 7
  • Windows Server 2016
  • Windows Server 2012 R2
  • Windows Server 2008 R2
  • PowerShell
  • VMWare
  • MS Office

Recent Posts

  • How to Disable NetBIOS and LLMNR Protocols in Windows Using GPO?

    April 9, 2021
  • Enable Windows Lock Screen after Inactivity via GPO

    April 8, 2021
  • How to Create and Manage Scheduled Tasks with PowerShell?

    April 7, 2021
  • Updating Windows VM Templates on VMWare with PowerShell

    April 5, 2021
  • Running Multiple IIS Websites on the Same Port or IP Address

    April 1, 2021
  • Can’t Copy and Paste via Remote Desktop (RDP) Clipboard

    March 31, 2021
  • UAC: This App Has Been Blocked for Your Protection on Windows 10

    March 30, 2021
  • How to Unlock a File Locked by Any Process or SYSTEM?

    March 29, 2021
  • Configuring a Domain Password Policy in the Active Directory

    March 26, 2021
  • Using Native Package Manager (WinGet) on Windows 10

    March 24, 2021

Follow us

woshub.com
  • Facebook
  • Twitter
  • RSS
Popular Posts
  • How to Allow Multiple RDP Sessions in Windows 10?
  • How to Repair EFI/GPT Bootloader on Windows 10?
  • How to Restore Deleted EFI System Partition in Windows 10?
  • Network Computers are not Showing Up in Windows 10
  • How to Run Program without Admin Privileges and to Bypass UAC Prompt?
  • Error Code: 0x80070035 “The Network Path was not found” after Windows 10 Update
  • How to Configure Google Chrome Using Group Policy ADMX Templates?
Footer Logo

@2014 - 2018 - Windows OS Hub. All about operating systems for sysadmins


Back To Top