:::MENU:::

Configure TPM platform validation profile for native UEFI firmware configurations



This policy setting allows you to configure how the computer’s Trusted Platform Module (TPM) security hardware secures the BitLocker encryption key. This policy setting does not apply if the computer does not have a compatible TPM or if BitLocker has already been turned on with TPM protection. Important: This group policy only applies to computers with a native UEFI firmware configuration. Computers with BIOS or UEFI firmware with a Compatibility Service Module (CSM) enabled store different values into the Platform Configuration Registers (PCRs). Use the “Configure TPM platform validation profile for BIOS-based firmware configurations” group policy setting to configure the TPM PCR profile for computers with BIOS configurations or computers with UEFI firmware with a CSM enabled. If you enable this policy setting before turning on BitLocker you can configure the boot components that the TPM will validate before unlocking access to the BitLocker-encrypted operating system drive. If any of these components change while BitLocker protection is in effect the TPM will not release the encryption key to unlock the drive and the computer will instead display the BitLocker Recovery console and require that either the recovery password or recovery key be provided to unlock the drive. If you disable or do not configure this policy setting BitLocker uses the default platform validation profile or the platform validation profile specified by the setup script. A platform validation profile consists of a set of Platform Configuration Register (PCR) indices ranging from 0 to 23. The default platform validation profile secures the encryption key against changes to the core system firmware executable code (PCR 0) extended or pluggable executable code (PCR 2) boot manager (PCR 4) and the BitLocker access control (PCR 11). Warning: Changing from the default platform validation profile affects the security and manageability of your computer. BitLocker’s sensitivity to platform modifications (malicious or authorized) is increased or decreased depending upon inclusion or exclusion (respectively) of the PCRs. Specifically setting this policy with PCR 7 omitted will override the “Allow Secure Boot for integrity validation” group policy preventing BitLocker from using Secure Boot for platform or Boot Configuration Data (BCD) integrity validation. Setting this policy may result in BitLocker recovery when firmware is updated. If you set this policy to include PCR 0 suspend BitLocker prior to applying firmware updates.


Additional Information

  1. Registry path is:

    HKEY_LOCAL_MACHINE -> SOFTWARE -> Policies -> Microsoft -> FVE -> OSPlatformValidation_UEFI # Enabled; HKEY_LOCAL_MACHINE -> SOFTWARE -> Policies -> Microsoft -> FVE -> OSPlatformValidation_UEFI # 0 HKEY_LOCAL_MACHINE -> SOFTWARE -> Policies -> Microsoft -> FVE -> OSPlatformValidation_UEFI # 1 HKEY_LOCAL_MACHINE -> SOFTWARE -> Policies -> Microsoft -> FVE -> OSPlatformValidation_UEFI # 2 HKEY_LOCAL_MACHINE -> SOFTWARE -> Policies -> Microsoft -> FVE -> OSPlatformValidation_UEFI # 3 HKEY_LOCAL_MACHINE -> SOFTWARE -> Policies -> Microsoft -> FVE -> OSPlatformValidation_UEFI # 4 HKEY_LOCAL_MACHINE -> SOFTWARE -> Policies -> Microsoft -> FVE -> OSPlatformValidation_UEFI # 5 HKEY_LOCAL_MACHINE -> SOFTWARE -> Policies -> Microsoft -> FVE -> OSPlatformValidation_UEFI # 6 HKEY_LOCAL_MACHINE -> SOFTWARE -> Policies -> Microsoft -> FVE -> OSPlatformValidation_UEFI # 7 HKEY_LOCAL_MACHINE -> SOFTWARE -> Policies -> Microsoft -> FVE -> OSPlatformValidation_UEFI # 8 HKEY_LOCAL_MACHINE -> SOFTWARE -> Policies -> Microsoft -> FVE -> OSPlatformValidation_UEFI # 9 HKEY_LOCAL_MACHINE -> SOFTWARE -> Policies -> Microsoft -> FVE -> OSPlatformValidation_UEFI # 10 HKEY_LOCAL_MACHINE -> SOFTWARE -> Policies -> Microsoft -> FVE -> OSPlatformValidation_UEFI # 11 HKEY_LOCAL_MACHINE -> SOFTWARE -> Policies -> Microsoft -> FVE -> OSPlatformValidation_UEFI # 12 HKEY_LOCAL_MACHINE -> SOFTWARE -> Policies -> Microsoft -> FVE -> OSPlatformValidation_UEFI # 13 HKEY_LOCAL_MACHINE -> SOFTWARE -> Policies -> Microsoft -> FVE -> OSPlatformValidation_UEFI # 14 HKEY_LOCAL_MACHINE -> SOFTWARE -> Policies -> Microsoft -> FVE -> OSPlatformValidation_UEFI # 15 HKEY_LOCAL_MACHINE -> SOFTWARE -> Policies -> Microsoft -> FVE -> OSPlatformValidation_UEFI # 16 HKEY_LOCAL_MACHINE -> SOFTWARE -> Policies -> Microsoft -> FVE -> OSPlatformValidation_UEFI # 17 HKEY_LOCAL_MACHINE -> SOFTWARE -> Policies -> Microsoft -> FVE -> OSPlatformValidation_UEFI # 18 HKEY_LOCAL_MACHINE -> SOFTWARE -> Policies -> Microsoft -> FVE -> OSPlatformValidation_UEFI # 19 HKEY_LOCAL_MACHINE -> SOFTWARE -> Policies -> Microsoft -> FVE -> OSPlatformValidation_UEFI # 20 HKEY_LOCAL_MACHINE -> SOFTWARE -> Policies -> Microsoft -> FVE -> OSPlatformValidation_UEFI # 21 HKEY_LOCAL_MACHINE -> SOFTWARE -> Policies -> Microsoft -> FVE -> OSPlatformValidation_UEFI # 22 HKEY_LOCAL_MACHINE -> SOFTWARE -> Policies -> Microsoft -> FVE -> OSPlatformValidation_UEFI # 23

  2. The Administrative Template path is:

    Windows Components -> BitLocker Drive Encryption -> Operating System Drives

Notes

* Making mistakes while changing registry values can affect your system adversely. We recommend you to create a System Restore point before making registry manipulation. If you're new to Registry Editor, read this beginner's guide.
** To locate the registry and administrative template path, checkout beginner's guide.
You're here :
Checkout Kapil Sparks™