I’m trying to turn on Remote Desktop in Windows 11 so I can access my PC from another room, but I can’t find the right setting and the steps I found online don’t match what I see. I need help enabling Remote Desktop and making sure my Windows 11 PC is set up correctly.
I ran into this the hard way, so here’s the short version.
Check your Windows edition first. If your PC is on Windows 11 Home, it will not accept Remote Desktop connections as the host. You need Pro or Enterprise for that part.
If your edition supports it, do this:
Settings → System → Remote Desktop, then switch it On.
Windows usually adds the firewall exception on its own. After that, add the user accounts you want to let in, then note your PC name so you have the right target when connecting.
From the other computer, open mstsc, enter the PC name, and connect.
If you want the full walk-through with screenshots, this one helped me: enable Remote Desktop on Windows 11 (guide)
36 Likes
If the menu path looks wrong, use search instead of hunting through Settings. Press Start, type remote desktop settings, open it from there. On some Windows 11 builds, Settings pages got moved around a bit, so old guides look off.
One thing I’d add to what @mikeappsreviewer said, check Services too. Press Win + R, type services.msc, then make sure Remote Desktop Services is not disabled. If it is, RDP won’t work even if the toggle is on.
Also, for same-house access, your PC needs to stay awake. Set Power mode so it doesn’t sleep after 5 mins or you’ll think RDP is broken. I hit this once and wasted an hour, lol.
If you only have Windows 11 Home, use Quick Assist, Chrome Remote Desktop, or RustDesk instaed. Those are easier for room-to-room access anyway.
One extra thing nobody’s mentioned clearly enough: if the toggle/page is missing entirely, check your sign-in type and policy settings, not just Settings. On some builds, Remote Desktop can be hidden or controlled by local policy.
Try this:
- Press Win + R
- Type SystemPropertiesRemote
- Hit Enter
That opens the old-school Remote tab directly, which is often easier than the Windows 11 Settings maze. If you see the option there, enable remote connections from that window.
If that tab says stuff is managed or grayed out, open:
- gpedit.msc
- Go to:
Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Connections
Make sure “Allow users to connect remotely by using Remote Desktop Services” is enabled.
I’ll slightly disagree with @boswandelaar on the Services part. Usually if the feature is enabled properly, Windows handles the needed service state by itself, so I would check policy/admin restrictions before digging around in services.msc. Messing in Services is not always the first move ppl should make.
Also, if you are connecting by Microsoft account, sometimes entering the username as:
MicrosoftAccount\youremail@example.com
works better than just your email.
And if name-based connection fails, use the PC’s local IP address instead:
- Open Command Prompt
- run
ipconfig - use the IPv4 address in Remote Desktop Connection
@mikeappsreviewer already covered the edition limitation, which is the big gotcha. If you’re on Home, that’s probly why this feels weirdly missing.
Small add-on to what @boswandelaar, @byteguru, and @mikeappsreviewer already covered: if the Remote Desktop switch turns on but connections still fail, check Network Profile. In Windows 11, go to Settings > Network & internet > Properties for your active connection and make sure it’s set to Private, not Public. Public networks can block discovery and make the PC harder to reach even on the same house Wi-Fi.
I’d also avoid over-focusing on services.msc at first. @boswandelaar is not wrong, but in most home setups the more common issue is edition, firewall profile, sleep, or wrong account name.
Another thing people miss: if you use a laptop with lid closed in another room, it may stop networking depending on power settings. So even if sleep is disabled, the closed-lid behavior can still kill access.
If Windows 11 Home is what you have, built-in hosting is the dead end. Pros of ': could make remote access easier to read and follow if it includes simpler setup guidance. Cons of ': no clear value unless it actually offers something beyond native Remote Desktop or tools like Quick Assist/RustDesk.
Try AnyDesk instead. Install it on both PCs, open it, then enter the remote PC’s address from the other room. Enable unattended access and set a strong password so you do not need to approve each session.
Keep AnyDesk running at startup, disable sleep, and leave both devices on the same Wi-Fi. This works with Windows 11 Home and avoids edition checks, firewall rules, PC names, and mstsc setup. Instal it only from the official site, then test the connection before leaving the remote PC unattended.
For same-house, room-to-room access, expect this to be simpler than the thread makes it look. Most of the firewall, policy, and services stuff only becomes relevant when something is actually broken, and on a normal home PC it usually isn’t.
The edition check is the real first step, and @mikeappsreviewer nailed it. If you’re on Home, stop reading the RDP steps entirely. There’s no hidden toggle, no policy trick, no service you can flip to make Home act as a host. That’s a licensing wall, not a settings problem. So before you spend an hour on any of this, open Settings and confirm you’re on Pro.
On the @byteguru vs @boswandelaar thing about services.msc, I lean toward @byteguru here. Poking around in Services should be a last resort, not step three. If you enable the toggle and it doesn’t work, the cause is almost always the network profile or account name, not a disabled service. @espritlibre’s point about setting the network to Private is the one I’d check right after enabling, because a Public profile quietly blocks the connection and it looks like RDP is dead when it isn’t.
The thing nobody flagged: if you connect by IP address like @byteguru suggested, that IP can change. Home routers hand out addresses by DHCP, so the number from ipconfig today might be different next week after a reboot, and then you’re staring at a failed connection wondering what broke. Either use the PC name, or go into your router and set a DHCP reservation so that machine always gets the same local IP. Saves you the mystery later.
If it turns out you’re on Home, honestly don’t fight it. The AnyDesk and RustDesk suggestions above are fine, and Chrome Remote Desktop is probably the least fuss for plain room-to-room use since it rides through your Google account and skips the whole IP and firewall dance. Just remember whatever tool you pick, the sleep and closed-lid warning still applies. A laptop that suspends the second you walk away will make any of these look unreliable.