Hi
TPM 2.0 Device Found: Required for Windows 11 and modern security features.
Security Device Support: Enabled
This enables TPM functionality. Required for BitLocker and secure boot.
Active PCR Banks: SHA256
SHA256 is active, which is the current standard for secure hashing. Good configuration.
Available PCR Banks: SHA256
Only SHA256 is available, indicating legacy SHA1 is not enabled. This is good.
SHA256 PCR Bank: Enabled
Ensures proper functionality for secure boot chains, BitLocker, and attestation.
Pending Operation: None
No pending TPM reset or configuration change. This is a normal and stable state.
Platform Hierarchy: Enabled
This is required for managing TPM platform-specific authorizations. Leave enabled.
Storage Hierarchy: Enabled
Enables TPM to securely store keys and encrypt data. Required for most uses.
Endorsement Hierarchy: Enabled
Essential for device identity and endorsement key usage. Should remain enabled.
Physical Presence Spec Version: 1.3
Latest spec version; defines how user approval is handled during TPM changes. This should be good.
Disable Block SID: Disabled
This allows automatic domain join in some environments. Default and recommended unless your org policy requires otherwise. (SID stands for Security Identifier, used by Windows to identify users, groups, and machines.)
- Disable Block SID: Disabled = Block SID is on, auto TPM SID-based ownership is blocked.
- This is the default and secure setting — don't change it unless your IT/security policy requires you to.
All I can tell you about the Secure Boot (namely custom) is what it says at the bottom. Are you able to set OS Type to: Windows UEFI Mode?
And Set Secure Boot Mode to: Standard? Because this is what I found:
- Secure Boot: Custom and not fully active is only really for unsigned Linux or manual key management
- Risk: Reduced boot-time integrity checks
- If you're using Windows or a Secure Boot-compatible Linux distro (e.g., Ubuntu, Fedora):
- Set OS Type to: Windows UEFI Mode
- Set Secure Boot Mode to: Standard
- Make sure Secure Boot State changes from "User" to "Enabled" or "Active"
- Save and exit BIOS
- This will load the Microsoft keyset and enforce Secure Boot as designed — preventing rootkits or unauthorized UEFI bootloaders from running.