Windows Certification Newsletter - March 26, 2013

New Windows Hardware Certification blog!

The Windows Certification Newsletter has been replaced by the Windows Hardware Certification blog. Go to the blog for the updates and info you’re used to seeing in the newsletter. Subscribe today!

In this issue

Windows 8 touch test jigs updated

System.Client.Tablet.Graphics.MinimumResolution relaxed for Windows 8

Tablet screen size now peaks at 17"

Choose the right USB 3 hub for HCK testing

Windows 8 touch test jigs updated

The Windows 8 Touch Test Jigs — Precision Touch Test Tool (PT3) and Rotation and Acoustic Tool (RA) — now are available from two sources to support both capacitive-based and optical-based touch technologies.

For detailed test specifications and availability, please contact one of these certified jig vendors:

  • Triex Technologies, Inc.

    Tim Wright,, +1 (206) 940-0943

  • Industrial Technology Research Institute

    Sen-Yih Chou,, +886 (03) 5743887

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 integrated display resolution of this system is below the threshold for snap, a feature that lets people view two Windows Store apps at the same time. App snapping will work if you attach an external display that supports a screen resolution of 1366 x 768 or higher.

The disclosure must use the same localized language that the system does.

Submission process

Ask 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, 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

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:

  • It's USB-IF certified. (Does it display the USB logo?)

  • It's HCK certified. (Does it have a Windows 8 logo?)

These criteria ensure that the hub has gone through rigorous testing and will hold up to Windows Hardware Certification Kit (Windows HCK) device testing. If a hub meets both criteria, it should be safe to use in this test.

Related topics

Hardware Dev Center
Windows hardware development kits and tools
Windows hardware development samples
Windows Hardware Certification
Newsletter archive
Your dashboard
Getting started



Send comments about this topic to Microsoft