System Testing with Secure Boot

In some cases, having Secure Boot enabled on a test computer can cause the HCK Client installation to fail. You should not see this failure on Windows RT devices, but might see them on non-Windows RT devices. Follow these steps to ensure proper installation:

For system tests and non-class driver device tests

  1. Disable Secure Boot protections.

    • For x86/x64, enter the BIOS configuration and disable Secure Boot.

    • For Windows RT, install the Windows Debug Policy; you don't need to disable Secure Boot.


      Only OEMs and Microsoft can perform this step.

  2. Install the Windows HCK Client software.

  3. Run the following applicable tests for the test platform:


    System Must include SuperSpeed Port

    USB 3.0 Hub Enumeration Stress

    USB 3.0 Insertion Test

    USB 3.0 Speed Switch Test

    USB 3.0 Suspend Test

    USB Controller Power State Test

    USB Controller Power State Test for System

    USB Descriptor Test

    USB Device Connection S3+S4

    USB Device Control Request Test

    USB Enumeration Stress

    USB Exposed Port Controller Test

    USB Exposed Port System Test

    USB Host Controller Enable Disable Test

    USB Hub Exposed Port Test

    USB Hub Selective Suspend Test

    USB Internal Device Idle

    USB MS OS Descriptor Test (xHCI)

    USB Selective Suspend Test (xHCI)

    USB Serial Number

    USB xHCI Compliance Suite (ARM)

    USB xHCI Register System test

    USB xHCI Register Test

    USB xHCI Runtime Power Management System Test

    USB xHCI Runtime Power Management Test

    USB xHCI Transfer Speed Test

    USB3 Termination

    USB-IF Certification Validation Test (Device)

    Debug Capability Test (Logo)

    xHCI Debug Capability Compliance (Logo)

    xHCI Debug Capability Device Compliance (Logo)

    GFXIntegration Power Management Test

    WDDM CCD Test for PersistentReset Monitor

    DMA Extension Test - UART DMA

    NPCTEST - Clock Interrupt Test

    PCI Hardware Compliance Test For a Single Device (PCIHCT)

    PCI Hardware Compliance Test For Systems

    UEFI Firmware Certification Test

    PPM Perf Logo Test

    WHEAHCT Logo

    Connected Standby IO Stress

    BitLocker Drive Encryption USB BIOS Logo Test

    TPM 2.0 Hardware Interface Test (Manual)

    TPM 2.0 TCG Physical Presence Interface 1.2 Test

    TPM 2.0 UEFI Preboot Interface Test

    TPM Revoke Attestation

    ACPI Logo Test

    Crypto Capabilities – UEFI Hash Provider

    Firmware Update test

    UEFI GOP Mode Test


  4. Enter the BIOS configuration, enable Secure Boot, and restore Secure Boot to the Default configuration. For Windows RT devices, remove the secure boot debug policy.

  5. Run the rest of the HCK tests.

  6. Enter the BIOS configuration and clear the Secure Boot configuration. This restores the system to Setup Mode by deleting PK and other keys.


    Support for clearing is required for x86/x64 and prohibited for production Windows RT devices.

  7. Run the Secure Boot Manual Logo Test.

For devices that use drivers on Windows RT

  1. Install the Windows HCK Client software.

  2. Run device tests for only your devices.


    System tests and tests that use drivers that are not signed by Microsoft will fail.




Send comments about this topic to Microsoft