| Previous | Next |
| TPM_E_READ_ONLY | TPM_E_FAMILYCOUNT |
TPM_E_PER_NOWRITE
What failed and what did not
TPM_E_PER_NOWRITE (0x8028003F) belongs to TPM 1.2 nonvolatile-storage policy. The base What Is page already shows the short Windows message; the additional diagnostic value is that this result marks the proposed TPM 1.2 NV definition leaves writes without the protection required by the command or platform policy.
The first producer to identify for this HRESULT is the TPM 1.2 NV permission and lifecycle checks. TPM 1.2 NV indices combine permissions, authorization mode, locality masks and lock semantics. Two indices of the same size can behave differently because those attributes were fixed when each index was defined.
Collect a useful trace
| Question | Evidence for this HRESULT |
|---|---|
| What exact state was rejected? | the proposed TPM 1.2 NV definition leaves writes without the protection required by the command or platform policy |
| Which layer owns the result? | The TPM 1.2 NV permission and lifecycle checks. |
| What must be correlated? | NV permission attributes, authorization mode, locality masks, write policy, index size, and the complete define-space structure |
| What is the controlled comparison? | define a disposable index with explicit owner, index-auth or locality protection and compare the accepted attributes |
Record the original command or API call before this result retry logic mutates its nonces, handles, buffers or state. Also retain the full HRESULT as 0x8028003F; signed decimal logging can hide the result TPM/TBS facility and make searches less precise.
Narrow experiment
- Establish the result baseline with the same device, Windows build, account and TPM generation.
- Perform one narrow experiment: define a disposable index with explicit owner, index-auth or locality protection and compare the accepted attributes.
- Compare raw this result inputs and the first response, not only the final application dialog.
- Stop after the first changed the checkpoint; a later error means this boundary was passed even if the whole workflow still fails.
Similar-looking outcomes
| Result | Different diagnostic question |
|---|---|
TPM_E_FAMILYCOUNT | The family count value does not match — a separate checkpoint when compared with this result. |
TPM_E_READ_ONLY | The NV area is read only and can't be written to — a separate checkpoint when compared with it. |
TPM_E_WRITE_LOCKED | The NV area has already been written to — a separate checkpoint when compared with it. |
The decisive distinction for this HRESULT is that TPM_E_READ_ONLY concerns an existing index that cannot be written, whereas it rejects an inadequately protected write policy. The short platform wording — “There is no protection on the write to the NV area.” — does not supply that differential diagnosis by itself.
Operational response
The corrective direction is to add a specification-supported write protection mechanism before defining the index. Do not undefine a production NV index until its public attributes and authorization policy have been recorded. NV policy is established at definition time, and destructive recreation can remove counters, certificates or provisioning state.
A verified it repair reproduces the original request with the same intended security policy and passes this checkpoint. Replacing it with a broader wrapper status, silently falling back to software keys, or suppressing verification is not proof of success.
Technical references
- TCG: TPM 1.2 Main Specification — source for the checkpoint.
- TCG: TPM 1.2 Part 2 — NV structures and permissions — source for the checkpoint.
- TCG: TPM 1.2 Part 3 — NV commands — source for the checkpoint.
- Microsoft: Win32_Tpm class — source for the checkpoint.
Looking for a different code? Search another status or error code.