What "internal error" actually means
"An internal error has occurred" is the RDP client's way of saying something broke on my end and I don't know what. It's deliberately vague — it's a catch-all for failures inside the client or the early handshake, not a diagnosis. The good news: the real-world causes behind it are a short, well-known list, and they resolve in a predictable order. This guide is that order.
Before starting, note two things this error is not. It's not a wrong password (that gives you a logon failure — see authentication errors). And it's usually not the server being down (that gives you a can't-connect timeout — see RDP not connecting). Internal error lives in between: the client starts the connection process and trips over itself. That "in between" is exactly where the fixes below operate.
The fixes, in the order that works
Work these top to bottom. Each takes a few minutes; stop when the connection succeeds. Roughly speaking, fix 1 solves it for a third of people, fixes 2–3 for the next third, and the rest need 4–6.
Fix 1–2: the client cache and the client itself
Fix 1 — Delete the stale connection cache. The RDP client stores per-connection data (including the Default.rdp template and cached bitmaps) that can corrupt — especially after updates or crashes. Close the client, open File Explorer, and go to Documents — delete or rename Default.rdp. Then clear the client's cache: the bitmap cache lives under %LOCALAPPDATA%\Microsoft\Terminal Server Client\Cache — delete the contents of that Cache folder. Reopen the client and try a fresh connection (retype the address; don't reuse a saved .rdp file yet). Corrupted cache is the single most common cause of this error.
Fix 2 — Update (or repair) the RDP client. The built-in Windows client gets fixes through Windows Update; the Store "Remote Desktop" app updates through the Microsoft Store. An outdated client against a recently-patched server is a classic internal-error pairing — the handshake assumptions no longer match. Update everything, reboot your local computer (not the server), and retry. If you're using a third-party RDP client, test with Microsoft's own client once to isolate whether the client is the variable.
Worth knowing: if the internal error started the morning after a Windows Update on your computer, fix 2 is almost certainly your answer — update again (Microsoft often ships the follow-up fix within days) or roll back that specific update.
Fix 3–4: the security handshake and the network path
Fix 3 — Change the security layer negotiation. The internal error frequently comes from the client and server failing to agree on a security layer (RDP Security Layer vs. SSL/TLS vs. Negotiate). On the client side, create a fresh connection and on the Advanced/Security settings try toggling between the options — or simpler: connect once with a brand-new saved connection (no imported settings), which uses defaults that match most servers. If you administer the server, check that its security layer is set to "Negotiate" rather than a forced specific layer; a forced layer that the client doesn't expect produces exactly this error.
Fix 4 — Look at MTU and VPN interference. This one is sneaky: if the error appears only when you're on a VPN (or only from one network), oversized packets are being silently dropped. VPNs add header overhead that can push packets past the path's MTU, and the RDP handshake is particularly sensitive to it. Test with the VPN off — if the error vanishes, the VPN path is the cause. Lowering the MTU on your network adapter (a common working value to try is 1400) or switching VPN protocols often resolves it. This also explains "internal error" that follows you between servers: it's your path, not any server.
Fix 5–6: reboots and the last resorts
Fix 5 — Reboot the server (properly). If the error happens from multiple client devices, the problem has moved server-side: a wedged RDP listener or a half-applied update. Reboot via your provider's client area — log into the RDP Temple client area, issue the reboot, and wait a full five minutes before reconnecting (services need time to settle; connecting at minute two can reproduce the error and mislead you).
Fix 6 — Test from a completely different device and network. Phone on mobile data, Microsoft's mobile RDP app, fresh credentials typed by hand. If that works while your main computer fails, you've proven the server is fine and the problem is isolated to one machine — reinstall or reset that machine's RDP client configuration rather than continuing to poke the server. If nothing connects from anywhere, it's server-side and it's support's turn: send them the error text, the fact that multiple devices fail, and the time of your tests.
A final note on documentation: when the internal error strikes, jot down three things — when it started, what changed recently (updates on either end, a new network, a new client device), and whether it's constant or intermittent. "Started Wednesday morning after Tuesday's Windows Update, happens on every connection attempt from my laptop but my phone connects fine" is a complete diagnosis in one sentence — it points straight at the client update. Most people skip this and spend an hour re-testing things they'd already ruled out. The error message won't tell you what's wrong, so your own notes have to.
Cause-to-fix reference table
| Pattern | Likely cause | Fix |
|---|---|---|
| Error after a Windows/client update | Client-handshake mismatch | Update client again / roll back the update |
| Error with saved connections, fresh ones work | Corrupted .rdp / cache | Delete Default.rdp + bitmap cache folder |
| Error only on VPN / one network | MTU / packet fragmentation | Test without VPN; lower MTU; change VPN protocol |
| Error from one computer only | That client's config | Fresh client install; test with Microsoft's client |
| Error from all devices | Server-side listener issue | Reboot via client area; then contact support |
RDP Internal Error: FAQ
It's a catch-all: the RDP client failed during connection setup without a more specific reason. In practice it comes from a short list — corrupted client cache, an outdated client after an update, a security-layer handshake mismatch, or MTU/VPN packet issues. Work through those in order rather than treating the message as a diagnosis.
Clearing the bitmap cache folder doesn't touch your saved .rdp files. Deleting Default.rdp only removes the default template settings — your named saved connections stay. To be safe, back up any .rdp files you care about before cleaning house; they're tiny.
VPN overhead can push packets past the network path's MTU, and the RDP handshake is sensitive to the resulting silent packet drops. Test with the VPN off to confirm, then try lowering your adapter's MTU (1400 is a common working value) or switching VPN protocols.
It's server-side at that point — likely a wedged RDP listener or a half-applied update. Reboot via your provider's client area and wait five full minutes before reconnecting. If it persists across devices after a clean reboot, contact support with the error text and your test times.
Occasionally — aggressive antivirus or firewall suites can intercept the RDP handshake and break it in ways the client reports as an internal error. Temporarily disable it for a 60-second test; if the connection succeeds, add a proper exception for the RDP client rather than leaving protection off.
CredSSP errors name themselves — the message mentions CredSSP or "encryption oracle remediation" and it's a specific patch-mismatch problem (see our CredSSP guide). "Internal error" names nothing; it's the vague one, and its causes are the client-cache, handshake, and network issues covered here.
Ready for your own RDP server?
Full admin access, dedicated IP, 24/7 support and a 3-day money-back guarantee on every plan. Pay by credit/debit card, bank transfer, Bitcoin or altcoins.
3-day money-back guarantee · Instant setup · 30+ server locations · 99% uptime SLA
