What does Windows error code 349 (ERROR_ENCLAVE_FAILURE) mean?

 
Could be also:
ConstantTypeOS
SOC_SUBSYSTEM_FAILURE_LIVEDUMPBugCheck CodeWindows
Previous Next
ERROR_MARKED_TO_DISALLOW_WRITES ERROR_FAIL_NOACTION_REBOOT

ERROR_ENCLAVE_FAILURE

The secure enclave could not complete the request

ERROR_ENCLAVE_FAILURE is a Win32 system result. Enclave operations depend on processor support, operating-system policy, image configuration, measurement, and strict memory rules. This generic result means the architecture-specific operation failed, so the surrounding API and platform details are essential.

What the result means

An architecture-specific secure-enclave operation failed. For ERROR_ENCLAVE_FAILURE, keep the symbolic name, numeric value, and failing operation together in diagnostics; that combination distinguishes the exact failure path from nearby system results.

What to check

  • Record the exact enclave API, operation phase, and architecture-specific status if one is available.
  • Verify CPU, firmware, virtualization, and Windows support for the selected enclave type.
  • Confirm that the enclave image, signatures, imports, and memory ranges satisfy platform requirements.
  • Check whether security policy or virtualization-based security configuration changed.

Recommended handling

Abort the affected enclave transaction and use documented cleanup. Retry only when the failing condition is known to be transient; otherwise disable the feature gracefully or select a supported platform path.

Developer notes

Never log enclave secrets while collecting diagnostics. Keep architecture-specific details, Windows build, processor capabilities, and image identity, and avoid translating the result into an ordinary allocation failure. When a Win32 API reports ERROR_ENCLAVE_FAILURE, capture GetLastError() immediately; subsequent cleanup, formatting, or logging calls can replace the thread-local value.

References


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