| Previous | Next |
| STATUS_CS_ENCRYPTION_NEW_ENCRYPTED_FILE | STATUS_INVALID_LABEL |
STATUS_CS_ENCRYPTION_FILE_NOT_CSE
A Client-Side Encryption control request targeted a normal file
The SMB client issued a CSE-specific file-system control operation, but the open file was not established as a Client-Side Encryption file. This usually means the client state machine, handle selection, or earlier create response does not match the FSCTL being sent.
Do not add encryption metadata blindly to make the control code succeed. Confirm that the handle belongs to the intended file and that the previous status actually required CSE mode. Reused handles and retry paths can accidentally send an encrypted-file control request to a different ordinary open.
What to inspect
- Match the FSCTL to the exact SMB file identifier and create response.
- Trace mode transitions after reconnect, retry, and handle reuse.
- Use ordinary SMB I/O for a non-CSE file or reopen the correct encrypted object.
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.