When an application can’t reach the network but internet access works fine for everything else, Windows Defender Firewall silently blocking that one app is one of the most common explanations.
Common Symptoms
- One specific application can’t connect while others work fine
- The app worked previously and stopped after a Windows Update
- No visible error, the app just times out or shows “connection failed”
Possible Causes
- The app was never granted a firewall rule (common on first install)
- A firewall rule exists but only for the wrong network profile (Private vs Public)
- A rule was accidentally removed or disabled
Before You Begin
Temporarily disable Windows Defender Firewall (never a third-party or corporate firewall without approval) to confirm it’s actually the cause before making permanent rule changes — then re-enable it immediately after the test.
Method 1 — Allow the app through the firewall
Method 2 — Create a specific inbound/outbound rule
Open Windows Defender Firewall with Advanced Security
Search for it in Windows search.
If the app worked before a Windows Update, check whether the update reset firewall rules to default — this happens occasionally with major feature updates.
Frequently Asked Questions
Is it safe to just disable the firewall to fix this?
No — disabling the firewall entirely removes protection for every application, not just the one you’re troubleshooting. Adding a specific rule for just that app is the safer approach.
Conclusion
Adding a specific, narrowly scoped firewall rule for the affected application resolves the block without reducing overall protection.
Related Articles
