[News] HCK & QFE release information for all HCK test engineer RRS feed

  • 問題

  • HCK & QFE release information for all HCK test engineer

    Which version of the Windows HCK do I have?

    Before you install QFEs for the Windows HCK, first determine if you are already up to date:

    1. On your controller, use Control Panel to go to the Uninstall a Program dialog.
    2. You will see Windows Hardware Certificate Kit on the list of installed programs. It will have a version number like 8.59.25584
    3. Compare the last five digits of the version number with the QFE list below.

    Most QFEs will be optional. This means that you can create submission packages that will be accepted without the QFE installed. If a QFE is required, you will need to install the QFE before you can create submission packages. You should restart any projects you have not completed after you install a QFE.

    How do I install the QFE?

    Before you begin installing QFEs on your controller, make sure that you do not have any tests running. Also be sure that all of the open Windows HCK Studio and HCK Manager windows attached to the controller have been closed. If a QFE includes changes to the ARM client, you may also be required to uninstall your ARM clients before you install the QFE. Each QFE will indicate if this is required.

    To install QFEs, rerun HCKsetup.exe by clicking the following link:

    When you run HCKsetup.exe, you are given the option to Install or Download.

    • If you select Install and the Windows HCK is already installed on the machine from which you are running, only the updates that have been released since you last ran setup will be installed.

    • If you select Download, you may select to download either Windows HCK Studio Only or Windows HCK Controller + Studio. The entire set of files required to do a clean installation of the option you select will be downloaded, including all cumulative updates. When you run HCKSetup.exe from the downloaded folder on a machine which already has the Windows HCK installed, only the updates that have been released since you last ran setup will be installed.

      • For Downloaded Windows HCK Studio Only:
        When you run HCKSetup.exe from the downloaded folder, your stand-alone HCK Studio will be updated. No uninstall/reinstall is required.
      • For Downloaded Windows HCK Controller + Studio:
        If the QFE contains updates for the Windows HCK Client, those updates will be automatically pushed out to any x86/x64 clients that are attached to the controller when you run HCKSetup.exe. If they contain changes to the ARM client, you will need to uninstall the ARM client before you install the QFE, then re-install the ARM client after the QFE has been installed to your controller.
        If the QFE contains updates for the Windows HCK Studio, for a remote installation of Windows HCK Studio that was installed from the Windows HCK Controller's Studio Install share, the next time the user starts Windows HCK Studio they will be informed that an update is available. To install the update, the user will need to uninstall and then reinstall Windows HCK Studio.

    IMPORTANT: After a QFE has been installed, it cannot be uninstalled.

    What are the latest QFE updates?

    Once you determine which version of the Windows HCK you have, review the following list of updates to determine whether you would benefit from downloading the latest version of the Windows HCK, which includes all of these updates.

    QFE Update 002 (Build ID: 8.59.29696)

    Release date: August 22, 2012

    Optional or required: Optional

    Description of changes:

    • Updated the logic for applying filters when the “IsLogRequired” property is set to false. When “IsLogRequired” is set to false, the filter will no longer be applied when a log file exists.
    • WindowsFilteringPlatform_Tests: Fixed issue where WFPLogo.exe AVs when not using answer scripts
    • WindowsFilteringPlatform_Tests: Fixed issue where Callout.sys bugchecks when unable to get an engineHandle
    • MJPEG Decoder MFTD Playback, MJPEG Decoder MFTDVisVal, MPEG4pt2 Decoder MFTD Playback, MPEG4pt2 Decoder MFTDVisVal: The test was changed to allow MFTs that don't expose NV12 as a preferred output type to be picked up over SW and be used.
    • Run Rsc Tests: The cleanup task "Uninstall RSC Test light-weight filter" hangs when trying to uninstall light-weight filter driver coealesce.sys. This is because coalesce.sys does not return all NBLs indicated by the miniport to the miniport. A user would need to login to the client machine (system under test) and close the command prompt window that is running the command "Drvinstall -c MS_Coalesce -d coalesce -uinst". Or they would need to kill DrvInstall process. This would cause the task to marked as failed which would also cause the job to mark as failed.
    • "Win8 LoadGen Server Stress - Start Test for Server" and "Win8 LoadGen Server Stress - Start Test for Fault Tolerant Server" tests would fail on Server 2012 RTM with the following error message: "CheckRequirements::CheckRequirement:Machine: WIN8SUT Class: Win32_OperatingSystem Property: BuildNumber Property Value: 9200 is higher than required max 9000."
    • Webcam Verification: Improve detection so tests will be scheduled even if the device drivers set the wrong device class name.

    QFE Update 001 (Build ID: 8.59.29692)

    Release date: August 17, 2012

    Optional or required: Optional

    Description of changes:

    • The "Present Validation 2 (Fullscreen)" test was not running properly on devices that do not enumerate one of the tests preferred display modes (1024x768, 800x600, or 640x480). This caused the test to skip all test cases. This fix allows the test to run in the current display mode if none of the preferred modes are available.
    • WGFVidMMWDDM1_2.exe OfferReclaim test has a test case (OfferReclaimInternalSurface) which validates a requirement that states that after Flush() UMD can have no more than 1 MB of UMD internal Staging Surfaces which are not Offered per Device. This test always assumes that there is only 1 Device and therefore only checks that the total of all non-offered Staging Surfaces from that Process is less than 1 MB. However, when test is run with "-whql" switch on Devices that are below Feature Level 11.1, there will be some extra devices created and not cleaned up properly, which might result in over 1 MB of Staging Buffers not being Offered from the test Process. This job has been modified to add "OrigD3DInterfaceLevel:11.0" to the command line. Doing so will tell the test framework to create DX11 device right away and the test won't ave extra DX10 devices created.
    • Lullaby - Update test to set and clear the Lock Screen registry key to allow the test to exit Connected Standby.
    • Webcam Basic Perf - Due to a regression, the test can no longer create an audio stream on the audio capture device. The test will stop past this failure and fail the test case due to the audio latency being too large.
    • Webcam BasicPerf System (Manual), incorrectly enumerates TV tuner as webcam device and tries to run validation on it. Test will always result in failure for TV tuner. If TV tuner is enumerated first will cause same test not to be run on system web cameras.
    • GFXIntegration Power Management Test will not correctly be excluded from DAM/PLM list if TESTSIGNING is not enabled. If the test is not on the exemption list, it will become froze and not complete without user interaction. In addition, power management tests will save and restore the system BDC store in order to maintain the test signing condition of the machine in tests.
    • DMR Playback Performance (PERF-01 PERF_05) is now properly categorized as a manual test.
    • The Fidelity Test update enables proper use of a registry key to allow audio offload on the Windows 8 desktop.
    • Validate HAL Extension loaded successfully
    • Microsoft.WindowsLogoKits.DevFund.MemoryTest.DriverFootprint was intended to check for the driver non-paged code pages in memory and fails if non-paged code pages are larger than the limits defined below. However, the current DriverFootprint test does not account for the memory category that accurately measures non paged code pages. With this QFE, the DriverFootprint will be updated to account for the appropriate category.

      Driver type x86 x64
      Graphics drivers <= 10 MB <= 10 MB
      All other driver types <= 1.66 MB <= 5.45 MB

    Also includes these earlier changes:

    • WGF11Precision.exe is not allowing some valid D3D9 round modes like round to nearest even. There are also some test issues with logging such that if the IHV fails the test, the test will crash when attempting to log output.
    • CHAOS Test - Update the test to no longer require any user intervention when running this test on S4 on systems that don't have RTC wake.
    • DMR Events (EVENT-01) - The eventing test no longer requires a "/r/n" character sequence at the end of NOTIFY payloads.
    • All DXVA and HMFT Tests - This change updates the tests to prevent the screen from idling off during the tests.
    • Connected Standby IO Stress test fails during the configuration stage causing a failure in the "Check Configuration" task. A fix to allow the test to correctly identify IO and power events has been applied so that the rest of the testing can continue uninterrupted.
    • PnPDTest should not rebalance for ARM systems - Resources are fixed on ARM systems during boot so there is no reason to try and perform a resource rebalance. This adjusts the tests to not test these sceanrios while on a ARM platform.
    • Glitchfree HD Video Playback on AC ( Manual on mobile systems)

      Glitchfree HD Video Playback on Battery (DC) Power Source (Manual on mobile systems)

      Description of changes:

      - Reduced kernel mode providers and used smaller buffer sizes to reduce chances of paging

      - Tolerance for video glitch & ISR/DPC metrics adjusted to 1.5 seconds after playback starts

      - Ignore bad vsyncs that occur prior to first 1.5 seconds after playback

    2012年8月27日 上午 04:11


  • QFE Update 003 (Build ID: 8.59.29702)

    Release date: August 31, 2012

    Optional or required: Optional

    Description of changes:

      • Storage Performance EMMC test requests the system suspend entering Connected Standby throughout the execution of the test in order to allow the test to complete without manual intervention.
      • NDISTest 6.5 - [2 Machine] - QosStorageInterop: Fixes following false failure "QosStorageInteropTest::InitializeHelpers: Failed to Initialize Storage Traffic Bandwidth Monitor, ensure that 'Storage Connection Mode' hot-parameter is configured correctly", this failure is caused when the SMB share configured as hot-parameter vanished because of a test-initiated reboot to alter Driver Verifier settings prior to commencing the test.
      • The job for WHCK "Brightness Test" was modified to not use powercfg.exe to change an ambient light sensor (ALS) influence on Win7, as this option is not present on this OS.
      • INPUT-01 INPUT-05 DMR playback test previously cached the IP address and port number of the DMR under test. This would cause DMRs that change port numbers between reboots to fail this test. The test has been updated to refresh the IP address and port number after device rediscovery.
      • PPM Logo Test: An issue with the test failing incorrectly has been fixed. The test failed because of an incorrect return value for one of the test cases.
      • DMR playback tests which do not enforce format requirements now correctly validate against the device protocolInfo string and will skip playing optional formats that are not supported by the device rather than failing. This fix affects the following tests:
        • DMR Playback Performance (PERF-01 PERF_05) - NetMedia_0132
        • DMRs must have seek support (SEEK-01 SEEK-05 SEEK-10 SEEK-15) - NetMedia_0070
        • DMRs plays media continuously (STRESS-01) - NetMedia_0048
        • DMRs Supports SetNextAVTransportURI (SETNEXT-01 SETNEXT-05 SETNEXT-10 SETNEXT-15) -NETMEDIA_0126
      • For the following tests:
        • Runtime Power Focused Stress (Logo)
        • Runtime Power Focused Stress with Driver Verifier's Concurrency Stress (Logo)
        • Connected Standby Stress with Driver Verifier's Concurrency Stress (Logo)
        • Connected Standby Stress (Logo)
        The following performance and diagnosability issues were addressed:
        1. The two runtime power tests make two calls to WDTF API GetInterfacesIfExist on each test cycle. Each GetInterfacesIfExist call can take up to one minute. The fix is to cache the handles for the WDTF interfaces. This eliminates 2 minutes for each test cycle, or 1000 mins for 500 test cycles in the Runtime Power Focused Stress tests.
        2. TE.exe will now shutdown gracefully when the test exceeds its expected run time rather than being canceled by the controller.
    2012年9月1日 下午 03:42
  • QFE Update 004 (Build ID: 8.59.29708)

    Release date: September 11, 2012

    Optional or required: Optional

    Description of changes:

    • The BatteryTest currently assume that the remaining capacity will never run backwards during a charging cycle. This might not be true all the time, due to temperature changes and OS usage. With updated Battery Guideline, the test will now relax the requirement during charging and discharging to consider this edge case.
    • The BatteryTest currently assume Last Full Charged Capacity to be static until the battery gets recharged. However, this is not true on some systems where the Last Full Charged Capacity is changing every 5 - 10 minutes. The OS expect this to be static and waiting on battery trip point using published MSDN library will fail whenever this static information changes. With updated Battery Guideline, the fix will enforce the rule of not allowing Last Full Charged Capacity to change during discharge but relaxes the requirement during charging.
    • Update for the audio gatherer to ensure that INF filename generated is correct to ensure audio gatherer xml file is written.
    • The device digitizer - panning latency test is being updated to to accommodate for measurement variance caused by different screen sizes and device types for Windows 8. The test will allow for a +-3ms variance in the results for the test. This change does not impact the requirements for response latency with respect to panning latency.
    • The Touch response latency test will now be divided into two separate tests - one for panning latency and one for down latency. These tests are being separated to make it easier to run the response latency tests individually.
    • The Display Colorimetric Tolerance test will now time out after 120 minutes, instead of the previous value of 30 minutes. This provides more time for the tester to complete the measurements.
    • This change fixes a failure in the AutoMemoryBenchmark setup task "MemoryBenchmark Setup" returning errorlevel=1 on configurations with a large %path% environment variable.
    • The SetNext-01 test was failing due to calling SetNextAVTransportUri before SetAVTransportUri since SetAVTransportUri clears the NextUri field. Test has been updated to call SetAVTransportUri before SetNextAVTransportUri per UPnP specification.
    • The code for Brightness Test was modified to prevent a monitor going into a dimmed state.
    • In "Webcam BasicPerf System (Manual)" the number of Frame memory copies during the camera latency measurement has been reduced.
    • Secure Boot Manual Logo Test is now using the value "Microsoft Corporation UEFI CA 2011" in the Microsoft Test Root. This change allows devices' UEFI drivers to function after reboot. This fix does not apply to WinRT systems.
    2012年9月12日 上午 03:44
  • QFE Update 005 (Build ID: 8.59.29723)

    Release date: October 2, 2012

    Optional or required: Optional

    Description of changes:

    • INPUT-01 INPUT-05 DMR playback test previously cached the IP address and port number of the DMR under test. This would cause DMRs that change port numbers between reboots to fail this test. The test has been updated to refresh the IP address and port number after device rediscovery.
    • Tests affected:
      • NDISTest 6.0 - 2c_Mini6CheckConnections
      • NDISTest 6.0 - 1c_Mini6Send
      • NDISTest 6.0 - 2c_Mini6SendRecvReply
      • NDISTest 6.0 - 2c_Mini6SendRecv
      • NDISTest 6.0 - 2c_Mini6Stress
      • NDISTest 6.0 - 1c_Mini6PerfSend
      • NDISTest 6.0 - 2c_Mini6Performance
      If you run any send/receive NDISTest 6.0 test on some systems it will bugcheck in the ndprot driver. This fix removes the illegal behavior in the ndprot driver that causes this bugcheck.
    • Connected Standby Stress (Logo) - This fix addresses the 4 minute delay in the test to instead proceed as soon as a GPS signal is available; reducing the overall runtime and timeout errors being hit today.
    • WGF11ResourceAccess.exe - The test will no longer crash in VideoDecode test cases when run on devices that don't support video decoder profiles.
    • Co-installer Version Check - This test will validate that the RTM version of co-installer is used for development. Using a Pre-RTM version will cause this test to fail.
    • The AutoMemoryBenchMark for graphics driver will now correctly use the steady state reference set value in consideration rather than the peak reference set value. This addresses issues where driver were not seeing improvement in their memory score after freeing some memory used temporarily during one of the scenario.
    • The tests TPM 1.2 UEFI Preboot Interface Test and TPM 2.0 UEFI Preboot Interface Test have been modified to catch the most likely implementation errors of Boot Manager measurements in PCR4. The tests also log an illustration of the correct Authenticode hashing of Boot Manager.
    • The test ACPI Logo Test has been modified to catch the most likely ACPI firmware errors in describing TPM 1.2 and 2.0 devices. The test now enforces the requirement that a TPM device sits behind buses/modules with PNP IDs mapping to inbox MSFT drivers (e.g. PCI/ISA)
    • The TPM 2.0 Hardware Interface test cases accessing non-volatile storage may fail if the size of the non-volatile storage is limited. This fix enables the respective test cases to deal with limited non-volatile storage space.
    • Reordered test cases and increased free space of some test cases to ease the burden on the storage device.
    • MTPTest has been reported to randomly hang based on an issue in the test logic infrastructure. If an MTP object on the device supports 10 or more properties the procedure to fill in these with random values may hang. The test is not cancellable and therefore it will invalidate the test run. This update will prevent the hang from occurring. This will not change or increase test coverage of the MTP device.
    • Windows Touch Response Latency Test: Improved stability in calibration that will cut down on errors and shorten the time it takes to run.
    • A fix in QFE 001 uncovered a bug in Round Trip test which caused in-air validation to start and then immediately stop. The test offers to retry, but all retries fail and the user must eventually cancel the test. This fixes the Round Trip bug, allow the recording to capture enough data to analyze and validate that the recording device works.
    • HCK OM: Drivers targeting Windows Server 2012 will no longer trigger signability tests for Windows Server 2008 during packaging.
    • This fix introduces a new test case: Validate WFP Usage. This case enables us to loosen the restrictions on the NetworkDiagnosticsFramework and PowerManagedState requirements for non-firewall products.
    2012年10月3日 上午 08:39
  • QFE Update 006 (Build ID: 8.59.29734)

    Release date: November 13, 2012

    Optional or required:Optional

    Description of changes:

    • ELAM logo test is fixed to ensure that the test does not fail when the ETL file generated by the test is greater than 2 GB.
    • D2DScenario and DImageScenario tests are now measuring the GlitchCount and FPS metrics after encountering the DirectFlip event. This ensures that no glitches happening before the DirectFlip event can cause failures for these metrics.

    • 已編輯 Ogis 2012年11月20日 上午 01:51
    2012年11月20日 上午 01:49
  • QFE Update 007 (Build ID: 8.59.29757)

    Release date: December 11, 2012

    Optional or required:Optional

    Description of changes:

    • DisplayGathere.dll was modified to better handle complex INF files and Hybrid systems.
    • "Verify Graphics Device Count is one" test was modified to better handle Hybrid systems.
    • The "VESA and CEA required display modes" and "Display Mode Filter Check" tests now base their results on the test log instead of the processes exit code.
    • Vertical Pairing Logo Test run against a 2.0 device the test will find the UUID in the Vertical Pairing Vendor Extension.
    • Plug and Play Driver Test: A fix prevents the test attempt to hot remove the processor on x86 SoC systems and prevents a bugcheck. This fix replaces manual errata #942.
    • SES Test (LOGO) - Test case enhancement to check for drive's serial number within the enclosure. Improve flexibility to handle multiple enclosure configurations.
    • Enumeration Test (LOGO) - Test cannot assume that all Descriptor elements are exclusively of Type 0, there can be expander Type 1. Test needs to compare ElementIndex for ascending order. Test needs calculate element descriptor length correctly based on the respective PHY size. Test is also enhanced for multi-pathed configuration (no MPIO) SES detection.
    • This fix will allow for the WindowsFilteringPlatform_Tests run fully in the case of a failure during the WFP Usage Validation case.
    2012年12月18日 上午 02:26
  • QFE Update 008 (Build ID: 8.59.29779)

    Release date: January 8, 2013

    Optional or required:Optional

    Description of changes:

    • The Roundtrip microphone validation will now release all open handles to microphones once they have been tested; this fixes a "device in use" failure when multiple microphones share an analog-to-digital converter.
    • D2DScenario and DImageScenario tests are now allowing up to 2 glitches each test. This ensures that occasional interruption by OS processes will not cause false failures.
    • WGF11 Resource Access Test
      • False failures due to incorrect decoder profile usage are fixed.
      • WGF11 Resource Access FL9.3 test will now be scheduled against D3D9 WDDM 1.2 hardware enforcing requirement Device.Graphics.AdapterRender.D3D11Level9WDDM12.D3D9UMDDIUpdate. A bug has been fixed in the feature XPath query.
      • Command line for WGF11 Resource Access FL9.3 test is corrected to avoid test requiring support for FL9.3. Job title was left unchanged to avoid breaking any existing automation or documentation.
    • GFXintegration Power Management Test modifies the power scheme. Once the test is complete, it does not restore the power scheme to the state before modification. The fix here is to save the power scheme before any modification, and to restore after the test is complete.
    2013年1月10日 上午 01:59
  • QFE Update 009 (Build ID: 8.59.29819)

    Release date: February 12, 2013

    Optional or required: Optional

    Description of change:

    2013年2月18日 上午 07:54
  • QFE Update 010 (Build ID: 8.59.29854)    


    Release date: April 9, 2013

    Optional or required: Optional

    Description of change:

    • DisplayGatherer.dll had a regression starting with QFE007. Capabilities for Display devices were not reported accurately. The effect was some of the relevant Windows HCK tests were not run on the display device. These issues are fixed in this release.
    • This fix adds a new Product Type, vSwitchExtension, to Windows HCK to specifically identify those certification submissions that are for Hyper-V Extensible Switch extensions. The product type is carried with the submission to Microsoft's web portal to identify switch extensions so that they may be added to the Windows Server Catalog under the Hyper-V Switch Extensions area. Previously, extensions could receive a logo certification, but would not be listed on
    2013年4月15日 上午 05:45
  • Hi,

    Present my QFE version is "QFE Update 007" and how to update the laest version QFE.

    When I run HCKsetup.exe it will show like "This feature is up-to-date"(something like ) getting ,what does't mean??

    Yesubabu Gude

    2013年4月19日 上午 01:47
  • Hi,

    Below install information for reference.

    After click HCKsetup.exe  and choose "Studio + Controler" to download the WHCK packages on your NB or desktop platform. Then copy and install  the WHCK packages under Windows Server 2008 OS. I don't used update to upgrade the QFE. I Just re-install Windows Server 2008 R2 (Pure OS) and then install WHCK package to WHCK server.


    2013年4月23日 上午 03:57