| Previous | Next |
| ERROR_TXF_ATTRIBUTE_CORRUPT | ERROR_TRANSACTIONAL_OPEN_NOT_ALLOWED |
ERROR_EFS_NOT_ALLOWED_IN_TRANSACTION
TxF does not allow the requested Encrypting File System operation inside the active transaction
ERROR_EFS_NOT_ALLOWED_IN_TRANSACTION is a Transactional NTFS (TxF) file-system status. The error describes an explicit interaction between EFS and TxF. CreateFileTransacted documentation also notes that transactional opens cannot be used to control file encryption. Encrypting or decrypting the object changes filesystem metadata under rules that TxF does not support as part of the active file transaction.
Find the EFS API, shell operation, or policy-driven component that attempts encryption while the transaction remains active. Complete or roll back the transaction, close its transacted handles, and perform the encryption transition outside that transaction. If atomic publication is required, design the workflow around a separately prepared file rather than trying to insert EFS enable or disable into the TxF unit of work. ACL changes do not change this operation restriction.
What to inspect
- Trace the EncryptFile, DecryptFile, or equivalent EFS operation that overlaps the transaction.
- Close transacted handles and resolve the transaction before changing encryption state.
- Keep encryption-state transitions outside the TxF transaction boundary.
References
- Microsoft: CreateFileTransacted and miniversion views
- Microsoft: TxF programming considerations and error range
- MS-ERREF: TxF and KTM status definitions
- Microsoft: TxF limitations and recommended alternatives
Looking for a different code? Search another status or error code.