HCK for Windows 8.1 and WLK 1.6 usage scenarios

HCK for Windows 8.1 usage scenarios

The new HCK for Windows 8.1 supports certification for these operating systems:

  • Windows 7
  • Windows 8
  • Windows 8.1
  • Windows Server 2008 R2
  • Windows Server 2012
  • Windows Server 2012 R2

    WLK 1.6 usage scenarios

    WLK 1.6 supports certification for these operating systems:

  • Windows Server 2003
  • Windows Server 2008
  • Windows Server 2008 R2

    Digital signatures for legacy operating systems

    When you successfully complete testing for a client certification of Windows 7, Windows 8, or Windows 8.1, use the Windows Dev Center hardware dashboard to create a submission package for uploading – the same process that you’ve used in the past. And, if you’re using a unified driver that’s properly decorated to include Windows Vista and Windows XP, the dashboard has check boxes for digital signatures.

    When you successfully complete testing for a server certification of Windows Server 2008 R2, Windows Server 2012, or Windows Server 2012 R2, you can also use the dashboard to create a submission package for uploading. Again, this is the same process that you’ve used in the past. And similarly, if you’re using a unified driver that’s properly decorated to include Windows Server 2003 and Windows Server 2008, the dashboard has check boxes for digital signatures. You can select the check boxes only if the driver being submitted was previously fully tested for certification. If you select these check boxes for Windows Server 2008 or Windows Server 2003, you must add to the supplemental folder a Readme file that includes the previous submission IDs for the Windows Server 2008 and Windows Server 2003 certification testing. All submissions for which you select these check boxes will go into the manual review queue so that the previous certification for Windows Server 2008 and Windows Server 2003 can be confirmed. If no Readme file is provided for the certification testing for Windows Server 2008 and Windows Server 2003, the submission will be canceled.

  • Comments (14)

    1. some doubt says:


      I have a question for your certification policy, If our new product need all OSs certifications, should I need to perform win7, win8, win8.1, 2008r2, 2012, 2012r2 on HCK2.1 and Server 2003, Server 2008 on WLK1.6 or just run testing on HCK2.1 and Server 2003 digital signature, Server 2008 digital signature will be get by free?

    2. Mark Hughes says:

      Run testing on HCK 2.1 on the following OS's Server 2008 R2, Server 2012, Server 2012 R2, Win 7, Win 8, and Win 8.1.  If you’re using a uniform driver that supports the lower level OS’s check boxes will appear to add digital signatures for the following OS’s if using a unified driver XP, Vista, Server 2003 and Server 2008.

      Per policy if you select the Server 2003 and Server 2008 digital signatures you need to provide a README file  that references where Server 2003 and Server 2008 were previously tested using either WLK 1.6 or HCK 2.0.  If not previously tested you need to use WLK 1.6 and run testing on Server 2003 and Server 2008 so you can provide submissions ID’s for those OS’s in the README file.

      For XP and Vista it’s not required to provide a README that verifies the product was previously tested for those OS.  You can select the XP and Vista digital signatures without further testing.  

    3. Andrew Fox at RIM says:

      I had WHQL'd v1.0 of a driver on all Windows OS's using the HCK 2.0 last year. This year I have v2.0 of the same driver and I'm running it again using HCK 2.1. Now I don't get 2K3 or 2K8 because of the policy change. Can I reference the submissions from last year for a previous version of the driver to get it passed on 2K3 and 2K8 OR do I have to run my driver v2.0 through HCK 2.0 for just 2K3 and 2K8? It's not clear to me how to handle multiple versions of the same driver. Thanks in advance for your response.

    4. Mark Hughes says:

      If the driver was previously tested for 2003 and 2008 reference that submission ID in the README and check the 2003 and 2008 signature boxes.  Its acceptable to update or change the driver that was previously tested and choose the free signature boxes for 2003 and 2008 as long as it was previously tested one time.    

    5. Mike says:

      We have a separate XP driver (WDM) and would still require to sign (to prevent warning message during installation especially installers) by big customers who still need to support XP in their products.

      Can you still provide us a way to sign the XP drivers which is not a unified driver with Win7/8? Thanks!

    6. Rocky says:

      Is it possible to sign a HCKX file on a different system than what was used to perform the HCK tests? For example, if we hire a 3rd party testing facility to perform the HCK test, and they provide us the HCKX file to digitally sign with our Verisign system?  This was possible with WLK and the Winqual submission tool, but not sure about HCK.

    7. Mark Hughes says:

      Hi Mike,

      The only way to obtain an XP or Vista digital signature at this time is to test for Win 7 or higher using a unified driver.    

    8. Mark Hughes says:

      HI Rocky,

      Yes.  You can sign the HCKX package with the HCK Studio only.  You will see two options as shown below.

      1. From Certificate Store: You would install the certificate on your controller machine and choose the 2nd option.

      2. Use Certificate File: Generate the HCKX file and sign it from 3rd option with studio. Make sure that certificate should be .CER format.

    9. Emily says:

      hi Mark,

      My question is simiar to the first one but just want to make sure it applies to our case.

      We are certifying a  new multipath driver on Windows2003&2008, Windows2008R2, Windows2012 and Windows2012R2. To get the new signatures on Windows2003&2008, should we just follow this new policy by selecting the checkbox for these two OSs and adding the README file? Both Windows2003&2008 had been certified using HCK2.0 for the old version of the multipath driver.

      And for Windows2012 and Windows2012 R2, is it possible to use a fully tested Windows2012 R2 submission package to certify Windows2012?


    10. Bruce says:

      Hi. Mark.

      We are currently performing WHQL certification for win7 & 8. As I learnt we can check box for legacy win xp and vista here when submitting package to dashboard, we do not proceed xp and vista.

      When installing driver on win 7 64 bit, it is not installed under test mode. in that case, driver package should be digitially signed? We have symantec key(pfx, pck, spc). In my understadning, the package created by HCK studio is signed before submitting it to dashboard. any idea, please?

    11. Mark Hughes says:

      Hi Emily,

      Since 2003 and 2008 was previously tested a reference in the README file to the original submission ID is the only requirement to check the 2003 and 2008 signature boxes.  So 2008 R2 would need to be full tested.  If you test on 2012 R2 its acceptable to only run the check inf test for 2012 and submit referencing errata ID 2657.  There is a Fast Track policy that allows running the Check INF test only on 2012 if you full test on 2012 R2.  

      This would allow you to receive a driver that's signed for 2003, 2008, 2008 R2, 2012 and 2012 R2.

    12. Mark Hughes says:

      Hi Bruce,

      Its very common for partners to use test sign or self signed drivers for testing purposes.  This is acceptable.  When you go to submit you should upload the driver that needs the Microsoft digital signature so you can distribute to 3rd parties without pop up warnings.

      When testing with a uniformunified driver that supports XP and Vista check boxes will appear to allow digital signatures for those OS.s without testing.   So you can receive one driver that's singed for multiple OS's.      

    13. Anacel says:

      Hi Mark,

      I was about to do the WLK 1.6 testing in Windows 2003 x86 and x64 platform. But my problem is, my client computer is not displayed in DTM Studio.

      Below is my set up:

      1. DTM Controller and Studio is running in Windows Server 2008 R2 x64.

      2. Client computer is running in Windows 2003 x86 and x64 platform.

      Based in MSDN website and in your blog, WLK 1.6 kit still supports Windows Server 2003 x86, x64 Device and Driver Certification.

      We already do some network configuration, restarted and re-installed both DTM Controller/Studio and DTM Client but still no luck.

      Thank you very much and your advise is really appreciated.

    14. Pradeepa says:


      I need the driver to work on Windows XP, Vista, 7, 8 and 8.1.

      Therefore, I used WDK7.1 for driver development. I noticed that the driver compiled for Win7 is working on Win8 and Win8.1 too.

      I'm going to install the HCK on Windows Server 2012 and test the driver on Win 7/8/8.1. Can I use the Win-7 driver for all the OSes or should I install WDK8.1 and create separate drivers for Win 7/8/8.1 and sign?

      If I need to use WDK8.1 compiled drivers will they work with Win XP?

      Thank you