Windows Firewall Remote Desktop Block Fix – Complete Guide (2026)

Windows Firewall Remote Desktop block fix is one of the most common troubleshooting searches for users who cannot connect to their Windows PC remotely. When you enable Remote Desktop but still can’t connect, the Windows Defender Firewall is often the culprit. According to Microsoft Q&A documentation, the “Public” network profile strictly blocks inbound Remote Desktop traffic (TCP Port 3389) by default[reference:0][reference:1]. This comprehensive Windows Firewall Remote Desktop block fix guide covers eight proven methods to allow RDP through the firewall and restore Remote Desktop access.

When you search for a Windows Firewall Remote Desktop block fix, you are likely seeing a “Remote Desktop can’t connect” error even though you’ve enabled Remote Desktop in Settings. According to Microsoft Q&A, the reason you might not be able to enable Remote Desktop is that your device is currently set to a Public network profile. Public networks are configured with stricter firewall settings to protect you on unsecured networks, blocking incoming connections like RDP[reference:2][reference:3]. This Windows Firewall Remote Desktop block fix guide walks you through every step needed to resolve this issue.

1. Understanding Why Windows Firewall Blocks Remote Desktop

Windows Defender Firewall is designed to protect your computer from unauthorized access. When you enable Remote Desktop, Windows creates firewall rules to allow inbound RDP traffic on TCP port 3389. However, several factors can prevent these rules from working properly:

• Public network profile: When Windows detects a Public network, it applies stricter firewall rules that block inbound RDP traffic by default[reference:4]. According to Microsoft Q&A, in the “Public” profile, Windows Defender Firewall strictly blocks inbound Remote Desktop traffic (TCP Port 3389) by default[reference:5].
• RDP firewall rule disabled: The pre-configured Remote Desktop firewall rule may be disabled or misconfigured.[reference:6]
• Corrupted firewall configuration: System updates or third-party software can corrupt firewall settings.[reference:7]
• Remote Desktop Services not running: The Remote Desktop Services may be stopped or set to Manual startup.[reference:8]

According to a Microsoft Q&A discussion, some users find that disabling the firewall allows RDP to work, but re-enabling it blocks the connection again—indicating that the firewall rules aren’t configured correctly[reference:9]. Understanding these root causes is the first step in any Windows Firewall Remote Desktop block fix guide.

2. Windows Firewall Remote Desktop Block Fix: Use Windows Settings

The simplest way to allow Remote Desktop through the firewall is using the Windows Settings interface. According to Microsoft Q&A, you need to go to Control Panel and click on “Allow an app or feature through Windows Firewall,” then scroll down until you see Remote Desktop and make sure the box is checked[reference:10][reference:11].

Step 1: Open Control Panel
- Press Win + R, type "control" and press Enter

Step 2: Navigate to Windows Defender Firewall
- Click "System and Security" → "Windows Defender Firewall"

Step 3: Allow an app or feature
- Click "Allow an app or feature through Windows Defender Firewall" in the left sidebar

Step 4: Enable Remote Desktop
- Click "Change settings" (requires administrator privileges)
- Scroll down and find "Remote Desktop" or "Remote Desktop (WebSocket)"
- Check the boxes for Private and Public (or at least Private)
- Click OK

Step 5: Verify the change
- Restart your computer and test the Remote Desktop connection

According to Microsoft Q&A, make sure it’s only enabled for the Private network; you don’t want anyone in the world being able to remotely connect to your computer[reference:12].

Outcome: Remote Desktop is allowed through the Windows Firewall via the app whitelist.

3. Enable RDP via Windows Firewall with Advanced Security

If the Settings method doesn’t work, the Advanced Security console provides more control. According to Microsoft Q&A, you should open Control Panel > Windows Defender Firewall > Advanced Settings, and under inbound rules, make sure there’s a rule allowing Remote Desktop (port 3389)[reference:13].

Step 1: Open Windows Firewall with Advanced Security
- Press Win + R, type "wf.msc" and press Enter[reference:14]
- Or go to Control Panel → Windows Defender Firewall → Advanced settings

Step 2: Check Inbound Rules
- Click "Inbound Rules" in the left navigation pane
- Look for rules named:
  - "Remote Desktop (TCP-In)"
  - "Remote Desktop - User Mode (TCP-In)"[reference:15]

Step 3: Enable the rule
- Right-click the rule and select "Enable" if it's disabled
- The rule should show a green checkmark icon[reference:16]

Step 4: Check rule properties (optional)
- Double-click the rule to open Properties
- Go to the "Scope" tab to restrict which IP addresses can connect[reference:17]
- Go to the "Advanced" tab to ensure it applies to the correct network profiles

According to Microsoft Q&A, you want to modify the Remote Desktop (TCP-in) rules that are green. There may be more than one[reference:18].

Outcome: The Remote Desktop inbound firewall rule is enabled and properly configured.

4. Fix Network Profile (Public vs Private)

Windows network profiles determine firewall strictness. According to Microsoft Q&A, switching your device to a Private network profile should resolve this issue and enable you to activate Remote Desktop successfully[reference:19].

Step 1: Open Settings
- Press Windows + I

Step 2: Go to Network & Internet
- Click on "Network & Internet"

Step 3: Select your active network
- Click on "Wi-Fi" or "Ethernet" (your active connection)
- Click on the network name

Step 4: Change network profile
- Under "Network profile," select "Private" to switch from Public
- Public = stricter firewall rules (blocks RDP)
- Private = more relaxed firewall rules (allows RDP)[reference:20]

Step 5: Verify the change
- Restart your computer and test Remote Desktop

According to Microsoft Q&A, after a power outage, the Network Location Awareness (NLA) service may misidentify the network as “Public,” causing the Windows Firewall to block inbound RDP traffic[reference:21]. You can also run Get-NetConnectionProfile in PowerShell to check the NetworkCategory[reference:22].

Outcome: The network profile is set to Private, allowing RDP through the firewall.

5. Use PowerShell to Enable RDP Firewall Rule

PowerShell provides a quick way to enable the Remote Desktop firewall rule. According to Microsoft Q&A, you can run Get-NetConnectionProfile in an elevated PowerShell session to check the NetworkCategory[reference:23].

Step 1: Open PowerShell as Administrator
- Press Win + X, select "Terminal (Admin)" or "Windows PowerShell (Admin)"

Step 2: Check the network profile
- Get-NetConnectionProfile
- Look for "NetworkCategory" – if it shows "Public," proceed to the next step

Step 3: Switch to Private network profile
- Get-NetConnectionProfile | Set-NetConnectionProfile -NetworkCategory Private
- Or use: Set-NetConnectionProfile -NetworkCategory Private -Force[reference:24]

Step 4: Enable the Remote Desktop firewall rule
- Enable-NetFirewallRule -DisplayGroup "Remote Desktop"

Step 5: Verify the rule is enabled
- Get-NetFirewallRule -DisplayGroup "Remote Desktop" | Select-Object Enabled, Direction, Action

According to Microsoft Q&A, if the NetworkCategory shows Public, run Set-NetConnectionProfile -NetworkCategory Private -Force to restore connectivity[reference:25].

Outcome: The Remote Desktop firewall rule is enabled via PowerShell.

6. Use Command Prompt (netsh) to Allow RDP

The netsh command provides another way to enable Remote Desktop through the firewall. According to Microsoft Q&A, you can open the firewall’s advanced settings and create a new rule to open port 3389[reference:26][reference:27].

Step 1: Open Command Prompt as Administrator
- Press Win + X, select "Terminal (Admin)" or "Command Prompt (Admin)"

Step 2: Enable the Remote Desktop firewall rule group
- netsh advfirewall firewall set rule group="remote" new enable=Yes[reference:28]

Step 3: Add a custom rule for port 3389 (if needed)
- netsh advfirewall firewall add rule name="Remote Desktop" dir=in protocol=TCP localport=3389 action=allow[reference:29]

Step 4: Verify the rule
- netsh advfirewall firewall show rule name="Remote Desktop"

Step 5: Restart your computer
- shutdown /r /t 0

According to Microsoft Q&A, a user on Reddit found that after using the command netsh advfirewall reset to reset everything, the GUI RDP setting was able to be toggled on[reference:30].

Outcome: The Remote Desktop firewall rule is enabled via netsh.

7. Reset Windows Firewall to Default Settings

If the firewall configuration is corrupted, resetting to defaults can resolve the issue. According to Microsoft Q&A, your Windows may have a corrupted definition of ‘Windows Defender Firewall with Advanced Security.’ Please restore it to default policy[reference:31].

Step 1: Open Windows Firewall with Advanced Security
- Press Win + R, type "wf.msc" and press Enter

Step 2: Restore default policy
- Right-click "Windows Defender Firewall with Advanced Security" at the top
- Select "Restore Default Policy"
- Click "Yes" to confirm

Step 3: Alternative method via Command Prompt
- Open Command Prompt as Administrator
- netsh advfirewall reset[reference:32]

Step 4: Re-enable Remote Desktop firewall rule
- After reset, go back to Settings → System → Remote Desktop
- Toggle Remote Desktop on and off to recreate the firewall rules

Step 5: Restart your computer

According to Microsoft Q&A, after using the command to reset everything, the GUI RDP setting is able to be toggled on[reference:33].

Outcome: The firewall is restored to default settings, resolving corruption issues.

8. Check and Restart Remote Desktop Services

Remote Desktop Services must be running for RDP to work. According to Microsoft Q&A, you should locate “Remote Desktop Services,” right-click, and select “Restart.” If the service is disabled, set the startup type to “Automatic” under Properties[reference:34].

Step 1: Open Services
- Press Win + R, type "services.msc" and press Enter

Step 2: Locate Remote Desktop Services
- Find "Remote Desktop Services" (or "Terminal Services")
- Right-click and select "Properties"

Step 3: Check service status
- Startup type should be "Automatic"
- Service status should be "Running"
- If not, click "Start" or change startup type to "Automatic"[reference:35]

Step 4: Restart the service
- Click "Stop" then "Start"
- Or right-click and select "Restart"[reference:36]

Step 5: Check Remote Desktop Services UserMode Port Redirector
- Also verify this service is running for proper RDP functionality

According to Microsoft Q&A, this often resolves temporary service issues post-updates[reference:37].

Outcome: Remote Desktop Services are running properly.

9. Advanced: Create a Custom Firewall Rule for RDP

If the default Remote Desktop rules aren’t working, you can create a custom firewall rule. According to PCOnline’s guide, you can open the “Run” dialog (Win+R), type wf.msc, go to Inbound Rules, and click “New Rule”[reference:38].

Step 1: Open Windows Firewall with Advanced Security
- Press Win + R, type "wf.msc" and press Enter[reference:39]

Step 2: Create a new inbound rule
- Click "Inbound Rules" in the left pane
- Click "New Rule…" in the right pane[reference:40]

Step 3: Select rule type
- Select "Port" and click Next[reference:41]

Step 4: Configure the port
- Select "TCP"
- Select "Specific local ports" and enter "3389"
- Click Next

Step 5: Allow the connection
- Select "Allow the connection"
- Click Next

Step 6: Choose network profiles
- Check Domain, Private, and Public (or at least Private)
- Click Next

Step 7: Name the rule
- Enter a name like "RDP Custom Rule"
- Click Finish[reference:42]

Step 8: Test the connection
- Verify the rule is enabled and test Remote Desktop

According to Microsoft Q&A, the default RDP port is 3389, and you need to forward TCP port 3389 to the local IP address of the computer you want to access[reference:43].

Outcome: A custom firewall rule allows RDP traffic on port 3389.

10. Frequently Asked Questions

Why is Windows Firewall blocking Remote Desktop?

Windows Firewall blocks Remote Desktop by default when the network profile is set to “Public.” According to Microsoft Q&A, in the “Public” profile, Windows Defender Firewall strictly blocks inbound Remote Desktop traffic (TCP Port 3389) by default[reference:44][reference:45]. Switch to a Private network profile or manually enable the RDP firewall rule.

How do I allow Remote Desktop through Windows Firewall?

Open Control Panel → Windows Defender Firewall → Allow an app or feature through Windows Defender Firewall → scroll to Remote Desktop and check the boxes. Alternatively, open Windows Firewall with Advanced Security (wf.msc), go to Inbound Rules, and enable the “Remote Desktop (TCP-In)” rule.

What port does Remote Desktop use?

Remote Desktop Protocol (RDP) uses TCP port 3389 by default. According to Microsoft Q&A, this port must be open in the firewall for RDP connections to work[reference:46].

How do I fix “Windows Firewall blocks Remote Desktop” error?

Check that Remote Desktop is enabled in Settings, allow Remote Desktop through the firewall, ensure the network profile is set to Private, and verify that the Remote Desktop Services are running. If the issue persists, reset the firewall or create a custom RDP rule.

How do I enable Remote Desktop using PowerShell?

Run PowerShell as Administrator and use: Enable-NetFirewallRule -DisplayGroup "Remote Desktop". You can also check the network profile with Get-NetConnectionProfile and switch to Private with Set-NetConnectionProfile -NetworkCategory Private.

How do I enable Remote Desktop using Command Prompt?

Open Command Prompt as Administrator and run: netsh advfirewall firewall set rule group="remote" new enable=Yes. For a custom rule, use: netsh advfirewall firewall add rule name="Remote Desktop" dir=in protocol=TCP localport=3389 action=allow.

Why can I RDP locally but not remotely?

If RDP works on the local network but not remotely, the issue is likely port forwarding on your router, not the Windows Firewall. According to Microsoft Q&A, you need to forward TCP port 3389 to the local IP address of your computer[reference:47].

How do I reset Windows Firewall to default?

Open Windows Firewall with Advanced Security (wf.msc), right-click on the top node, and select “Restore Default Policy.” Or run netsh advfirewall reset in Command Prompt as Administrator.[reference:48]

What is the difference between Public and Private network profiles?

According to Microsoft Q&A, Public networks have stricter firewall settings that block incoming connections, including RDP. Private networks have more relaxed firewall rules allowing services like Remote Desktop[reference:49].

Where can I find more Windows Remote Desktop troubleshooting help?

Explore our Windows 11 Troubleshooting Hub and guides on how to add firewall exceptions and how to update network drivers.

11. Conclusion

Windows Firewall Remote Desktop block fix covers everything you need to resolve RDP connection issues caused by the Windows Defender Firewall. From allowing Remote Desktop through the firewall and fixing network profiles to using PowerShell, netsh, and creating custom rules, this guide provides all proven methods. According to Microsoft’s documentation, the “Public” network profile strictly blocks inbound Remote Desktop traffic by default[reference:50].

Start with the simplest fix — allowing Remote Desktop through the firewall in Settings — and escalate to more advanced solutions only if needed. For more Windows troubleshooting, explore our Windows 11 Troubleshooting Hub and guides on how to add firewall exceptions and how to update network drivers. With the right approach from this Windows Firewall Remote Desktop block fix guide, you can restore remote access to your computer.

For more Windows networking troubleshooting, explore our Windows 11 Troubleshooting Hub and guides on network performance optimization and DHCP not enabled. With the right approach, you can resolve any Windows Firewall issues and keep your remote access working.