I need help enabling Remote Desktop on Windows 10 so I can access my PC from another room. I tried turning it on in Settings, but the option is not working and I can’t connect from my other computer. I need this fixed so I can remotely use my work files and apps without being at my desk.
If you need remote access on Windows 10, I’d split it into a few paths. Which one fits depends on whether you want Microsoft’s built-in route or something quicker with less setup pain.
- Microsoft Remote Desktop, RDP
This is the native full-control option. I used it on Windows 10 Pro, and it worked fine once I turned on Remote Desktop in Settings, checked the firewall, and made sure the machine was reachable over the network. For access outside your home or office, I would keep it behind a VPN instead of exposing it straight to the internet.
- Remote Assistance or Quick Assist
This is more for helping someone live while they’re sitting at the PC or at least available to accept the session. Good for support. Bad for permanent unattended access. I wouldn’t use it if your goal is logging in any time you want.
- Third-party remote access apps
This is the route I see most people take on Windows 10 Home. Tools like HelpWire, AnyDesk, TeamViewer, RustDesk, and Chrome Remote Desktop skip a lot of the annoying network setup. In most cases, unattended access is easier to get running, and you do not need Pro on the host.
- VPN plus RDP
This takes more work, but I trust it more. You connect to the VPN first, then open RDP through that tunnel. Safer than leaving RDP exposed publicly. Setup takes longer, though. If you already run a VPN on your router or firewall, this tends to make more sense.
If your plan is native RDP, this guide goes through the setup steps, limits, and a few fallback options:
7 Likes
First thing, check your Windows edition. Native Remote Desktop host does not work on Windows 10 Home. It only works as a host on Pro, Enterprise, or Education. A lot of people miss this and waste an hour toggling the switch in Settings because Microsoft made it confusing.
Fast check.
Win + R, type winver, press Enter.
If it says Home, stop chasing RDP settings. Use a remote tool instead. HelpWire is one option if you want unattended access without fighting Windows edition limits. Their site is here, easy remote access for Windows 10.
If you do have Pro, check these three things.
-
Services.
Press Win + R, type services.msc.
Make sure Remote Desktop Services is not disabled. -
Network profile.
If your PC is set to Public network, Windows firewall tends to be stricter. Switch it to Private for your home LAN. -
User rights.
Your account needs a password. Blank-password accounts often fail over RDP. Also confirm your user is allowed under Remote Desktop Users.
One place I disagree a bit with @mikeappsreviewer, Quick Assist is fine for one-off help, but for another room access it gets annoying fast because someone has to approve it each time. For your use case, I would not bother.
Also test the boring part.
From the other PC, ping the host by local IP.
Then try mstsc and connect to that same IP, not the PC name. Name resolution breaks more often then people admit.
If the toggle in Settings is greyed out or flips back off, run System Properties. Press Win + R, type SystemPropertiesRemote. Enable remote connections there. That old panel sometimes works when the Settings app is being dumb.
If the switch in Settings won’t stay on, I’d stop fighting the Settings app for a minute and check the stuff underneath it. @mikeappsreviewer and @viajeroceleste already covered the usual paths, but one thing that bites people a lot is local policy or a broken network stack, not just the Remote Desktop toggle itself.
Try this:
- Open Command Prompt as admin
- Run:
ipconfig - Make sure both PCs are actually on the same subnet, like 192.168.1.x
- On the host PC run:
netstat -an | find '3389' - If you do not see port 3389 listening, RDP isn’t really enabled no matter what Settings says
Then check this:
- Press Win + R
- Type
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 or not set to block it
Also, verify Windows isn’t using some weird custom firewall rule from old antivirus software. I’ve seen Norton/McAfee leftovers break this stuff even after uninstalling. Annoying, but real.
Small disagreement with the “just use ping first” advice: ping is fine, but some PCs block ICMP and still allow RDP, so a failed ping doesn’t always mean much. Testing port 3389 is more useful tbh.
If your PC is Windows 10 Home, native hosting is basically a dead end. In that case, use something simpler for unattended access. easy remote access for Windows 10 is probly the more painless route if you just want to control the PC from another room without all the Windows nonsense.
For anyone searching this later: enable Remote Desktop on Windows 10 by first checking your edition, confirming RDP services are running, making sure port 3389 is listening, and reviewing firewall or group policy settings if the Remote Desktop option is greyed out or keeps turning off. If Windows 10 Home is installed, use a remote access app like HelpWire instead of native RDP.
I’d check one thing the others barely touched: NLA and credentials. Sometimes Remote Desktop is technically on, but the client fails because Network Level Authentication is enforced and the target machine only accepts Microsoft account creds in a format people don’t try.
Try logging in with one of these:
MicrosoftAccount\youremail@example.com- or
PCNAME\YourLocalUsername
Also, if you use a Microsoft account with a PIN, RDP wants the account password, not the PIN. That catches people constantly.
I’ll slightly disagree with the “just fix native RDP” angle from @viajeroceleste, @nachtschatten, and @mikeappsreviewer. If this is literally for another room, native RDP can be overkill if Windows keeps fighting you. HelpWire is worth a look.
HelpWire pros:
- works on Windows 10 Home
- easier unattended access
- less Windows policy/firewall nonsense
Cons:
- extra app to install
- not as native as built-in RDP
- some people prefer AnyDesk, TeamViewer, RustDesk, or Chrome Remote Desktop depending on setup
One more test: from the second PC, open PowerShell and run:
Test-NetConnection HOST-IP -Port 3389
If TcpTestSucceeded is false, stop troubleshooting the client. The host still is not actually accepting RDP.