What does NTSTATUS 0xC0220027 (STATUS_FWP_TYPE_MISMATCH) mean?

 
Previous Next
STATUS_FWP_MATCH_TYPE_MISMATCH STATUS_FWP_OUT_OF_BOUNDS

STATUS_FWP_TYPE_MISMATCH

The condition value type and its selected data representation disagree

STATUS_FWP_TYPE_MISMATCH is different from a bad comparison operator. Here the problem is the FWP_VALUE0 or FWP_CONDITION_VALUE0 type itself: the field expects a compatible WFP data type, and the selected union member must hold the corresponding representation.

Check the source value before it reaches WFP. Configuration parsers commonly collapse an address, port, SID, string, and byte blob into one generic variant; that works only if the adapter maps each input to the field-specific WFP type. Logging only the human-readable value hides the type mismatch.

What to inspect

  • The field GUID and the documented value type it accepts at the chosen layer.
  • The type tag and the union member populated by the policy client.
  • Pointer validity for pointer-based types, including byte blobs, SIDs, strings, and ranges.
  • Any type conversion performed from configuration, RPC, JSON, or a higher-level rule model.

References


Looking for a different code? Search another status or error code.