| Previous | Next |
| FWP_E_KM_CLIENTS_ONLY | FWP_E_BUILTIN_OBJECT |
FWP_E_LIFETIME_MISMATCH
FWP_E_LIFETIME_MISMATCH means that the caller tried to associate WFP objects whose lifetimes are incompatible. It often points to mixing session-owned policy with an object intended to persist across the engine or with a dependency owned by another lifetime boundary.
Why this matters
WFP sessions can be dynamic, in which case objects added during the session are deleted when the session ends. Persistent and boot-time objects have different lifetimes. Linking them incorrectly can leave a policy object referring to data that must disappear earlier, so WFP rejects the association instead.
How to correct it
- Map every provider, sublayer, filter, callout, and context to its intended lifetime before recreating anything.
- Keep a transient enforcement graph entirely within its dynamic session, or create the required persistent graph using compatible objects.
- Do not solve the issue by making everything persistent; that can leave security policy behind after crashes or uninstall.
Microsoft: WFP error codes · Microsoft: dynamic-session object lifetime · Microsoft: persistent and boot-time filter flags
Looking for a different code? Search another status or error code.