Fix STATUS_FWP_CANNOT_PEND (0XC0220103) in Windows

What's this error anyway?

0XC0220103 is a Windows Filtering Platform (WFP) error. It means a filter driver tried to pend a classify operation but couldn't. In plain English: something tried to pause network traffic for inspection and the system said no. This usually happens when you're running a VPN, a firewall, or some security software that hooks into WFP. I've seen it most often after a Windows update or when two security tools fight over the same network stack.

Don't bother with Google's first page of generic advice. The culprit here is almost always a stale WFP filter or a third-party driver messing with things. Let's fix it in order of effort.

Fix 1: The 30-second reset (try this first)

This resets all WFP filters to default. It sounds scary but it only affects Windows Firewall and related rules. Your personal files and apps stay untouched.

Open Command Prompt as administrator. Hit Start, type cmd, right-click and pick Run as administrator.
Run these two commands:

netsh advfirewall reset

netsh advfirewall set allprofiles state on

The first command wipes custom firewall rules (yes, all of them, so write down any weird ones you added). The second ensures the firewall is actually on. Once done, restart your VPN or the app that threw the error. I'd say this fixes 60% of cases.

If the error still shows up, move on.

Fix 2: The 5-minute check for third-party conflicts

WFP errors like this love to happen when you've got more than one security product running. Common offenders: Comodo Firewall, Malwarebytes, McAfee, or any VPN client with a kill switch. They all install WFP filters, and sometimes one of them fails to pend correctly.

Here's what to do:

Open Device Manager. Press Win + X and select Device Manager.
Go to Network adapters. Look for entries like WFP Native MAC Layer or WFP Lightweight Filter—you might see several.
Right-click each one and choose Properties. Go to the Driver tab and note the provider. If any say a third-party company (not Microsoft), that's your suspect.
Uninstall the driver for that specific filter. Reboot. Windows will reinstall its own.

Also, check your security software's settings. Most have a reset filters or repair option. For VPNs, just reinstall the client—it often clears the broken filter.

If you're still stuck after 5 minutes, we go deeper.

Fix 3: The 15-minute Winsock reset and driver refresh

This is the nuclear option. It resets the entire network stack, including WFP. Do this only if the first two didn't help.

Open Command Prompt as admin again.
Run these in order:

netsh winsock reset

netsh int ip reset

ipconfig /flushdns

Then reboot. This clears any corrupted Winsock catalog entries that WFP depends on. I've seen this fix weird VPN disconnections too, so it's worth doing anyway.

While you're in there, update your network drivers. Go to your motherboard or laptop manufacturer's site and grab the latest Ethernet/Wi-Fi driver. Windows Update often lags. Outdated drivers can cause exactly this error after a feature update.

If you're using an older VPN (like some OpenVPN-based ones from 2019), check for a beta or dev version. The TAP drivers they use are notorious for breaking WFP.

Still not fixed? Check the event log

Sometimes the error is triggered by a specific service. Open Event Viewer (eventvwr.msc), go to Windows Logs > System, and look for events with source Microsoft-Windows-Base-Filtering-Engine. They'll reference the failing filter GUID. Google that GUID plus "0XC0220103"—you might land on a vendor-specific fix.

In my experience, the third-party driver route is the real culprit 80% of the time. If you're running a corporate managed machine, check with IT—they might have a policy that conflicts.

That's the whole flow. Start with the reset, work through the drivers, and you'll kill this error. Good luck.