| Previous | Next |
| STATUS_VOLSNAP_HIBERNATE_READY | STATUS_INTERRUPT_VECTOR_ALREADY_CONNECTED |
STATUS_FSFILTER_OP_COMPLETED_SUCCESSFULLY
The FsFilter callback supplied the final successful result
FsFilter callbacks participate in selected file-system operations before or after the underlying file system. This success status communicates that the callback path itself completed the operation. It is more specific than generic success because it controls whether normal downstream processing should continue.
A filter returning it must have produced all required output and maintained file-object, resource, and callback-data invariants. Returning it merely to suppress a lower call can skip work the file system expected, while continuing the operation after this result can execute the same action twice.
What to inspect
- Identify the registered FsFilter callback, operation type, file object, volume, and final output fields.
- Verify the callback contract for whether this status is permitted in the current pre- or post-operation phase.
- Confirm that locks, references, and top-level IRP state are restored before returning.
- Trace whether any lower driver or file system routine still runs after the completed result.
References
- Microsoft Open Specifications: NTSTATUS values
- Microsoft WDK: FsRtlRegisterFileSystemFilterCallbacks
- Microsoft Windows SDK metadata: ntstatus.h
- Microsoft WDK: How to complete an IRP in a dispatch routine
Looking for a different code? Search another status or error code.