| Previous | Next |
| STATUS_FWP_CONDITION_NOT_FOUND | STATUS_FWP_LAYER_NOT_FOUND |
STATUS_FWP_FILTER_NOT_FOUND
The rule object is missing, not merely inactive
STATUS_FWP_FILTER_NOT_FOUND means that the requested WFP filter object cannot be found in the filter engine. A filter is the rule that ties conditions, action, layer, weight, and optional context together. Therefore this status is different from a packet that did not match a filter: the rule object itself is absent from the requested lookup or operation.
Investigate the filter ID or GUID, provider and sublayer ownership, session lifetime, and transaction result. If a management tool displays a rule with a similar name, confirm that it is the same object and that it was installed in the correct layer and policy store; display names are not stable object identifiers.
What to verify
- Use the filter’s GUID or run-time ID, not only its display name.
- Check the provider, sublayer, layer, action, and effective weight.
- Review transaction commit and dynamic-session cleanup events.
- Do not infer that all firewall or IPsec policy is disabled because one filter is absent.
References
- Microsoft Open Specifications: NTSTATUS values
- Microsoft: FWPM_FILTER0 structure
- Microsoft: Windows Filtering Platform object model
- Microsoft: WFP operation
Looking for a different code? Search another status or error code.