Fix “An Internal Error Has Occurred” in Remote Desktop Connection: Complete Solutions

The “An Internal Error Has Occurred” message in Remote Desktop Connection usually means your computer can’t complete the connection handshake with the remote computer. This happens because of outdated drivers, corrupted cache files, network issues, or permission problems. You can fix it by clearing your RDP cache, updating display drivers, resetting network settings, or adjusting Remote Desktop settings. Most people solve this within 15 minutes using the methods below.

What This Error Means

When you see “An Internal Error Has Occurred” on your Remote Desktop Connection screen, it’s telling you something went wrong during the connection process. This isn’t a specific error code, which makes it frustrating. Your computer started connecting but hit a problem before establishing the full connection.

This error stops you from accessing your remote computer entirely. You can’t work, access files, or do anything on that remote machine until you fix it.

The error happens at different stages depending on the cause. Sometimes your computer connects briefly then disconnects. Other times it fails immediately. Understanding which scenario you’re in helps you fix it faster.

Why This Error Happens

Several things trigger this error. Network problems are common. If your internet connection drops or becomes unstable, Remote Desktop fails. Connection timeouts also cause this issue, especially on slow networks.

Your graphics drivers play a role too. Remote Desktop relies on your display driver to compress and send video information from the remote computer. Outdated or corrupted drivers can’t handle this properly.

RDP cache files store connection data. When these files become corrupted, your computer tries to use broken information to connect. This creates the internal error.

Permission issues matter as well. If your user account doesn’t have the right access level on the remote computer, the connection fails. Windows needs specific permissions to establish Remote Desktop sessions.

Server-side problems can also cause this. The remote computer itself might have connection service issues, outdated Windows versions, or firewall blocks.

Method 1: Clear Your Remote Desktop Cache Files

This is the fastest fix for most people because corrupted cache files cause frequent internal errors.

Step-by-step process

Step 1: Open File Explorer
Click on the File Explorer icon in your taskbar. You can also press Windows key plus E.

Step 2: Navigate to the cache folder
In the address bar, copy and paste this exact path:

%LOCALAPPDATA%\Microsoft\Terminal Server Client\Cache

Press Enter. Your computer automatically expands the path to the full location.

Step 3: Select all cache files
You should see several files with names like “Cache” or other similar names. Press Ctrl plus A to select everything in this folder.

Step 4: Delete the files
Right-click the selected files and choose Delete. Your computer removes all cached connection data.

Step 5: Empty the Recycle Bin
Right-click your Recycle Bin and select Empty Recycle Bin. This permanently removes the files.

Step 6: Try connecting again
Open Remote Desktop Connection and attempt to connect. Your computer creates new cache files during the new connection attempt.

This method works because you’re removing potentially corrupted data. Remote Desktop creates fresh cache files on your next successful connection.

Why this works

Cache files speed up connections by storing information about previous connections. When a file becomes corrupted, Remote Desktop can’t use it properly. Instead of skipping the bad file, it stops entirely and shows the error.

Clearing the cache forces Remote Desktop to rebuild connection data from scratch. Most of the time, this solves the problem immediately.

Method 2: Update Your Display Drivers

Graphics drivers handle the video compression and transmission that Remote Desktop needs. Old drivers can’t handle modern connection protocols.

Finding and updating drivers

Option 1: Use Windows Device Manager

Open Device Manager by right-clicking the Start button and selecting Device Manager. Look for Display adapters in the list and expand it.

Right-click your graphics card and select Update driver. Choose Search automatically for updated driver software. Windows checks for newer versions online.

If Windows finds an update, it downloads and installs it automatically. Restart your computer when prompted.

Option 2: Use manufacturer websites

If Device Manager doesn’t find updates, visit your graphics card manufacturer’s website directly.

For Nvidia, go to nvidia.com/Download/driverDetails.aspx. For AMD, visit amd.com/en/support. For Intel integrated graphics, check intel.com/content/www/us/en/support/detect.html.

Download the driver file matching your graphics card model and Windows version. Run the installer and follow the prompts. Always restart after installation.

Why driver updates help

Remote Desktop sends compressed video from the remote computer to your screen. This requires your graphics driver to decode the information correctly. Outdated drivers lack support for current RDP protocols and compression methods.

Modern drivers include bug fixes that prevent internal errors. They also handle edge cases that older versions couldn’t manage.

Method 3: Reset Your RDP Settings

Sometimes Remote Desktop settings become misconfigured. Resetting them to defaults often resolves internal errors.

Using the Remote Desktop settings reset

Open Remote Desktop Connection by typing “Remote Desktop Connection” in your Windows search bar. Click the application to open it.

Click the Show Options button at the bottom left of the window. This expands the connection settings.

Look for the General tab. In the Logon settings section, verify you’ve entered the correct username and password.

Click the Display tab. Check that Color depth is set to True Color (32 bit). Make sure Resolution is appropriate for your network speed.

Switch to the Experience tab. Here you see performance settings. Change these based on your network speed.

For slow connections, select Modem. For faster connections, select LAN. These presets adjust settings that prevent connection errors on different network types.

Click the Advanced tab if available. Look for options about encryption and security. Set these to the recommended defaults.

Creating a new RDP file

Sometimes creating a completely new Remote Desktop connection file helps. This eliminates any corrupted settings in your existing connection.

Open Notepad. Copy and paste this basic RDP configuration:

full address:s:your-computer-name-or-ip
username:s:DOMAIN\username
prompt for credentials:i:1

Replace “your-computer-name-or-ip” with the actual address. Replace “DOMAIN\username” with your actual credentials.

Save this file with a .rdp extension. For example, “myconnection.rdp”. Then double-click it to connect using this fresh configuration.

Method 4: Check Your Network Connection

Network problems are responsible for many internal error messages. Your connection might be dropping without you realizing it.

Testing network stability

Open Command Prompt as administrator. Press Windows key plus R, type cmd, and press Enter.

Type this command:

ping 8.8.8.8 -t

This sends continuous packets to Google’s servers. Watch the results for 30 seconds. Your computer should get replies from every packet.

If you see Request timed out messages, your internet is dropping packets. This causes Remote Desktop failures.

Press Ctrl plus C to stop the ping test.

Checking your router

Restart your router by unplugging it for 30 seconds. Plug it back in and wait for it to fully boot. Lights on the front should stabilize in about two minutes.

Move closer to your router if you’re using WiFi. Distance and obstacles weaken wireless signals. Ethernet cables are more stable than wireless connections.

Use an Ethernet cable instead of WiFi if possible. Remote Desktop requires stable connections. Wireless networks introduce unnecessary instability.

Firewall and port settings

Windows Firewall might block Remote Desktop connections. Open Windows Defender Firewall by searching for it in Windows settings.

Click Allow an app through firewall on the left side. Look for Remote Desktop in the list. Make sure both Private and Public columns have checkmarks.

If Remote Desktop isn’t listed, click Allow another app. Browse to C:\Windows\System32\ and select mstsc.exe. This adds Remote Desktop to the allowed apps list.

Check your router’s firewall too. Some routers block RDP by default. Log into your router’s admin panel and look for port forwarding or firewall rules. Port 3389 is the default Remote Desktop port.

Method 5: Disable Unnecessary Features

Some Windows features conflict with Remote Desktop connections. Disabling them might resolve the internal error.

Turn off Fast User Switching

Press Windows key plus R, type gpedit.msc, and press Enter. This opens Group Policy Editor.

Navigate to Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host.

Look for Limit number of connections. Double-click it and set it to 2 or higher.

Find the policy called Restrict Remote Desktop Services user session by time limits and disable it.

Click OK and close the editor. Restart your computer.

Disable Visual Themes

Remote Desktop sometimes struggles with heavy visual effects. Disabling themes can improve stability.

Right-click your desktop and select Personalize. Click Colors on the left side.

Toggle off Transparency effects. This reduces graphics processing during remote connections.

Turn off Sleep Mode

When your computer sleeps, Remote Desktop connections drop. Set your computer to never sleep.

Open Settings and go to System > Power & sleep. Under Sleep, change the dropdown to Never.

This ensures your connection remains active even during idle periods.

Method 6: Update Windows and Remote Desktop Components

Outdated Windows versions contain bugs that cause connection errors. Microsoft releases updates specifically to fix Remote Desktop issues.

Checking for Windows updates

Open Settings by pressing Windows key plus I. Click Update & Security. Select Check for updates.

Windows downloads and installs available updates. This might take several minutes. Your computer might restart automatically.

Allow all updates to install completely. Some fixes require multiple restart cycles.

Updating Remote Desktop specifically

Go to Microsoft Store and search for Remote Desktop. If you’re using the Microsoft Store version, updates happen automatically. Check that you have the latest version installed.

Some people use the built-in mstsc.exe version instead of the Store version. The Store version usually handles connections better.

Method 7: Check Remote Computer Settings

The problem might be on the remote computer’s side, not your local computer. You need access to the remote computer to check its settings.

Enable Remote Desktop on the target computer

On the remote computer, right-click This PC and select Properties. Click Remote settings on the left side.

Under Remote Desktop, select Allow remote connections to this computer. Click Apply and OK.

Make sure your user account is added to Remote Desktop Users group. Click Select Users, then Add. Type your username and click Check Names.

Restart Remote Desktop Service

On the remote computer, press Windows key plus R, type services.msc, and press Enter.

Find Remote Desktop Services in the list. Right-click it and select Restart.

Wait 30 seconds for the service to fully restart. Then try connecting again from your local computer.

Check the remote computer’s firewall

On the remote computer, open Windows Defender Firewall. Allow Remote Desktop through the firewall as described in Method 4.

If the remote computer uses third-party firewall software, check its settings too. The firewall might be blocking port 3389.

Method 8: Adjust RDP Security Settings

Sometimes overly strict security settings prevent connections.

Changing encryption levels

Open Remote Desktop Connection and click Show Options. Go to the General tab.

In the Connection settings section, look for Computer name. Before connecting, click on the Options tab.

Find Experience tab and look for Network connection speed. Set this to LAN or higher for best compatibility.

In the Security tab, change the Security layer to RDP Security Layer. This uses a less strict connection method that works in more situations.

Troubleshooting Quick Reference

Problem	Solution	Time Required
Corrupted cache	Clear RDP cache files	5 minutes
Outdated drivers	Update graphics drivers	10 minutes
Misconfigured settings	Reset RDP settings	5 minutes
Network instability	Check connection stability	10 minutes
Firewall blocking	Allow RDP through firewall	5 minutes
Remote service offline	Restart Remote Desktop Service	5 minutes
Windows outdated	Install Windows updates	15 minutes
Visual effects conflict	Disable transparency effects	5 minutes

When to Try Each Method in Order

First attempt: Clear your RDP cache (Method 1). This works in roughly 40 percent of cases.

If that fails: Update your display drivers (Method 2). Graphics driver issues cause about 25 percent of errors.

If still not working: Check your network connection (Method 4). Network problems account for 20 percent of cases.

If network is fine: Reset RDP settings (Method 3) and adjust security settings (Method 8).

Last resorts: Update Windows (Method 6) and check remote computer settings (Method 7).

Most people resolve this error using the first three methods. Only a small percentage need all eight solutions.

When the Error Means Something More Serious

Usually this error is fixable with the methods above. But sometimes it indicates a deeper problem that requires professional help.

You might need IT support if:

The error persists after trying all eight methods. Every connection attempt fails with the same error. Multiple different remote computers show the same error.

Your organization’s network blocks RDP deliberately. Some companies disable Remote Desktop for security reasons. Your IT department should provide alternative remote access methods.

The remote computer is offline or unreachable. You can’t control whether the remote computer stays powered on. Check with whoever manages that computer.

Your Windows installation is corrupted. This is rare but happens after failed updates. You might need to repair or reinstall Windows.

Summary

The “An Internal Error Has Occurred” message in Remote Desktop Connection frustrates many users, but it’s usually fixable. Most people solve this problem by clearing their RDP cache, updating graphics drivers, or fixing network issues.

Start with the cache clearing method. It’s fast, safe, and works frequently. If that doesn’t help, work through the other methods in the order listed above.

Keep in mind that some errors come from the remote computer’s side, not your computer. Make sure Remote Desktop is properly enabled on the remote machine and that the service is running.

Network stability matters more than many people realize. A stable, wired internet connection prevents many connection errors that wireless connections experience.

Always keep your Windows installation and drivers updated. Microsoft releases updates specifically to fix Remote Desktop compatibility issues. Running outdated software increases the likelihood of hitting bugs that cause internal errors.

If you’ve tried these methods and the error persists, the problem likely requires help from your IT department or a professional technician. Sometimes the issue involves network configuration, security policies, or hardware problems that go beyond standard troubleshooting.

Document which methods you’ve tried and what happened with each one. This information helps support staff diagnose the real cause faster.

FAQ

Is the internal error on my computer or the remote computer?

Usually your computer. Most internal errors come from corrupted cache, outdated drivers, or network issues on the client side. However, the remote computer’s firewall settings, service status, or permissions can also cause the error. Try the methods in this article first, as they address the most common client-side causes.

Can I connect through a VPN to fix this error?

Yes, sometimes. A VPN creates a more stable connection path. Try connecting through a VPN if you have one available. This bypasses local network issues. However, if the error is caused by driver problems or cache corruption, a VPN won’t help. The VPN method works best if you suspect network instability.

Why does the cache clearing method work so often?

Remote Desktop stores connection data locally to speed up future connections. These cache files occasionally become corrupted from unexpected disconnections or software conflicts. When Remote Desktop tries to read a corrupted file, it throws an error instead of skipping the file. Clearing the cache forces your computer to rebuild the data from scratch, eliminating the corrupted information.

Do I need to update my drivers if they’re already recent?

Check the date. Graphics driver updates come out every few weeks. If your drivers are more than three months old, update them. Newer drivers fix bugs and improve RDP compatibility. Even recent drivers sometimes have issues that updates address. Updating is quick and rarely causes problems.

What’s the difference between Remote Desktop Connection and Windows Remote Desktop from the Store?

Remote Desktop Connection (mstsc.exe) is built into Windows. The Store version is a separate application with a newer interface. The Store version generally has better compatibility with modern systems and receives updates more frequently. If you’re using the built-in version and experiencing errors, try the Store version instead. Both use the same underlying RDP protocol, but the Store version handles it better in many cases.