Share via

DE OOBE_EOW Sequence Tests

  • Article

This test verifies that Encryption On Write (EOW) of the volumes is started after completion of OOBE. It also tests if Device Encryption is not blocked by the OEM by setting registry key PreventDeviceEncryption.

Test details

   
Specifications
  • System.Fundamentals.TPM.CS.ConnectedStandby
Platforms
  • Windows 10, client editions (x86)
  • Windows 10, client editions (x64)
  • Windows 10, client editions (Arm64)
Supported Releases
  • Windows 10
  • Windows 10, version 1511
  • Windows 10, version 1607
  • Windows 10, version 1703
  • Windows 10, version 1709
  • Windows 10, version 1803
  • Windows 10, version 1809
  • Windows 10, version 1903
  • Next update to Windows 10
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.

This test returns Pass or Fail.

Troubleshooting

For generic troubleshooting of HLK test failures, see Troubleshooting Windows HLK Test Failures.

For troubleshooting information, see Troubleshooting System Fundamentals Testing.

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

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

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

    • Manage-bde -status [volume]

  3. 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

  4. Check TCG logs

    • Collect TCG log (*.txt).

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

    • Make sure WHLK tests with TPM in the name pass.