Поделиться через


BitLocker Tpm and Recovery Password tests for Non-AOAC devices for Legacy PCRs

This test determines whether PCR [0,2,4,11] are consistent across restarts.

Test details

Associated requirements

Device.DevFund.Firmware.UpdateDriverPackage System.Fundamentals.TPM.NonCS.NonConnectedStandby

See the system hardware requirements.

Platforms

Windows 8 (x64) Windows 8 (x86) Windows Server 2012 (x64) Windows 8.1 x64 Windows 8.1 x86 Windows Server 2012 R2

Expected run time

~15 minutes

Categories

Certification Functional

Type

Automated

 

Running the test

Before you run the test, remove any bootable CD/DVD media from the system under test and run this test from the Desktop instead of the Start Screen. Complete the test setup as described in the test requirements: WDTF System Fundamentals Testing Prerequisites.

This test will restart and hibernate the system to check whether PCRs are consistent.

Troubleshooting

For troubleshooting information, see Troubleshooting System Fundamentals Testing.

If this test fails, review the test log from Windows Hardware Certification Kit (Windows HCK) Studio.

  1. Make sure you can see fveapi.dll from %systemroot%\system32\.

  2. Check test output directly from command prompt when the test runs or open te.wtl in the HCK Manager.

  3. If a test script fails, check the BitLocker status:

    • Manage-bde –status [volume]
  4. Collect BitLocker event logs from event viewer at two locations:

    • Filter \Windows logs\System logs by event sources started with BitLocker

    • Applications and Services Logs\Microsoft\Windows\BitLocker-API\Management

  5. Make sure TPM is turned on by running tpm.msc to ensure that the TPM Status is ON and that ownership has been taken.

  6. Check TCG logs

    • Collect TCG log (*.txt).

    • Compare multiple copies of the TCG log and see whether PCR [0,2,4,11] are consistent across reboot and hibernate.

Note  

If the BitLocker WHCK test results in a recovery event, the BitLocker recovery key is 48-zeros (0000-0000-0000-0000-0000-0000-0000-0000-0000-0000-0000-0000).

 

 

 

Send comments about this topic to Microsoft