BitLocker Tpm and Recovery password tests for Non-AOAC devices with PCR 7
This automated test verifies whether PCR [7] is consistent across reboot and hibernates, and determines whether PCR [7] has the correct measurements.
Test details
|
Associated requirements |
Device.DevFund.Firmware.UpdateDriverPackage |
|
Platforms |
Windows 8 (x64)
|
|
Expected run time |
~15 minutes |
|
Categories |
Certification |
|
Type |
Automated |
Running the test
Before you run the test, complete the test setup as described in the test requirements: WDTF System Fundamentals Testing Prerequisites.
Secure boot should be enabled if it is supported by the platform.
This test will reboot and hibernate to determine 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.
-
Make sure you can see fveapi.dll in %systemroot%\system32\.
-
Check test output directly from command prompt when the test runs or open te.wtl in the HCK Manager.
-
If a test script fails, check the BitLocker status:
-
Manage-bde –status [volume]
-
Manage-bde –status [volume]
-
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
-
Filter \Windows logs\System logs by event sources started with BitLocker
-
Run tpm.msc to ensure that the TPM Status is ON and that ownership has been taken.
-
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.
-
Collect TCG log (*.txt).
 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). |