| Previous | Next |
| ERROR_TRANSACTION_FREEZE_IN_PROGRESS | ERROR_NO_SAVEPOINT_WITH_OPEN_FILES |
ERROR_NOT_SNAPSHOT_VOLUME
The operation requires snapshot-volume semantics that the target volume does not have
ERROR_NOT_SNAPSHOT_VOLUME belongs to the Windows Kernel Transaction Manager transaction-processing model. Some transactional resource-manager operations are defined only for a volume mounted in a snapshot role. A normal NTFS volume can support transactional metadata yet still be the wrong target for a snapshot-specific control. This status is therefore about the volume role and operation contract, not whether the filesystem generally supports KTM or TxF.
Resolve the path to its volume and inspect how the snapshot was created and mounted. Backup software can accidentally pass the live source volume when it intends the exposed snapshot, especially when drive letters or mount points are reassigned. Record the volume identifier rather than only the path string. Do not attempt to mark an ordinary live volume as a snapshot by editing filesystem metadata; correct the snapshot orchestration and target selection.
What to inspect
- Resolve the target path to a volume GUID and compare it with the created snapshot.
- Check mount-point and drive-letter reassignment in backup orchestration.
- Use the actual mounted snapshot volume for snapshot-specific transactional controls.
References
- Microsoft: TxF savepoint and snapshot transaction structures
- Microsoft: Transactional NTFS and KTM coordination
- Microsoft: transactional resource manager and log management
Looking for a different code? Search another status or error code.