What does NTSTATUS 0xC0220016 (STATUS_FWP_LIFETIME_MISMATCH) mean?

 
Previous Next
STATUS_FWP_KM_CLIENTS_ONLY STATUS_FWP_BUILTIN_OBJECT

STATUS_FWP_LIFETIME_MISMATCH

The referenced policy objects would outlive each other incorrectly

STATUS_FWP_LIFETIME_MISMATCH prevents an association between WFP objects whose lifetimes are incompatible. WFP distinguishes dynamic objects, static objects, persistent objects, and built-in objects. A dynamic object can disappear when its owning session ends, whereas a persistent object is intended to survive BFE and system restarts.

Follow every reference in the attempted association—provider, sublayer, filter, callout, and context—and classify each object’s lifetime before changing flags. Converting an object to persistent policy just to avoid the error can leave enforcement active after the service that owns its configuration is gone.

What to inventory

  • The lifetime of the caller’s session and every linked object.
  • Persistent and boot-time flags used during creation.
  • Provider ownership and whether policy should exist when the provider service is disabled.
  • The cleanup behavior expected when the client or BFE restarts.

References


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