STATUS_FWP_LAYER_NOT_FOUND (0xC0220004) Fix for Windows Firewall

I've seen this error pop up on a lot of help desk tickets. You're trying to start a VPN client, enable a firewall rule, or maybe a game's anti-cheat just failed. The error code 0xC0220004 with the message STATUS_FWP_LAYER_NOT_FOUND shows up. It's annoying, but it's fixable. Let's get you back up in about 15 minutes.

The Quick Fix: Reset Windows Filtering Platform and Firewall

Don't waste time hunting for missing DLLs or reinstalling drivers. The real fix is resetting the Windows Filtering Platform (WFP) state. Here's exactly how to do it.

1. Press Windows Key + X and select Windows Terminal (Admin) or Command Prompt (Admin). You need admin rights for this.
2. Run this command to reset the WFP configuration:
   

   netsh wfp reset

   You'll see a message: Resetting WFP configuration... OK.
3. Then reset the Windows Firewall rules:
   

   netsh advfirewall reset

   Expect: Resetting firewall settings... OK.
4. Now restart the Windows Firewall service. Run:
   

   net stop MpsSvc && net start MpsSvc

   You should see The Windows Firewall service was stopped successfully. followed by The Windows Firewall service was started successfully.
5. Finally, restart your computer. This clears any cached states.

After reboot, try whatever was giving you the error. It should work now. If it doesn't, move to the next section.

Why This Works

The Windows Filtering Platform is the backbone of the firewall. It defines layers — like network, transport, application — where filters hook in. If a layer gets corrupted or removed (common after a failed Windows update or a third-party firewall uninstall), Windows can't find it. The netsh wfp reset command rebuilds the entire WFP database from scratch. The advfirewall reset then resets all firewall rules to defaults. Together, they give you a clean slate.

I've seen this happen most often after uninstalling antivirus software that had its own firewall (like Norton or McAfee) or after a Windows 10 22H2 update that went sideways. Sometimes a VPN client like Cisco AnyConnect or WireGuard triggers it when it tries to register custom filtering layers.

When the Reset Doesn't Work

If you're still getting the error after the reset, try these in order:

1. Check for Corrupted System Files

1. Open Command Prompt as admin again.
2. Run sfc /scannow. This checks system files. Let it finish — it can take 15 minutes.
3. If it finds corrupted files, run DISM /Online /Cleanup-Image /RestoreHealth. This fixes the component store.
4. Restart after all repairs complete.

2. Reset Winsock and IP Stack

Sometimes the issue is deeper. Run these three commands in order (admin prompt):

netsh winsock reset
netsh int ip reset
ipconfig /flushdns

Restart again. This has fixed the error for a handful of users after VPN updates.

3. Uninstall Problematic Software

If the error started after installing a specific app (VPN, firewall, game anti-cheat like BattlEye or EasyAntiCheat), uninstall that app, restart, then try your task again. If it works, reinstall the app — it likely installed bad WFP layers that need a fresh install.

Preventing This in the Future

Three things I tell everyone:

• Never uninstall third-party firewall software without using their official removal tool. Many leave behind WFP filters that corrupt the platform. Go to the vendor's site and download their uninstaller.
• Keep Windows fully updated. Microsoft has patched several bugs that caused WFP layer corruption. Run Windows Update monthly at minimum.
• Use System Restore points before installing VPN or firewall software. If something breaks, you can roll back in minutes instead of troubleshooting for an hour.

That's it. The 0xC0220004 error is a pain, but it's almost always just a corrupted WFP database. The reset command fixes it nine times out of ten. Save the full repair sequence above somewhere — you'll need it again if you tinker with network software.