Enable Remote Desktop in Windows 11: Settings, PowerShell, Home

Check your edition first: Home cannot host RDP

Remote Desktop has two sides: the client you connect from and the host that accepts the connection. Every Windows 11 edition includes the client, but only Pro, Enterprise, and Education include the host service. Windows 11 Home can connect out to other machines all day long; it cannot accept an incoming session itself. If the protocol is new to you, start with what RDP actually is and how it works — the rest of this guide deals with switching the host side on.

Check which edition you are running from PowerShell:

(Get-ItemProperty 'HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion').EditionID

Professional means you are good to go. Core means Home — skip straight to the Windows 11 Home section below, because the toggle you are about to look for does not exist on your machine.

Method 1: turn it on in Windows 11 Settings

The GUI route takes under a minute and opens the firewall for you.

1. Open the Remote Desktop settings page

Press Win + I and go to System > Remote Desktop.

2. Enable the toggle

Switch Remote Desktop to On and click Confirm in the dialog. Leave the Network Level Authentication requirement checked — it forces clients to authenticate before Windows creates a session, and there is no good reason to turn it off on any modern network.

3. Note the PC name and allowed accounts

The same page shows the PC name you will type into the client later. By default only members of the Administrators group may connect; click Remote Desktop users to allow a standard account instead of handing out admin credentials.

Method 2: enable RDP with PowerShell

For scripted setups, or when you are already in a shell anyway, two lines in an elevated PowerShell do the whole job:

Set-ItemProperty -Path 'HKLM:\SYSTEM\CurrentControlSet\Control\Terminal Server' -Name 'fDenyTSConnections' -Value 0
Enable-NetFirewallRule -DisplayGroup "Remote Desktop"

The first command writes the same registry value the Settings toggle flips: fDenyTSConnections = 0 allows incoming sessions. The second enables the built-in firewall rules for RDP. On a non-English Windows install the display group name is localized and that second command fails, so target the rules by their stable internal names instead:

Enable-NetFirewallRule -Name "RemoteDesktop-UserMode-In-TCP","RemoteDesktop-UserMode-In-UDP"

Two sensible follow-ups: enforce NLA explicitly, then confirm the listener answers.

Set-ItemProperty -Path 'HKLM:\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp' -Name 'UserAuthentication' -Value 1
Test-NetConnection -ComputerName localhost -Port 3389

If the output ends with TcpTestSucceeded : True, the host side is up and listening.

Make sure the firewall is really open

Both methods above handle Windows Defender Firewall automatically, but two things still block connections in practice:

• Third-party security suites. If your antivirus replaces the Windows firewall, add an inbound allow rule for TCP and UDP 3389 in its own console.
• Network profile mismatch. Firewall rules apply per profile (Domain, Private, Public). Run Get-NetConnectionProfile to see which profile your current network uses, then check the RDP rules are enabled for it.

Get-NetFirewallRule -DisplayGroup "Remote Desktop" | Select-Object Name, Enabled, Profile

RDP listens on TCP and UDP port 3389 by default. You can move it to another port, but read our guide to RDP port 3389 — and what changing it does and does not get you first: a non-standard port keeps your logs quieter, it does not make the service any harder to break into.

Connect from another device

On the host, grab the two identifiers a client can target:

hostname
ipconfig | findstr IPv4

• From Windows: press Win + R and run mstsc /v:PC-NAME, or open the Remote Desktop Connection app, then sign in with an allowed account.
• From macOS, iOS, or Android: install Windows App (formerly Microsoft Remote Desktop) from the platform's store and add the PC by name or IP.

A note on credentials, because this trips up more first connections than the firewall does: for a local account, sign in as PC-NAME\username (or .\username), and for a Microsoft account use the full email address you sign in to Windows with — the same password you type at the lock screen. If the account has no password at all, RDP refuses the login by default; set one before connecting.

On the same local network this works immediately. From outside your network, resist the urge to forward port 3389 on your router — connect through a VPN into your LAN instead, as covered in the security section below.

Two classic failure modes are worth knowing up front. A sleeping host does not answer at all — set sleep to Never when plugged in, under Settings > System > Power & battery. And if the client sits on the connecting screen before giving up, work through fixing a Remote Desktop connection timeout — it is almost always a firewall, profile, or routing issue rather than RDP itself.

Windows 11 Home: the real answer

There is no supported way to make Windows 11 Home accept RDP connections. The host functionality is disabled at the licensing level, so flipping fDenyTSConnections by hand achieves nothing, and the Settings toggle is simply absent. Guides that promise otherwise usually point to RDP Wrapper, a third-party patch that reactivates the host service — it breaks unpredictably with Windows updates and violates the Microsoft license terms, which makes it a poor foundation for anything you rely on.

The honest options:

• Upgrade to Pro. Go to Settings > System > Activation > Upgrade your edition of Windows; it is a one-time US$99 purchase through the Microsoft Store. Files and apps stay in place, and you get the RDP host plus BitLocker and Group Policy.
• Use a different remote-control tool. Chrome Remote Desktop, AnyDesk, or RustDesk can drive a Home PC. They are fine for occasional access, but they are not RDP, and the PC still has to stay on and connected at home.
• Rent a Windows VPS. If what you actually want is "a Windows machine I can reach over RDP from anywhere", a Windows Server VPS ships with the host enabled out of the box — no edition restrictions, and it stays online when your laptop does not.

Lock it down before you rely on it

A fresh RDP host is a remote login portal into your machine; treat it like one.

• Keep NLA on. Network Level Authentication makes the client authenticate before Windows spins up a session, which shuts out a whole class of pre-authentication attacks.
• Connect with a dedicated standard account. Add it with Add-LocalGroupMember -Group "Remote Desktop Users" -Member "yourname" and keep your admin account out of sessions that do not need it.
• Never expose 3389 directly to the internet. Internet-wide scanners find newly opened RDP ports and start hammering them with password guesses. Use a VPN — WireGuard, Tailscale, or your router's built-in server — and keep RDP reachable only inside it. A non-standard port does not change this.
• Check the lockout policy. Windows 11 22H2 and later lock an account for 10 minutes after 10 failed sign-ins by default; run net accounts to confirm it is active on yours.

If the real blocker is the machine itself — no Pro license, or no desire to keep a home PC awake and reachable around the clock — you can skip the whole exercise: a Windows VPS with RDP comes with everything in this guide already configured, full admin access on dedicated CPU and RAM, no KYC at checkout, and it is ready about 10 seconds after payment confirms. Log in with the credentials on screen and you are exactly where this tutorial ends.

Frequently Asked Questions

Is Remote Desktop free on Windows 11?

Yes — the RDP host is included in Pro and higher, and the client apps are free on every platform.

There is no separate license to buy for personal remote access. Windows 11 Pro, Enterprise, and Education include the Remote Desktop host, and the clients — Remote Desktop Connection (mstsc) on Windows and Windows App on macOS, iOS, and Android — cost nothing. What Microsoft does charge for is the Pro upgrade itself if you are on Home, and per-user licensing when many people share a Windows Server host.

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

No — client editions of Windows allow only one interactive session at a time.

When you connect over RDP, whoever is signed in at the physical screen gets disconnected (Windows asks them to confirm), and the other way around. This is a licensing restriction on all client editions, including Pro. If you need several people working on one Windows machine simultaneously, that is what Windows Server with Remote Desktop Services and per-user licensing is for — or simply one VPS per user.

Why is the Remote Desktop toggle missing in my Settings?

You are almost certainly on Windows 11 Home, which has no RDP host.

Check your edition with winver: on Home the host toggle is simply not offered, and no registry edit brings it back. On Pro machines managed by a company, Group Policy can also hide or disable the setting — ask your IT department. Finally, make sure you are looking under Settings > System > Remote Desktop, not the older Remote Assistance options in Control Panel.

Does Remote Desktop work when the PC is asleep or hibernating?

No — the host must be awake; RDP cannot wake a sleeping machine by itself.

A sleeping or hibernating PC does not answer on port 3389, so the client just times out. Set sleep to Never while plugged in (Settings > System > Power & battery) on any machine you want to reach remotely. Wake-on-LAN can work around it, but it needs BIOS and adapter support plus extra configuration to trigger from outside your network — most people keep the host awake or use an always-on server instead.