大网数据广告活动
启动与系统组件

PCR7 configuration in System Information shows as Binding not possible

· 52CE 我爱测

Explains why System Information on either Windows Server or Windows Client shows the PCR7 configuration as Binding not possible, and how to troubleshoot the issue.

Summary

This article applies to both Windows Server and Windows Client. It explains why the PCR7 configuration in System Information (msinfo32) shows Binding not possible even when TPM 2.0 and Secure Boot are enabled and BitLocker protection is active. The article also shows how to investigate EFI boot components that prevent PCR7 binding.

Symptoms

When you open msinfo32 and review System Summary, PCR7 Configuration displays the value Binding not possible.

Cause

PCR7 binding depends on the measurements created during the UEFI Secure Boot process. If an additional certificate authority (CA) hash or an EFI driver or boot application measurement appears in the PCR7 measurement sequence before the final Windows boot manager Windows Production CA measurement, BitLocker might not select the PCR 7, 11 validation profile.

In this situation, BitLocker can use the PCR 0, 2, 4, and 11 validation profile. Using that profile, Windows measures the exact binary hashes of the applicable boot components instead of relying on the CA certificate of measurement.

Important:
The Binding not possible status doesn't by itself mean BitLocker is disabled or that the TPM isn't ready. Confirm the protector status and PCR validation profile by using manage-bde.

Resolution

Troubleshoot the PCR7 binding

To identify the PCR validation profile that the BitLocker TPM protector uses, open an elevated PowerShell window, and then run the following command:

manage-bde -protectors -get $env:systemdrive

In the command output, review the TPM's PCR Validation Profile. This part of the output resembles the following example:

    TPM:
      ID: {00000000-0000-0000-0000-000000000000}
      PCR Validation Profile:
        7, 11
        (Uses Secure Boot for integrity validation)

This output shows one of the following sets of values:

  • 7, 11: BitLocker is using the PCR7-based validation profile.
  • 0, 2, 4, 11: BitLocker didn't select PCR7 binding.

If your environment requires the PCR7 binding, analyze the Measured Boot log to determine whether an extra EFI boot component or CA measurement prevents the PCR7 binding. For information about how to work use the Measured Boot log, see Decode the Measured Boot log. Search the decoded output for PCR[07], and review the PCR7 measurements in the order in which they occur. For example, the sequence can include the following statements:

  1. EV_EFI_VARIABLE_AUTHORITY
  2. EV_SEPARATOR
  3. EV_EFI_VARIABLE_AUTHORITY

Review the EV_EFI_VARIABLE_AUTHORITY entries to determine which certificate authority is associated with the measured EFI driver or boot application. An extra CA hash before the final Windows boot manager Windows Production CA measurement can prevent BitLocker from selecting PCR7.

For more information about Measured Boot, see Measured Boot.

Contact hardware or software vendor

If the Measured Boot log identifies an extra EFI driver, Option ROM, boot application, boot loader, or associated CA measurement, contact the hardware or software vendor. Ask the vendor to identify the component and provide a supported update, configuration change, or removal method.

Don't manually remove Secure Boot certificates or boot components without vendor guidance. Before making firmware or boot-chain changes, ensure the BitLocker recovery key is available and follow the vendor's supported procedure.

Alternative: Use the PCR 0, 2, 4, 11 validation profile

If BitLocker uses the PCR 0, 2, 4, 11 validation profile, no change is required solely because PCR7 binding is unavailable. Verify that BitLocker protection is enabled, and record the active PCR validation profile for troubleshooting purposes. Windows remains protected when BitLocker uses either the PCR 0, 2, 4, 11 profile or the PCR 7, 11 profile.

Data collection

If you need assistance from Microsoft Support, collect the applicable deployment and servicing information by using the Gather information by using TSS for deployment-related issues.

More information

Source: Microsoft Learn / IT Pro troubleshooting by Microsoft and contributors. Documentation licensed CC BY 4.0. Code samples are covered by the MIT License. Converted from Markdown, with links normalized and embedded media omitted.

资料来源与适用范围

资料来源
Microsoft Learn / IT Pro troubleshooting
适用范围
- Supported versions of Windows Server - Supported versions of Windows Client · Source date 10/09/2026
内容语言
中文;命令、路径和错误标识保留技术原文
本地收录日期
2026-11-15
授权说明
CC BY 4.0 (documentation), MIT (code samples)

正文与所需资源由本站本地存储。查看来源及更新记录 ↗

请按适用版本和实际日志确认原因;本站没有对每一种系统或设备逐项执行文中的操作。