| Previous | Next |
| ERROR_IPSEC_TRANSPORT_FILTER_EXISTS | ERROR_IPSEC_MM_AUTH_EXISTS |
ERROR_IPSEC_TRANSPORT_FILTER_NOT_FOUND
The filter identity is the compiled traffic match
ERROR_IPSEC_TRANSPORT_FILTER_NOT_FOUND appears when code tries to delete, update, or associate a transport-mode filter that is absent from the addressed policy database. The lookup can fail even when a similarly named connection-security rule exists, because the runtime filter is derived from the rule’s full traffic selectors and policy-store source.
Re-enumerate policy immediately before modification. Group Policy refresh, service restart, dynamic-session teardown, or a previous partial cleanup can remove the effective filter while leaving cached identifiers in management software. Also confirm that the request describes transport mode: tunnel-mode policy uses different endpoints and a different set of WFP objects.
Evidence to capture
- The filter key or complete selector used by the failing call.
- The writable policy store and the effective source shown in
ActiveStore. - Whether the rule was created dynamically and disappeared with its owner session.
- Whether the intended configuration is actually tunnel mode.
References
- Microsoft: WFP sessions and dynamic object lifetime
- Microsoft: transport-mode Quick Mode policy
- RFC 4301: transport-mode processing
Looking for a different code? Search another status or error code.