How To Fix Remote Desktop Can’t Connect On Windows 11 (2026)
Remote Desktop cannot connect to a Windows 11 PC when the PC is not a Pro edition, the setting is off, your account is not allowed, or something blocks the connection.
Windows 11 Home can connect out to other PCs, but it cannot accept Remote Desktop connections at all.
This guide uses Microsoft’s setup and troubleshooting pages, and it is meant for reaching your own PC or one you manage with the owner’s permission.
Quick answer: why Remote Desktop cannot connect
| Cause | How to check | Fix |
|---|---|---|
| The target PC runs Windows 11 Home | Settings, System, About, Edition | Home cannot host. Upgrade to Pro or use another tool. |
| Remote Desktop is off | Settings, System, Remote Desktop | Turn on Remote Desktop and select Confirm. |
| Your account is not allowed | Remote Desktop users list | Add the account, or use an Administrators account. |
| The PC is off or on another network | Check power and network | Turn it on, or use a VPN or port forwarding. |
| Firewall blocks the connection | Test-NetConnection on port 3389 | Enable the Remote Desktop firewall rules. |
| The RDP listener or service is not running | qwinsta and Services | Start the Remote Desktop services. |
Which Windows editions can use Remote Desktop
| Role | Editions |
|---|---|
| Host (the PC you connect to) | Windows Pro, Enterprise and Education, plus Windows Server |
| Client (the device you connect from) | Any Windows edition, including Home, plus macOS, iOS and Android |
Open Settings, then System, then About, and look at Edition under Windows specifications to see what you have.
If it says Home, the PC cannot be the host, and no setting changes that.
How to turn on Remote Desktop in Windows 11 Pro
- Select Start, then Settings, then System.
- Select Remote Desktop.
- Turn on Enable Remote Desktop, then select Confirm.
- Write down the PC name shown on that page.
You need to be an administrator on the PC to change this setting.
A box to make the PC discoverable on private networks is checked by default.
Allow the right accounts
Members of the Administrators group can connect by default.
To let someone else in, open Remote Desktop settings, select the option for the users that can remotely access this PC, select Add, type the username, and select OK.
Every account with remote access should have a strong, unique password.
How to connect from another PC
- Search for Remote Desktop Connection on the PC you are connecting from and open it.
- Type the PC name, or its IP address, of the remote PC.
- Select Connect and sign in with the account that is allowed.
On a Mac or iPhone, install the Windows App; on Android, install the Remote Desktop app from Google Play.
If the PC name fails, try the IP address, because that shows whether the problem is name resolution.
The error messages Microsoft documents
The classic message says Remote Desktop cannot connect for one of three reasons: remote access is not enabled, the remote computer is turned off, or it is not available on the network.
A second message says the computer cannot connect to the remote computer and to try again.
Microsoft says the main root causes are a listener that is not working and incorrect network configuration.
Check the Remote Desktop listener
- On the remote PC, open an elevated Command Prompt or PowerShell window.
- Run qwinsta.
- Look for rdp-tcp with the state Listen.
If rdp-tcp is listening, the listener works and the problem is elsewhere.
If it is not, check the services next.
Check the Remote Desktop services
Both of these services must be running on the remote PC:
- Remote Desktop Services (TermService)
- Remote Desktop Services UserMode Port Redirector (UmRdpService)
If one is stopped, start it, and select Yes if Windows offers to restart the other.
Check the setting and any policy blocking it
The fDenyTSConnections value under HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server must be 0 for Remote Desktop to be enabled.
A value of 1 means it is disabled, and Microsoft tells you to back up the registry before changing anything.
If the setting keeps reverting to 1, a Group Policy is probably overriding it.
Run gpresult /H c:\gpresult.html and open the file to check the policy Allow users to connect remotely by using Remote Desktop Services.
If you are on a work PC, ask the IT administrator rather than editing policies yourself.
Test the network and the firewall
Run this from another PC on the same network in an elevated PowerShell window, using the remote PC’s name or address:
Test-NetConnection -ComputerName PCNAME -Port 3389 -InformationLevel Detailed
| Result | Meaning |
|---|---|
| TcpTestSucceeded: True | No connectivity problem. Look at the listener, services and your account. |
| TcpTestSucceeded: False | Something is blocking the connection or the port is wrong. |
The default Remote Desktop port is 3389.
In Windows Defender Firewall with Advanced Security, open Inbound Rules and make sure Remote Desktop – User Mode (TCP-In) and Remote Desktop – User Mode (UDP-In) are enabled for all profiles.
Check that no other program is listening on port 3389, because the process using it should be TermService.
Connecting from outside your home network
Microsoft says access from outside the local network needs port forwarding or a VPN.
It also says to enable Remote Desktop only on trusted networks such as a home network, and to leave it off if you only use the PC locally.
Keep Network Level Authentication on
Network Level Authentication makes users authenticate before a session starts, which reduces the risk of unauthorized access and malicious software.
Microsoft recommends it for most environments, and says to turn it off only temporarily for older clients that cannot use it.
Never give Remote Desktop access to a caller
Microsoft warns that tech support scammers ask for remote access to your device.
It does not make unsolicited calls to offer technical support, and its error messages never include a phone number.
For family help where the owner is sitting at the PC, Quick Assist is the simpler option, since the owner approves each session.
If Windows sign-in is the problem, see our guide on fixing the Windows sign-in error.