| Previous | Next |
| STATUS_FWP_SUBLAYER_NOT_FOUND | STATUS_FWP_ALREADY_EXISTS |
STATUS_FWP_NOT_FOUND
The generic WFP lookup failed; identify the object class first
STATUS_FWP_NOT_FOUND is the generic WFP “object does not exist” result. Unlike the more specific STATUS_FWP_FILTER_NOT_FOUND, STATUS_FWP_CALLOUT_NOT_FOUND, or STATUS_FWP_LAYER_NOT_FOUND, it does not itself identify which class of policy object was absent.
That makes the API call and identifier type the central evidence. Determine whether the caller was resolving a provider, filter, layer, sublayer, context, callout, or another object, and whether it supplied a GUID, LUID, enumeration handle, or a stale cached ID. Generic retries tend to hide lifecycle defects; an explicit object inventory is more useful.
What to verify
- Log the API call, object class, identifier type, and session handle.
- Re-enumerate the relevant object class before relying on a cached ID.
- Check dynamic-session cleanup, transactions, and policy reload timing.
- Use the more specific WFP status when the calling API provides one.
References
- Microsoft Open Specifications: NTSTATUS values
- Microsoft: Windows Filtering Platform object model
- Microsoft: WFP operation
- Microsoft: FWPM_FILTER0 structure
Looking for a different code? Search another status or error code.