| Previous | Next |
| STATUS_ENLISTMENT_NOT_SUPERIOR | STATUS_CANT_BREAK_TRANSACTIONAL_DEPENDENCY |
STATUS_FILE_IDENTITY_NOT_PERSISTENT
The file identity is not stable until another transaction is resolved
STATUS_FILE_IDENTITY_NOT_PERSISTENT indicates that a file's identity depends on the outcome of an unresolved transaction. Until that transaction commits or rolls back, TxF cannot safely expose a persistent identity for the requested transactional open.
This matters for code that relies on file IDs, hard links, renames, or directory enumeration results while another transaction is still changing the namespace. The path may look valid, but the durable object identity is not yet settled.
What to check
- Uncommitted create, rename, hard-link, or delete operations involving the same file.
- Concurrent transactions touching the same directory entry or stream.
- Code that caches a file ID before the transaction that defines that identity has completed.
- Whether the operation can wait for the owning transaction outcome.
Useful distinction
This is not just a sharing violation. Sharing conflicts are about simultaneous access modes; this status is about whether the file identity is durable enough to be used transactionally.
References
- Microsoft: About Transactional NTFS
- Microsoft: How to use Transactional NTFS
- Microsoft: Alternatives to using Transactional NTFS
- Microsoft Open Specifications: NTSTATUS values
Looking for a different code? Search another status or error code.