BitLocker Tpm And Recovery Password tests for AOAC devices with Legacy PCR's
This automated test contains TPM and recovery tests for devices that support InstantGo without Secure Boot
Test details
Specifications |
|
Platforms |
|
Supported Releases |
|
Expected run time (in minutes) | 15 |
Category | Scenario |
Timeout (in minutes) | 900 |
Requires reboot | false |
Requires special configuration | false |
Type | automatic |
Additional documentation
Tests in this feature area might have additional documentation, including prerequisites, setup, and troubleshooting information, that can be found in the following topic(s):
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.
Troubleshooting
For generic troubleshooting of HLK test failures, see Troubleshooting Windows HLK Test Failures.
For troubleshooting information, see Troubleshooting System Fundamentals Testing.
This test returns Pass or Fail.
If this test fails, review the test log from Windows Hardware Lab Kit (Windows HLK) 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 HLK Manager.
If a test script fails, check the BitLocker status:
- 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
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.
Note
If the BitLocker WHLK 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).