Windows Certification Newsletter - July 23, 2013
This newsletter provides up-to-date news about the Windows Certification (formerly Logo) Program and often provides info you can't get anywhere else. Did you get this from a friend? Subscribe now so you don't miss any important updates or changes.
For testing of systems running Windows Server, HCK 2.0 will be retired at the same time that it will be retired for Windows client testing.
Some previously created errata for HCK 2.0 for have been fixed in HCK for Windows 8.1. These errata are now retired. Also, some errata expire every month. Other errata will still be applicable, and of course new errata will be created to address issues.
You can find current errata status here or through your TAM.
Contingencies created to address issues with your product will expire as planned, as the kit version usually has no bearing on contingencies.
Current contingency status can be found here.
Because of improvements to the testing of class filter drivers in HCK for Windows 8.1, as well as other test improvements that apply to other types of drivers that don’t have a PnP ID associated, it’s now beneficial for customers to be able to see products submitted for Windows Server that aren’t associated with a specific product type. These products will be listed in the “Other” section of the catalog, even though no certification has been awarded.
To provide flexibility for vendors, and to ensure that the fastest possible memory configuration is tested for certification, a change was made to this test policy: “Test memory at the highest memory clock speed that is supported on the largest memory capacity configuration of the server, regardless of the number of memory channels or DIMM slots.”
The policy now states that if a system isn’t populated with the maximum supported memory during server system testing, this message will appear in the results:
"SMBiosCheckSystemMemoryDeviceTables - That write-up must include the following….” The message provides instructions on what information is required in the Readme file attached to the submission. This information is required because it’s not possible for Microsoft to know the combinations of memory size and memory speed in systems being tested. After review, a manual errata will be applied as appropriate.
We encourage vendors of systems that support Class 2 UEFI implementations (UEFI+CSM) to certify and submit them as UEFI platforms. For Windows Server 2012 R2, we no longer require the Class 2 UEFI systems to certify and submit twice (once for legacy BIOS mode and again for UEFI mode).
For further inquiries, please contact AskWSHC@microsoft.com.
For information about QFE updates, see Windows Hardware Certification Kit QFE Updates.
To get the latest QFEs for the Windows HCK, run HCKSetup.exe. The Windows HCK download includes all previous QFE updates.
Before applying the QFE, close all active DTM Studio sessions. Applying this QFE might affect in-progress submissions, so please complete any submissions before applying the QFE. After installing this QFE, you'll need to regenerate any affected submission that was generated before the QFE was installed.
- Hardware Dev Center
- Windows hardware development kits and tools
- Windows hardware development samples
- Windows Hardware Certification
- Newsletter archive
- Your dashboard
- Getting started