| Previous | Next |
| WER_E_TOO_HEAVY | ERROR_FLT_CONTEXT_ALREADY_DEFINED |
ERROR_FLT_NO_HANDLER_DEFINED
The operation is outside the registered callback contract
ERROR_FLT_NO_HANDLER_DEFINED indicates that Filter Manager was asked to process an operation for which the relevant minifilter supplied no callback definition. A minifilter opts into operation types through the terminated FLT_OPERATION_REGISTRATION array passed in FLT_REGISTRATION; unregistered major functions are not generic extension points.
This status is most useful when code constructs or reissues callback data itself. It points to a mismatch between the operation’s MajorFunction and the filter’s registration, not to a missing filesystem dispatch routine. Adding a callback merely to suppress the error is unsafe unless the filter can honor that operation’s parameter layout and completion rules.
Registration checks
- Log the major and minor function from the callback data that could not be dispatched.
- Confirm that the operation appears exactly once in the registration array before the
IRP_MJ_OPERATION_ENDsentinel. - Check whether the initiating code allocated callback data for an operation the filter never intended to issue.
- Review pre-operation and post-operation pairing requirements before adding a new handler.
References
- Microsoft: FLT_OPERATION_REGISTRATION
- Microsoft: FltRegisterFilter
- Microsoft: minifilter pre-operation callbacks
Looking for a different code? Search another status or error code.