| Previous | Next |
| ERROR_NO_USER_KEYS | ERROR_NOT_EXPORT_FORMAT |
ERROR_FILE_NOT_ENCRYPTED
The selected code path assumes EFS state that the file does not have
A plaintext file lacks the encrypted data streams and key metadata expected by raw EFS backup, restore, or management operations. This error therefore points first to the caller's choice of API or protocol mode, not to missing permissions.
Check the file with FileEncryptionStatus before choosing between ordinary file I/O and EFS-specific processing. Note that DecryptFile treats an already unencrypted file as success, so this error often identifies a lower-level or raw-encryption workflow rather than the normal decrypt function.
Do not add fake EFS metadata to make an import or control request succeed. Use normal backup/copy semantics for plaintext data, or encrypt the file through the supported EFS API when encryption is actually required.
What to inspect
- The API, FSCTL, or SMB operation that required an encrypted source.
- The file's current encryption status and the file system hosting it.
- Branching logic that selects ordinary I/O versus raw EFS export/import.
References
Looking for a different code? Search another status or error code.