Windows Certification Newsletter
January 15, 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.
UEFI POST TIME requirement relaxed for some all-in-one systems
Based on industry feedback, we're relaxing the UEFI POST TIME requirement to enable large storage capacity in all-in-one systems.
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
Windows Touch Test Lab closed for Chinese New Year
We'd like to remind our partners that Windows Touch Test Lab will be closed from February 9–17 for Chinese New Year. There will be no device delivery or submission processing during those 9 days.
Partners who want to ensure device certification prior to the holiday should:
Submissions made or devices delivered after January 31 might not be processed before the holiday. We also expect submission volume to be heavy, so plan for a 5–10 business day turnaround, in addition to the holiday break.
UEFI submission review processes changed
UEFI submissions will no longer go through an automated signing process. Instead, we'll review them manually twice a week. You can expect your submission to be processed in about 5 business days. To avoid delays, please follow the guidelines posted on the UEFI submission page on the Hardware Dashboard. Remember when submitting to the UEFI signing portal to:
Please join us in our new online forum
We'd like to invite you to the brand new Windows Hardware Testing and Certification forum on MSDN.
The forum is a place for engineers testing and certifying Windows hardware, drivers, and systems to share knowledge, get questions answered, and learn from shared experiences. To begin leveraging the collective knowledge of the community, just post a question on your topic of interest.
The forums are public, so please don't post questions or comments about prerelease versions of the Hardware Certification Kit. As with all other online discussions, be mindful of your privacy — never post info that can personally identify you, like your email address or company name.
We'll be monitoring the forum, so if you have any suggestions or feedback for us on the kit, tests, or certification process, please feel free to post that, too!
Linking your device to your app
Now that Windows 8 is hitting the marketplace, more partners are beginning to grasp the potential of the Windows Store apps that are connected to your device. Although the experience is simple and seamless for end users, the process to create this linkage requires attention to details. We're finding that metadata submissions are failing because of minor issues.
The white paper "Windows Store Device App Lifecycle" details the .xml files that are needed to make the linkage, how to test the app and .xml files, and how to submit packages properly.
For help with Windows Store apps, check the forum or contact CSS.
In this issue