| Previous | Next |
| ERROR_NO_LINK_TRACKING_IN_TRANSACTION | ERROR_EXPIRED_HANDLE |
ERROR_OPERATION_NOT_SUPPORTED_IN_TRANSACTION
The file operation is valid normally but is outside the set of operations TxF can transact
ERROR_OPERATION_NOT_SUPPORTED_IN_TRANSACTION is a Transactional NTFS (TxF) file-system status. TxF does not make every filesystem operation transactional. Microsoft documents a dedicated set of transacted file functions and a range of programming restrictions. This status is the general operation-level rejection used when the requested action cannot be performed in a transaction, even though the same action may be valid through the normal nontransacted filesystem API.
Capture the exact API or filesystem control, not merely the file path and error code. Generic wrappers often apply a transaction handle to every file operation and discover unsupported cases only at runtime. Compare the call with the TxF function and control-code reference. Move unsupported work before or after the transaction, or replace TxF with an application-level staging and atomic-replace design. A broader access mask or transaction retry does not add transactional semantics to the operation.
What to inspect
- Log the exact API or FSCTL that returned the error.
- Check whether TxF documents a transacted equivalent for that operation.
- Move unsupported work outside the transaction or redesign the atomic update workflow.
References
- Microsoft: TxF filesystem control codes
- Microsoft: TxF programming considerations and error range
- Microsoft: Transactional NTFS overview
- Microsoft: TxF limitations and recommended alternatives
Looking for a different code? Search another status or error code.