| Previous | Next |
| STATUS_TPM_DEFEND_LOCK_RUNNING | STATUS_TPM_TOO_MANY_CONTEXTS |
STATUS_TPM_COMMAND_CANCELED
Cancellation does not prove the final TPM state
STATUS_TPM_COMMAND_CANCELED reports a canceled request in the Windows TPM stack. It is a request-lifecycle result, not a cryptographic verdict about the command parameters. The status alone does not provide a safe basis for declaring a persistent operation completed or not completed.
For read-only operations, a retry may be straightforward through the same API contract. For provisioning, enrollment, key creation, ownership or policy changes, inspect the resulting state first. This prevents a cancellation race from being converted into duplicate objects, conflicting policy requests or an unnecessary TPM reset.
What to establish before changing state
- Record which layer requested cancellation: application timeout, service shutdown, user cancellation or driver path.
- Query the relevant TPM or application state before reissuing a persistent operation.
- Treat repeated cancellations as a latency or lifecycle problem rather than adding unbounded retries.
References
Looking for a different code? Search another status or error code.