| Previous | Next |
| FWP_E_INVALID_NET_MASK | FWP_E_INVALID_INTERVAL |
FWP_E_INVALID_RANGE
FWP_E_INVALID_RANGE means an FWP_RANGE condition is malformed. Its endpoints must be comparable values of the expected type and must describe a valid lower-to-upper interval.
What to verify for FWP_E_INVALID_RANGE
- Confirm the lower and upper values use the same WFP data type.
- Check that the lower bound does not exceed the upper bound.
- Use a range only on a condition field and filtering layer that accept range matching.
Diagnostic interpretation of FWP_E_INVALID_RANGE
FWP_E_INVALID_RANGE has the HRESULT value 0x80320020. AllStat records the condition as “An FWP_RANGE is not valid.”. For FWP_E_INVALID_RANGE, in practice, interpret that wording at the boundary owned by Windows Filtering Platform or IPsec policy state, rather than treating the value as a generic Windows message.
Evidence to capture for FWP_E_INVALID_RANGE
- Record the exact COM method or Windows API, its input object, the calling thread, and the full 0x80320020 value before a wrapper converts it to an exception or Boolean result.
- Capture any IErrorInfo text, activity identifier, event-log entry, and subsystem trace that mentions FWP_E_INVALID_RANGE or the fwp / range operation.
- Reproduce FWP_E_INVALID_RANGE with the smallest valid input and note whether the result changes with identity, architecture, service state, or target object.
Retry and recovery for FWP_E_INVALID_RANGE
Retry FWP_E_INVALID_RANGE only when the owning API documents a transient state or after the condition described as “An FWP_RANGE is not valid.” has changed. For FWP_E_INVALID_RANGE, configuration, policy, format, and authorization failures normally require correction first; an immediate loop can hide the original call site and add secondary errors.
Looking for a different code? Search another status or error code.