| Previous | Next |
| ERROR_CANNOT_EXECUTE_FILE_IN_TRANSACTION | ERROR_TRANSACTION_FREEZE_IN_PROGRESS |
ERROR_TRANSACTIONS_NOT_FROZEN
The transactional resource manager received a thaw without a matching freeze
ERROR_TRANSACTIONS_NOT_FROZEN belongs to the Windows Kernel Transaction Manager transaction-processing model. Freeze and thaw operations are paired state transitions used by snapshot-related coordination. A thaw is meaningful only after transactional processing was successfully frozen. If the earlier freeze failed, was skipped, or another path already thawed the RM, a later thaw request has no frozen state to release.
Trace the snapshot operation as a sequence and record the result of every freeze and thaw request. Cleanup code often calls thaw unconditionally after a partial failure; that can produce this status while the original freeze error is the real cause. Concurrent snapshot coordinators can also interfere with shared RM state. Make the pairing explicit with ownership or state tokens, and diagnose the first failed transition rather than treating the harmless-looking thaw error as the root problem.
What to inspect
- Correlate the thaw request with the exact preceding freeze attempt.
- Check cleanup paths that thaw unconditionally after partial snapshot setup.
- Prevent multiple snapshot coordinators from managing the same RM freeze state concurrently.
References
- Microsoft: TxF savepoint and snapshot transaction structures
- Microsoft: KTM recovery processing and presumed abort
- Microsoft: transactional resource manager and log management
Looking for a different code? Search another status or error code.