| Previous | Next |
| STATUS_FLT_INSTANCE_NOT_FOUND | STATUS_FLT_INVALID_CONTEXT_REGISTRATION |
STATUS_FLT_CONTEXT_ALLOCATION_NOT_FOUND
Filter Manager allocates only the context types declared by the minifilter's context-registration table. This status means that no registered allocation definition matched the requested context type or request.
Check the FLT_CONTEXT_REGISTRATION entries passed to FltRegisterFilter, including the context type, flags, size, and cleanup callback. Do not replace a missing Filter Manager context with an arbitrary side allocation when the state must follow an object or transaction lifecycle; that bypasses the framework's attachment and cleanup model.
What to inspect
- The requested context type at the failing
FltAllocateContextcall. - The registration table compiled into the loaded driver, including its terminator.
- Whether the context belongs on the filter, instance, volume, stream, handle, file, or transaction object.
FltAllocateContext | Managing minifilter contexts | NTSTATUS reference
Looking for a different code? Search another status or error code.
