| Previous | Next |
| WINBIO_E_INVALID_BUFFER_ID | WINBIO_E_TRUSTLET_INTEGRITY_FAIL |
WINBIO_E_INVALID_BUFFER
WINBIO_E_INVALID_BUFFER differs from WINBIO_E_INVALID_BUFFER_ID: a buffer reference can resolve, yet the buffer contents still fail the contract expected by the secure biometric component. This is a data-shape or integrity boundary inside the protected pipeline, not a normal poor-quality biometric rejection.
Preserve buffer metadata and producer/consumer boundaries
- Record buffer version/type metadata, byte length, producing adapter stage, and consuming operation without logging raw biometric payloads.
- Check that the same driver, adapter, and secure-component versions agree on the buffer format after updates.
- Separate this result from
WINBIO_REJECT_DETAILvalues used for capture quality or placement problems.
Secure biometrics intentionally keeps sample contents out of untrusted application space, so debugging should focus on the adapter and protected-component contract rather than dumping the payload. A format/version mismatch, truncated transfer, or stale protected buffer can all be investigated using metadata and operation sequencing. Asking the user to scan the same finger repeatedly is not a meaningful response to a structural buffer failure.
Secure biometric sensor model · WBF plug-in architecture · Enhanced Sign-in Security
Looking for a different code? Search another status or error code.