| Previous | Next |
| TBS_E_SERVICE_START_PENDING | TBS_E_COMMAND_CANCELED |
TBS_E_PPI_NOT_SUPPORTED
Where the failure is raised
TBS_E_PPI_NOT_SUPPORTED (0x8028400C) belongs to the TPM physical-presence interface. The base What Is page already shows the short Windows message; the additional diagnostic value is that this result marks the requested public TBS physical-presence operation is unavailable on this platform or firmware interface.
The first producer to identify for it is the TBS-to-firmware ACPI PPI path rather than an ordinary key command. The physical-presence interface is a firmware-mediated administrative channel. It is intentionally separate from ordinary TPM commands so that destructive or ownership-changing requests can require platform policy and local confirmation.
Evidence that changes the diagnosis
Preserve these this result items before changing anything:
- This result and
0x8028400C, the exact returning method or command, and the first nested status. - PPI capability, ACPI interface data, firmware version, requested operation, output buffer, and Win32_Tpm physical-presence capabilities.
- 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: query supported physical-presence operations without issuing a destructive request and compare with OEM documentation. 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 |
|---|---|
| the requested public TBS physical-presence operation is unavailable on this platform or firmware interface | 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 |
|---|---|
TBSIMP_E_PPI_NOT_SUPPORTED | The physical presence interface is not supported — a separate checkpoint when compared with it. |
TPM_E_ERROR_MASK | This is an error mask to convert TPM hardware errors to win errors — a separate checkpoint when compared with it. |
TPM_E_FAIL | The operation failed — a separate checkpoint when compared with it. |
The practical distinction is that TBSIMP_E_PPI_NOT_SUPPORTED is the internal-layer counterpart, while TBS_E_PPI_FUNCTION_UNSUPPORTED can identify a particular PPI function.
Correction and proof
The supported direction is to use the platform-supported provisioning path or firmware UI; do not emulate physical presence in user mode. Do not attempt to emulate physical presence by elevating a user-mode process. PPI operations can require firmware support, reboot and local confirmation outside the normal TBS command channel.
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
- Microsoft: Tbsi_Physical_Presence_Command — source for the checkpoint.
- Microsoft: Win32_Tpm physical-presence methods — source for the checkpoint.
- Microsoft: TBS return codes — source for the checkpoint.
- TCG: TPM 1.2 Main Specification — source for the checkpoint.
Looking for a different code? Search another status or error code.