| Previous | Next |
| FWP_E_ZERO_LENGTH_ARRAY | FWP_E_INVALID_ACTION_TYPE |
FWP_E_NULL_DISPLAY_NAME
FWP_E_NULL_DISPLAY_NAME — 0x80320023
This code places the first failure in WFP display metadata. Operationally, the WFP object lacks the required human-readable name in FWPM_DISPLAY_DATA0 for an operation that requires it.
Meaning in the subsystem
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.
The filterKey may be generated when zero, but the display name has its own required contract for the affected object.
Minimum useful evidence
- Object type, displayData. Name, description, localization source, and lifetime
- FWPM_FILTER0/provider/sublayer/callout structure passed to the add API
- Whether an empty string or null pointer was produced by configuration parsing
- BFE transaction state and generated object key
Isolate the responsible condition
- Supply a stable nonempty name while keeping all filtering semantics unchanged.
- Test localization/resource failure separately from object creation.
- Enumerate the committed object and verify its display metadata.
Regression proof
A defensible correction is specific to the evidence: Populate an operator-meaningful stable name and keep the backing string valid for the duration of the call.
Close the incident only when objects can be enumerated and distinguished by name after restart, while a null-name control remains rejected.
Technical references
These references define the HRESULT family and subsystem contract used above:
Looking for a different code? Search another status or error code.
