Welcome to the Windows Hardware Certification blog


This is the new Windows Hardware Certification blog, where you can get Windows Certification Program news and info. All the updates and info you’re used to seeing in the Windows Certification Newsletter will be available here, and you’ll be able to post comments and join in conversations with the Certification team and other community members. You can also expect to see updates on a more timely and flexible schedule.

After a short transition period, the email newsletter will be retired.

To subscribe to this blog, see the Feeds options on this page.

Comments (24)

  1. GossipNews says:

    Good improve.SHAFA

  2. Mudit Garg says:

    Nice move. But Certification Letters mail should be continue

  3. Nagesh S says:

    Nice one! must needed!:)

  4. TimKan says:

    But the import news where shall i can get?

  5. antonio-jr says:

    I want to ugrapde my current cert from Enterprise Desktop Administrator, Windows 7 into server path. What particular exams should I take and focus on.

    Regards

    antonio-jr

  6. Certification team says:

    Thanks, Mudit, for the feedback. We will discontinue the newsletter to avoid duplication, but if you want to continue to get your Windows Certification news in email, you can sign up for that in the Feeds section on this page. Hope that meets your needs.

  7. Certification team says:

    TimKan, this is the best place to get news related to Windows Hardware Certification. To subscribe, click the email link in the Feeds section of this page.

  8. Certification team says:

    antonio-jr, you're looking for a different kind of certification. This blog is for manufacturers and developers looking for information about certifying their hardware. For information on certification exams, try this forum: social.microsoft.com/…/home

    Hope that helps.

  9. A. J. W. says:

    Hi

    I need to implement a multi-touch + pen device. In the "Windows pointer device data delivery protocol", section "Supported usages in digitizer report descriptors" there is a table specifying required, recommended, optional and N/A usages for both, touch and pen reports.

    I think the table is wrong for following usages:

    – Width: N/A for Touch Digitizer N/A; Required for Pen Digitizer

    – Height: N/A for Touch Digitizer N/A; Required for Pen Digitizer

    However, with all other statements in the same document, this makes no sense IMO and it should rather be the other way round: "Width and Height both Required or Recommended for Touch Digitizer; Width and Height both Optional or N/A for Pen Digitizer".

    Can you please clarify this point and necessarily correct the specifying document ASAP?

    Thanks

    A. J. W.

  10. Certification team says:

    Hi AJW.

    For support questions, please see the resources at msdn.microsoft.com/…/gg454528. There is a link to this page under Support on the right side of this page.

    I'm also looking into whether we need to make changes to the documentation, but if you need assistance in a hurry, please use the resources on that page. Thanks for your feedback.

  11. Will.yy.Mao says:

    Hi team,

    I need write a software driver to support a third party application to control LED of front panel on computer,I got a information that the driver needn't  Windows Certification, just need to sign.I refer the online document:

    msdn.microsoft.com/…/ff554651(v=vs.85).aspx

    The driver must do Windows Certification when sign for public release.

    It confuse me,what on earth am I?

    1.Only sign the driver ues my company .cer file.

    2.Follow up the WHQL process to do Windows certification

    Thanks

    Will Mao

  12. Mark Hughes says:

    HI Will,

    If your driver is INF based it can be submitted through the hardware certification program for a Microsoft digital signature and certification.  Here is a link on the getting started process.

    msdn.microsoft.com/…/hh833792.aspx

    The Sysdev@microsoft.com alias can help assist with dashboard site account set up questions if necessary.  

  13. radonlaud says:

    Hi Certification Team

    I have upgraded my HCK from version 2.0.9200 to 2.1.9600.

    I got passed Windows Server 2008 R2 with HCK 2.0.9200 and regenerated my .hckx file with version 2.1.9600. But I still got the error "It looks like your package was created with an older version of the HCK. Ensure you’re using the latest version of the HCK and regenerate your .hckx file and try again. " when submitting. Do I have to rerun all the test with the latest version of the HCK?

  14. De Brabandere Martin-stevens isabel says:

    wij zitten geplaagd met een assistent digilock en kunnen bijna niets meer op pc, vind bijna nergens oplossing want telkens ik iets vind wordt het geblokkeerd, kan iemand ons helpen aub? alle verwezen pagina's die ik vind zijn al van het web verdwenen……

    Alvast bedankt

    isabel

  15. Mark Hughes says:

    Radonlaud,

    Contact the sysdev@Microsoft.com alias for a solution.    Currently the Dashboard site expects the RTM version of HCK for Windows 8.1. (HCK 2.1) to allow the submission to upload.  

  16. Mark Hughes says:

    De Brabandere Martin-stevens Isabel.

    The certification blog is designed to answer questions in the English language.   The HCK test kit is detection based and will assign the Product Type for testing to the devicedriver upon devicedriver install.   There would not be a Product Type for a digital lock device so it will not get assigned a Product Type by the HCK.  In that situation you would run all tests that appear and submit under the "Other" Product Type for a digital signature only.

    Feel free to send follow up questions directly to Sysdev@microsoft.com on this situation for more clarity.  

  17. Shruti Aggarwal says:

    Hi! I have question regarding Windows HCK. As per pre-requisites, a test server, a test computer and an external device for external device certification is needed. Is there a way, so that certification testing can be performed on one system?

    Can the certification testing for a device be performed properly using standalone HCK studio?

  18. Mark Hughes says:

    Each product type slightly varies on the equipment that will be required for testing.   Here is a link to the testing pre-requisites.  

    msdn.microsoft.com/…/hh998741

  19. Shruti Aggarwal says:

    Thanks for the link, Mark!

    My concern is Device.Portable Testing.

    Is there any link/video via which I can get more information specific to Device.Portable Testing? A demo may be.

  20. Mark Hughes says:

    Not aware of any videos specific to the device portable testing.  Here is a link to the current HCK videos.  

    msdn.microsoft.com/…/hh998373.aspx

  21. Bedabrata Chakrabarti says:

    Problem Name – DP-WLK – Hot Replace Device Test is failing

    Problem Description – DP WLK – Hot-Replace – Device Test – Verify driver support for D3 power state is getting failed on Windows Storage Server 2012 R2. It fails in Run IO Stress Test.

    Error Message –

    Log File Output:

    WDTF_SIMPLE_IO : – PerformIO(Matrox G200eh (WDDM 1.2) PCIVEN_102B&DEV_0533&SUBSYS_3381103C&REV_004&15D41075&0&01E7 ) Failed : The workstation is locked: Direct3D testing is not possible when the workstation is locked. Please ensure that the workstation is unlocked before starting this test, perhaps by enabling auto-admin-logon. You might have a domain or group policy that forces the workstation to be locked after resuming from sleep states: If so, please contact your network Administrator or remove the computer from the domain. HRESULT=0x80004005 Count 2830

    Steps Followed –

    1. Create an ISCSI Virtual Disk and map it to the initiator system

    2. Make sure the LUN is not initialized in Diskmgmt.msc and do not assign any drive letter to it.

    3. Execute the DP-WLK – Hot Replace Device Test from HCK Controller

  22. Bedabrata Chakrabarti says:

    Problem Name – iSCSI Target iSNS Test (LOGO) is failing

    Problem Description – iSCSI Target iSNS Test (LOGO) is failing in Windows Storage Server 2012 R2.

    It fails during running ISCSI ISNS test.

    Steps Followed –

    1. Create an ISCSI Virtual Disk and map it to the initiator system

    2. Add the ISNS server in Target System

    3. Type the ISNS server IP in ISNS address field

    Error Message –

    Log File Output:

    29908 29912 2014:5:29 20:42:39:35 Machine: Build=9200.00    Platform=AMD64    OS=Windows Storage Server 2012 R2 Standard    ServicePack=""    Version=6.3    BuildLab="winblue_gdr"    BuildDate=131030-1505    Language=English (US) (REDMOND)    Config=n/a    

    29908 29912 2014:5:29 20:42:39:35 iSCSI Target iSNS Client Test Version 0.9.0  

    29908 29912 2014:5:29 20:42:39:35 Copyright (c) 2003 Microsoft Corporation  

    29908 29912 2014:5:29 20:42:39:35 6.3.9600.16384  

    29908 29912 2014:5:29 20:42:39:113 Info: Initializing iSCSI test environment  

    29908 29912 2014:5:29 20:42:39:113 Info: Checking for registered ISNS servers  

    29908 29912 2014:5:29 20:42:39:113 Info: Removing iSNS server: 16.78.91.213  

    29908 29912 2014:5:29 20:42:39:129 TESTING DEVICE iqn.1991-05.com.microsoft:initiator1630.nas.lab  

    29908 29912 2014:5:29 20:42:39:129 TEST 1: Basic iSNS Test  

    29908 29912 2014:5:29 20:42:39:129 Start: ASSERTION 1.1 Adding iSNS Server WDKTUID: 3914cad4-c43c-11da-94f4-00123f3a6b60, TUID=  

    29908 29912 2014:5:29 20:42:39:160 Result: PASS.  Adding iSNS Server  

    29908 29912 2014:5:29 20:42:39:160 End: Pass, ASSERTION 1.1 Adding iSNS Server WDKTUID: 3914cad4-c43c-11da-94f4-00123f3a6b60, TUID=, Repro=iscsi_targetisns.exe  -hct -v 1    

    29908 29912 2014:5:29 20:42:39:160 Start: ASSERTION 1.2 Querying for current targets WDKTUID: 3914cad5-c43c-11da-94f4-00123f3a6b60, TUID=  

    29908 29912 2014:5:29 20:42:39:176 Result: PASS.  Query current targets complete  

    29908 29912 2014:5:29 20:42:39:176 End: Pass, ASSERTION 1.2 Querying for current targets WDKTUID: 3914cad5-c43c-11da-94f4-00123f3a6b60, TUID=, Repro=iscsi_targetisns.exe  -hct -v 1    

    29908 29912 2014:5:29 20:42:39:176 Start: ASSERTION 1.3 Finding target in list of current targets WDKTUID: 3914cad6-c43c-11da-94f4-00123f3a6b60, TUID=  

    29908 29912 2014:5:29 20:42:39:176 Response: Target not found  

    29908 29912 2014:5:29 20:42:39:176 Error: 0x80004005, Unspecified error   Result: FAIL.  Finding target   File=testsrcdriversteststoragewdkiscsihctlibtest.cpp Line=286  

    29908 29912 2014:5:29 20:42:39:176 End: Fail, ASSERTION 1.3 Finding target in list of current targets WDKTUID: 3914cad6-c43c-11da-94f4-00123f3a6b60, TUID=, Repro=iscsi_targetisns.exe  -hct -v 1    

    29908 29912 2014:5:29 20:42:39:176 TARGET ISNS TEST FAILED!  

    29908 29912 2014:5:29 20:42:39:176 Warn: Failed to reconnect to iSCSI target iqn.1991-05.com.microsoft:initiator1630.nas.lab   File=testsrcdriversteststoragewdkiscsitargetisnsmain.cpp, Line=315  

    29908 29912 2014:5:29 20:42:39:176 Summary: Total=3, Passed=2, Failed=1, Blocked=0, Warned=0, Skipped=0  

  23. Mark Hughes says:

    All HCK test support is designed to go through the CSS team (Customer Support Services).   Some partners use the certification forum for test support.  See link below for the forum.    Probably worth searching on the forum to see if others encountered the same or similar issue before opening up a CSS case.  

    social.msdn.microsoft.com/…/home