| Previous | Next |
| STATUS_NO_LINK_TRACKING_IN_TRANSACTION | STATUS_TRANSACTION_INTEGRITY_VIOLATED |
STATUS_OPERATION_NOT_SUPPORTED_IN_TRANSACTION
The operation is outside TxF's supported transaction model
STATUS_OPERATION_NOT_SUPPORTED_IN_TRANSACTION is the general TxF limitation status for operations that are not valid inside a transaction. It should not be reduced to a generic unsupported-feature message; the key context is that the caller is in a transacted file-system operation.
TxF supports a defined set of transacted file operations, but not every NTFS control, metadata change, or cross-component behavior can be made transactional.
What to check
- The exact API or FSCTL being issued and whether there is a documented transacted form.
- Whether the handle was opened with
CreateFileTransactedor inherited a transaction context. - Nearby more-specific statuses such as EFS, compression, sparse, link tracking, or mapping restrictions.
- Whether the work should be moved outside the transaction or replaced with an application-level atomic pattern.
Useful distinction
This is the broad fallback. When a more specific TxF status is available, it usually gives better direction about the unsupported operation.
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.