Windows System Software -- Consulting, Training, Development -- Unique Expertise, Guaranteed Results


Before Posting...

Please check out the Community Guidelines in the Announcements and Administration Category.

More Info on Driver Writing and Debugging

The free OSR Learning Library has more than 50 articles on a wide variety of topics about writing and debugging device drivers and Minifilters. From introductory level to advanced. All the articles have been recently reviewed and updated, and are written using the clear and definitive style you've come to expect from OSR over the years.

Check out The OSR Learning Library at:

HLK HyperVisor Code Integrity Readiness fails for a software driver on Windows 10

PascalQuesseveurPascalQuesseveur Member Posts: 6


I am trying to run HLK tests for a software driver on Windows 10. I want to build a test packet and have the driver signed. I know about attestation signing but that is not what interests me.

I have setup a test network with HLK Studio running on a Windows Server 2019, and a client running Windows 10 2004. The Windows systems are in English version.

I defined a project with the driver on HLK Studio. Studio says there are 2 tests to pass:
+ HyperVisor Code Integrity Readiness
+ TDI filters and LSPS are not allowed

The first test fails. The following items are marked as failed:
+ HLK Config Library Tasks
+ Copy Test Binaries
+ CheckForTooManyDrivers
+ EnableDriverVerifier
+ SetDriverVerifierOptions
+ QueryDriverVerifierSettings

The second test run fine. I have no idea what it takes to pass the failed test.

  • HLK Filters are up to date on controler.
  • Secure boot is disabled and testsigning is enabled on the client.
  • Driver only allocates NonPagegPoolNx memory.
  • I have tried to run Device Guard and Credential Guard hardware readiness tool on client but it fails because Secure Boot is disabled.

Do I have to enable Secure Boot to run HyperVisor Code Integrity Readiness? But in that case how should I install the driver to be tested?


  • Mark_RoddyMark_Roddy Member - All Emails Posts: 4,628

    Have you looked at the test logs? Also the HLK provides you with the config scripts to re-run a failed test, so you should be able to repro and debug the problem.

  • PascalQuesseveurPascalQuesseveur Member Posts: 6

    OK, I'll look.

  • PascalQuesseveurPascalQuesseveur Member Posts: 6

    It seems to me quite difficult to interpret. If I look for example the first test:

    • HLK Config Library Tasks Per Test - Native / Failure
      • Runjob - HLK Config Library Tasks Per Test / OK
        • Copy Test Binary and Verifier Scripts / OK
        • Setup TAEF Root (Test Arch) / OK
        • Setup TAEF Root Alt (Test Arch Alt) / OK
        • Configure Crash dump event kog setting / OK
          o Logs
        • Configure Umdf Driver Verification / OK
        • Set Driver Registry Settings / OK
          o Logs
        • WaitforShellReady / OK
      • Setup TAEF Root (Test Arch) / OK
      • Setup TAEF Root Alt (Test Arch Alt) / Failure

    There is no available logs for the failed item. When I look at the existing logs I don't detect any failure.

Sign In or Register to comment.

Howdy, Stranger!

It looks like you're new here. Sign in or register to get started.

Upcoming OSR Seminars
OSR has suspended in-person seminars due to the Covid-19 outbreak. But, don't miss your training! Attend via the internet instead!
Internals & Software Drivers 19-23 June 2023 Live, Online
Writing WDF Drivers 10-14 July 2023 Live, Online
Kernel Debugging 16-20 October 2023 Live, Online
Developing Minifilters 13-17 November 2023 Live, Online