| Previous | Next |
| STATUS_CS_ENCRYPTION_INVALID_SERVER_RESPONSE | STATUS_CS_ENCRYPTION_EXISTING_ENCRYPTED_FILE |
STATUS_CS_ENCRYPTION_UNSUPPORTED_SERVER
The server advertised Client-Side Encryption but cannot perform it
The SMB client reached a server that appeared to support the Client-Side Encryption workflow, but the server could not complete the required operation. This is stronger than a server that never advertised the capability: negotiation or behavior was internally inconsistent.
Do not work around the error by sending plaintext file content when EFS semantics are required. Verify the server version, SMB implementation, file-system support, and any proxy or appliance modifying SMB messages. A non-Windows server can support ordinary SMB while lacking this Windows-specific encrypted-file behavior.
What to inspect
- Confirm the server capability advertisement and actual SMB dialect.
- Test whether the target file system supports the required encrypted-file metadata.
- Use a compatible server or copy through a trusted local decrypt-and-reencrypt workflow.
References
- Microsoft: System error codes 6000 through 8199
- Microsoft Open Specifications: NTSTATUS values
- Microsoft Open Specifications: SMB error classes and codes
Looking for a different code? Search another status or error code.