To fix Remote Desktop not connecting, make sure the destination PC is awake, enable Remote Desktop, and check its address, account permissions, and firewall access. The destination also needs a Windows edition that supports incoming connections. These steps use Windows 11 menus, with a separate Windows 10 update path below.
The short version
- Check the destination: The remote PC must be powered on, awake, and connected to its network.
- Confirm its edition: Windows 11 Pro, Enterprise, and Education can host Remote Desktop connections; Home can connect to another PC.
- Check access: Enable Remote Desktop and give the connecting account permission.
- Check the connection: Use the correct PC name or reachable IP address, and allow Remote Desktop through Windows Firewall.
| Check or fix | When it helps |
|---|---|
| Power on or wake the destination | The remote PC is off, asleep, or hibernating |
| Adjust sleep and hibernation timeouts | Access stops after the destination sits idle |
| Check the Windows edition | The destination cannot host incoming connections |
| Enable Remote Desktop | Remote access is turned off |
| Correct the PC name | The connection points to the wrong destination |
| Try a reachable IP address | You need to isolate a name resolution problem |
| Include the configured port | The host uses a nondefault RDP port |
| Update saved credentials | The remote account password has changed |
| Grant remote access permission | The connecting account lacks access |
| Allow Remote Desktop through Windows Firewall | The destination firewall blocks connections |
| Connect through the network owner's VPN | You are outside the destination's network |
| Check existing router forwarding | Direct internet RDP uses an incorrect port mapping or address |
| Install applicable Windows updates | A Windows issue affects connections |
| Try Windows App | You need to isolate a client problem |
Make sure the remote PC is awake
Check the computer you want to control first. It must be powered on, awake, and connected to its network. Remote Desktop cannot connect while that computer is off, asleep, or hibernating, so power it on or wake it before trying again.
If access stops working after the destination sits idle, adjust its sleep timeout. On Windows 11, open Start > Settings > System > Power & battery > Screen, sleep, & hibernate timeouts. For the relevant power condition, under Make my device sleep after, choose Never.
Power and hibernation options vary by device. If hibernation timeouts are listed, review those too, since preventing sleep alone does not address a host that hibernates.
Check the Windows edition and enable Remote Desktop
Windows Home cannot host Microsoft's built-in Remote Desktop connections. The destination needs a supported host edition, such as Windows 11 Pro, Enterprise, or Education. Your connecting PC can run Home; the edition restriction applies to the PC you want to control.
On the destination running Windows 11, open Start > Settings > System > About. Read Edition under Windows specifications. If it says Home, you need a supported host edition before continuing with incoming Remote Desktop setup.
On a supported Windows 11 destination, open Start > Settings > System > Remote Desktop. Turn on Remote Desktop, then select Confirm. You need administrator access to enable it.
Connect to the correct PC name or address
On the destination running Windows 11, open Settings > System > Remote Desktop and note PC name. On the connecting Windows 11 PC, search for Remote Desktop Connection, open it, enter that name, and select Connect.
For a direct connection where the destination's IP address is reachable, try that IP address instead of the computer name. If the IP address works, investigate the original name or DNS name resolution. Some organization authentication configurations require a hostname, so keep using the required hostname for those connections.
If the destination uses a configured nondefault listening port, include it in the Computer field. Use the format hostname:port or IPaddress:port, replacing the placeholders with the actual destination and configured port.
Check your password and remote access permission
Retry with the correct username and current password for the remote PC account. If that password recently changed, update any credentials saved in the connection configuration. An old saved password can prevent sign-in.
The account also needs permission to connect remotely. On the Windows 11 destination, open Settings > System > Remote Desktop > Remote Desktop users, then select Add. Enter the username and select OK.
Administrators already have remote access by default. On older releases, select Select users that can remotely access this PC to manage who can connect.
Allow Remote Desktop through Windows Firewall
On a Windows 11 destination using Windows Firewall, open the Windows Security app, select Firewall & network protection, then select Allow an app through firewall. Select Change settings, then find Remote Desktop in the list of apps. You need administrator access to change these settings.
Select Remote Desktop, then select OK and retry the connection. If it still fails, check whether you are connecting from the destination's own network or from somewhere else, since outside access needs additional network configuration.
Check access from outside the destination network
To reach the destination's internal address from outside its network, establish a VPN connection using the configuration supplied by the network owner. Then connect to the remote PC's internal address. The VPN must provide access to the network containing that PC.
Microsoft prefers VPN access because forwarding an RDP port exposes the destination to the internet. If you already use direct internet RDP through a router you control, check its existing port forwarding configuration. The external RDP port must map to the destination's internal IP address and RDP port, normally 3389.
For that router setup, connect using the router's public address. Keep the destination's internal address stable, and consider Dynamic DNS if the public address changes. Port forwarding steps and labels vary by router model, so follow your router's own instructions.
Install applicable Windows updates
On a supported Windows 11 release, open Start > Settings > Windows Update and select Check for updates. Install applicable updates. If the connection failure began after an update, review Update history to identify what was installed.
On Windows 10 with an applicable servicing entitlement, open Settings > Update & Security > Windows Update. Select Check for updates and install the applicable updates for that device.
Try Windows App for the same destination
Try another supported client after checking the destination, account, and network. Install Windows App from the Microsoft Store on a Windows device that meets its requirements. Windows App supports direct remote PC connections on supported Windows 11 and eligible Windows 10 clients.
Open Windows App and choose Add a remote PC. On Devices, select Add (+) or Choose a resource to add, enter PC Name, then select Add & Connect. Supply the remote PC account when prompted; direct PC access does not require signing in to Windows App itself.
The separate Microsoft Store Remote Desktop app is retired, so use Windows App or built-in Remote Desktop Connection for applicable PC connections. If both current clients fail against the same destination, check the destination's permissions and network access again.
Frequently Asked Questions
Why does Remote Desktop ask for a password when credentials are saved?
On devices with Credential Guard enabled, RDP cannot send saved Windows credentials. Enter your credentials manually at the connection prompt instead of relying on automatic sign-in.
Where can you find saved Remote Desktop credentials?
On Windows 11 or Windows 10, search for Credential Manager and open it. Select Windows Credentials to locate and manage the destination's saved credentials.
Should you turn off Network Level Authentication to connect?
Microsoft recommends keeping Network Level Authentication enabled normally and using an NLA-capable client. Temporarily disabling the requirement is a compatibility measure for older incompatible clients, rather than a general connection fix.
Can you connect to your home PC through Windows App in a browser?
Windows App in a browser does not provide direct access to an ordinary home PC. Its browser connections support Azure Virtual Desktop, Windows 365, and Microsoft Dev Box.
Was there a Windows update that caused Remote Desktop sign-in failures?
A January 2026 authentication regression affected Windows 11 24H2 and 25H2 following KB5074109. Microsoft issued KB5077744 to fix it, so affected systems should use the appropriate current servicing update. That historical issue does not establish the cause of a new connection failure.