| Previous | Next |
| STATUS_CANT_OPEN_MINIVERSION_WITH_MODIFY_INTENT | STATUS_HANDLE_NO_LONGER_VALID |
STATUS_CANT_CREATE_MORE_STREAM_MINIVERSIONS
The stream has exhausted its TxF miniversion slots
STATUS_CANT_CREATE_MORE_STREAM_MINIVERSIONS indicates a TxF limit rather than a name-resolution failure. The stream already has as many miniversions as the implementation is willing to maintain for the active transaction state.
This can appear in code that creates a miniversion before every small write, retry, or savepoint operation. It is a sign to review the transaction design because excessive miniversions increase metadata pressure and complicate rollback behavior.
What to check
- The number of miniversions created for the same stream before commit or rollback.
- Loops that create miniversions for every retry instead of only at meaningful checkpoints.
- Whether old savepoints are cleared when they are no longer needed.
- Whether a shorter transaction or application-level temporary file would be simpler.
Useful distinction
This is not the same as running out of disk space. Disk pressure may coexist, but the named failure is the TxF stream-miniversion limit.
References
- Microsoft: Transactional NTFS overview
- Microsoft: How to use Transactional NTFS
- Microsoft: TXFS_SAVEPOINT_INFORMATION
- Microsoft: Kernel Transaction Manager
Looking for a different code? Search another status or error code.