How to Enable and Use Remote Desktop (RDP) in Windows
A complete guide to enabling Remote Desktop in Windows 11 and Windows 10, adding users, connecting from another device, securing remote access, and fixing common RDP problems.
πͺ Windows 11 & 10π₯ Remote Desktopπ RDP Securityπ Troubleshootingπ Updated June 2026
Overview
What Is Windows Remote Desktop and How Does RDP Work?
Remote Desktop is a built-in Windows feature that lets you control another Windows computer over a network. After connecting, you can open programs, manage files, change settings, and work with the remote desktop almost as if you were sitting in front of that PC.
The connection uses the Remote Desktop Protocol, usually abbreviated as RDP. One computer acts as the host or remote PC, while the device used to connect acts as the client.
π₯οΈ
Full Desktop Control
Open apps, work with files, change Windows settings, and use the remote PC from another device.
π
Clipboard and Device Redirection
Copy text and files, redirect printers, play remote audio, and optionally expose local drives to the session.
π
Local or Remote Access
Connect across the same home or office network, through a VPN, or through a managed Remote Desktop Gateway.
π
Encrypted Authentication
RDP supports encrypted sessions and Network Level Authentication to verify a user before the desktop session starts.
βΉοΈ
Remote Desktop versus Quick Assist
Remote Desktop signs you in to a Windows session using an account on the remote PC. Quick Assist is designed for temporary support and screen sharing with another person who approves the connection.
Compatibility
Remote Desktop Requirements in Windows 11 and Windows 10
Before enabling RDP, verify that the computer you want to control can act as a Remote Desktop host. The edition installed on the remote PC matters; the edition on the client device is less restrictive.
Windows edition or device
Can receive RDP connections?
Can connect to another RDP host?
Windows 11 Pro, Enterprise, or Education
Yes
Yes
Windows 10 Pro, Enterprise, or Education
Yes
Yes
Windows 11 Home or Windows 10 Home
No
Yes
Windows Server
Yes
Yes
macOS, iOS, iPadOS, or Android client
Client only
Yes, with a compatible Microsoft client
Basic RDP Requirements
The remote PC must be powered on and connected to the network.
Remote Desktop must be enabled on the remote PC.
The Windows account used for the connection must have permission to sign in remotely.
The account should have a password; a Windows Hello PIN is not normally used as the RDP password.
Windows Firewall must allow the Remote Desktop rules.
The client must be able to reach the remote PC by computer name or IP address.
β οΈ
Windows Home limitation
A Windows Home PC can run the Remote Desktop client and connect to another computer, but it cannot accept incoming RDP connections using the built-in Microsoft Remote Desktop host.
π
Windows 10 support status
Standard support for Windows 10 ended on October 14, 2025. RDP can still function, but an unsupported operating system should not be exposed to remote access. Upgrade to Windows 11 or use an eligible Extended Security Updates plan where applicable.
Before Setup
How to Prepare a Windows PC for Remote Desktop Access
Collect the remote computer name, account name, and local IP address before you connect. This makes troubleshooting much easier if Windows cannot resolve the PC name automatically.
Check the Windows Edition
Press Win + I to open Settings.
Open System and select About.
Under Windows specifications, check the Edition field.
Confirm that the remote PC runs Windows Pro, Enterprise, or Education.
Find the Computer Name
SettingsβΊSystemβΊAboutβΊDevice name
You can also open Command Prompt and run:
hostname
Find the Local IP Address
Open Command Prompt and run:
ipconfig
Look for the IPv4 Address under the network adapter currently in use. A home network address commonly looks like 192.168.1.50 or 10.0.0.25.
Find the Windows Account Name
Run the following command on the remote PC:
whoami
The result may appear as PC-NAME\username. For a Microsoft account, Windows may instead ask for the account email address and its full password.
β
Recommended preparation
Give the remote PC a clear device name and reserve its local IP address in the router's DHCP settings. A stable address prevents saved RDP connections from breaking after the router assigns a different IP.
Main Method
How to Enable Remote Desktop in Windows Settings
The Settings app is the simplest and safest way to enable the built-in Remote Desktop host. The path is nearly identical in Windows 11 and Windows 10.
StartβΊSettingsβΊSystemβΊRemote Desktop
Sign in to the remote PC using an administrator account.
Press Win + I to open Settings.
Select System, then open Remote Desktop.
Turn on Remote Desktop.
Select Confirm when Windows asks whether you want to enable the feature.
Note the displayed PC name; you can use it later in the Remote Desktop client.
When Remote Desktop is enabled through Settings, Windows also enables the corresponding Windows Firewall rules. You normally do not need to create a manual firewall exception.
Keep Network Level Authentication Enabled
Open the Remote Desktop settings and keep the option requiring devices to use Network Level Authentication (NLA) enabled. NLA verifies credentials before Windows creates the full remote session, reducing the system resources exposed to unauthenticated connection attempts.
π
Best practice
Keep NLA enabled unless you are temporarily diagnosing a compatibility problem with a trusted legacy client. Re-enable it immediately after testing.
Prevent the Remote PC from Sleeping
A sleeping or hibernating computer usually cannot accept an RDP connection unless Wake-on-LAN has been configured separately. Review the power settings on a PC that must remain remotely available.
SettingsβΊSystemβΊPower & batteryβΊScreen and sleep
Alternative Methods
Other Ways to Enable Remote Desktop in Windows
Administrators can also enable RDP through the classic System Properties dialog or with PowerShell. These methods are useful when the Settings page is unavailable or when configuring several PCs.
Method 1
Windows Settings
The recommended method for most home and small-office computers. It enables RDP and the firewall rules together.
Recommended
Method 2
System Properties
Use the classic Remote tab to allow connections and configure Network Level Authentication.
Classic interface
Method 3
PowerShell
Enable the required registry setting and firewall rule from an elevated terminal.
Administrators
Enable RDP with System Properties
Press Win + R.
Enter SystemPropertiesRemote.exe and press Enter.
On the Remote tab, select Allow remote connections to this computer.
Keep the NLA option selected.
Click Apply, then OK.
Enable RDP with PowerShell
Open Windows Terminal or PowerShell as administrator, then run:
Administrator rights required
Enabling or disabling the Remote Desktop host changes system-wide settings. Run these commands only from an elevated terminal and only on a computer you administer.
Permissions
How to Add Users Allowed to Connect Through Remote Desktop
Members of the local Administrators group can normally connect through RDP automatically. Standard users must be added to the list of Remote Desktop users.
Open Settings β System β Remote Desktop.
Select Remote Desktop users or Select users that can remotely access this PC.
Click Add.
Enter the local, Microsoft, or domain account name.
Select Check Names if the dialog provides that option.
Click OK to save the user.
Account type
Typical username format
Password to use
Local Windows account
PC-NAME\username or .\username
The local account password
Microsoft account
The Microsoft account email address
The Microsoft account password, not the Windows Hello PIN
Active Directory domain account
DOMAIN\username or user@domain.example
The domain account password
Microsoft Entra account
AzureAD\user@company.example or a configured web sign-in flow
The organization account credentials required by its policy
π‘οΈ
Use least privilege
Do not make an account an administrator only to allow Remote Desktop access. Add a standard account to Remote Desktop Users unless administrative rights are genuinely required.
Connect
How to Connect to a Windows PC with Remote Desktop on a Local Network
Once the host is configured, use the built-in Remote Desktop Connection app on another Windows computer. The executable name is mstsc.exe.
Connect with Remote Desktop Connection
On the client PC, press Win + R.
Enter mstsc and press Enter.
In the Computer field, enter the remote PC name or local IP address.
Select Connect.
Enter the username and full account password for the remote PC.
Review the certificate warning. Continue only if the computer name or IP address is the one you intended to reach.
π₯οΈ
mstsc.exe
Enter a computer name such as OFFICE-PC or an address such as 192.168.1.50, then authenticate with an account that exists on the remote computer.
Connect from Windows App
Microsoft also provides Windows App for supported platforms. It can create a saved remote PC entry using a hostname or IP address. On Windows, the built-in mstsc.exe client remains the simplest choice for a direct one-time RDP connection.
Connect from macOS, iPhone, iPad, or Android
Install Microsoft's current remote desktop client for the platform.
Add a new PC connection.
Enter the remote PC name or IP address.
Add the Windows account or enter its credentials when prompted.
Open the saved PC entry to start the session.
π‘
No internet required on the LAN
Two computers on the same local network can use RDP without an active internet connection, provided they can reach each other through the router or switch.
Client Settings
How to Configure Remote Desktop Connection Options
Before selecting Connect, click Show Options in Remote Desktop Connection. The additional tabs let you control the display, local devices, audio, performance, and authentication behavior.
Tab
Useful settings
When to change them
General
Computer, username, save credentials, save an .rdp file
Create a reusable shortcut for the same remote PC
Display
Window size, full screen, use all monitors
Match the session to your monitor arrangement
Local Resources
Remote audio, clipboard, printers, local drives, smart cards
Control which client resources appear inside the remote session
Improve responsiveness over a slow or high-latency connection
Advanced
Server authentication and Remote Desktop Gateway settings
Connect through an organization gateway or enforce certificate behavior
Use Multiple Monitors
Open mstsc.
Select Show Options.
Open the Display tab.
Enable Use all my monitors for the remote session.
Return to the General tab and connect.
Redirect Local Drives or USB Storage
Open the Local Resources tab.
Under Local devices and resources, select More.
Choose the drives or supported devices you want available remotely.
Connect and open File Explorer in the remote session.
π
Privacy reminder
Redirect only the resources you need. A redirected local drive becomes accessible to programs running inside the remote session for the duration of that connection.
Remote Networks
How to Use Remote Desktop Over the Internet Safely
A local RDP connection works because both devices can reach each other directly. Connecting from outside the home or office network requires a secure path into that network.
Preferred
VPN
Connect to the home or office VPN first, then use the remote PC's private hostname or IP address as though you were on the local network.
Best for most users
Business
Remote Desktop Gateway
An RD Gateway carries RDP traffic through HTTPS and can integrate with organization access policies and authentication controls.
Managed environments
Higher risk
Router Port Forwarding
Forwarding TCP port 3389 directly to a PC is possible, but it exposes the RDP service to internet scanning and password attacks.
Not recommended
π«
Do not expose RDP casually
Avoid publishing port 3389 directly to the internet. A VPN or properly configured Remote Desktop Gateway provides a safer access layer and reduces direct attack exposure.
If Port Forwarding Is Unavoidable
Keep Windows fully updated and do not use an unsupported Windows release.
Keep Network Level Authentication enabled.
Use long, unique passwords and disable unused accounts.
Restrict the firewall rule to known source IP addresses when possible.
Use a non-administrator account for routine remote work.
Review failed sign-in events and disable access when it is no longer required.
Prefer a gateway or VPN that supports multifactor authentication.
Security
How to Secure Windows Remote Desktop
RDP is an administrative access path to a full Windows desktop, so it should be protected as carefully as local sign-in. Use several layers of defense rather than relying on a password alone.
β Recommended
Keep Network Level Authentication enabled.
Use a VPN or RD Gateway for internet access.
Install Windows security updates promptly.
Use unique passwords and least-privilege accounts.
Limit membership in Remote Desktop Users.
Lock or disconnect the session when finished.
Disable RDP when it is not needed.
β Avoid
Exposing port 3389 to the entire internet.
Disabling NLA without a specific temporary reason.
Using blank, reused, or weak passwords.
Giving every remote user administrator rights.
Ignoring certificate name or identity warnings.
Enabling drive redirection on an untrusted client.
Leaving an unsupported Windows host online.
Disconnect Versus Sign Out
Disconnecting closes the client window but leaves programs running in the remote session. Signing out closes applications and ends the Windows user session. Use Disconnect when you plan to return, and Sign out when the work is complete.
π
Local screen behavior
On standard Windows desktop editions, an incoming RDP session normally locks the physical console. The person at the remote PC does not watch the desktop in the same collaborative way as with Quick Assist.
Troubleshooting
Remote Desktop Not Working in Windows: Common Fixes
Most RDP failures are caused by an unsupported Windows edition, a sleeping computer, an incorrect address, blocked firewall traffic, missing user permission, or invalid credentials.
1. βRemote Desktop Can't Connect to the Remote Computerβ
Confirm that the remote PC is powered on and not sleeping.
Verify that Remote Desktop is enabled in Settings β System β Remote Desktop.
Try the remote PC's IPv4 address instead of its computer name.
Make sure both devices are connected to the same local network, or connect to the required VPN first.
Restart the remote PC after installing updates or changing network settings.
2. Test Whether TCP Port 3389 Is Reachable
On the client PC, open PowerShell and run:
Test-NetConnection 192.168.1.50 -Port 3389
Replace 192.168.1.50 with the remote PC name or IP address. If TcpTestSucceeded is False, check the address, firewall, VPN, router path, and whether the RDP service is listening.
On the remote PC, open Command Prompt as administrator and run:
netstat -ano | findstr :3389
A listening entry indicates that the RDP service is accepting TCP connections on the default port. If no entry appears, confirm that Remote Desktop is enabled and restart the Remote Desktop Services service or reboot the PC.
5. βYour Credentials Did Not Workβ or βThe Logon Attempt Failedβ
Use the full account password, not the Windows Hello PIN.
For a local account, try PC-NAME\username or .\username.
For a Microsoft account, try the complete email address.
Remove incorrect saved credentials from Credential Manager and reconnect.
Make sure the account is enabled and not locked out.
6. βThe Requested Session Access Is Deniedβ
Add the account to Remote Desktop Users.
Check local or domain Group Policy restrictions.
Confirm that the account has the Allow log on through Remote Desktop Services user right.
Remove the account from policies that deny Remote Desktop logon.
7. Network Level Authentication Error
Update both the RDP client and the remote Windows PC.
Verify the date and time on both devices.
Confirm that the client supports NLA.
For domain devices, confirm that the domain controller is reachable through the required network or VPN.
Disable NLA only as a temporary diagnostic step on a trusted network.
8. Black Screen, Frozen Session, or Poor Performance
Disconnect and reconnect instead of repeatedly opening new sessions.
Restart the remote PC if the display driver or session is stuck.
Install current graphics, network, and Windows updates.
Open Show Options β Experience and choose a lower connection speed profile.
Disable desktop background, animation, or unnecessary resource redirection on a slow connection.
Symptom
Likely cause
First check
Remote Desktop option is missing
Windows Home or managed policy
Check Windows edition and organization policy
PC name does not connect
Name resolution problem
Try the IPv4 address
Port 3389 test fails
Firewall, routing, VPN, or service issue
Check RDP firewall rules and service state
Password is rejected
Wrong username format or PIN used
Use the full password and correct account prefix
Connection works only sometimes
Sleep, changing IP address, or unstable Wi-Fi
Review power settings and reserve the local IP
Session is slow
High latency or excessive visual effects
Reduce display quality and resource redirection
FAQ
Frequently Asked Questions About Windows Remote Desktop and RDP
Q Is Remote Desktop available in Windows 11 Home?
Windows 11 Home includes the client needed to connect to another RDP host, but it cannot act as the built-in Remote Desktop host for incoming connections. The remote PC must run a supported Pro, Enterprise, Education, or Windows Server edition.
Q Can Windows 10 Home connect to a Windows 11 Pro PC?
Yes. Windows Home can be used as the client. Enable Remote Desktop on the Windows 11 Pro host, then connect from Windows 10 Home with mstsc.exe.
Q Does Remote Desktop work without the internet?
Yes. RDP works between devices on the same local network without internet access. The devices still need a working network connection and must be able to reach each other by name or IP address.
Q Why does my Windows PIN not work in Remote Desktop?
A Windows Hello PIN is tied to a particular device and is not generally the password used for a standard RDP connection. Enter the full password for the local, Microsoft, domain, or organization account.
Q What port does Windows Remote Desktop use?
The default RDP port is TCP and UDP 3389. Do not expose it directly to the entire internet unless you fully understand and mitigate the security risks. A VPN or RD Gateway is preferable.
Q Can I wake a sleeping PC with Remote Desktop?
RDP itself normally cannot connect to a sleeping or powered-off PC. Wake-on-LAN can be configured separately if the network adapter, firmware, router, and power state support it.
Q Can two people use the same Windows PC through RDP at the same time?
Standard Windows desktop editions are designed for one interactive user session at a time. An incoming RDP connection normally locks or takes over from the local console session. Multi-user Remote Desktop Services requires Windows Server and the appropriate licensing.
Q Is RDP encrypted?
Modern RDP sessions support encrypted transport and secure authentication features, but encryption does not make direct internet exposure risk-free. Keep NLA enabled and place remote access behind a VPN or RD Gateway whenever possible.
Q How do I close an RDP session without shutting down the remote PC?
Close the Remote Desktop window or select Disconnect from the remote Start menu. This leaves the remote PC running. Select Sign out only when you want to close the user's applications and end the session.
Q Should I change the default RDP port?
Changing the port may reduce basic automated noise, but it is not a substitute for real security. Use a VPN or RD Gateway, strong authentication, NLA, updates, firewall restrictions, and least-privilege accounts.
Summary
Best Way to Enable and Use Remote Desktop in Windows
For a local connection, confirm that the remote PC runs a supported Windows edition, enable Remote Desktop in Settings, add the required users, note the PC name or IP address, and connect with mstsc.exe. Keep Network Level Authentication enabled and make sure the computer stays awake when remote access is needed.
For access from outside the local network, use a trusted VPN or a properly managed Remote Desktop Gateway. Avoid exposing port 3389 directly to the internet.
π₯οΈ Bottom Line
Windows Remote Desktop is reliable when the host edition, user permissions, network path, firewall rules, and credentials are configured correctly. Start with a local-network test, use the PC's IP address if its name does not resolve, and add secure remote access only after the basic RDP connection works.