Windows Certification Newsletter
March 12, 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.
This page contains archived content. Technical details and URLs may not remain accurate over time.
System.Client.Tablet.Graphics.MinimumResolution relaxed for Windows 8
We're changing the System.Client.Tablet.Graphics.MinimumResolution requirement to create a consistent minimum resolution of 1024 x 768 at a depth of 32 bits across all Windows 8 system form factors. The physical dimensions of the display panel must still match the aspect ratio of the native resolution. This doesn't imply that we're encouraging partners to regularly use a lower screen resolution. In fact, we see customers embracing the higher resolution screens that make a great Windows experience. We understand that partners exploring designs for certain markets could find greater design flexibility helpful.
The lower resolution would disable snap, a feature that allows two Windows Store apps to be viewed simultaneously side by side. To avoid potential consumer disappointment, OEMs need to disclose the loss of snap.
To achieve certification with a sub-1366 x 768 panel, OEMs must explain how they will provide appropriate, clear, and conspicuous disclaimers that customers can see before they buy their PCs. For example, OEMs may use ads, websites, packaging, and/or point-of-purchase materials. This disclaimer must disclose that the system doesn't support snap. OEMs can also disclose what's needed to get snap to work, like connecting an external display that meets the standard minimum display resolution requirement of 1366 x 768. That part is optional, but providing a solution tells people that snap can be used, with some system modifications. Plus, it's a nice thing to do.
When creating their own disclaimers, OEMs should do something like this:
The disclosure must use the same localized language that the system does.
Ask Sysdev@microsoft.com for a copy of the screen relaxation form. Use the form to describe how you will handle the disclosure. On submission, include the completed form in your Readme folder, kind of how you would include a reference to a manual errata. The reviewers check to see if the form is all filled out. If you have questions on the process or need to discuss your disclosure plans with us before submission, email Sysdev@microsoft.com, or whatever you normally use to make submissions.
Tablet screen size now peaks at 17"
We evaluate feedback from partners as they propose new designs, and we've found that the current definition of tablets also applies to touch all-in-ones that have a battery. That's not what we intended. These larger systems aren't really designed to be handheld and mobile, so the tablet features aren't appropriate for them.
For certification purposes, we're tightening the definition of tablet by restricting it to systems with a screen size of 17" or less. Above that size, touch systems without batteries and attached accessible keyboards don't need to meet all of the tablet requirements.
If you have questions about your design, email Sysdev@microsoft.com
Some errata in the HCK extended
We've updated all active errata filters for the Hardware Certification Kit (HCK) 2.0. Any errata still indicating they're expiring on 3/1/2013 are either delayed enforcements with expired grace periods or were fixed in a QFE with a fix you need to incorporate into your testing environment. All active errata that weren't fixed in the test kit are now extended until 9/30/2013.
We'll reevaluate active errata again about 3 months before the new expiration dates. We'll either retire errata or extend it again, depending on whether fixes are in place for the test issues. A few errata are set to expire between 3/1 and 9/30 by design for delayed enforcement reasons. Those errata won't be extended again.
You can check the status of all errata anytime on the Hardware Dashboard. To narrow down the list, use the filters to view only active, expired, or expiring within 30 days. You can also search by ID and title.
Any extension date shouldn't be considered an indication of any retirement date.
More updates to UEFI POST time relaxations for some all-in-one systems
Based on industry feedback, we're further relaxing the UEFI POST time requirement to enable all-in-one systems with large storage capacity.
This delayed enforcement erratum begins April 15, 2013, when the UEFI requirement Erratum 478 relaxation expires, and ends in October 2014. To take advantage of this new delayed enforcement, Include ID 1250 in your README file starting April 15, 2013.
Choose the right USB 3 hub for HCK testing
The HCK erratum 339 and 526, which require USB 3 hubs for testing purposes, are being extended until 6/30/2013. This is the final extension for these errata. After June 30, all products must pass the test without the use of these errata.
Right now, you have your choice of 2 USB 3 hubs.
For hubs to qualify, we require two simple things:
These criteria ensure that the hub has gone through rigorous testing and will hold up to HCK device testing. If a hub meets both criteria, it should be safe to use in this test.
Logo License style guidelines updated
To support flexibility for logo placement and clarify logo size and greyscale info, the style specifications for the Windows Logo License Agreement for Hardware Version 2013 were recently revised with the following updates:
In this issue