| Previous | Next |
| ERROR_TRANSACTIONS_NOT_FROZEN | ERROR_NOT_SNAPSHOT_VOLUME |
ERROR_TRANSACTION_FREEZE_IN_PROGRESS
Concurrent freeze coordination is already controlling transactional activity
ERROR_TRANSACTION_FREEZE_IN_PROGRESS belongs to the Windows Kernel Transaction Manager transaction-processing model. Freezing transactional work is a serialized state transition because the RM must reach a snapshot-consistent boundary. A second freeze request while the first is still in progress cannot independently establish another boundary. This differs from an RM that cannot be frozen because of its transaction state: here a freeze operation already owns the transition.
Identify the snapshot or management request that initiated the first freeze and wait for its completion or failure. Check for a hung coordinator, lost completion, or overlapping backup jobs. Do not issue parallel freeze retries on a short timer; they increase contention without advancing the original state machine. If the first requester disappeared, use the documented RM and snapshot recovery path and verify whether transactional processing is actually frozen before attempting cleanup.
What to inspect
- Find the owner and start time of the in-progress freeze.
- Check overlapping backup, snapshot, and management jobs.
- Wait for or recover the existing state transition rather than launching parallel freeze requests.
References
- Microsoft: TxF savepoint and snapshot transaction structures
- Microsoft: transactional resource manager and log management
- Microsoft: KTM recovery processing and presumed abort
Looking for a different code? Search another status or error code.