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

Home NTDEV
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: https://www.osr.com/osr-learning-library/


Signing driver for Windows 7

ksupallksupall Member Posts: 18
edited February 18 in NTDEV

Hi, NTDEV!
Now I have to sign driver for Windows 7, so I adjusted test server and test machine, I passed tests that I need in Windows HLK (but some tests failed, so I didn't run them to have only successfull ones).

As a result I created .hlkx file and uploaded it in Microsoft Partner Dev Center to get my driver signed by Microsoft. But on Manual Review step I got an error - "Fail. Errata ID not provided for not run tests".

So I have several questions: what is happening on Manual Review step? Does that error means that I have to run all tests in target (even those that are failed)? I also found information that I have to complete this document and add it as supplement.

http://webcache.googleusercontent.com/search?q=cache:HSUJUpVMr0gJ:download.microsoft.com/download/4/C/3/4C34C72F-FD65-41C9-B89A-A0858A2C3562/windows-hardware-dashboard-submission-readme-v2.2.docx+&cd=1&hl=ru&ct=clnk&gl=ru

So do I need to fill table with failed tests in this document? And where can I find Waiver ID Number?

Comments

  • Tim_RobertsTim_Roberts Member - All Emails Posts: 13,823

    (but some tests failed, so I didn't run them to have only successfull ones).

    Well, that's not how it works. The HLK uses your device class to determine which tests to run. You must pass ALL the tests it chooses, unless there is an errata that documents a problem in the test. The HLK should load filters for the current errata automatically. If you don't pass some tests, then your driver is broken, and you need to fix it.

    Are you ONLY looking for Windows 7? If so, why go through HLK at all? Why not just use self-signing and cross-signing, like we always have in the past?

    Tim Roberts, [email protected]
    Providenza & Boekelheide, Inc.

  • ksupallksupall Member Posts: 18
    edited February 19

    The HLK uses your device class to determine which tests to run.

    What should I do to make HLK choose tests for my driver? Do I have to upload .inf file? If so, where do I have to upload it?
    So I have client on test system, I installed my driver there. So what do I have to choose on Selection tab in Windows HLK Studio on Controller?

    P.S. Thank you so much for helping me!

    Post edited by ksupall on
  • ksupallksupall Member Posts: 18

    Do I have to see my driver in the list on Selection Tab in Software device section?

  • ksupallksupall Member Posts: 18

    Are you ONLY looking for Windows 7? If so, why go through HLK at all? Why not just use self-signing and cross-signing, like we always have in the past?

    But here it's written that cross-signing will be elaminated in July this year.
    https://docs.microsoft.com/en-us/windows-hardware/drivers/install/deprecation-of-software-publisher-certificates-and-commercial-release-certificates

  • Tim_RobertsTim_Roberts Member - All Emails Posts: 13,823

    What should I do to make HLK choose tests for my driver? Do I have to upload .inf file?

    Aren't you already doing that? If not, how did you create an .hlkx file? How did you run tests at all?

    The normal process is that the HLK server connects to the HLK client system being tested and enumerates all of its devices. It then presents you with a list and lets you choose. Note that the HLK can only test client systems running Windows 10. Does your driver run under Windows 10? If you need to test on earlier systems, you'll need to use the HCK instead.

    But here it's written that cross-signing will be elaminated in July this year.

    That's their current story, but you're trying to sign a driver now. Right? The process still works today.

    Tim Roberts, [email protected]
    Providenza & Boekelheide, Inc.

  • ksupallksupall Member Posts: 18

    The normal process is that the HLK server connects to the HLK client system being tested and enumerates all of its devices. It then presents you with a list and lets you choose. Note that the HLK can only test client systems running Windows 10. Does your driver run under Windows 10? If you need to test on earlier systems, you'll need to use the HCK instead.

    Can you tell me please what I should do if HCK chooses zero tests for my driver for win7?

Sign In or Register to comment.

Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

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!
Writing WDF Drivers 7 Dec 2020 LIVE ONLINE
Internals & Software Drivers 25 Jan 2021 LIVE ONLINE
Developing Minifilters 8 March 2021 LIVE ONLINE