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

Associated requirements

System.Fundamentals.Security.DeviceEncryption System.Fundamentals.TPM.CS.ConnectedStandby

See the system hardware requirements.

Platforms

Windows RT (ARM-based) Windows RT 8.1 Windows 8.1 x64 Windows 8.1 x86

Expected run time

~15 minutes

Categories

Certification Functional

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.

This test returns Pass or Fail.

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. Check test output directly from command prompt when the test runs or open te.wtl in the HCK 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 WHCK tests with TPM in the name pass.

 

 

Send comments about this topic to Microsoft