Ошибка an internal error has occurred

Microsoft’s Remote Desktop Service is a great way to administer your Windows clients and Windows Servers. However, occasionally, you may encounter issues with the RDP server, preventing you from connecting to your remote host. One is the RDP an internal error has occurred” error message. This post will consider several different troubleshooting workarounds to help fix rdp error messages like the one described.

What is Remote Desktop Protocol (RDP)?

Remote Desktop Protocol (RDP) is a proprietary protocol developed by Microsoft that allows users to access and control a Windows operating system computer remotely. Using RDP, users can work on their remote computers as if sitting in front of them. Businesses, IT professionals, and home users widely use this powerful tool to manage and troubleshoot remote systems.

Launching the Remote Desktop Connection from a client computer (mstsc.exe)

What Triggers the Remote Desktop Internal Error for Windows?

Various factors can trigger the remote desktop connection an internal error message. These factors include incorrect Remote Desktop Connection settings, network issues, security settings, Windows Firewall configuration, and problems with the Remote Desktop Service itself.

Ensure Remote Desktop Connection Settings (RDP Settings) are Correct

First, ensure that your RDP Connection settings are correct to fix the “internal error has occurred” issue. Follow these steps:

1. Open the Remote Desktop Connection app.

2. Click on “Show Options” to access advanced settings.

3. Ensure that the correct computer name or IP address is entered in the General tab.

4. Verify that the User name and Password are correct.

5. Adjust the screen resolution and color depth in the Display tab according to your preference.

6. In the Experience tab, select the appropriate connection speed from the drop-down menu to optimize performance.

Allow Remote Connections

To enable remote connections on the target computer, follow these steps:

1. Right-click on “This PC” and select “Properties.”

2. Click on “Remote settings” in the System Properties window.

3. Under “Remote Desktop,” select “Allow remote connections to this computer.”

4. Click “Apply” and then “OK.”

Domain of Computer

Ensure the client and the remote computer are part of the same domain or workgroup. This can help avoid authentication issues that might trigger the “internal error has occurred” message.

Enable Reconnect If the Connection is Dropped

In the Remote Desktop Connection window, go to the Experience tab and check the box “Reconnect if the connection is dropped.”

This setting allows the RDP client to automatically attempt to reconnect to the remote computer if the connection is lost.

Restart Remote Desktop Service

Restarting the Remote Desktop Service on your RDP server can sometimes resolve the rdp error. To do this, follow these steps:

1. Press Windows Key + R to open the Run dialog.

2. Type services.msc and press Enter.

3. Find Remote Desktop Services in the list of services.

4. Right-click and select Remote Desktop Services and select “Restart.”

RDP Security

RDP security layer feature settings are crucial in ensuring a stable and secure remote connection. Incorrect or incompatible security settings can trigger the “internal error has occurred” message.

Change RDP Security Settings

To change RDP security settings, follow these steps:

1. Open the Local Group Policy Editor by pressing Windows Key + R, typing gpedit.msc, and pressing Enter.

2. Navigate to “Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Security.”

3. Double-click on “Require use of specific security layer for remote (RDP) connections” and select “Enabled.”

4. In the “Options” section, select the appropriate security layer from the drop-down menu, such as “RDP Security Layer” or “Negotiate.”

5. Click “Apply” and then “OK.”

How to Fix Windows RDP Internal Error?

To fix the “RDP aninternal error has occurred” issue, several solutions can be attempted. Here are some of the most effective methods:

Delete MachineKeys

Corrupt or outdated MachineKeys can cause RDP internal errors. To delete MachineKeys, follow these steps:

1. Press Windows Key + R to open the Run dialog.

2. Type %ProgramData%MicrosoftCryptoRSAMachineKeys to find the machine keys folder and press Enter.

3. Back up the MachineKeys folder by copying it to a different location.

4. Delete all files in the original MachineKeys folder.

5. Restart the computer and try the Remote Desktop Connection again.

Other Solutions to Fix RDP an Internal Error Has Occurred

If the above methods do not resolve the issue, try the following solutions:

Reconnect the Domain

If the remote computer is part of a domain, try removing it from the domain and then rejoining it. This can resolve potential authentication issues.

Modify the Startup of Services

Ensure that the Remote Desktop Services and its dependencies have the correct startup type. Set the startup type to “Automatic” for these services:

1. Remote Desktop Services

2. Remote Desktop Configuration

3. Remote Desktop Services UserMode Port Redirector

Adjust Remote Desktop Connection Configuration

In the Remote Desktop Connection app, go to the “Advanced” tab and click “Settings” under “Connect from anywhere.”

Ensure that the correct RD Gateway server name is entered, and select “Use my RD Gateway credentials for the remote computer.”

Allow the Windows Firewall to Connect to RDP

Ensure that the Windows Firewall is not blocking RDP connections. To do this:

1. Press Windows Key + R and type firewall.cpl, then press Enter.

2. Click on “Allow an app or feature through Windows Firewall.”

3. Locate “Remote Desktop” in the list and ensure that it is allowed for both “Private” and “Public” networks.

Disable Network Level Authentication

Disabling Network Level Authentication can sometimes resolve RDP internal errors. To do this, follow the steps mentioned in the “Allow Remote Connections” section and uncheck the box “Allow connections only from computers running Remote Desktop with Network Level Authentication.”

Disabling VPN Settings

VPN connections can interfere with RDP connections. Disable any active VPN connections and try the Remote Desktop Connection again.

Reinstall Windows Update

Some Windows updates might cause RDP internal errors. Uninstall the problematic update, and then reinstall it to resolve the issue.

Modifying Your Local Security Policy

1. Press Windows Key + R, type secpol.msc, and press Enter to open the Local Security Policy utility.

2. Navigate to “Local Policies > Security Options.”

3. Locate and double-click “System cryptography: Use FIPS compliant algorithms for encryption, hashing, and signing.”

4. Select “Disabled” and click “Apply” and “OK.”

Disable VPN Connections

Disable any active VPN connections and try connecting to the remote computer again.

Change the Startup Status of the Remote Desktop Protocol Service

Ensure the Remote Desktop Protocol service has the correct startup status. Set the startup type to “Automatic” for this service.

Disabling Static IP on Your Computer

If your computer has a static IP address, try disabling it and switching to DHCP. This can resolve RDP internal errors caused by network issues.

1. Press Windows Key + R, type ncpa.cpl, and press Enter to open the Network Connections window.

2. Right-click on your network adapter and select “Properties.”

3. Double-click on “Internet Protocol Version 4 (TCP/IPv4).”

4. Select “Obtain an IP address automatically” and “Obtain DNS server address automatically.”

5. Click “OK” and restart your computer.

Modifying RDP Security in Group Policy Editor

1. Open the Local Group Policy Editor.

2. Navigate to “Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Security.”

3. Double-click on “Set client connection encryption level” and select “Enabled.”

4. In the “Options” section, select “High Level” from the drop-down menu.

5. Click “Apply” and then “OK.”

Change the MTU Value

Changing the Maximum Transmission Unit (MTU) value can help resolve RDP internal errors caused by network issues.

1. Open an elevated Command Prompt by right-clicking on the Start button and selecting “Command Prompt (Admin).”

2. Type netsh interface ipv4 show subinterfaces and press Enter to view the current MTU value.

3. Note the name of the network interface you are using for RDP.

4. Type netsh interface ipv4 set subinterface “Interface Name” mtu=1458 store=persistent and press Enter, replacing “Interface Name” with the name of your network interface.

5. Restart your computer and try the Remote Desktop Connection again.

Enable Persistent Bitmap Caching

Enabling persistent bitmap caching can improve the performance of your Remote Desktop Connection and potentially resolve RDP internal errors.

1. Open the Remote Desktop Connection app.

2. Click on “Show Options” to access advanced settings.

3. In the Experience tab, check the box “Persistent bitmap caching.”

4. Click “Connect” to establish the RDP connection.

Additional Workarounds

Check the following additional workarounds if the above doesn’t resolve the issue.

Monitor Windows System Logs

Monitoring Windows System Logs can provide valuable information about the cause of the “RDP an internal error has occurred” issue. To access the Event Viewer and check the logs, follow these steps:

1. Press Windows Key + R, type eventvwr.msc, and press Enter to open the Event Viewer.

2. In the left pane, navigate to “Windows Logs > System.”

3. Look for events related to Remote Desktop Services or any errors that occurred around the time the issue was encountered.

You may also want to check the “Windows Logs > Application” section for any related events or errors.

Adjust Remote Desktop Connection App Settings

In some cases, adjusting the settings of the Remote Desktop Connection app may resolve the internal error. To do this:

1. Open the Remote Desktop Connection app.

2. Click on “Show Options” to access advanced settings.

3. In the “Display” tab, adjust the screen resolution and color depth settings.

4. In the “Local Resources” tab, configure the settings for audio, keyboard, and local devices.

5. In the “Experience” tab, select the appropriate connection speed from the drop-down menu and enable or disable specific performance options.

Experiment with these settings to find the optimal configuration that resolves the internal error.

Update Remote Desktop Connection Client

An outdated Remote Desktop Connection client may cause internal errors. To update the client, follow these steps:

1. Press Windows Key + R, type appwiz.cpl, and press Enter to open the “Programs and Features” window.

2. Look for “Remote Desktop Connection” or “Microsoft Remote Desktop” in the list of installed programs.

3. Follow the on-screen instructions to update the client if an update is available.

Alternatively, you can visit the Microsoft Download Center or the Microsoft Store to download the latest Remote Desktop Connection client version.

Check Proxy Server Settings

A misconfigured proxy server providing an Internet connection can interfere with RDP connections, causing internal errors. To check and adjust your proxy server settings:

1. Press Windows Key + I to open the Windows Settings app.

2. Click on “Network & Internet.”

3. In the left pane, select “Proxy.”

4. Ensure that the correct proxy settings are configured, or disable the proxy server if it is not required.

Check Control Panel Settings

The Control Panel provides additional settings related to Remote Desktop connections. To check these settings:

1. Press Windows Key + R, type control, and press Enter to open the Control Panel.

2. Click on “System and Security.”

3. Under “System,” click on “Allow remote access.”

4. Ensure that the correct settings are configured for remote connections, including allowing Remote Desktop and enabling Network Level Authentication.

Update Windows Server

An outdated Windows Server may cause RDP internal errors. To update your server, follow these steps:

1. Press Windows Key + I to open the Settings app.

2. Click on “Update & Security.”

3. In the “Windows Update” tab, click on “Check for updates” and follow the on-screen instructions to install any available updates.

Troubleshoot Network Connectivity

Network connectivity issues can cause RDP internal errors. To troubleshoot your network connection:

1. Check the physical connections between your computer and the network, such as cables and switches.

2. Use the ping command to test the connection between your and remote computers.

3. Check your router or switch for any configuration issues, such as incorrect VLAN settings or IP address conflicts.

Wrapping up

In conclusion, the “RDP an internal error has occurred” issue can be caused by various factors, such as incorrect settings, network issues, or outdated software. By following the solutions and workarounds outlined in this blog post, you should be able to address the issue and establish a successful Remote Desktop Connection. Remember to carefully analyze your specific situation and tailor the solutions to your needs for optimal results.

An internal error has occurred error for Remote Desktop Connection is a very vague error message. It occurs mostly when a user is trying to connect to a remote computer. This could be caused by a weak network connection, an invalid configuration of the remote connection, and more.

Some of the working solutions that have been known to help resolve this RDC error in Windows 11/10 are as follows:

1. Configure the settings.
2. Turn off any VPN Connections.
3. Leave and re-join a domain.
4. Use the Local Security Policy utility.
5. Change MTU Value
6. Disable Network Level Authentication

You will need an administrator account to execute these suggestions.

1] Configure the settings

Open the Remote Desktop Connection client by searching for it in the Windows Search box.

Select the Show Options button from the bottom left portion of the screen. Navigate to the Experience tab.

Uncheck the option that says Reconnect if the connection is dropped.

2] Turn off any VPN Connections

Open Windows 10 Settings app. Navigate to the following path: Network & Internet > VPN.

Select the VPN network that your computer is connected to and select Disconnect.

If you are using any third-party VPN software, exit that application.

3] Leave and re-join a domain

To remove a system from the domain, use the following procedure:

1. Click on the Start button and open the Settings app.
2. Go to System > Accounts > Access work or school.
3. Select the organization you want to disconnect your computer from.
4. Select Disconnect in order to disconnect from the organization.
5. Restart the system.

This would disconnect the system from the domain.

4] Use the Local Security Policy utility

Search for Local Security Policy and select the appropriate result. Select Local Policies > Security options in the left side navigation panel.

On the right-side panel, double click on System cryptography: Use FIPS compliant algorithms for encryption, hashing, and signing.

It will open the configuration dialog.

Select Enabled. Select Apply and then select OK.

Reboot your computer and check if that fixes your issues.

5] Change MTU Value

MTU or maximum transmission unit measures the largest data packet that a network device will accept. If the data size is increased, it will reduce the chance of any connection drop. While Windows doesn’t offer a direct method, you can use the TCP optimizer tool available here and then change the MTU value.

Choose the custom mode to enable the MTU box, and then increase the size. You may have to experiment a bit to get the right value to resolve the error.

6] Disable Network Level Authentication

• Open Windows Settings (Win + I)
• Navigate to System > Remote Desktop
• Un-tick the Allow connections only from computers running Remote Desktop with Network Level Authentication checkbox.
• Close the settings Windows.

Now try connecting to a remote desktop, and it should hopefully resolve the problem.

Is higher or lower MTU better?

While a larger MTUY can carry more data if it’s too large, the data can get fragmented. You will need to experiment with different values to determine what works between your router and the computer.

Why is the Remote Desktop connection not working?

There can be various reasons, even if your password is correct. Some of them are network issues, authentication issues on the server-side, Firewall, and the option to connect to a computer via remote.

Remote Desktop Connection stops all of a sudden

If you face this often, you may want to reduce the number of connected devices that carry along with the connection. it includes printers, audio playback settings, and so on. The best way to figure this out is to connect with the bare minimum setting and then add one at a time.

I hope the post was easy to follow, and you were able to figure out the problem where you get the internal error with Remote Desktop.

If you use Remote Desktop to work with remote computers in Windows environment, you will frequently come across the following error.

This error commonly occurs in Windows 8.1 and 10 when the username for remote computer is saved in Windows registry.

The following video will delete the saved username from Windows registry and the error will go away.

If you work with a lot of remote computers and you probably encounter this error quite often. This will make it cumbersome to browse Windows registry and delete the registry value for every single remote computer. In the next section, I will show you how to create a PowerShell module which will feel and behave like a traditional PowerShell cmdlet. Using this module, you can fix “An internal error has occurred” issue with just a single command.

Creating Fix-RDPError PowerShell Module

Launch the Windows PowerShell console with administrator privilege , paste the following code and hit enter:

$module = New-Item -Path "$env:userprofile\documents\WindowsPowerShell\Modules\Fix-RDPError" -Name Fix-RDPError.psm1 -ItemType File -Force
if($module){
notepad $module
}

This command will create new new PowerShell module file under “$env:userprofile\documents\WindowsPowerShell\Modules” and then opens the modules file in notepad.

Now copy the following code, paste it in notepad and press Ctrl+S to save it.

<#
.Synopsis
Fixes "An internal error has occurred" issue.
.DESCRIPTION
This cmdlet will fix "An internal error has occurred" issue while trying to connect a computer through Remote Desktop.
.Parameter <ComputerName>
This is a required parameter where you need to specify a computer name or IP address of the remote computer.
.EXAMPLE
Fix-RDPError -ComputerName DC01
This command will delete the saved "UsernameHint" value in registry for remote computer DC01, which will fix "An internal error has occurred" issue.
.EXAMPLE
Fix-RDPError -IP 192.168.10.10 -Verbose
This command will verbosely delete the saved "UsernameHint" value in registry for remote computer 192.168.10.10, which will fix "An internal error has occurred" issue.
#>
function Fix-RDPError
{
[CmdletBinding()]
Param
(
# Required parameter ComputerName
[Parameter(Mandatory=$true,
Position=0)]
[Alias ('HostName','cn','Host','Computer', 'IP')]
[string]$ComputerName
)
$BasePath = "HKCU:\SOFTWARE\Microsoft\Terminal Server Client\Servers"
$RegPath = "$BasePath\$ComputerName"
$exists = Test-Path "$BasePath\$ComputerName"
if ($exists) {
if((Get-ItemProperty $RegPath).PSObject.Properties.Name -contains "UsernameHint") {
Write-Host "Saved Username found in registry!" -ForegroundColor Green
Write-Verbose ("Removing the `"UsernameHint`" value from [$RegPath] registry key!")
Remove-ItemProperty -Path $RegPath -Name "UsernameHint" -Force
if($?){
Write-Host "Operation completed successfully!"-ForegroundColor Green
} else {Write-Host "Something went wrong! Try running the command again." -ForegroundColor Red}
}
else {Write-Error "Username is not saved for `"$ComputerName`""}
}
else {Write-Error "Computer name `"$ComputerName`" doesn't exist in registry!"}
}

If you followed the steps correctly, your Fix-RDPError module is now created and ready for use. This module requires you to have administrative privilege on local computer since it involves deleting value(s) from Windows registry.

Using the Fix-RDPError Module

Now that you created the FIx-RDPError module, let me tell you how to use it. Launch a PowerShell console with administrator privilege. copy the following command:

Fix-RDPError -ComputerName SRV01

Make sure you change the SRV01 with your remote computer name.

The module will search for a saved username in Windows registry and deletes it if found. This will fix “An internal error has occurred” issue.

This PowerShell module may be useful for the windows administrators who frequently uses Remote Desktop to connect remote computers and face this error quite often.