| Previous | Next |
| STATUS_MINIVERSION_INACCESSIBLE_FROM_SPECIFIED_TRANSACTION | STATUS_CANT_CREATE_MORE_STREAM_MINIVERSIONS |
STATUS_CANT_OPEN_MINIVERSION_WITH_MODIFY_INTENT
Miniversions are historical views, not writable working copies
STATUS_CANT_OPEN_MINIVERSION_WITH_MODIFY_INTENT means the caller tried to open a TxF miniversion with access that implies modification. A miniversion is useful for reading or comparing an earlier transacted stream state; it is not the object to modify when the transaction should continue changing the file.
The usual fix is to separate the read-only inspection path from the path that opens the current transacted stream for writes. Reusing a generic open helper can accidentally request write, append, delete, or metadata-modification access and trigger this status.
What to check
- Requested access flags, create options, share flags, and desired disposition on the miniversion open.
- Whether the helper always requests write access even for comparison or recovery reads.
- Whether metadata updates such as attributes, rename, or delete are being requested indirectly.
- Whether the caller should open the live transacted stream for modification instead.
Useful distinction
If a miniversion cannot be found or has been invalidated, TxF will report a different status. This one specifically says the requested operation conflicts with the read-only role of the miniversion view.
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.