What does NTSTATUS 0xC0000810 (STATUS_ENCRYPTED_IO_NOT_POSSIBLE) mean?

Status / error code:		Category:

Constant name:
Source:		Operating System:
Description: STATUS_ENCRYPTED_IO_NOT_POSSIBLE the read or write operation to an encrypted file could not be completed because the file has not been opened for data.

Previous	Next
STATUS_PROACTIVE_SCAN_IN_PROGRESS	STATUS_CORRUPT_LOG_UPLEVEL_RECORDS

STATUS_ENCRYPTED_IO_NOT_POSSIBLE

The current file open is not a data-access context

STATUS_ENCRYPTED_IO_NOT_POSSIBLE ties the failure to how the encrypted file was opened. EFS-aware read or write work has reached a file context that was not opened for data access. The fact that code has a valid file handle or file object is not enough: a metadata, control, or otherwise restricted open cannot automatically be reused for encrypted data transfer.

Trace the handle or file object back to its creation rather than debugging the transfer buffer first. The supported raw encrypted-file APIs use an explicit lifecycle: OpenEncryptedFileRaw creates the context for export or import, the matching raw read or write function performs callback-driven transfer, and CloseEncryptedFileRaw closes that context.

Reopen the file through the API and access mode intended for the data operation. Do not widen an unrelated long-lived handle or cache an EFS context across a close/reopen boundary. In file-system or filter code, keep metadata/control opens distinct from data opens so the request is sent with the context the encrypted I/O path expects.

What to inspect

The original create/open operation and desired data access associated with the failing file object or context.
Whether a metadata-only handle, stream-file object, or stale cached context is being reused for data transfer.
The complete OpenEncryptedFileRaw to read/write to close lifecycle when using the public raw EFS APIs.

References

Looking for a different code? Search another status or error code.