| Previous | Next |
| ERROR_FLT_INSTANCE_NOT_FOUND | ERROR_FLT_INVALID_CONTEXT_REGISTRATION |
ERROR_FLT_CONTEXT_ALLOCATION_NOT_FOUND
Allocation depends on the filter registration table
ERROR_FLT_CONTEXT_ALLOCATION_NOT_FOUND means FltAllocateContext could not match the requested context to allocation information registered with the filter. The filter must declare every context type it uses in its FLT_CONTEXT_REGISTRATION array before registration; fixed-size contexts also reject a runtime size larger than the registered size.
This status is distinct from pool exhaustion. Adding memory or retrying does not create the missing registration. Compare the context type and requested size at the failing call with the exact table compiled into the running driver, especially when optional features alter the registration array or use FLT_VARIABLE_SIZED_CONTEXTS.
Registration-to-allocation comparison
- Log
ContextType,ContextSize, and pool type at the failing allocation. - Confirm that the registration array contains one matching entry before its terminating record.
- For fixed-size contexts, keep every request at or below the registered size.
- After changing the table, verify that the running driver binary and symbols are the updated build.
References
- Microsoft: FltAllocateContext return values
- Microsoft: FLT_CONTEXT_REGISTRATION fields
- Microsoft: registering context types
Looking for a different code? Search another status or error code.