| Previous | Next |
| ERROR_IPSEC_TUNNEL_FILTER_EXISTS | ERROR_IPSEC_MM_FILTER_PENDING_DELETION |
ERROR_IPSEC_TUNNEL_FILTER_NOT_FOUND
A cached tunnel identifier may outlive its policy objects
ERROR_IPSEC_TUNNEL_FILTER_NOT_FOUND means a management operation could not locate the tunnel filter it intended to modify or delete. Tunnel installation creates several associated WFP objects from the supplied endpoints, Quick Mode policy, optional Main Mode policy, and traffic conditions. Partial cleanup or transaction rollback can make a cached identifier invalid even when a higher-level rule record remains.
Enumerate the current tunnel policy and compare its unique key and conditions with the request. Dynamic policies disappear when their owning WFP session closes, and Group Policy refresh can replace effective objects. Also verify address family and endpoint ordering; a transport rule or a tunnel with different outer endpoints is not the same object.
Reconstruction data for troubleshooting
- The policy key returned when the tunnel was originally added.
- Outer tunnel endpoints and inner filter conditions.
- The WFP session and transaction that owned the objects.
- The policy-store source after the most recent Group Policy refresh.
References
- Microsoft: tunnel policy object creation
- Microsoft: WFP transactions and object lifetime
- Microsoft: filters created for tunnel mode
Looking for a different code? Search another status or error code.