STATUS_FWP_CONDITION_NOT_FOUND (0xC0220002) Fix

Quick Fix for 0xC0220002

This error usually pops up when Windows Firewall can't find a filter condition it expects. It's almost always a corrupted firewall rule, not a hardware problem. The fix is two commands — run them in order.

1. Open Command Prompt as Administrator (right-click Start > Command Prompt (Admin) or PowerShell (Admin)).
2. Type (or copy-paste) this first command:
   

   netsh advfirewall reset

   Hit Enter. This resets the Windows Firewall rules back to defaults. It doesn't delete your third-party firewall if you have one.
3. Once that finishes, run:
   

   netsh advfirewall set allprofiles state on

   Hit Enter. This turns the firewall back on for all network profiles (Domain, Private, Public).
4. Reboot your machine. Just to be safe.

That's it. 90% of the time, this clears the error. If you still see it, there's likely a deeper issue (keep reading).

Why This Works

Windows Firewall stores filter conditions in a database that can get corrupted when rules are added or removed poorly. Common triggers:

• A VPN client (like Cisco AnyConnect, OpenVPN, or WireGuard) messes with rules during connection/disconnection.
• A software firewall (Norton, McAfee, ZoneAlarm) leaves orphaned conditions after uninstall.
• You manually edited firewall rules via PowerShell or third-party tools and broke something.

The netsh advfirewall reset command rebuilds that database from scratch. It's like clearing the cache for the firewall — it removes corrupted entries and starts fresh. The second command makes sure the firewall is active on all network profiles after the reset.

Note: This reset will remove any custom rules you created. If you have specific open ports or app exceptions, you'll need to add them back afterward. Write them down first if that matters.

Less Common Variations (When Reset Doesn't Work)

1. Third-Party Firewall Leftovers

If you uninstalled a third-party firewall weeks ago, its drivers might still be loaded. Check Device Manager > View > Show hidden devices. Look under "Non-Plug and Play Drivers" for anything named after that firewall. Uninstall those too. Then run the two commands again.

2. Corrupted Windows Security Center Service

The Windows Security Center service (wscsvc) manages firewall status. If it's stuck or corrupted, the firewall reset won't hold. Restart it manually:

1. Press Win+R, type services.msc, hit Enter.
2. Find "Security Center". Right-click > Stop.
3. Wait a few seconds, then right-click > Start.
4. Reboot and test the firewall again.

3. Group Policy Override (Domain-Joined Machines)

If you're on a corporate network, Group Policy might enforce specific firewall rules that conflict. Check with your IT team — they might need to push a policy refresh (gpupdate /force) or remove a bad rule from the domain controller.

4. Windows Registry Corruption (Rare)

I've seen this twice in 14 years. The firewall rules are stored under HKLM\SYSTEM\CurrentControlSet\Services\SharedAccess\Parameters\FirewallPolicy. If that registry key is corrupted, even the netsh reset fails. Back up the key first, then delete the subkeys and run the netsh commands again. This is advanced — don't try it unless you're comfortable with registry editing.

Prevention Tips

• Don't mix firewalls. Use one — either Windows Defender Firewall or a third-party one, not both. Double firewalls cause conflicts.
• Uninstall VPN clients properly. Use the vendor's uninstaller, not just delete the folder. Residual drivers are a common cause.
• Keep Windows updated. Microsoft has patched several firewall-related bugs over the years. The latest cumulative update often resolves these errors silently.
• Export your rules before making changes. Run netsh advfirewall export "C:\backup.wfw" to save a backup. Takes 2 seconds and saves headaches later.

If you've tried everything above and still get 0xC0220002, it's probably time for a Windows repair install. Backup your data, run setup from within Windows, and choose "Keep personal files and apps." That's the nuclear option, but I've seen it fix firewall issues that nothing else could.