| Previous | Next |
| STATUS_STREAM_MINIVERSION_NOT_VALID | STATUS_CANT_OPEN_MINIVERSION_WITH_MODIFY_INTENT |
STATUS_MINIVERSION_INACCESSIBLE_FROM_SPECIFIED_TRANSACTION
The miniversion is scoped to another transaction
STATUS_MINIVERSION_INACCESSIBLE_FROM_SPECIFIED_TRANSACTION is a TxF isolation error. Miniversions are not general historical file versions; they are transaction-scoped views used by the transaction that created them.
Seeing this status usually means a miniversion ID or handle has been passed outside the transaction context that owns it. That can happen in helper threads, callbacks, broker processes, or code that stores miniversion identifiers and later reuses them after switching transaction handles.
What to check
- The transaction handle used when the miniversion was created and the handle used for the failing open.
- Thread-local transaction context and any impersonation or broker layer that changes it.
- Whether a helper component is treating a miniversion ID as globally reusable.
- Whether the operation should be done through the owning transaction or through a committed file view.
Useful distinction
This is not a permissions problem in the ordinary ACL sense. The isolation boundary is the TxF transaction, so adding file rights will not make a miniversion accessible from the wrong transaction.
References
- Microsoft: Transactional NTFS overview
- Microsoft: How to use Transactional NTFS
- Microsoft: Kernel Transaction Manager
- Microsoft Open Specifications: NTSTATUS values
Looking for a different code? Search another status or error code.