| Previous | Next |
| STATUS_FWP_INVALID_ENUMERATOR | STATUS_FWP_INVALID_NET_MASK |
STATUS_FWP_INVALID_FLAGS
A flags field mixes lifecycle and object-state bits incorrectly
STATUS_FWP_INVALID_FLAGS means BFE rejected a bitmask before applying the requested operation. Flags are specific to each WFP structure; a bit that is documented for a provider or a session is not automatically meaningful for a filter. Some filter flags are mutually exclusive, and some state flags are returned by BFE but cannot be supplied when creating a filter.
Diagnose the numeric flags field against the exact structure and target Windows version. Do not mask off unknown bits blindly in durable policy code: that may remove a required lifecycle choice such as persistence or boot-time behavior, while leaving the original installer defect unexplained.
What to inspect
- The declaring structure, all requested flag names, and the raw hexadecimal value.
- Mutually exclusive combinations, including persistent and boot-time filter settings.
- Flags that are output-only or valid only after BFE has created the object.
- The SDK or WDK version used to compile the policy client and the target OS support level.
References
- Microsoft: WFP error codes
- Microsoft: FWPM_FILTER0 flags
- Microsoft: FwpmFilterAdd0
- Microsoft WFPSampler source
Looking for a different code? Search another status or error code.