How to Use Remote Desktop on Windows 11 (2026)

Being able to sit down at any device and pick up exactly where you left off on your main PC is one of those things that sounds complicated but is genuinely fast to set up when you know the steps. Windows 11 ships with a full Remote Desktop implementation — you just have to know where to turn it on, and what to do about the edition limitation that catches most people off guard.

This guide covers the whole picture: enabling RDP on Windows 11 Pro, connecting from Windows, macOS, Android, and iOS, making the session work over the internet without exposing your machine, and the free tools that solve the Home edition problem cleanly.

A Windows 11 developer desktop with system stats and folder widgets visible on a synthwave wallpaper — the kind of machine you would want to access remotely — Remote Desktop gives you a full session on your main machine — your layout, your apps, your widgets — from any device anywhere.

The edition check you need to do first

Windows 11 Home cannot host RDP sessions. This is the most common stumbling block. If the PC you want to connect to runs Home edition, the Remote Desktop toggle in Settings is either missing or non-functional as a host.

Home machines can still connect to other machines — they just cannot be the target. Your options if you are on Home: upgrade to Windows 11 Pro (available in Settings → System → Activation → Change product key), or use one of the free third-party alternatives in the last section of this guide.

Windows 11 Pro, Enterprise, and Education all support hosting. If you have any of those editions, proceed.

Enable Remote Desktop on the host PC

The host is the machine you want to connect to. Do these steps on that machine:

Open Settings with Win + I and navigate to System → Remote Desktop.
Toggle Remote Desktop to On. Windows shows a confirmation dialog — click Confirm.
Note the PC name shown directly on that page (something like DESKTOP-AB12CD). Write it down — you will need it on the client side.
Under User accounts, your own account is pre-listed. To give another user access, click Select users that can remotely access this PC and add their Windows account.

There is also a classic path: right-click the Start button → System, scroll to Remote Desktop, or run SystemPropertiesRemote.exe from Run (Win + R). Both open the same underlying setting.

Keep the host from sleeping

A sleeping PC drops incoming connections immediately. Fix this before you leave the host:

Go to Settings → System → Power & sleep. Set Sleep to Never when plugged in.
If the host is a laptop, also check Settings → System → Power → Screen and sleep and make sure the "when plugged in" sleep timer is off.
Optionally, in Device Manager → Network adapters → your adapter → Properties → Power Management, untick Allow the computer to turn off this device to save power. This prevents the NIC from going offline even if Windows enters a low-power state.

Connect from another Windows PC (local network)

On the client — the machine you are connecting from:

Press Win, type Remote Desktop Connection, and open it. You can also run mstsc from the Run box (Win + R).
In the Computer field, type the host's PC name or its local IP address. Find the IP on the host under Settings → Network → your connection → Properties.
Click Connect, enter the host's Windows credentials at the login screen, and accept the certificate warning on first connection (expected and safe on a trusted local network).
You now have a full desktop session. The host screen goes to the lock screen while you are connected — a single physical user session at a time is the Windows Home/Pro limit.

To disconnect without ending the session: close the RDP window. The session stays alive on the host. To log off entirely: use Start → your profile → Sign out inside the RDP window.

The Options panel in Remote Desktop Connection is worth exploring. Display lets you set resolution and multi-monitor mode. Local Resources lets you share clipboard, drives, and audio between machines. Experience lets you reduce bandwidth when on a slow connection by disabling desktop composition and backgrounds.

A Windows 11 desktop with calendar, email and notes widgets visible on a dark space wallpaper — the kind of productive setup accessible via Remote Desktop — A full Remote Desktop session gives you everything on the host — widgets on the wallpaper, open apps, pinned files — exactly as you left them.

Connect from macOS, Android, or iOS

Microsoft publishes free RDP client apps for every major platform. They are all called Microsoft Remote Desktop and are available from each platform's official store:

macOS: available on the Mac App Store. Works on Apple Silicon; supports Retina resolution. Add the host via the plus icon → Add PC → enter name or IP.
Android: available on Google Play. Touch is mapped to mouse clicks; a Bluetooth keyboard dramatically improves usability. Good for quick access when away from a desk.
iOS / iPadOS: available on the App Store. The iPad version with an external keyboard is comfortable for real work. Split-screen on iPad lets you keep a local app alongside the remote session.

The workflow is the same on all three: open the app → add a PC → enter host name or IP → save → tap to connect → enter credentials.

Connect over the internet

Local network access requires no firewall changes. Internet access does — and how you approach it matters a lot for security.

Option A: VPN (recommended)

If your router supports WireGuard or OpenVPN (most modern routers running OpenWrt, pfSense, or certain consumer firmware do), set up a VPN server on the router. When you connect the client device to that VPN, it looks like a local network device and can reach the host exactly as in the previous section — no ports exposed, no brute-force attack surface.

If your router does not support a VPN server, Tailscale is an excellent free option. Install Tailscale on both machines, log in with the same account, and they appear to each other as local network peers regardless of where they are physically. No port forwarding, no configuration, works on Windows Home too (though the host still cannot serve RDP — it is useful for the alternatives below).

Option B: Port forwarding (quick but less secure)

Forward TCP port 3389 on your router to the host PC's local IP. Connect using your router's external IP address (check it at any "what's my IP" site, or set up Dynamic DNS if it changes). This works but is significantly riskier — change the RDP listening port from 3389 to a random high port number (e.g., 54321) in the Registry (HKLM\System\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp\PortNumber) to reduce automated scan hits, and use a long, unique password on the Windows account.

Free alternatives for Windows 11 Home

If the host is Home edition, these tools do the job without requiring an upgrade:

Chrome Remote Desktop

Free, no port forwarding, works on Windows Home, macOS, Linux, Android, and iOS. The host installs a small service via the Chrome browser (or Chrome Remote Desktop standalone host installer). Access is tied to your Google account. Latency is slightly higher than direct RDP because connections route through Google's relay servers, but for most use it is unnoticeable. Best free option for Home edition.

AnyDesk

Free for personal use. Each machine gets a numeric AnyDesk address. No Google account, no Chrome dependency, lower latency than Chrome Remote Desktop in most network conditions. The free personal tier limits unattended access in certain scenarios and lacks some enterprise features. Fine for home use.

TeamViewer

Free for personal use. The most feature-complete option — file transfer, multi-monitor, session recording, mobile app — and it has been around long enough to be extremely reliable. The free tier has become more aggressive about detecting commercial use patterns; occasional personal sessions work without issue.

Quick Assist (built-in, support sessions only)

For helping someone else fix a problem (not for unattended access to your own machine), Windows 11 ships with Quick Assist. Press Win, search Quick Assist, click Get assistance, and share the 6-digit code. The helper takes control, sessions end when the window closes. No third-party app needed — and it works on Home.

A Windows 11 desktop productivity dashboard with email, calendar and system widgets visible — the kind of setup worth accessing remotely from any device — Your full Windows desktop — apps, widgets, everything — is available from a phone or tablet once Remote Desktop or Chrome Remote Desktop is set up.

Which option is right for you

Host is Pro, same local network: built-in Remote Desktop Connection (mstsc), no extra apps.
Host is Pro, need internet access: set up Tailscale or a router VPN, then use RDP over it.
Host is Home: Chrome Remote Desktop — fastest setup, no cost, works everywhere.
Connecting from macOS or mobile: Microsoft Remote Desktop app for Pro hosts; Chrome Remote Desktop for Home hosts.
One-off support session: Quick Assist (built-in) or AnyDesk — no pre-setup required on the host.

If you are building a proper remote-work setup, a well-organized Windows desktop makes remote sessions significantly more productive. Our guides on virtual desktops on Windows 11 and setting up Windows 11 for working from home cover the desktop organization side. For the developer angle, the best Windows desktop setup for developers covers monitoring and quick-access widgets that are especially useful when you cannot see the physical machine.

FAQ

Can I use Remote Desktop on Windows 11 Home?

Windows 11 Home cannot host RDP sessions — other machines cannot connect to it using Remote Desktop. Home machines can still connect to Pro hosts. If you need to access a Windows 11 Home PC remotely, your options are Chrome Remote Desktop (free, no account required on the host), AnyDesk (free for personal use), or TeamViewer (free for personal use). All three work on Home without upgrading.

What is the default RDP port and do I need to open it on my router?

Remote Desktop uses TCP port 3389 by default. On a local network you do not need to open anything — both machines are already on the same subnet. If you are connecting over the internet, you need port 3389 forwarded on your router to the host PC. That said, exposing 3389 to the public internet is risky because automated scanners probe it constantly. A VPN is a much safer approach for internet access.

Is Remote Desktop the same as Quick Assist?

No. Quick Assist (search for it in the Start menu) is designed for temporary remote support sessions: one person shares their screen, the other sees and optionally controls it. It requires a Microsoft account on the helper side, and sessions end when you close the app. Remote Desktop (RDP) is a full login session on the host machine — you get the host desktop as if you were sitting in front of it, and the session can persist unattended. Quick Assist is for support calls; RDP is for ongoing remote access to your own machines.

How do I connect to a remote PC by computer name instead of IP address?

On a local network, type the host's computer name (e.g., DESKTOP-AB12CD — shown in Settings → System → About) in the Remote Desktop Connection client. Windows resolves it via mDNS or NetBIOS as long as both machines are on the same subnet. Over the internet, you need the router's external IP address, or a Dynamic DNS hostname (services like No-IP or Cloudflare give you a stable domain that follows your changing IP).

Does Remote Desktop work across multiple monitors?

Yes. In the Remote Desktop Connection client, click Options → Display before connecting. Drag the resolution slider to Full Screen and tick 'Use all my monitors for the remote session' to spread the remote desktop across all your local displays. The Microsoft Remote Desktop app from the Store has a similar Display tab in the connection settings.

Why does my Remote Desktop connection keep dropping?

The most common causes are: (1) the host PC went to sleep — set sleep to Never in Settings → System → Power & sleep; (2) a network timeout — in Remote Desktop Connection, open Options → Experience and adjust the connection setting; (3) the Remote Desktop Services process stopped — check that the Remote Desktop Services entry is running in services.msc on the host and set it to Automatic startup.