Fix 0xC0220034: Provider Context Mismatch Error

This Windows Filtering Platform error means the provider context is the wrong type. Usually caused by a corrupted firewall rule or a third-party VPN/firewall driver.

The 30-Second Fix: Reset WFP with netsh

This is the fastest way to clear out corrupted WFP state. Open Command Prompt as Administrator and run:

netsh wfp reset

Reboot the machine. If the error was from a transient corruption, it's gone. This command resets the Windows Filtering Platform store, not the firewall rules themselves—so it won't break your network config.

Still here? Let's move to the 5-minute fix.

The 5-Minute Fix: Remove the Offending Firewall Rule

The culprit here is almost always a single firewall rule that got its provider context mangled. This happens a lot after a VPN or antivirus product uninstall leaves behind a rule pointing to a missing provider.

Open Windows Defender Firewall with Advanced Security (wf.msc). Go to Inbound Rules, then Outbound Rules. Sort by Program and look for any rule with a blank or weird program path. Also check Connection Security Rules and Monitor - those sometimes show orphaned rules.

Delete any rule that looks suspicious, especially ones from third-party firewall tools like ZoneAlarm, Norton, or McAfee. If you can't identify the bad rule, export all rules first (netsh advfirewall export "C:\backup.wfw"), then delete them in bulk by resetting the firewall:

netsh advfirewall reset

This nukes every custom rule. You'll lose your custom ports, but it's the nuclear option that works.

The 15+ Minute Fix: Advanced Registry and Driver Cleanup

If the above didn't fix it, we're dealing with a deeper driver or registry issue. This happens when a third-party network driver (usually a VPN like Cisco AnyConnect, Pulse Secure, or a firewall like Comodo) leaves behind a corrupted provider context in the registry.

Step 1: Check for Bad Drivers

Open Device Manager, expand Network adapters. Look for any device with a yellow exclamation mark or marked as disabled. Right-click and uninstall it, especially if it's from a VPN or security product you've removed.

Step 2: Clean the Registry

Back up your registry first. Then open Regedit and navigate to:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WinSock2\Parameters

Under Namespaces, look for keys referencing your old VPN software (e.g., "Cisco", "AnyConnect"). Delete them. Also check:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WFP

If there's a Providers subkey, export it first, then delete any entries that don't look like default Microsoft ones (e.g., keys with GUIDs pointing to missing DLL paths).

Step 3: Reinstall WFP Base Drivers

Open an admin PowerShell and run:

dism /online /cleanup-image /restorehealth
sfc /scannow

After that, manually reinstall WFP base drivers:

pnputil /delete-driver oem*.inf /force
pnputil /scan-devices

This forces Windows to re-enumerate all network devices, including WFP providers.

One more thing: If you're running a third-party firewall or VPN, just uninstall it completely using the vendor's cleanup tool. For example, Cisco AnyConnect has a vpncleanup utility. Norton has a removal tool. These apps leave behind junk that causes this exact error.

Step 4: Last Resort — Export and Reimport Firewall Rules

If nothing else worked, the XML store for WFP rules is corrupt. You can sometimes fix it by exporting, then importing again:

netsh advfirewall export "C:\fw.xml"
netsh advfirewall reset
netsh advfirewall import "C:\fw.xml"

If that fails, skip the import and rebuild your rules manually. It's painful, but it's the final fix. I've seen this once in a thousand cases—usually on a domain-joined machine with GPO conflicts.

Real-world trigger: This error shows up most often after a user uninstalls Cisco AnyConnect but leaves the firewall rules intact. The rule tries to call a provider context that no longer exists. The netsh wfp reset command clears that provider context table and lets the system recover.