| Previous | Next |
| TPM_E_PERMANENTEK | TPM_E_NOCONTEXTSPACE |
TPM_E_BAD_SIGNATURE
Where the failure is raised
TPM_E_BAD_SIGNATURE (0x80280062) belongs to TPM 1.2 key migration and endorsement policy. The base What Is page already shows the short Windows message; the additional diagnostic value is that this result marks a TPM 1.2 certified-migration-key ticket signature does not validate.
The first producer to identify for it is the certified-migration, key-policy or EK administrative checkpoint. TPM 1.2 migration policy is encoded when a key is created and reinforced by signed authority tickets and source/destination bindings. Migration errors therefore require the original binary artifacts and key attributes, not only the user-visible key name.
Evidence that changes the diagnosis
Preserve these this result items before changing anything:
- This result and
0x80280062, the exact returning method or command, and the first nested status. - ticket content, signer public key, signature scheme, digest calculation, canonical structure encoding, and the CMK authority relationship.
- The TPM generation, manufacturer/firmware revision, Windows build, caller identity and TBS/provider state for it.
- The complete opaque request artifacts, redacting authorization secrets but not rewriting structure boundaries.
A controlled verification
Run this focused check: verify the signature over the exact ticket bytes outside the TPM and compare with a freshly issued ticket. Do not combine the result test with firmware updates, TPM clearing, account changes, key recreation and policy edits in the same trial; such a result cannot isolate this boundary.
| Checkpoint | Pass condition |
|---|---|
| a TPM 1.2 certified-migration-key ticket signature does not validate | The original this result command reaches the next defined state without returning it. |
| Security behavior | The result verification still uses the intended TPM, authorization, locality and policy. |
| Output integrity | The object, digest, event log or state transition produced after it validates independently. |
Related TPM and TBS results
| Related result | Separate meaning |
|---|---|
TPM_E_PERMANENTEK | Attempt to revoke the EK and the EK is not revocable — a separate checkpoint when compared with it. |
TPM_E_MA_AUTHORITY | Incorrect migration authority — a separate checkpoint when compared with it. |
TPM_E_MA_SOURCE | Migration source incorrect — a separate checkpoint when compared with it. |
The practical distinction is that TPM_E_MA_TICKET_SIGNATURE is the more specific migration-authority ticket check.
Correction and proof
The supported direction is to replace the invalid ticket and correct digest or serialization handling; never edit signed fields in place. Do not edit a signed ticket, migration blob or opaque private-key structure. Binary normalization, JSON conversion or base64 line handling can invalidate the authority and integrity relationships.
If the same bytes still return it after the documented preconditions are satisfied, retain this code-specific trace for the platform vendor or Windows component owner rather than erasing state.
Technical references
- TCG: TPM 1.2 Main Specification — source for the checkpoint.
- TCG: TPM 1.2 Part 2 — Certified migration structures — source for the checkpoint.
- TCG: TPM 1.2 Part 3 — Migration commands — source for the checkpoint.
- Microsoft: How Windows uses the TPM — source for the checkpoint.
Looking for a different code? Search another status or error code.