| Previous | Next |
| STATUS_FLT_VOLUME_ALREADY_MOUNTED | STATUS_FLT_CONTEXT_ALREADY_LINKED |
STATUS_FLT_ALREADY_ENLISTED
This status belongs to Filter Manager transaction support. The minifilter has already enlisted in the transaction, so registering it again would create duplicate transaction participation rather than a second independent callback stream.
Enlist once per relevant filter instance and transaction, and preserve the transaction context that records that decision. Before calling FltEnlistInTransaction, the driver must have registered a transaction-notification callback; afterward, commit, rollback, or abort notifications should drive the state transition instead of a second enlist call.
Review points
- Whether duplicate pre-operation paths or retry logic can reach enlistment twice.
- Transaction-context ownership and cleanup during rollback or instance teardown.
- The registered notification mask and callbacks for the transaction lifecycle.
FltEnlistInTransaction | Managing minifilter contexts | NTSTATUS reference
Looking for a different code? Search another status or error code.