| Previous | Next |
| STATUS_TXF_ATTRIBUTE_CORRUPT | STATUS_TRANSACTIONAL_OPEN_NOT_ALLOWED |
STATUS_EFS_NOT_ALLOWED_IN_TRANSACTION
EFS work is blocked by the active transaction
STATUS_EFS_NOT_ALLOWED_IN_TRANSACTION means the requested Encrypting File System operation cannot be performed while the file operation is inside a TxF transaction. Encryption changes affect file metadata and keying state in ways that TxF does not allow for this active transacted context.
The useful fix is usually to change operation ordering: finish or abort the transaction first, then perform encryption work outside that transaction, or design the workflow so EFS state is established before TxF work begins.
What to check
- Whether the handle was opened through a transacted API such as
CreateFileTransacted. - Calls that encrypt, decrypt, import keys, or alter EFS-related metadata while the transaction is active.
- Whether the operation can be moved before transaction start or after commit/rollback.
- Policy or filter drivers that trigger EFS changes indirectly during file creation.
Useful distinction
This is not the same as lacking EFS permission or certificate material. The named blocker is the active TxF transaction.
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.