Share via

Secure Boot Logo Test

  • Article

This test verifies the out-of-box configuration and basic functionality of Secure Boot. Most of this test is automated, with the exception of dialog boxes that remind you of prerequisites for this test and the post-test step of turning Secure Boot off to run other tests.

Test details

   
Specifications
  • System.Fundamentals.Firmware.UEFISecureBoot
Platforms
  • Windows 10, client editions (x86)
  • Windows 10, client editions (x64)
  • Windows Server 2016 (x64)
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) 10
Category Compatibility
Timeout (in minutes) 60
Requires reboot false
Requires special configuration true
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.

Before you run the test, Secure Boot option should be in the default shipping (out-of-box) configuration, specifically:

  • Secure Boot option must be ON.

  • Microsoft Keys are in Key-Exchange key (KEK) and signature database (db).

  • No Microsoft test keys are allowed in the Public Key (PK), KEK or signature database.

  • DBX is shipped up-to-date out-of-the-box.

Note

The following commands must be run on the test system before running the Secure Boot tests.

reg add HKLM\System\CurrentControlSet\Services\iospy\StartOverride /v 0 /t REG_DWORD /d 3 /f
reg add HKLM\System\CurrentControlSet\Services\MSDMFilt\StartOverride /v 0 /t REG_DWORD /d 3 /f

This test requires that the system is imaged through the OEM manufacturing process (TPM should be cleared before OS is laid down and installed as part of the deployment). This test should only be run on systems that have gone through an OEM-style imaging process.

Troubleshooting

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

For troubleshooting information, see Troubleshooting the Windows HLK Environment.

This test returns Pass or Fail. To review test details, review the test log from Windows Hardware Lab Kit (Windows HLK) Studio.

Note

This test will fail unless a production signed OS is used and all the driver are signed.