Remote Desktop Not Working on Windows 11: The Pro-Only Rule and 9 Fixes

If Remote Desktop won't connect on Windows 11, the single most common cause has nothing to do with settings: the PC you're trying to reach is running Windows 11 Home, and Home has never been able to host an incoming Remote Desktop connection — not with a registry tweak, not with a hidden setting, not ever. A closed padlock icon doesn't mean Remote Desktop is protected on that PC; it means Windows Defender Firewall is quietly doing exactly what it's supposed to do, and on a Home edition, the feature it's guarding was never installed at all. If your PC is Pro, Enterprise, or Education, the error almost always traces to one of eight other things, and every one of them has a fix below, cheapest first.

Jake's spent two Saturdays on this, and it cost him more than time — a supplier called about a bulk order while he was mid-sale, and by the time Jake got upstairs to the flat to check the inventory PC, the call had gone to voicemail and the order went to someone else who answered faster. He wants to pull up his shop's inventory PC from the flat without walking down every time a supplier calls. Every attempt gives him the same wall of text: Remote Desktop can't connect to the remote computer for one of these reasons. Three reasons, no indication which one applies, and a search box that returns results written for Windows Server 2012.

Why that error never tells you which of the three it is

The message lists three generic reasons — remote access isn't enabled, the computer is off, or it's not on the network — because the client machine genuinely can't tell which one is true. All it knows is that it sent a connection request on port 3389 and got nothing back before the timeout. That single symptom can be caused by a missing feature, a toggle, a firewall rule, a network profile, a mismatched security setting, a sleeping PC, a closed router port, or bad credentials arriving too late in the process to even show a different error. This post walks them in the order that actually finds the problem fastest: things that make Remote Desktop impossible first, then things that make it merely blocked.

First, confirm this PC can host Remote Desktop at all

Microsoft's own support documentation states it plainly: you can use Remote Desktop to connect to Professional and Enterprise editions of Windows, and you can't connect to a Home edition. That rule hasn't changed for Windows 11 — the PC you want to reach (the host) must be Windows 11 Pro, Enterprise, or Education. The PC you're connecting from (the client) can be any edition, including Home, or even a phone.

To check which edition a PC is running: Settings > System > About, and look at Edition under Windows specifications. If it says "Windows 11 Home," Settings won't even show a Remote Desktop item under System — the page genuinely isn't there, which is why so many people assume they've missed a hidden toggle. They haven't. It's a feature that Home simply doesn't ship.

Fix 1: Confirm Remote Desktop is actually turned on

This sounds too obvious to be the answer, and it's the fix more often than anything on this page. Windows 11 moved this out of Control Panel entirely — there's no "Allow remote access" link the way there was for years, which trips up anyone following an old guide.

1. Press Win + I to open Settings, or Start > Settings.
2. Select System, then Remote Desktop.
3. Set the Remote Desktop toggle to On, then select Confirm on the pop-up.
4. Note the PC name shown on this page — you'll type it into Remote Desktop Connection or the Windows App on the client side.
5. Select Remote Desktop users and confirm the account you're signing in with is listed, or add it with Add.

Members of the Administrators group can always connect without being added to that list — anyone else on the PC needs to be added explicitly, or the connection will be refused after the password is entered rather than before, which is a different failure point covered under credentials below.

Fix 2: The network profile trap — Public vs. Private

This is the one nobody thinks to check, because it isn't part of the Remote Desktop settings page at all — it's a network setting that silently overrides everything else. Windows Firewall treats every network connection as belonging to one of three profiles: Domain, Private, or Public. On a Public profile, inbound connections including RDP's port 3389 are blocked by default, no matter what the Remote Desktop toggle says.

To check and fix it: Settings > Network & internet, select your active Wi-Fi or Ethernet connection, and look at Network profile type. If it says Public, switch it to Private — but only do this on a network you actually trust, like your home or the shop's own router, never on a café or airport connection.

Jake had already worked this one out by the time he called Ethan, but only by accident. "Mine's set to Private already, so that's not it, right?" Ethan wasn't so sure it would stay that way. "Check it again after your next Windows Update," he said. "Private isn't a setting Windows treats as sacred — it's just the default state until something resets it. I'd rather you know to look than assume it's fixed forever."

Fix 3: Windows Defender Firewall rules

Turning on Remote Desktop in Settings should automatically enable the matching firewall rules, but third-party antivirus suites, IT management tools, or a manual "harden this PC" pass can leave them disabled even while the feature itself shows as on. Open Windows Defender Firewall — type firewall.cpl into the Run box (Win + R, then type it and press Enter) — select Advanced settings, then Inbound Rules. Find Remote Desktop (TCP-In) and Remote Desktop - User Mode (TCP-In). Both should show a green checkmark, meaning enabled, for whichever profile (Private, Public, or Domain) matches your network. Right-click a disabled rule and choose Enable Rule.

If you'd rather use the simpler view: Settings > Privacy & security > Windows Security > Firewall & network protection > Allow an app through firewall, find Remote Desktop in the list, and make sure the checkbox is ticked for your current network type.

This is the one that got Jake's shop PC, as it turned out — a free antivirus bundle from his internet provider had quietly disabled the Domain and Private profile rules for Remote Desktop during its own install, months before he ever tried to connect remotely. Nothing in the antivirus app mentioned it. Ethan's take: "That's the annoying part of layered security tools — they each think they're the only one guarding the door, so they don't always tell you what they've locked."

Fix 4: Network Level Authentication mismatch

Network Level Authentication (NLA) makes the client prove your credentials before a full remote session even starts, rather than after — it's a security improvement, and it's on by default. It usually isn't the cause of a total connection failure, but it does explain a specific variant: the connection reaches the PC, then fails with a message about the remote computer requiring Network Level Authentication that the client doesn't support. That mismatch shows up most often when the client is an older device, a non-Windows RDP app, or when a VPN or an older cumulative update has left the two ends disagreeing.

On the host: Remote Desktop settings > Advanced settings, and look at "Require devices to use Network Level Authentication to connect." Ethan's advice on this one is blunt: don't turn it off as a first move. "It's the last checkbox on this whole list I'd touch. Turning off NLA to fix a connection problem is like taking the lock off your door because the key stopped fitting — you should get the key fixed first."

Fix 5: The PC is asleep, hibernating, or shut down

A sleeping PC's network adapter goes quiet along with everything else, so the second listed reason in the error — "the remote computer is turned off" — is exactly what's happening even though the PC looks fine sitting on a desk with its power light off, when really it's just in a low-power state. Two options: change the power plan so the host never sleeps when it's meant to be reachable (Settings > System > Power > Screen and power, set "When plugged in, put my device to sleep after" to Never), or set up Wake on LAN so a "magic packet" from the client wakes it on demand.

Wake on LAN needs three things lined up: the network adapter's power management settings must allow it to wake the computer (Device Manager > Network adapters > right-click the adapter > Properties > Power Management tab), the option must also be enabled in the adapter's Advanced tab if present, and the motherboard's BIOS/UEFI must have Wake on LAN enabled. If any one of those three is off, the magic packet arrives and nothing happens — there's no error message, the PC just stays asleep.

Ethan's preference for a shop PC like Jake's is simple: "Just stop it sleeping. Wake on LAN is neat, but it's three separate settings that all have to agree, and any one of them can quietly stop agreeing after a driver update. A PC that's plugged in behind a counter doesn't need to save power that badly."

Fix 6: Wrong credentials or missing group membership

If you get further than the generic "can't connect" error and instead reach a sign-in prompt that then rejects your password, the problem has shifted from network to identity. Two common causes: you're typing a local account password when the PC actually expects the Microsoft account password (or the reverse), or your account genuinely isn't in the Remote Desktop Users group.

To add a user to that group without digging through menus, open an elevated Command Prompt or PowerShell on the host and run:

1. Right-click Start, choose Terminal (Admin).
2. Run net localgroup "Remote Desktop Users" "UserName" /add, replacing UserName with the actual account name.
3. Confirm it worked with Get-LocalGroupMember -Group "Remote Desktop Users" in PowerShell.

Administrators never need to be added — they can always connect. If the account you're trying to use is a standard (non-admin) account and isn't on that list, this is almost certainly why credentials keep failing even though you're sure the password is right.

"Wait, so my part-time employee's account could be the problem and not mine?" Jake asked, once he realized the PC he'd been testing from used his own admin account the whole time. That was exactly it — his own login worked because he's an administrator, but the account he actually wanted to use for the till PC wasn't in the Remote Desktop Users group at all, and never would have connected no matter how many other settings got fixed.

Fix 7: Connecting from outside the local network

Everything above assumes both PCs are on the same network. Reaching a PC from a different network — from the coffee shop into the house, or from Jake's flat into his shop — needs one more piece: your router has to forward RDP's port (TCP 3389 by default) to the host PC's local IP address, or you need a VPN into that network instead.

1. Find the host PC's local IP address: Settings > Network & internet > your connection > look for IPv4 address (or run ipconfig in a Command Prompt).
2. Log into the router's admin page — usually 192.168.1.1 or 192.168.0.1, printed on the router itself.
3. Find Port Forwarding (sometimes under Firewall or NAT settings) and create a rule sending external TCP port 3389 to the host PC's local IP address on port 3389.
4. From outside the network, connect using the router's public IP address (or a dynamic DNS hostname if the public IP changes) rather than the PC's local IP.

Ethan doesn't love recommending step three on its own. "Port forwarding works, and I'll walk anyone through it, but if it's genuinely just you needing access from the flat above the shop, a VPN into the same router does the same job without leaving 3389 sitting open to the entire internet. I'd rather spend twenty extra minutes setting up a VPN once than explain a compromised PC later."

Fix 8: Using the right client — the Remote Desktop app is gone

If you're following an older guide and it tells you to download "Remote Desktop" from the Microsoft Store, that app stopped being supported and available starting May 27, 2025. It's been replaced by the Windows App, which handles the same connections plus Windows 365 and Azure Virtual Desktop. If your connection attempts are silently failing from a phone or another PC, check first that you're actually using a current client rather than a leftover install of the old app that Microsoft no longer updates.

On a Windows PC you can also skip the app entirely and use the classic built-in tool: type Remote Desktop Connection into the Start menu search box, enter the PC name noted earlier, and select Connect.

Jake's phone still had the old Store app installed from a promo he'd forgotten about — it opened, it just never found the PC, no matter how many times he retyped the name. Swapping to the Windows App fixed that particular dead end in under a minute, which he pointed out was "the first thing today that just worked."

Fix 9: When it worked yesterday and doesn't today

"Nothing changed" is rarely true after Windows installs a cumulative update — something changed, it just wasn't a setting you touched. The pattern reported often enough to be worth checking first: a Windows Update or restart resets a network connection's profile from Private back to Public, silently re-blocking RDP through the reasoning covered in Fix 2. It's worth checking Network & internet > your connection > Network profile type again after any update, even if you're sure you set it to Private before.

As of this writing, Microsoft hasn't listed a known Remote Desktop-specific issue for the current August 2026 cumulative updates — so don't assume the update itself is broken before checking the ordinary suspects above. If you want to see what a given update actually changed on your PC before troubleshooting further, our breakdown of the August 2026 Windows 11 update covers what shipped and what to watch for. If it's the taskbar or File Explorer behavior that changed around the same time rather than Remote Desktop itself, that's a separate, unrelated change covered in our taskbar position update post.

On Windows 10, the same rule applies — with one extra warning

Windows 10's Remote Desktop settings live in the same place as Windows 11's — Settings > System > Remote Desktop — and every fix above applies identically: the Home edition still can't host, the network profile still needs to be Private, the firewall rules and NLA settings work the same way. All nine fixes are the same on both.

The one thing specific to Windows 10: it reached the end of free support on October 14, 2025, and that date has already passed. A Windows 10 PC still boots, runs, and can host Remote Desktop exactly as before, but it no longer receives free security updates outside of Extended Security Updates (ESU). If the PC you're trying to remote into is on Windows 10 22H2, you can still enroll it in consumer ESU through Settings > Windows Update > "Enroll now" — it requires a Microsoft account and covers the device for free if you sync settings through Windows Backup, for 1,000 Microsoft Rewards points, or for a one-time roughly $30 fee, and coverage now runs to October 2027 following a later extension. None of that changes whether Remote Desktop itself works — it's just worth knowing before you invest more time troubleshooting a machine that's otherwise going unpatched.

When none of this works

Two last things worth checking before deciding the PC itself has a deeper problem. First, confirm the RDP listener is actually running on the host: open an elevated Command Prompt and run qwinsta. You're looking for a line reading rdp-tcp in a Listen state. If it isn't there, the Remote Desktop Services aren't running correctly and a restart of the host, or the "Remote Desktop Services" service via services.msc, is the next step. Second, check Event Viewer on the host under Windows Logs > System and Applications and Services Logs > Microsoft > Windows > TerminalServices-LocalSessionManager for errors around the time you attempted to connect — they won't fix anything by themselves, but they'll tell you whether the connection attempt reached the PC at all, which narrows the problem to either the network path or the RDP service itself.

If you've been through every fix above and it still won't connect, that's a genuine signal to stop and try a different approach rather than keep guessing: a fresh restart of both PCs (not sleep — a full restart), a temporary disable of third-party antivirus to rule out software firewalls layered on top of Windows Defender Firewall, or, if none of that moves the needle, a third-party remote access tool as a stopgap while you dig further. There's no shame in that — RDP is powerful, but it's also one of the more finicky built-in Windows features, and admitting a particular PC needs more time isn't a failure, it's just where troubleshooting sometimes ends for the day.

For Jake, it never got that far — the firewall rule in Fix 3 turned out to be the whole problem, and once he re-enabled it, the connection to his inventory PC came up on the first try. The next time a supplier called mid-sale, he pulled up stock levels from his phone before the call ended.

Frequently asked questions

Can I use Remote Desktop with Windows 11 Home?

Not as the host. Windows 11 Home can start a Remote Desktop session to another PC as the client, but it can't receive one — that ability is limited to Pro, Enterprise, and Education editions.

Why did Remote Desktop stop working after an update?

The most commonly reported cause is the network connection's profile getting reset from Private to Public during the update or the restart that follows it, which quietly re-blocks inbound RDP through Windows Firewall. Check Settings > Network & internet > your connection > Network profile type first.

What port does Remote Desktop use, and do I need to open it?

RDP uses TCP port 3389 by default. You only need to open or forward it on your router if you're connecting from outside your local network — on the same network, Windows Firewall just needs the built-in Remote Desktop rules enabled.

How do I know if my PC is on a Private or Public network?

Go to Settings > Network & internet, select your active connection (Wi-Fi or Ethernet), and check the Network profile type field. It shows Public or Private plainly.

Can I connect to a Windows 11 PC from an iPhone or Android?

Yes, using the Windows App, available for iOS, Android, macOS, and Windows. The host PC still needs to be Pro or above with Remote Desktop enabled, exactly as when connecting from another PC.

Why does it say the remote computer requires Network Level Authentication?

The host has NLA turned on (the default) and the device you're connecting from doesn't support it or isn't negotiating it correctly — often an outdated client app or a VPN interfering with the connection. Update the client first rather than disabling NLA on the host.

What's the difference between Remote Desktop Connection and the Windows App?

Remote Desktop Connection (mstsc.exe) is the classic built-in Windows tool. The Windows App is the current cross-platform client, which replaced the old Microsoft Store Remote Desktop app after that app stopped being supported on May 27, 2025. Both connect to the same RDP host feature.

Can I remote into my PC over the internet without port forwarding?

Yes — set up a VPN into the home or office network and connect over that instead of forwarding port 3389 directly to the internet. It's the safer option since it doesn't expose RDP to public scanning.

Why does Remote Desktop work at home but not from outside?

Inside the house, both devices are on the same network and the connection never has to leave the router. From outside, the connection needs port forwarding on the router or a VPN — without one of those, the request never reaches the PC.

How do I add another user who's allowed to connect?

Settings > System > Remote Desktop > Remote Desktop users > Add, or run net localgroup "Remote Desktop Users" "UserName" /add from an elevated Command Prompt. Administrators can always connect without being added.

Can I Remote Desktop into a PC that's asleep?

Not directly — a sleeping PC's network adapter isn't listening for RDP traffic. Either set the host to never sleep while it should be reachable, or configure Wake on LAN so a signal from the client wakes it before you connect.

Is Remote Desktop safe to leave enabled all the time?

On a local network with NLA on and a strong password, it's reasonable. Forwarded straight to the internet on port 3389, it's a known target for automated attacks, so a VPN is the safer way to reach it remotely.

Why do I get a black screen or freeze after connecting?

This is a different problem from a failed connection — it happens after the session establishes. Check Event Viewer's TerminalServices-LocalSessionManager log for errors around that time, and confirm the host's graphics driver and Windows are both current.

What if I don't know the admin password?

You're not getting in. Remote Desktop requires valid credentials for an account with permission on that PC — there's no bypass through the RDP client itself, and there shouldn't be.

Do I need Remote Desktop Users group membership if I'm already an administrator?

No. Members of the local Administrators group can always connect via Remote Desktop, regardless of whether they're also listed in the Remote Desktop Users group.

Can two people use Remote Desktop on the same Windows 11 PC at once?

Not on a standard Windows 11 Pro license — connecting remotely signs out (or locks) whoever's using the PC locally, and only one remote session is supported at a time on client editions of Windows.

Revision note. Written September 2026, covering Windows 11 25H2 and 24H2 and current Windows 10 22H2. This will need a revisit if Microsoft changes where the Remote Desktop settings live or shifts the Home/Pro hosting rule in a future release.so refer latest details on MS website if not worked or let me know through contact us page, i will check and update... If you've spent an evening on this error already, you're not missing something obvious — RDP just has more moving parts than the error message admits, and you'll get there.