| Previous | Next |
| STATUS_TPM_FAMILYCOUNT | STATUS_TPM_BAD_ATTRIBUTES |
STATUS_TPM_WRITE_LOCKED
STATUS_TPM_WRITE_LOCKED is a Windows NTSTATUS value in the TPM facility. For STATUS_TPM_WRITE_LOCKED, it belongs to the TPM 1.2 error family and is normally surfaced through the Windows TPM stack, such as TPM Base Services, rather than by ordinary file, registry or network APIs.
Some TPM NV areas are intended to be written once, or to become locked after a write command. This status indicates that the caller is attempting another write after the TPM has already moved the area into a write-locked state.
This can be expected during provisioning idempotence checks: a second provisioning run may fail because the first run successfully sealed the NV data and locked the index.
Diagnostic focus
- Check whether a previous provisioning attempt already wrote the index.
- Treat a repeated write differently from a failed first write; the correct response may be to read and validate existing data.
- Compare with STATUS_TPM_AREA_LOCKED for broader lock-state failures.
References for STATUS_TPM_WRITE_LOCKED
- TCG: TPM 1.2 Main Specification
- Microsoft: TPM Base Services
- Microsoft: NTSTATUS values
- TCG: TPM Main Part 1, NV storage design principles
Looking for a different code? Search another status or error code.