| 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
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.
Preserve the callout notification type and the callback result that failed. The relevant defect is usually in callout add/delete notification handling, not in later packet classification.
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
Looking for a different code? Search another status or error code.