| Previous | Next |
| STATUS_FWP_CALLOUT_NOT_FOUND | STATUS_FWP_FILTER_NOT_FOUND |
STATUS_FWP_CONDITION_NOT_FOUND
The match criterion being referenced is unavailable
STATUS_FWP_CONDITION_NOT_FOUND identifies a missing WFP filter condition. In WFP, a condition is the match criterion that tests a field, a match type and a value before a filter action is taken. It is not the filter itself and it is not the traffic that the filter would have matched.
This status is usually a configuration or object-reference problem. Check the exact condition identity, the layer where the condition is meaningful, and the transaction or session that should have created it. A condition can also be invalid in a different way when its field or operand is incompatible with the selected layer; that is distinct from the object not being found.
What to verify
- Capture the condition field key, match type, value type, and intended layer.
- Verify that creation and lookup use the same object identity and API version.
- Check transaction boundaries and dynamic-session lifetime.
- Keep missing-condition diagnosis separate from filter-not-found and type-mismatch errors.
References
- Microsoft Open Specifications: NTSTATUS values
- Microsoft: FWPM_FILTER_CONDITION0 structure
- Microsoft: Windows Filtering Platform object model
- Microsoft: WFP operation
Looking for a different code? Search another status or error code.