Remote desktop keeps disconnecting when the network path, RDP transport, Windows session policy, or remote computer is dropping the connection. Follow these eight fixes in order so you can tell whether the fault is on your device, inside Windows, or at the server.
Before you start
Note when the disconnect happens: immediately after sign-in, after the same number of minutes, only when idle, or at random while working. Record whether the window reconnects, your programs keep running, and another device can connect.
You need the server IP or hostname and administrator access to Windows.
Microsoft distinguishes an active, idle, locked, and disconnected session. A fixed interval points more strongly to a session policy; an irregular drop is more likely to be a network problem. That distinction prevents you from changing server settings when your Wi-Fi is the actual cause.
Step 1: Find which side is failing
Why this helps: the same symptom can come from the client, the route between you and the server, or the Windows host.
- Connect from a second network, such as a phone hotspot. If the session stays stable there, inspect your normal Wi-Fi, VPN, router, or ISP path.
- Try a second client device. If only one device disconnects, troubleshoot that client rather than changing the server.
- If every client drops together, check the server console, Windows logs, and provider status.
- If the window closes but applications continue running, reconnect and check whether you returned to the same session.
Success looks like a clear pattern: one client, one network, all clients, or the server itself. Write down the exact time of each drop before moving on.
For a clean baseline, review how to connect to a Windows VPS using RDP and confirm the address and credentials.
Step 2: Test the network path and RDP port
Why this helps: a successful login does not prove that the connection remains stable. A brief route interruption can break an RDP session even when web browsing still works.
On a Windows client, run this in PowerShell, replacing the address with your server’s hostname or IP:
Test-NetConnection -ComputerName SERVER_ADDRESS -Port 3389
Success looks like TcpTestSucceeded : True during the drop. If it flips to False, investigate your connection, VPN, firewall, router, or server firewall. If it stays True while the desktop freezes, continue to Step 3. A failed ping alone is not proof that the server is down because many hosts block ICMP.
See what port RDP uses and how TCP and UDP fit together for a port reference.
Step 3: Force TCP to test for a UDP problem
Why this helps: current RDP clients can use both TCP and UDP. UDP can improve responsiveness, but a broken or filtered UDP path can produce freezes, repeated reconnects, or drops after a few minutes.
On a Windows client, open an elevated Command Prompt and run:
reg add "HKLM\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services\Client" /v fClientDisableUDP /t REG_DWORD /d 1 /f
Close every Remote Desktop Connection window, reopen it, and test. Success looks like a stable session after the TCP-only change. Microsoft documents the same behavior through Turn Off UDP On Client, under Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Connection Client. If needed, test the host too: in gpedit.msc, go to Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Connections and set Select RDP transport protocols to Use only TCP. (Microsoft transport policy)
To undo the client test, run the same command with 0 instead of 1, or remove the policy value through Group Policy. Test one change at a time so you know which setting helped.
Step 4: Check session time limits and idle policies
Why this helps: a session that disconnects at a predictable time is usually being told to do so by Windows, Group Policy, an RD Gateway, or an organization’s security policy.
On the Windows host, open gpedit.msc and inspect Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Session Time Limits. Check these settings:
- Set time limit for active but idle Remote Desktop Services sessions
- Set time limit for active Remote Desktop Services sessions
- Set time limit for disconnected sessions
- End session when time limits are reached
For a privately managed server, set an unintended limit to Not Configured and reconnect. If the machine is managed by a company or domain, ask the administrator first. Success looks like the session no longer disconnects at the fixed interval.
An idle timeout normally gives a warning shortly before disconnecting. An active-session limit can disconnect you while working. If the message mentions a total logon or session timeout, focus here.
Step 5: Keep the remote computer awake
Why this helps: RDP cannot keep a remote computer available if Windows enters sleep or hibernation.
On the remote Windows machine, open Settings > System > Power & battery > Screen, sleep, & hibernate timeouts and set sleep to Never while connected to AC power. On Windows Server, review the active power plan as well.
Inspect the current plan from an elevated Command Prompt:
powercfg /getactivescheme
If the server is physical, check the lid, power button, UPS, and BIOS behavior. Success looks like the server remaining reachable after its old sleep time. A display turning off is fine; system sleep is the issue. Microsoft notes that RDP cannot connect to a sleeping or hibernating PC.
Step 6: Allow reconnects and use keep-alive when appropriate
Why this helps: a short network interruption should not force a new session, and a keep-alive can help the server notice the real client state.
In the Windows RDP client, open Show Options > Experience and make sure Reconnect if the connection is dropped is selected. Microsoft documents automatic reconnect as the normal behavior for temporary link loss unless policy disables it.
If the server shows your old session as active after a drop and you cannot reconnect cleanly, open gpedit.msc on the host. Go to Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Connections, enable Configure keep-alive connection interval, and use a modest interval such as 5 minutes. Apply policy and reconnect.
Success looks like reconnecting returns to the original session instead of creating a duplicate. Keep-alive cannot repair a bad network, but it helps when the host still believes a vanished client is active.
Step 7: Check the RDP service, firewall, and event logs
Why this helps: a listener, firewall rule, service, or authentication problem can look like an unstable connection after the session drops.
From an elevated PowerShell window on the server, check the service and firewall rules:
Get-Service TermService
Get-NetFirewallRule -DisplayGroup "Remote Desktop" | Select-Object DisplayName, Enabled, Profile
Get-NetTCPConnection -LocalPort 3389 -State Listen
Success looks like the service is running, Remote Desktop inbound rules are enabled for the active profile, and a listener is present on your port. Do not restart TermService through your only RDP session unless you have console access.
Open Event Viewer and review Applications and Services Logs > Microsoft > Windows > TerminalServices-LocalSessionManager, TerminalServices-RemoteSessionManager, and RemoteApp and Desktop Connections. Look for events immediately before the drop. (Microsoft disconnected-error troubleshooting)
Step 8: Prove when it is a provider or route issue
Why this helps: once the client and Windows policy checks pass, you need evidence that the host or upstream route is responsible.
Run the same RDP test from two networks and, if possible, two devices. Success looks like a repeatable pattern you can report: note the UTC time, client public IP, server address, whether all sessions dropped together, and the exact message.
For a hosted RDP, check the provider’s public site with the VPSLake website down checker, but treat that as a separate web check, not proof that the RDP port is healthy. A provider can use different networks for its website and servers.
Verify the fix
After each change, keep one session open for longer than its normal failure period. Test active use and idle time, then reconnect deliberately and confirm that applications and session state behave as expected.
If TCP-only solved the problem, restore UDP only after the route is stable. If removing a session limit solved it, record the policy change so Group Policy does not reintroduce the timeout. If multiple clients still fail, send the provider your timestamps and tests.
Troubleshooting by symptom
| Symptom | Most likely area | First check |
|---|---|---|
| Drops at the same minute every time | Idle or active session policy | Session Time Limits in gpedit.msc |
| Freezes, then reconnects after a few minutes | UDP path, VPN, or unstable Wi-Fi | Force TCP on the client |
| Only one laptop disconnects | Client network or RDP client | Test a hotspot and a second device |
| All users disconnect together | Host, firewall, route, or provider | Event Viewer and server console |
| Reconnect creates a new session | Keep-alive or session policy | Enable keep-alive and check disconnected-session limits |
| It stops only after the server is idle | Sleep or hibernation | Remote power settings |
FAQ
Why does my RDP disconnect every few minutes?
Common causes are an unstable network path, an RDP UDP problem, or an idle/session time limit. Check whether the interval is exact and whether another device or network has the same result.
Does disabling UDP fix remote desktop disconnects?
It can fix a broken or filtered UDP path, but it is a test, not a universal cure. Force TCP on the client, reconnect, and compare stability.
Why does RDP disconnect when idle but stay connected while I work?
An idle-session policy, router timeout, VPN rule, or power setting may be expiring the quiet connection. Check Session Time Limits and remote sleep settings.
Will my programs keep running after an RDP disconnect?
Usually, a network disconnect leaves the Windows session running, so programs may continue. Reconnect to the same session before starting a new one.
When should I contact my RDP provider?
Contact the provider after testing a second network or device, checking the port, and recording the time and error. If all clients drop together, include that fact.