What Windows Firewall does and why it stops working
Windows Defender Firewall is a built-in network security feature in Windows 10 and Windows 11 that filters inbound and outbound traffic based on rules, profiles, and app permissions.
If it stops working, programs may lose network access, security prompts may disappear, or the firewall service may fail to start at all.
This guide explains how to fix Windows Firewall not working using the most reliable checks first, then moving into deeper repair steps if the problem is caused by corrupted services, damaged system files, or conflicting security software.
How to tell whether Windows Firewall is actually failing
Before changing settings, confirm the problem is truly with the firewall and not with a single app or network profile.
Common signs include missing firewall notifications, errors when opening Windows Security, disabled firewall toggles that revert back, or applications that are blocked even after being allowed.
- Windows Security shows firewall status as off when it should be on.
- The MpsSvc or BFE service is stopped.
- Network profiles are incorrectly marked as Public or Domain.
- Third-party antivirus or VPN software is managing filtering rules.
- Group Policy or registry settings are overriding local controls.
Check for third-party security software first
One of the most common reasons Windows Firewall appears broken is that another security suite is controlling firewall behavior.
Products from McAfee, Norton, Bitdefender, Kaspersky, ESET, or even a VPN client with network protection features can disable or replace Microsoft Defender Firewall.
Open the security app and look for firewall, network protection, or web filtering settings.
If you recently installed or updated one of these tools, temporarily disable it or uninstall it to test whether Windows Firewall starts working again.
If the issue disappears after removal, reinstall the product using its default configuration or keep only one firewall active at a time.
Use Windows Security to reset firewall settings
Windows includes a built-in reset option that restores firewall policies to their default state.
This is often the fastest fix when the configuration has been altered by software, manual changes, or corrupted profiles.
- Open Windows Security.
- Select Firewall & network protection.
- Scroll down and choose Restore firewalls to default.
- Confirm the reset.
After the reset, test whether the firewall turns on normally and whether apps can connect again.
This step removes custom rules, so only use it if you are comfortable re-creating exceptions later.
Start the required services
Windows Firewall depends on a small set of background services.
If they are stopped or disabled, the firewall may not open, may refuse to save changes, or may display an error message.
Press Win + R, type services.msc, and press Enter.
Check these services:
- Base Filtering Engine (BFE)
- Windows Defender Firewall (MpsSvc)
- Security Center
For each one, set the startup type to Automatic or Automatic (Delayed Start) where available, then click Start.
If a service refuses to start, note the error text because it often points to permission issues, registry corruption, or a damaged dependency.
Run the built-in network and security troubleshooters
Windows 11 and Windows 10 include troubleshooters that can repair common network and policy problems.
They will not fix every firewall issue, but they can restore settings that were changed by an update or a misconfigured adapter.
Go to Settings > System > Troubleshoot > Other troubleshooters, then run the following tools if available:
- Network Adapter
- Internet Connections
- Windows Store Apps
After the scan, restart the PC and check the firewall status again.
If the problem started after a major update, also run Windows Update and install any pending patches.
Repair system files with SFC and DISM
Corrupted system files can break Windows Defender Firewall, especially if the firewall service, security center components, or policy files are damaged.
The most useful repair sequence is running System File Checker first, then DISM if needed.
Open Command Prompt as administrator and run:
sfc /scannow
If SFC reports that it found and repaired files, restart and retest.
If the issue remains, run:
DISM /Online /Cleanup-Image /RestoreHealth
After DISM finishes, run sfc /scannow again.
This combination repairs the Windows component store and restores missing or corrupted firewall-related files.
Check Group Policy and registry restrictions
On managed devices, Windows Firewall may be controlled by Group Policy, Microsoft Intune, or an organization’s security baseline.
If the machine belongs to a work or school environment, local settings may not stick because centralized policy overrides them.
Open Local Group Policy Editor on supported editions and review firewall policies under Computer Configuration > Administrative Templates > Network > Network Connections > Windows Defender Firewall.
Look for settings that disable the firewall, block rule changes, or force a specific profile.
If policy is not the cause, check for registry damage only if you are comfortable editing advanced settings.
Incorrect registry edits can create new problems, so back up the system or create a restore point first.
Reset the network stack if apps still cannot connect
Sometimes Windows Firewall is functioning, but the TCP/IP stack, Winsock catalog, or adapter configuration is corrupted.
In that case, the firewall can appear to be the problem while the network layer is actually broken.
Run Command Prompt as administrator and enter:
netsh winsock reset
netsh int ip reset
Then restart the computer.
If needed, also use Settings > Network & internet > Advanced network settings > Network reset to reinstall network adapters and restore defaults.
This is especially helpful after VPN installs, driver updates, or malware cleanup.
Test firewall behavior with a clean boot
A clean boot helps identify whether a startup program, service, or background filter is interfering with firewall operations.
This is useful when the firewall works briefly, then fails after login or after another security tool loads.
Use msconfig to hide Microsoft services, disable the rest, and turn off startup items in Task Manager.
Reboot and test the firewall.
If it works in a clean boot, re-enable items in batches until the conflicting software is found.
Recreate firewall rules when only one app is affected
Sometimes the firewall itself is healthy, but a specific application is blocked by a damaged or missing rule.
This often happens after an application update, a change in executable path, or a migration to a new user profile.
Open Windows Defender Firewall with Advanced Security and check inbound and outbound rules for the app.
Make sure the correct executable is allowed, the profile matches the current network, and the rule is enabled.
If necessary, delete the broken rule and add it again using the app’s current installation path.
When to use a system restore or repair install
If none of the above works, the firewall components may be too damaged for normal troubleshooting.
A System Restore point can roll back recent changes that broke Windows Firewall without affecting personal files.
If restore points are unavailable, an in-place repair install of Windows can replace core components while keeping apps and data.
Repair install is often the best last step when the service infrastructure, security center, or policy engine is corrupted and standard commands no longer help.
It is also a good option after repeated malware infections or failed feature updates.
Common causes to remember
- Third-party antivirus or VPN firewall replacement
- Stopped BFE or MpsSvc services
- Corrupted Windows system files
- Group Policy restrictions on managed devices
- Broken firewall rules for specific apps
- Damaged TCP/IP or Winsock settings
- Failed Windows update or partial upgrade
By working through these checks in order, you can usually fix Windows Firewall not working without guessing.
Start with service status and security software, then move into resets and repairs only if the simpler steps do not restore normal behavior.