| Previous | Next |
| STATUS_FWP_ZERO_LENGTH_ARRAY | STATUS_FWP_INVALID_ACTION_TYPE |
STATUS_FWP_NULL_DISPLAY_NAME
The object can have a GUID but still fail its required display annotation
STATUS_FWP_NULL_DISPLAY_NAME occurs when the required displayData.name member is null for an object being added. The display name is not the object key: BFE can generate or store identifiers separately, but the management structure still requires this annotation for the relevant object class.
Correct the object construction code rather than synthesizing a changing name from an address or random value. Stable names improve policy inventory and support diagnosis, while the GUID or run-time ID remains the identifier that must be used for later lookup and cleanup.
What to inspect
- The exact
FWPM_DISPLAY_DATA0member passed to the add call. - The string lifetime and termination at the call boundary.
- The stable GUID or LUID used for identity, kept separate from the display name.
- Whether localization or configuration generation can emit a null name for one policy path.
References
- Microsoft: WFP error codes
- Microsoft: FWPM_FILTER0 displayData requirements
- Microsoft: FwpmFilterAdd0
- Microsoft WFPSampler source
Looking for a different code? Search another status or error code.