| Previous | Next |
| TBSIMP_E_TOO_MANY_RESOURCES | TBSIMP_E_TPM_INCOMPATIBLE |
TBSIMP_E_PPI_NOT_SUPPORTED
Classify the layer correctly
TBSIMP_E_PPI_NOT_SUPPORTED (0x80290219) 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 internal TBS physical-presence path is unavailable on the platform.
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.
Incident worksheet
| Question | Evidence for it |
|---|---|
| What exact state was rejected? | the internal TBS physical-presence path is unavailable on the platform |
| Which layer owns the result? | The TBS-to-firmware ACPI PPI path rather than an ordinary key command. |
| What must be correlated? | ACPI PPI capability, firmware version, requested function, TBS service event, output size, and Win32_Tpm capability data |
| What is the controlled comparison? | query supported PPI operations without requesting a state-changing action |
Separate caller data from platform state. The result caller data includes the command, structures, lengths, handles and flags; platform state includes TPM generation, provisioning, locality, lockout, resource inventory, firmware and the TBS service lifecycle. This result is actionable only after the rejected side is identified.
A reproducible comparison
Use the following verification sequence:
- Capture the unmodified failing input and
0x80290219. - Query supported ppi operations without requesting a state-changing action.
- Compare the first result divergent field or state transition.
- Repeat this result only after restoring the same baseline, with a bounded retry policy where the specification permits retry.
Boundaries often confused with this one
| Other code | Why a different remedy follows |
|---|---|
TBS_E_PPI_NOT_SUPPORTED | The physical presence interface is not supported — a separate checkpoint when compared with this result. |
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. |
TBS_E_PPI_NOT_SUPPORTED is the public API form of the same platform limitation. The result difference determines whether to change serialization, authorization, resource lifetime, firmware/PPI state, command policy or only retry timing.
Restore service safely
Correct the original boundary by choosing this direction: use the OEM firmware or supported Windows provisioning flow and avoid assuming every TPM platform exposes PPI. 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.
A successful it outcome preserves the intended hardware trust boundary, passes the original request, and produces verifiable output. Masking it, swallowing this HRESULT or switching silently to a software provider is not remediation.
References used for this checkpoint
- 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.