| Previous | Next |
| ERROR_TRANSACTED_MAPPING_UNSUPPORTED_REMOTE | ERROR_TRANSACTION_SCOPE_CALLBACKS_NOT_SET |
ERROR_TXF_METADATA_ALREADY_PRESENT
The file already has transactional metadata, so TxF refuses to supersede it
ERROR_TXF_METADATA_ALREADY_PRESENT is a Transactional NTFS (TxF) file-system status. TxF backup controls can read and write transactional metadata associated with a file. That metadata carries object-specific transactional state and is not an arbitrary extended attribute. This error indicates that metadata is already present and the attempted operation would replace or overlay it.
Inspect the restore, cloning, or metadata-write path that targeted the file. Verify whether the destination should be a newly created object or whether it already participated in TxF. Compare file identities and backup workflow stages before deleting or recreating anything. The documented backup-information output is intended to be passed to the corresponding TxF write operation as part of a controlled backup flow; it is not safe to force a second metadata image over existing state.
What to inspect
- Determine why the destination already has TxF metadata before the write.
- Check restore ordering and whether the destination file was reused.
- Recreate the correct destination through the supported backup workflow rather than overwriting metadata.
References
- Microsoft: reading TxF backup metadata
- Microsoft: TxF filesystem control codes
- MS-FSCC: NTFS attribute types including transactional data
- Microsoft: retrieving TxF metadata and locking transaction
Looking for a different code? Search another status or error code.