| Previous | Next |
| STATUS_FLT_CONTEXT_ALREADY_DEFINED | STATUS_FLT_DISALLOW_FAST_IO |
STATUS_FLT_INVALID_ASYNCHRONOUS_REQUEST
STATUS_FLT_INVALID_ASYNCHRONOUS_REQUEST is a request-model error. In particular, FltPerformAsynchronousIo cannot issue an IRP_MJ_CREATE request asynchronously; Filter Manager permits this API only for the supported IRP-based operations and not for fast-I/O or FSFilter callback operations.
Do not convert every operation to the asynchronous API merely because a driver needs deferred work. Separate the open/create decision from later read or write activity, and prefer the dedicated FltReadFile or FltWriteFile routines where those APIs match the intended operation.
What to check
- The major function in the allocated callback data.
- The initiating instance and the required completion ownership for the callback data.
- Whether the real requirement is asynchronous file I/O, deferred post-processing, or a pre-create policy decision.
FltPerformAsynchronousIo | Pre-operation and post-operation callbacks | NTSTATUS reference
Looking for a different code? Search another status or error code.