| Previous | Next |
| STATUS_CANNOT_EXECUTE_FILE_IN_TRANSACTION | STATUS_TRANSACTION_FREEZE_IN_PROGRESS |
STATUS_TRANSACTIONS_NOT_FROZEN
STATUS_TRANSACTIONS_NOT_FROZEN indicates an unmatched thaw operation: the system received a request to resume transactions that were not in the frozen state. It is a state-pairing issue, not proof that a transaction has failed.
Freeze and thaw can be relevant to snapshot workflows. Windows documentation notes that VSS coordinates freezing of KTM and DTC before creating shadow copies, so a backup or snapshot component should preserve the ownership and ordering of its freeze/thaw calls.
Thaw was requested without a matching frozen state
- Log the component that initiated the freeze or thaw, the snapshot operation ID, and the timing of both calls.
- Check for duplicate cleanup paths after a failed snapshot attempt.
- Do not issue repeated thaw requests as a generic recovery action; first establish whether a freeze actually completed.
References
- Microsoft: VSS interoperability with KTM and DTC
- Microsoft: KTM transaction managers
- Microsoft Open Specifications: NTSTATUS values
Looking for a different code? Search another status or error code.