When Remote Desktop is not working, the cause is usually one of four things: the PC you're connecting to runs Windows 11 Home, Remote Desktop isn't switched on, a firewall or network setting is blocking port 3389, or your sign-in details aren't accepted. Check them in that order. Start with the edition, because Home can't accept incoming Remote Desktop connections at all. That's the one cause no setting change can fix.
Why Is Remote Desktop Not Working? Quick Diagnosis
The message you see points to the cause. Use this table to jump to the right fix:
| Symptom | Most likely cause | Where to look |
|---|---|---|
| No Remote Desktop option in Settings on the remote PC | The remote PC runs Windows 11 Home | Check the edition and upgrade to Pro |
| "Remote Desktop can't connect to the remote computer" | Remote Desktop is off, the PC is asleep or off, or the network is blocking it | Remote Desktop settings, firewall, network profile |
| Connection times out by PC name but works by IP address | Name resolution (DNS) problem | Connect by IP address and fix DNS |
| "Your credentials did not work" | Wrong username format, a PIN instead of a password, or the user isn't allowed | Account name, password and Remote Desktop users |
| Worked before, stopped after a change | A policy, service or port change, or a new security prompt | Services, Group Policy, update history |
Can Windows 11 Home Accept Remote Desktop Connections?
No. Windows 11 Home can start Remote Desktop connections to other PCs, but it can't be the PC you connect to. Microsoft's Remote Desktop guide says the remote PC must run a Pro edition of Windows. The device you connect from can run Home, macOS, iOS or Android.
To check, open Settings → System → About on the remote PC and look at Edition under Windows specifications. If it says Windows 11 Home, no firewall or registry change will make it a supported Remote Desktop host. The fix is an edition upgrade, which keeps your files and apps. Our guide on how to upgrade Windows 11 Home to Pro walks through it, and our Windows 11 Home vs Pro comparison explains what else Pro adds.
How Do You Check That Remote Desktop Is Turned On?
Remote Desktop is off by default, even on Pro. On the remote PC:
- Open Settings → System → Remote Desktop.
- Turn on Remote Desktop and select Confirm.
- Note the PC name shown on that page. That's the name you'll type on the other device.
- Leave Network Level Authentication turned on. It checks your credentials before a full session starts, which reduces the PC's exposure to attacks.
- Make sure the PC isn't set to sleep. A sleeping PC doesn't answer connection requests. Adjust this in Settings → System → Power & battery.
Then connect from the other device. On Windows, search for Remote Desktop Connection and enter the PC name. On a Mac, iPhone or iPad, use Microsoft's Windows App. On Android, use the Remote Desktop app from Google Play.
How Do You Fix Remote Desktop Not Connecting on Your Network?
If Remote Desktop is on but you can't connect, something between the two devices is blocking traffic on TCP port 3389. Work through these checks on the remote PC:
- Set the network to Private. Go to Settings → Network & internet → Wi-Fi (or Ethernet), select your network and choose Private network. On Public networks, Windows is stricter about incoming connections.
- Check the firewall rule. Open Control Panel → Windows Defender Firewall → Allow an app or feature through Windows Defender Firewall and make sure Remote Desktop is ticked for the Private profile. A third-party security suite may have its own firewall that needs the same exception.
-
Test the port. On the device you're connecting from, open PowerShell and run
Test-NetConnection -ComputerName PC-NAME -Port 3389. If TcpTestSucceeded shows False, a firewall or the network is still blocking the connection. - Try the IP address. If connecting by IP address works but the PC name doesn't, the problem is name resolution, not Remote Desktop. Our guide to fixing DNS lookups on Windows covers that.
Connecting from outside your home or office is a separate problem. Don't open port 3389 directly to the internet on your router, because exposed Remote Desktop ports are a frequent attack target. Use a VPN into your network, or a remote access service, and then connect as if you were on the local network.
What If Remote Desktop Connects but Won't Sign You In?
A credentials error means the network path works and the problem lies with the account. Check these in order:
- Use a password, not a PIN. A Windows Hello PIN only works on the device it was set up on. Over Remote Desktop, sign in with the account's password.
- Use the right username format. For a Microsoft account, enter the full email address. For a local account, use the PC name followed by a backslash and the username, for example PC-NAME\username.
- Check passwordless settings. If the remote PC is set to allow only Windows Hello sign-in for Microsoft accounts, password sign-in over Remote Desktop may be refused. This option is in Settings → Accounts → Sign-in options.
- Allow the user. Administrators can connect by default. Other accounts must be added under Settings → System → Remote Desktop → Remote Desktop users.
How Do You Fix the Remote Desktop Service Itself?
If the settings look right but connections still fail, check the Remote Desktop service on the remote PC. These are the checks in Microsoft's general Remote Desktop troubleshooting guide:
- Press Win+R, type
services.mscand confirm that Remote Desktop Services and Remote Desktop Services UserMode Port Redirector are running. Start them if they aren't. - Open Command Prompt as administrator and run
qwinsta. A line showing rdp-tcp with the state Listen means the service is ready for connections. - Run
netstat -ano | find "3389"to make sure no other program is using port 3389. - If the Remote Desktop toggle keeps switching itself off, a Group Policy may be overriding it. Run
gpresult /H c:\gpresult.htmland look for the policy Allow users to connect remotely by using Remote Desktop Services. On a work PC, this is set by your IT team.
If Remote Desktop stopped working after a Windows update, look at what changed. Since the April 2026 security update, opening a saved .rdp file shows every setting the file requests, such as drive or clipboard sharing, with each one turned off until you allow it. Shared drives that seem to have "broken" often just need ticking again in that dialog.
A Common Mistake We See
The most common mistake is spending hours on firewall rules and registry edits for a PC that runs Windows 11 Home. Online guides that "enable" hosting on Home rely on unsupported workarounds that can break after updates and fall outside Microsoft's licence terms. The supported fix is a Windows 11 Home to Pro upgrade key, which turns on Remote Desktop hosting without a reinstall.
Servers are a different case. Windows Server allows two simultaneous administrative sessions without extra licensing. More users need the Remote Desktop Services role with RDS CALs installed, as our guide to applying and activating RDS CALs explains. If you see a "busy" message instead, our Remote Desktop Services is currently busy fix covers that error.
Frequently Asked Questions
Why does Remote Desktop not work on Windows 11 Home?
Windows 11 Home includes only the Remote Desktop client, so it can connect out to other PCs but can't accept incoming connections. Microsoft requires the remote PC to run Windows Pro or a higher edition. Upgrading Home to Pro adds the Remote Desktop host feature without reinstalling Windows or losing your files.
Why is Remote Desktop not connecting even though it's enabled?
The usual causes are a network set to Public, a firewall blocking TCP port 3389, a sleeping remote PC, or a PC name that doesn't resolve to the right address. Test the port with Test-NetConnection and try the IP address instead of the name. Check any third-party firewall too.
Why does Remote Desktop say my credentials did not work?
Remote Desktop needs the account password, not a Windows Hello PIN. Use your full Microsoft account email address, or PC-NAME\username for a local account. Also confirm that the account is an administrator or is listed under Remote Desktop users on the remote PC, because other accounts are refused.
Can I use Remote Desktop over the internet?
Yes, but don't forward port 3389 on your router directly to the PC, because exposed Remote Desktop ports attract constant attacks. Connect through a VPN to your network first, or use a secure remote access gateway. Then start Remote Desktop as if you were on the local network.
Why did Remote Desktop connection stop working after an update?
Check whether a policy reset the setting, whether the Remote Desktop services are still running, and whether a security prompt is waiting. Since April 2026, .rdp files show each requested setting turned off until you approve it. If a specific update is to blame, Windows release health lists known issues.
Do I need a different app to connect from a Mac?
Yes. On macOS, iPhone and iPad, Microsoft's Windows App, available from the Apple App Store, replaces the older Remote Desktop client. Add the remote PC's name, sign in with its account details and connect. The remote PC still needs Windows 11 Pro with Remote Desktop turned on.
Conclusion
Most cases of Remote Desktop not working come down to the edition, the Remote Desktop toggle, the firewall and network profile, or the sign-in details. Check them in that order and you'll find the cause quickly. If the PC you want to reach runs Home, a genuine upgrade from our Windows 11 collection is the supported way to enable Remote Desktop hosting.
Useful Links
| Resource | Link |
|---|---|
| Windows 11 licences | Windows 11 collection |
| Home to Pro upgrade key | Windows 11 Home to Pro Upgrade |
| Upgrade walkthrough | How to Upgrade Windows 11 Home to Pro |
| Edition comparison | Windows 11 Home vs Pro |
| Server session errors | Remote Desktop Services Is Currently Busy fix |
| Remote Desktop setup (Microsoft) | How to use Remote Desktop |
| Troubleshooting (Microsoft) | General Remote Desktop connection troubleshooting |
Deixe um comentário