| Previous | Next |
| STATUS_FWP_TOO_MANY_SUBLAYERS | STATUS_FWP_INVALID_AUTH_TRANSFORM |
STATUS_FWP_CALLOUT_NOTIFICATION_FAILED
The filtering engine called a callout notification routine and it failed
These status values come from the Windows Filtering Platform path. For STATUS_FWP_CALLOUT_NOTIFICATION_FAILED, wFP classifies traffic through layers, filters, provider contexts, sublayers, and callouts; IPsec policy is also configured through WFP at IKE/AuthIP-related layers.
Callouts can receive notifications for filter addition, deletion, and other lifecycle events. This status means WFP reached the callout but the notification callback rejected or failed the event.
For STATUS_FWP_CALLOUT_NOTIFICATION_FAILED, for diagnostics, keep the failing API call, layer or sublayer key, provider context type, filter condition set, callout id, engine state, and whether the Base Filtering Engine, IKEEXT, TCP/IP stack, or L2 path was ready.
What to inspect
- Check the callout driver logs around notifyFn.
- Verify filter/action/context compatibility for that callout.
- Do not treat this as a TCP failure; it is a callout lifecycle failure.
References for STATUS_FWP_CALLOUT_NOTIFICATION_FAILED
- Microsoft Open Specifications: NTSTATUS values
- Microsoft: Windows Filtering Platform
- Microsoft: WFP error codes
Looking for a different code? Search another status or error code.