How to Fix Windows Firewall Blocking an Application
Published 2026-10-16 · Marion Remote Fix
You install a program or game, it tries to connect to the internet, and nothing happens — it hangs on loading, shows a connection error, or cannot reach its server. The program works fine offline, but any feature that requires network access fails. The most common cause is Windows Defender Firewall blocking the application's network traffic because it does not have a rule allowing it through. Windows blocks unknown programs by default to protect your computer, but this means legitimate software sometimes gets blocked too.
How Windows Firewall decides what to block
Windows Defender Firewall uses a set of rules that define which programs are allowed to send and receive network traffic. When a program tries to access the network for the first time, Windows usually shows a popup asking if you want to allow it on private networks, public networks, or both. If you clicked Cancel, Block, or missed the popup entirely, the program gets blocked. Some programs install silently (automatic updates, background services) and never trigger the popup — Windows blocks them by default.
The firewall treats inbound connections (other computers connecting to a program on your computer) and outbound connections separately. By default, Windows blocks all inbound connections that do not match a rule and allows all outbound connections. This means most programs can reach the internet but cannot receive incoming connections (which matters for multiplayer game hosting, remote access, peer-to-peer software, and server applications).
Allow an app through Windows Firewall
The simplest method to unblock an application:
- Open Settings, Privacy and Security (or Update and Security on Windows 10), Windows Security
- Click Firewall and Network Protection
- Click Allow an app through firewall
- Click Change settings (you need administrator privileges)
- Look for the blocked application in the list. If it is listed, make sure both the Private and Public checkboxes are checked (or whichever network type you use)
- If the application is not in the list, click Allow another app, Browse, and navigate to the program's executable file (.exe). Add it and check the appropriate network boxes
- Click OK
The program should now be able to connect. Test it immediately after making the change.
Create a firewall rule manually
For more control over what the application is allowed to do, create a specific rule using Windows Defender Firewall with Advanced Security:
- Press Windows + R, type
wf.msc, and press Enter - In the left pane, click Inbound Rules (if the program needs to receive connections) or Outbound Rules (if it needs to send connections). For most applications, you need both
- In the right pane, click New Rule
- Select Program, click Next
- Browse to the program's executable file. Use the full path, for example
C:\Program Files\AppName\app.exe - Select Allow the connection, click Next
- Check Domain, Private, and Public (or only the network profiles you use), click Next
- Give the rule a descriptive name (for example, Allow MyApp Network Access), click Finish
If you need to allow both inbound and outbound traffic, repeat the process for the other direction.
Check if the firewall is actually blocking the app
Before making firewall changes, confirm that the firewall is the actual problem and not a different network issue:
- Temporarily disable Windows Firewall: go to Firewall and Network Protection, click your active network profile (Private or Public), and toggle Windows Defender Firewall to Off
- Test the application. If it works with the firewall off, the firewall was blocking it. Turn the firewall back on immediately and create the appropriate rule
- If the application still does not work with the firewall off, the problem is not the firewall — it is something else (DNS, proxy, ISP blocking, server down, etc.)
Important: do not leave the firewall disabled. Turn it back on as soon as the test is complete. The test should take less than a minute.
Check firewall logs
If you are not sure which program is being blocked, enable firewall logging to see exactly what traffic is being dropped:
- Open Windows Defender Firewall with Advanced Security (
wf.msc) - In the left pane, click Windows Defender Firewall Properties
- Click the tab for your active profile (Private, Public, or Domain)
- Under Logging, click Customize
- Set Log dropped packets to Yes, and note the log file path (default:
%systemroot%\system32\LogFiles\Firewall\pfirewall.log) - Click OK, reproduce the connection failure, then open the log file in Notepad. Look for DROP entries with the IP address and port your application is trying to reach
Third-party firewall conflicts
If you have installed a third-party security suite (Norton, McAfee, Kaspersky, Bitdefender, ESET, or similar), it likely includes its own firewall that runs alongside or instead of Windows Defender Firewall. Adding a rule in Windows Firewall will not help if the third-party firewall is the one blocking the traffic:
- Open the third-party security software and look for its firewall or network protection settings
- Find the application control or program rules section and add an allow rule for the blocked program
- Some security suites have a silent or gaming mode that blocks popups but also silently blocks programs. Check if a mode like this is active
Common applications that get blocked
- Games (Steam, Epic, game executables): Multiplayer games need both inbound and outbound rules. The game launcher (Steam, Epic) and the actual game executable are separate programs that each need their own rule. After a game update, the executable path may change, requiring a new rule
- Remote desktop and remote access: Programs like Remote Desktop, TeamViewer, and AnyDesk need inbound rules to accept connections from other computers. Remote Desktop uses port 3389 by default
- Development tools: Local web servers, database servers, Node.js applications, and Docker containers all need inbound rules to be accessible from other devices or sometimes even from other programs on the same computer
- VPN software: VPN clients modify network routing and need firewall rules for their tunnel interfaces. If a VPN stops working after a Windows update, its firewall rules may have been reset
- Email clients: Desktop email clients like Outlook or Thunderbird need outbound access on specific ports (25, 465, 587 for SMTP; 993 for IMAP; 995 for POP3)
Reset Windows Firewall to defaults
If the firewall rules have become a tangled mess of conflicting allow and block rules (common after years of software installations and uninstallations), resetting to defaults can fix issues that are hard to diagnose:
- Open Windows Security, Firewall and Network Protection
- Click Restore firewalls to default (at the bottom)
- Confirm the reset
This removes all custom rules and restores the firewall to its original Windows configuration. After resetting, programs will prompt for access again when they first try to connect, and you can approve them one by one.
Firewall help in Marion
If Windows Firewall is blocking applications and you cannot identify or fix the rule causing the problem, Marion Remote Fix can connect to your computer remotely, review the firewall configuration, create the correct rules, and verify the application connects properly — without needing your computer in the shop.