| Previous | Next |
| ERROR_CS_ENCRYPTION_EXISTING_ENCRYPTED_FILE | ERROR_CS_ENCRYPTION_FILE_NOT_CSE |
ERROR_CS_ENCRYPTION_NEW_ENCRYPTED_FILE
The new remote file needs its CSE creation data
When an encrypted file is being created, overwritten, or superseded and no user certificate was supplied, the file-system algorithm requests the Client-Side Encryption workflow. The client must provide the certificate information needed to establish authorized users and create the encrypted stream.
The public message mentions $EFS because the new file needs its encryption metadata as part of a coherent creation sequence. Do not create a normal plaintext file first and bolt raw encrypted data onto it later. If the sequence fails, remove or quarantine incomplete output before retrying.
What to inspect
- The create disposition and encrypted attribute requested for the destination.
- The user certificate supplied on the retry and its private-key availability.
- Destination file-system and server support for EFS metadata.
- Cleanup behavior for partially created files after a failed CSE transition.
References
- Microsoft Open Specifications: Open/create algorithm for encrypted files
- Microsoft Open Specifications: NTSTATUS values
- Microsoft Open Specifications: Win32 error codes
- Microsoft Open Specifications: EFS overview
Looking for a different code? Search another status or error code.