| Previous | Next |
| STATUS_TPM_BAD_SCHEME | STATUS_TPM_BAD_MODE |
STATUS_TPM_BAD_DATASIZE
The data or blob size is invalid for this TPM operation
STATUS_TPM_BAD_DATASIZE is a Windows NTSTATUS value mapped from the TPM facility. For STATUS_TPM_BAD_DATASIZE, in this package the code belongs to TPM 1.2 style command processing, where Windows software, TBS, the TPM driver, and the hardware device all may be visible in the same failure path.
The relevant area is TPM blob and data-size validation. The command frame may be well formed, but a data payload, encrypted blob, digest, or command-specific buffer has a size that is not valid for the referenced key or operation.
This is a semantic size failure. Check the size relationship between the payload and key scheme, not only the outer command paramSize. It is common when a caller passes the wrong blob type, wrong digest length, or a buffer produced by a different TPM/key version.
Diagnostic focus
- Record outer command size and inner blob/data sizes separately.
- Check digest length, key modulus/algorithm requirements, and blob structure version.
- Do not truncate or pad the blob silently; regenerate it through the correct TPM command path.
References for STATUS_TPM_BAD_DATASIZE
- TCG: TPM 1.2 Part 2 Structures of the TPM
- TCG: TPM 1.2 Part 3 Commands
- Microsoft: TPM fundamentals
- Microsoft: MS-ERREF NTSTATUS values
Looking for a different code? Search another status or error code.