I’m trying to enable Remote Desktop on my Windows 10 PC so I can access it from another computer, but I can’t find the right setting and the connection isn’t working. I need help figuring out what to turn on and whether there’s anything else in Windows 10 I need to configure.
Windows 10 Home trips up a lot of people on this.
The short version, I ran into the same thing once. Home supports connecting out with the Microsoft Remote Desktop app, but it does not support acting as the host for incoming RDP sessions.
Windows 10 Home:
- lets you connect to another PC with the Remote Desktop client
- does not let other PCs connect into it over built-in RDP
So if the PC you want to reach is running Windows 10 Home, Microsoft’s built-in Remote Desktop host feature is off the table unless you move up to Pro.
What I found easiest was skipping unofficial RDP patch stuff. Third-party remote access tools are less messy and usually faster to set up.
If you want a clearer breakdown, this article covers the limits on Windows 10 Home and some ways around them with third-party remote access software like HelpWire:
how to allow rdp on windows 10
First, check your Windows edition. This is where most people get stuck.
If the target PC runs Windows 10 Pro, Enterprise, or Education:
- Open Settings.
- Go to System, then Remote Desktop.
- Turn on Remote Desktop.
- Click Confirm.
- Leave the PC powered on and awake.
Then verify these items:
- On the same page, note the PC name.
- Use a Windows account password on the host PC. Blank passwords often fail.
- In Windows Defender Firewall, make sure Remote Desktop is allowed.
- On your router or VPN, your network must permit RDP traffic on port 3389 if you are connecting from outside your home.
I slightly disagree with @mikeappsreviewer on one point. Upgrading to Pro is not always the best move if your goal is simple remote help or quick access across the internet. Built-in RDP works well on local networks, but over the internet it often turns into a port-forwarding mess, and that gets annoying fast.
If your PC runs Windows 10 Home, the Remote Desktop host switch will not appear. That edition does not accept incoming RDP sessions. At that point, your options are:
- upgrade the host PC to Pro
- use another remote access tool
For the second route, HelpWire is a clean option if you want remote access without fighting Windows edition limits. You can check it here, easy remote desktop access for Windows 10.
One more thing people miss. If the connection fails on your local network, try connecting with the host PC’s local IP address instead of the device name. Run ipconfig on the host PC and look for the IPv4 address. That fixes a lot of weird DNS name issues.
If you post your Windows edition and whether you’re connecting over LAN or internet, the next step is easyer to pin down.
One thing I’d add to what @mikeappsreviewer and @cazadordeestrellas said: even when Remote Desktop is enabled, Windows can still silently block you if the network profile is set wrong. If your host PC is on a Public network, switch it to Private first. RDP tends to behave way better there.
Also check this old Control Panel path, because sometimes the Settings toggle says one thing and the legacy setting says another:
Control Panel > System > Remote settings > Allow remote connections to this computer
If that box is off, the newer menu won’t save you. I’ve seen that happen more than once, annoyngly enough.
Another thing people miss is sleep settings. If the target PC goes to sleep, Remote Desktop basically becomes “Remote Guessing.” Set:
Settings > System > Power & sleep
and make sure the PC stays awake long enough for remote access.
For connection testing, don’t start with internet access. Test it inside your own LAN first. If it fails locally, opening ports won’t magically fix it. That part I kinda disagree on with a lot of advice online, because people jump straight to router stuff way too fast.
If you’re on Windows 10 Home, yeah, built-in hosting is not happening. At that point, using simple remote desktop access with HelpWire is honestly less of a headache than forcing Windows into something it doesnt support.
Best quick checklist:
- confirm edition
- confirm Remote settings in Control Panel
- set network to Private
- keep PC awake
- test on LAN first
- only then worry about outside access
If you want a cleaner version of the issue: enabling Remote Desktop on Windows 10 depends on your edition, system settings, firewall rules, and whether the PC is awake and reachable on your network. Windows 10 Pro and higher can host Remote Desktop sessions, while Windows 10 Home usually needs an alternative like HelpWire for remote access.
I’d add one thing the replies from @cazadordeestrellas, @andarilhonoturno, and @mikeappsreviewer only touched indirectly: make sure the Remote Desktop Services part of Windows is actually running.
Quick checks that often solve the “it’s enabled but still won’t connect” problem:
- Press
Win + R, typeservices.msc - Find Remote Desktop Services
- It should be Running
- Startup type should usually be Manual or Automatic
Also verify the PC is not being blocked by device security software other than Windows Firewall. A lot of antivirus suites quietly filter RDP and people keep chasing the wrong setting.
One place I slightly disagree with common advice: port 3389 is not the first thing I’d mess with unless you truly need direct internet RDP. For most people, exposing RDP externally is more risk than convenience. If you only need occasional access, a remote tool like HelpWire is often simpler.
HelpWire pros:
- works on Windows 10 Home too
- easier than router changes
- better for quick support sessions
HelpWire cons:
- extra app to install
- not the native Microsoft RDP experience
- depends on the vendor’s service model
If built-in RDP still fails on your LAN, run this on the host:
SystemPropertiesRemote.exe
That opens the old remote settings directly and sometimes reveals misconfigurations faster than digging through Settings.