| Previous | Next |
| FWP_E_INVALID_INTERVAL | FWP_E_NULL_DISPLAY_NAME |
FWP_E_ZERO_LENGTH_ARRAY
FWP_E_ZERO_LENGTH_ARRAY identifies this condition: a WFP object supplied an array whose contract requires at least one element but whose count is zero.
What the status narrows down
A Windows Filtering Platform management call is defined by the exact FWPM structure revision, layer, sublayer, action, conditions, provider context, and BFE transaction. Zero-initialization and backing-buffer lifetime matter because the engine validates the submitted object graph, not the caller’s high-level intent.
A null pointer and a non-null zero-element array are different contract violations and should not be collapsed.
Evidence worth preserving
- API and structure member containing the array
- Count, pointer, allocation capacity, and source collection size
- Filter condition/action/provider-context semantics that require membership
- Serialization or language projection that may drop an empty collection
A controlled diagnostic sequence
- Submit one valid element and compare with the empty case.
- Assert count/pointer consistency before calling BFE.
- Test an omitted optional array separately from a required empty array.
Correction and proof
Repair the failed contract rather than the surrounding system: Reject the empty configuration earlier or omit the optional object entirely when the API permits omission.
Close the incident only when empty, singleton, and multi-element tests produce documented outcomes and no invalid filter is committed.
Technical references
The following documentation is most relevant when checking the code against the actual Windows contract for Windows Filtering Platform array cardinality:
Looking for a different code? Search another status or error code.