| Previous | Next |
| STATUS_FVE_OSV_KSR_NOT_ALLOWED | STATUS_FWP_CONDITION_NOT_FOUND |
STATUS_FWP_CALLOUT_NOT_FOUND
The custom classification component is missing
STATUS_FWP_CALLOUT_NOT_FOUND means a WFP callout object identified by the request does not exist in the filter engine. A callout represents custom classification processing associated with a specific WFP layer; it is not interchangeable with a filter rule or with the kernel driver binary that may implement the callout.
The failure can occur when policy installation, driver registration, and filter creation happen in the wrong order, or when a dynamic session removed the object before a later operation. Diagnose the object key or run-time ID, the applicable layer, the owner/provider, and the lifecycle of the management session. Do not substitute a broad permit rule merely because the custom callout is missing.
What to verify
- Record whether the operation used a GUID or a run-time ID.
- Confirm that the callout is registered at the intended WFP layer.
- Check dynamic-session teardown and driver/service startup ordering.
- Verify filters referencing the callout rather than assuming they are active.
References
- Microsoft Open Specifications: NTSTATUS values
- Microsoft: Windows Filtering Platform object model
- Microsoft: FwpmCalloutAdd0
- Microsoft: WFP operation
Looking for a different code? Search another status or error code.