| Previous | Next |
| STATUS_CANT_RECOVER_WITH_HANDLE_OPEN | STATUS_TRANSACTION_SCOPE_CALLBACKS_NOT_SET |
STATUS_TXF_METADATA_ALREADY_PRESENT
Existing TxF metadata must be reconciled, not overwritten
This warning usually appears in backup, restore, or migration code that attempts to write TxF-specific metadata to a file that already participates in transactional state. Overwriting that metadata could disconnect the file from the resource manager and its recovery history.
Determine whether the destination is a pre-existing transactional file, a partially restored object, or a file left by an interrupted operation. The correct action depends on the backup format and resource-manager state; a generic metadata replacement is unsafe.
What to inspect
- Compare source and destination file identities and the transaction metadata captured by the backup.
- Verify whether the destination belongs to the same volume resource manager.
- Use the documented TxF backup/restore sequence rather than direct attribute manipulation.
- Prefer restoring to a clean destination when the existing transactional state cannot be proven compatible.
References
- Microsoft Open Specifications: NTSTATUS values
- Microsoft: Transactional NTFS concepts
- Microsoft: TxF programming considerations
- Microsoft: alternatives to Transactional NTFS
Looking for a different code? Search another status or error code.