| Previous | Next |
| STATUS_RTPM_UNSUPPORTED_CMD | STATUS_HV_INVALID_HYPERCALL_CODE |
STATUS_TPM_ZERO_EXHAUST_ENABLED
This is a policy-induced network block, not a TPM key failure
STATUS_TPM_ZERO_EXHAUST_ENABLED is associated with TPM-related network operations while Zero Exhaust mode is enabled. Microsoft's TPMPolicy CSP describes Zero Exhaust as a policy intended to prevent Windows and inbox applications from sending network traffic to public IP addresses unless the traffic is directly intended by the user. The matching TPM error documentation explicitly says TPM-related network operations are blocked in this mode.
The practical distinction is important: the status does not say that a TPM command failed, that a key is corrupt, or that the TPM has run out of storage. The operation is being stopped because of network policy. Resetting or clearing the TPM would not remove that policy and can destroy protected key material.
What to inspect
- Whether Zero Exhaust policy is enabled on the client and how it was provisioned.
- The Windows or inbox component attempting the TPM-related network operation.
- The destination and whether the operation is classified as user-intended traffic under the policy scenario.
- Policy-management and diagnostic events around the rejected network attempt.
Diagnose the policy decision first. Change the managed policy only if the deployment requirements call for the traffic; do not weaken TPM state or rotate keys in response to a network block imposed by Zero Exhaust mode.
References
- Microsoft: TPMPolicy CSP
- Microsoft: TPM error codes
- Microsoft: Windows diagnostic fields including Zero Exhaust state
- Microsoft Open Specifications: NTSTATUS values
Looking for a different code? Search another status or error code.