| Previous | Next |
| STATUS_TPM_EMBEDDED_COMMAND_UNSUPPORTED | STATUS_TPM_NEEDS_SELFTEST |
STATUS_TPM_RETRY
Temporary busy state and bounded retry
STATUS_TPM_RETRY is a documented non-fatal TPM result. The TPM 1.2 specification states that the module can be too busy to respond immediately and that the command can be resubmitted later; it may return this result for any command.
Use bounded retry with backoff and preserve operation identity in the calling software. Do not turn every retry into a new provisioning, enrollment or key-creation workflow. For a command that could alter persistent state, record the request and reconcile the resulting TPM or application state before generating additional independent requests.
What to establish before changing state
- Differentiate a one-off busy result from repeated retry loops or growing latency.
- Use the client library or Windows API retry semantics; do not alter TPM state merely because a retry is required.
- Capture concurrency and background TPM consumers when the condition persists.
References
- TCG TPM 1.2 non-fatal return values
- TCG TPM 2.0 Library Specification
- Microsoft: TPM error-code reference
Looking for a different code? Search another status or error code.