| Previous | Next |
| STATUS_TRANSACTION_FREEZE_IN_PROGRESS | STATUS_NO_SAVEPOINT_WITH_OPEN_FILES |
STATUS_NOT_SNAPSHOT_VOLUME
The operation expects a snapshot-mounted volume
STATUS_NOT_SNAPSHOT_VOLUME indicates that the caller used a TxF operation that is valid only for a volume mounted as a snapshot volume. The target may be an ordinary mounted NTFS volume, but the requested control path expects snapshot semantics.
This can occur in backup, restore, or volume-shadow-copy related code that mixes handles from the live volume with handles intended for a snapshot view.
What to check
- Whether the handle actually points to the snapshot volume, not the original live volume.
- Volume mount paths, device paths, and reparse points used by backup or restore code.
- Whether
FSCTL_TXFS_TRANSACTION_ACTIVEor similar snapshot-only logic is being used on the wrong handle. - Whether the snapshot was created and mounted before the TxF query was issued.
Useful distinction
This is a volume-context error. It does not say that the transaction itself is invalid; it says the operation was aimed at a volume view that lacks the required snapshot role.
References
- Microsoft: About Transactional NTFS
- Microsoft: How to use Transactional NTFS
- Microsoft: Alternatives to using Transactional NTFS
- Microsoft Open Specifications: NTSTATUS values
Looking for a different code? Search another status or error code.
