| Previous | Next |
| ERROR_NO_RECOVERY_POLICY | ERROR_WRONG_EFS |
ERROR_NO_EFS
The request reached a system without an available EFS implementation
ERROR_NO_EFS is different from a volume that simply lacks encryption support. It reports that the required EFS component or encryption driver is not available to service the operation. The target path may be on NTFS, yet the system can still fail earlier because EFS is unavailable in the current installation or execution environment.
Record whether the problem occurs locally, in Windows PE or another reduced environment, inside a container, or through a remote EFSRPC operation. Verify the Windows edition and system configuration before modifying the file. Copying encrypted data through software that cannot preserve EFS metadata risks producing an unusable backup.
What to inspect
- Whether EFS operations work on a known local NTFS test file under the same boot environment.
- The Windows edition, effective EFS policy, and availability of the EFS service components.
- For remote operations, the EFSRPC endpoint and authenticated RPC/SMB path.
- The distinction from
ERROR_VOLUME_NOT_SUPPORT_EFSandERROR_EFS_DISABLED.
References
- Microsoft: File Encryption
- Microsoft Open Specifications: EFSRPC introduction
- Microsoft Open Specifications: EFSRPC transport
- Microsoft Open Specifications: Win32 error codes
Looking for a different code? Search another status or error code.