| Previous | Next |
| ERROR_IPSEC_MM_FILTER_PENDING_DELETION | ERROR_IPSEC_TUNNEL_FILTER_PENDING_DELETION |
ERROR_IPSEC_TRANSPORT_FILTER_PENDING_DELETION
Deletion is a lifecycle state, not a missing-filter result
ERROR_IPSEC_TRANSPORT_FILTER_PENDING_DELETION says the transport-mode filter was found, but its removal is already in progress. Management code can observe this state when overlapping operations delete and recreate policy, when a transaction is being committed, or when asynchronous policy propagation has not finished releasing dependent objects.
Do not immediately create a replacement with the same identity in a tight loop. First serialize policy updates, finish or abort the owning transaction, and re-enumerate the filter engine after the delete completes. If the filter belonged to a dynamic WFP session, closing that session is the authoritative cleanup path. Repeated delete calls do not accelerate reference release and can obscure which operation initiated teardown.
Safe recovery pattern
- Record the transaction and session responsible for the delete.
- Wait for policy enumeration to stop returning the old filter before recreating it.
- Avoid simultaneous GPO refresh and application-owned policy replacement.
- Use one explicit transaction for related filter and provider-context changes.
References
- Microsoft: WFP sessions, transactions, and lifetimes
- Microsoft: transport policy structure
- Microsoft: Windows IPsec error code definitions
Looking for a different code? Search another status or error code.