Skip to main content

Current News and Notices

Updated: October 5, 2010

See also:
   Windows Logo Program Requirement Updates
   Windows Logo Program Newsletter Archive

On This Page

New Requirement to Improve Experience with USB 3.0 and USB 2.0 Devices  New Requirement to Improve Experience with USB 3.0 and USB 2.0 Devices
Windows 7 SP1: Software Logo Program Unchanged  Windows 7 SP1: Software Logo Program Unchanged
System Logo Requirement for Biometric Devices (Follow-Up)  System Logo Requirement for Biometric Devices (Follow-Up)
Errata Expiring Before December 31, 2010   Errata Expiring Before December 31, 2010
Windows Logo Kit 1.6 to include SQL Server 2008 R2 Express  Windows Logo Kit 1.6 to include SQL Server 2008 R2 Express
Logo Programs Retiring: Network Attached Storage Devices   Logo Programs Retiring: Network Attached Storage Devices
Errata Expiring Before December 1, 2010  Errata Expiring Before December 1, 2010
Touch Test Changes Coming for WLK 1.6  Touch Test Changes Coming for WLK 1.6
INPUT-0012, "Tablet systems implement buttons using a HID-compliant, mini-port driver and include a dedicated security button," applies to Windows 7  INPUT-0012, "Tablet systems implement buttons using a HID-compliant, mini-port driver and include a dedicated security button," applies to Windows 7
Video Fidelity Requirements Enforcement Date Extended  Video Fidelity Requirements Enforcement Date Extended
Windows Logo Program Requirement and Policy Updates  Windows Logo Program Requirement and Policy Updates
Information on Windows Logo Kit 1.6  Information on Windows Logo Kit 1.6
New Logo Program Category: Filter Drivers   New Logo Program Category: Filter Drivers
DISPLAY-0113 Retired Immediately  DISPLAY-0113 Retired Immediately
Errata Expiring Before November 1, 2010  Errata Expiring Before November 1, 2010
Original Equipment Manufacturers Can Continue to Ship Unclassified Biometric Fingerprint Readers  Original Equipment Manufacturers Can Continue to Ship Unclassified Biometric Fingerprint Readers
New Logo License Agreement 2011 Available for Signing on July 1  New Logo License Agreement 2011 Available for Signing on July 1
New Billing Service Features Go Live On July 1  New Billing Service Features Go Live On July 1
Retiring Windows Logo Program Categories  Retiring Windows Logo Program Categories
Retirement Date Postponed for Tape Drive, Medium Changer, and Serial Port Adapters Categories  Retirement Date Postponed for Tape Drive, Medium Changer, and Serial Port Adapters Categories
Windows Logo Kit 1.5 QFE 002 Is Now Available on Connect  Windows Logo Kit 1.5 QFE 002 Is Now Available on Connect
Windows Logo Kit 1.5 QFE 004 Is Now Available on Connect  Windows Logo Kit 1.5 QFE 004 Is Now Available on Connect
Windows Summit 2010 Virtual Event: Device Track To Be Extended on June 30!  Windows Summit 2010 Virtual Event: Device Track To Be Extended on June 30!
New Billing Service Features Go Live On July 1  New Billing Service Features Go Live On July 1
Retiring Windows Logo Program Categories  Retiring Windows Logo Program Categories
New FAQs for the Windows 7 Software Logo Program  New FAQs for the Windows 7 Software Logo Program
Windows Summit 2010 Virtual Event  Windows Summit 2010 Virtual Event
Enforcement Delayed for NETWORK-0212 and NETWORK-0227  Enforcement Delayed for NETWORK-0212 and NETWORK-0227
Link Layer Topology Discovery Will Not Be Required  Link Layer Topology Discovery Will Not Be Required
Preview Errata Currently in Effect  Preview Errata Currently in Effect
Errata That Will Expire Before October  Errata That Will Expire Before October
Windows Summit 2010 Begins Today!  Windows Summit 2010 Begins Today!
Windows Logo Kit 1.5 QFE 001 Is Now Available on Connect  Windows Logo Kit 1.5 QFE 001 Is Now Available on Connect
Network-Connected Printers Must Implement Windows Rally  Network-Connected Printers Must Implement Windows Rally
Clarifications to STORAGE-0026 for Optical Drives  Clarifications to STORAGE-0026 for Optical Drives
GPU Family Update Submissions Are Back Online  GPU Family Update Submissions Are Back Online
Expiration Dates for Preview Errata and Regular Errata  Expiration Dates for Preview Errata and Regular Errata
Reminder About New Requirements for June 2010  Reminder About New Requirements for June 2010
Windows Summit 2010: Wherever You Are, Be Here  Windows Summit 2010: Wherever You Are, Be Here
Windows Summit 2010: Wherever You Are, Be Here  Windows Summit 2010: Wherever You Are, Be Here
Windows Logo Kit 1.5 QFE 003 Is Now Available on Connect  Windows Logo Kit 1.5 QFE 003 Is Now Available on Connect
Latest DTM Help Documentation Available for Download  Latest DTM Help Documentation Available for Download
GPU Family Update Program Temporarily Suspended  GPU Family Update Program Temporarily Suspended
Windows Summit 2010 Session Update  Windows Summit 2010 Session Update
Reminder About New Requirements for June 2010  Reminder About New Requirements for June 2010
Register for Windows Summit 2010!  Register for Windows Summit 2010!
New Windows Error Reporting Agreement Version 1.3 Now Available  New Windows Error Reporting Agreement Version 1.3 Now Available
Register for Windows Summit 2010!  Register for Windows Summit 2010!
New Windows Error Reporting Agreement Version 1.3 Now Available  New Windows Error Reporting Agreement Version 1.3 Now Available
Your Last Chance to Change the Windows Client Software Logo Program!  Your Last Chance to Change the Windows Client Software Logo Program!
Some Preview Errata Have Been Converted to Regular Errata  Some Preview Errata Have Been Converted to Regular Errata
Your Chance to Change the Windows Client Software Logo Program!  Your Chance to Change the Windows Client Software Logo Program!
Release Schedule for Windows Logo Kit 1.6  Release Schedule for Windows Logo Kit 1.6
Your Chance to Change the Windows Client Software Logo Program!  Your Chance to Change the Windows Client Software Logo Program!
Your Chance to Change the Windows Client Software Logo Program!  Your Chance to Change the Windows Client Software Logo Program!
Device Metadata Announces Bulk Upload Functionality  Device Metadata Announces Bulk Upload Functionality
Device Metadata Announces Bulk Upload Functionality  Device Metadata Announces Bulk Upload Functionality
MPIO Test Removed from Hardware-Based RAID (Storage Array) Test Category  MPIO Test Removed from Hardware-Based RAID (Storage Array) Test Category
Devices Must Support x64-Based Versions of Windows  Devices Must Support x64-Based Versions of Windows
Windows Vista SP2 Deadline Extension  Windows Vista SP2 Deadline Extension


New Requirement to Improve Experience with USB 3.0 and USB 2.0 Devices

Starting December 1, 2010, logo requirement ID SYSFUND-0225 goes into effect for motherboards and all system form factors. The requirement states that systems and motherboards that have xHCI controllers should route the USB 3.0 (Super Speed) and USB 2.0 ports corresponding to each connector to the same xHCI controller.

The rationale behind this requirement is to avoid companion controller implementation of xHCI controllers in systems. It can lead to bug checks and bad device states when switching USB ports on the system.

Work with your suppliers to ensure your motherboard implementation meets this logo requirement. For complete details, see SYSFUND-0225 on LogoPoint. LogoPoint can be accessed through your Winqual account.

(Announcement Date: October 5, 2010)

Windows 7 SP1: Software Logo Program Unchanged

For Windows 7 Service Pack 1 (SP1), the Windows 7 Software Logo Program will continue unchanged. For partners who have attained the Windows Software Logo for their applications, the logo continues to apply for SP1. For partners who have a new application or a new version of an application that already has a logo, you can continue to use the current Windows Software Logo Kit (WSLK) and process as described on MSDN: http://msdn.microsoft.com/en-us/windows/dd203105.aspx.

(Announcement Date: September 28, 2010)

System Logo Requirement for Biometric Devices (Follow-Up)

In an earlier edition of the Windows Logo newsletter, we informed you that with the release of Windows Logo Kit version 1.6, the Windows Logo Program will have a category for biometric fingerprint readers. We also notified you that we would delay enforcement of those requirements for systems until December 1, 2012. We have posted a requirement clarifying this (SYSFUND-0234). All requirements are posted on LogoPoint, which can be accessed through your Winqual account.

(Announcement Date: September 7, 2010)

Errata Expiring Before December 31, 2010

This is a list of all errata expiring between September 1, 2010, and December 31, 2010. Most errata that previously were expiring in December 2010 have been extended to June 1, 2011, or later.

Expiring September 9, 2010:

  • 2088. Due to a unique and customer specific issue, a specific failure in the IPSecOffloadv2 logo verification (Win7) test is being waived for a short period.

Expiring September 30, 2010:

  • 1198. UAA Test Preview errata: S/PDIF pin "Pin Sense" responses cannot use "Impedance" bits

  • 1279. Reinstall with IO doesn't consider other methods of install/uninstall

Expiring December 1, 2010:

  • 1315. PREVIEW: IO Cancellation with Direct IO: This test is preview in WLK 1.4 & 1.5

  • 1326. Display: D3D Content Protection -CPAuthChannelAPI fail due to missing GUID

  • 1608. NDIS: WLAN: Statistics_ext has been modified for WLK 1.5 some failures should be in PREVIEW mode

  • 1609. NDIS: WLAN: SoftAP_WPS_ext is a PREVIEW test

  • 1719. LOGO Wireless router WPS preview test errata WCN Wireless Default Configuration (Router Reset)

  • 1720. Wireless router WPS preview test errata WCN UPnP Configure And Connect to AP with WPA2PSK AES PassPhrase using PIN over Wireless

  • 1786. USB Host Controller Tramsfer Speed Test - PREVIEW

  • 1789. USB DRIVER RE-ENUMERATION TEST - PREVIEW

  • 1796. Preview filter for the Storage Trim Test

  • 1812. Preview: VWiFiStress is a preview test for WLK 1.5

  • 1871. The Windows Client System Check for WDDM 1.1 Display Driver Support test is not required for Ultra Mobile PCs per SYSFUND-0192 Version 4

  • 1963. Sensor tests: PREVIEW Errata: Several Sensor tests new to WLK 1.5 are in preview mode

(Announcement Date: September 7, 2010)

Windows Logo Kit 1.6 to include SQL Server 2008 R2 Express

Windows Logo Kit (WLK) 1.6 will support running the controller on Windows Server 2008 R2, fulfilling a request from partners to move to a current operating system. The WLK 1.6 controller will not be supported on any other operating system or edition. Also, WLK 1.6 will include Microsoft SQL Server 2008 R2 Express. If SQL Server is not installed on the system, then SQL Server 2008 R2 Express will be installed automatically; however, if SQL Server 2005 or SQL Server 2008 is already installed on the controller, WLK setup will use the installed version of SQL Server. We are pleased to be able to deliver these improvements to the ecosystem community in the WLK 1.6 release, along with hundreds of content quality improvements.

(Announcement Date: August 17, 2010)

Logo Programs Retiring: Network Attached Storage Devices

The Windows Logo programs for network attached storage devices will retire in concert with the release of Windows Logo Kit (WLK) 1.6. WLK 1.6 will no longer contain programs for "Storage > Network Attached Storage" and "Storage > Wireless Network Attached Storage." Partners who wish to continue to use logos for this class of devices may be able to do so through the "Networked Media Device > Digital Media Server" and "Networked Media Device > Digital Media Server Wireless" categories, respectively.

(Announcement Date: August 10, 2010)

Errata Expiring Before December 1, 2010

Expiring August 31, 2010:

  • 1338. UAA Test: PREVIEW Errata: This test enforces Low Power DCN requirement that D3 Cold support entails EPSS support

Expiring September 30, 2010:

  • 1198. UAA Test Preview errata: S/PDIF pin "Pin Sense" responses cannot use "Impedance" bits

  • 1279. Reinstall with IO doesn't consider other methods of install/uninstall

(Announcement Date: August 10, 2010)

Touch Test Changes Coming for WLK 1.6

In Windows Logo Kit 1.6, the Windows Touch team is making the following updates to the Windows Touch test:

  • Random test locations: Test patterns have random placement on the screen.

  • Tighter tolerances: Bugs were fixed that better align the tolerances for jitter and offset to the logo requirements.

  • Removal of visual feedback: Visual feedback from the trace will only be available after the completion of the individual tests.

  • Test iterations and consistency: Most logo test items must pass three of three attempts.

  • Power states: Logo test items must be passed in all power states, including post-boot, post-sleep, and post-hibernate.

(Announcement Date: July 27, 2010)

INPUT-0012, "Tablet systems implement buttons using a HID-compliant, mini-port driver and include a dedicated security button," applies to Windows 7

An error in LogoPoint prevented INPUT-0012 from appearing to be applicable to the Windows 7 "Client Device-W7" category. The verbiage within the requirement implies that this requirement applies to all operating systems. The error has been corrected, and now INPUT-0012 appears properly attributed.

(Announcement Date: July 20, 2010)

Video Fidelity Requirements Enforcement Date Extended

In response to partner feedback, the enforcement date of the video fidelity requirements (STREAM-0082, STREAM-0083, STREAM-0084, and STREAM-0085) has been extended to December 1, 2010. The Windows Logo Kit currently optionally enforces these tests, so no changes will be made.

(Announcement Date: July 13, 2010)

Windows Logo Program Requirement and Policy Updates

The Windows Logo Program would like to inform partners of the following requirement and policy updates. You can find complete details in the LogoPoint tool on the Winqual site ( https://winqual.microsoft.com/default.aspx).

New Requirements
The following requirements are new and open for feedback:

  • GRAPHICS-0083. Graphics - Additional Qualifications - Cold Tuning.

  • STREAM-0091. Tuner- Additional Qualifications - Hybrid/Combo Implementation.

  • STREAM-0092. Tuner- Additional Qualifications - Signal Quality and Signal Lock Test Suite.

  • CONNECT-0132. USB 3.0 hubs properly implement the SuperSpeed hub descriptor, standard SuperSpeed Descriptors, and the USB 2.0 ports in USB 3.0 hubs report version 2.1.

  • CONNECT-0133. USB 3.0 hubs map their ports as defined in section 10.1 of the USB 3.0 specification.

  • CONNECT-0134. USB 3.0 Hub should always report the port status bits correctly, as per the USB spec.

  • CONNECT-0135. In the scenario where SuperSpeed termination was disabled and device has been enumerated on 2.0 port, if the software enables the SuperSpeed and then resets the 2.0 port, device should correctly move over.

  • CONNECT-0136. USB 3.0 Hubs should not turn off SuperSpeed termination on downstream ports on over-current and port reset.

  • CONNECT-0137. USB hubs support suspend, and downstream devices should not fall off the bus when the hub resumes from selective suspend.

  • CONNECT-0138. USB Hubs correctly report whether they are bus or self-powered.

  • CONNECT-0139. All USB devices must enumerate and operate on EHCI and xHCI controllers as well as downstream of full speed, a high speed and SuperSpeed USB hubs.

  • CONNECT-0140. Devices should signal attach within 500ms after system resumes. If the hub lost power during system suspend, this interval will be calculated from the time hub has powered on the port.

  • CONNECT-0141. If the upstream SuperSpeed termination is on, devices should always connect on the 3.0 port and never connect on the 2.0 port.

  • CONNECT-0142. USB devices should not disconnect from the upstream port while going to or resuming from selective suspend.

  • SYSFUND-0230. Desktop and All-In One systems with Ethernet devices must implement network presence conform to the Power Management specification on the NDIS Program and Wake on LAN patterns.

  • SYSFUND-0229. Systems with a greater than 2.2 terabyte boot drive must comply with UEFI specification.

  • SYSFUND-0228. Server systems supporting RemoteFX must meet requirements.

  • GRAPHICS-0082. Graphics device intended for use with RemoteFX must meet requirements.

  • DEVFUND-0047. Drivers must support all PnP IRPs.

Retired Requirements
The following requirements will be retired. See the individual requirement details for retirement dates.

  • GRAPHICS-0059

  • NETMEDIA-0039

  • NETMEDIA-0012

  • NETMEDIA-0057

  • NETMEDIA-0075

  • DISPLAY-0113

  • All MODEM requirements

  • NETWORK-0141, 0142, and 0143 (Winsock Direct)

  • NETWORK-0026, 0027, 0029, 0030, 0033, 0130, 0131, 0132 (ISDN)

  • CONNECT-0025, 0026, 0027, 0028, 0029 (IrDA)

  • DISPLAY-0103, 0106, 0107, 0108, 0109, 0110 and SYSFUND-0138 (Sideshow)

  • GRAPHICS-0014

  • GRAPHICS-0068

  • SYSFUND-0211

  • STORAGE-0004

  • STORAGE-0017

  • BUSPORT-0020

  • GRAPHICS-0021

  • DISPLAY-0112

  • SYSFUND-0218

  • DISPLAY-0063

  • DISPLAY-0095

Updated Requirements
The following requirements have been updated:

  • GRAPHICS-0010. Restructure of details.

  • CONNECT-0120. Republished.

  • NETMEDIA-0002. Clarification.

  • NETMEDIA-0008. Added "if-implemented."

  • NETMEDIA-0011. Added "if-implemented."

  • NETMEDIA-0017. Reworded exception.

  • NETMEDIA-0021. Minor edits.

  • NETMEDIA-0022. Clarification.

  • NETMEDIA-0026. Clarification.

  • NETMEDIA-0029. Clarification.

  • NETMEDIA-0032. Clarification.

  • NETMEDIA-0036. Removed "if-implemented," added clarification.

  • NETMEDIA-0037. Clarification, added exception.

  • NETMEDIA-0043. Clarification.

  • NETMEDIA-0047. Removed "if-implemented," clarified exception.

  • NETMEDIA-0049. Clarification.

  • NETMEDIA-0053. Added regional profiles, clarified exceptions.

  • NETMEDIA-0054. Removed "if-implemented."

  • NETMEDIA-0059. Clarification.

  • NETMEDIA-0060. Changed to "if-implemented."

  • NETMEDIA-0061. Clarification.

  • NETMEDIA-0066. Removed "if-implemented," added exception.

  • NETMEDIA-0078. Changed to "if-implemented."

  • PORTABLE-0036. Clarification.

  • NETMEDIA-0001. Clarification.

  • NETMEDIA-0003. Clarification.

  • NETMEDIA-0008. Clarification.

  • NETMEDIA-0018. Exemption clarified.

  • NETMEDIA-0041. Clarification.

  • NETMEDIA-0042. Clarification.

  • NETMEDIA-0048. Clarification.

  • NETMEDIA-0050. Clarification.

  • NETMEDIA-0051. Clarification.

  • NETMEDIA-0062. Clarification.

  • NETMEDIA-0070. Clarification.

  • NETMEDIA-0071. Clarification.

  • NETMEDIA-0072. Clarification.

  • STREAM-0084. Fixed typo.

  • BUSPORT-0041. Changed effective date to June 1, 2012.

  • SYSFUND-0192. Clarified intent on allowing only Windows 7 logo drivers on Windows 7 systems.

  • CONNECT-0123. Clarified meaning of "alternate."

  • NETWORK-0212. Changed effective date to January 1, 2011 for client devices.

  • NETWORK-0227. Changed effective date to January 1, 2011. Added clarification.

  • BUSPORT-0045. Deleted portion of text about CSZ bit.

  • DEVFUND-0039. Fixed typo.

  • DEVFUND-0048. Clarification.

  • STORAGE-0026. Clarification.

  • CONNECT-0034. Deleted section 5.

  • BUSPORT-0042. Changed effective date to June 1, 2012.

  • DISPLAY-0069. Restructured for clarity.

  • GRAPHICS-0007. Restructured for clarity.

  • GRAPHICS-0015. Updated title and added details.

  • GRAPHICS-0031. Restructured for clarity.

  • GRAPHICS-0036. Restructured for clarity.

  • GRAPHICS-0071. Restructured for clarity.

  • DISPLAY-0105. Added detail to design notes section.

  • GRAPHICS-0074. Added detail to the WDDM driver checklist.

  • GRAPHICS-0075. Added second paragraph.

  • STORAGE-0001. Changed end of life for Medium Changer and Tape programs to June 1, 2010.

  • STORAGE-0003. Clarifications, changed end of life for Medium Changer and Tape programs to June 1, 2010.

  • STORAGE-0024. Updated note, superseded STORAGE-0017.

  • STORAGE-0006. Clarification.

  • STORAGE-0007. Clarification.

  • BUSPORT-0019. Combined with BUSPORT-0020.

  • DISPLAY-0111. Does not apply to network projectors. Text clarification.

  • GRAPHICS-0016. Updated minimum color depth to 32 bpp.

  • STREAM-0082, 0083, 0084, 0085. Changed enforcement date to December 1, 2010.

  • INPUT-0067. Deleted references to Terminal Services.

  • SYSFUND-0009. Same change as GRAPHICS-0016.

  • SYSFUND-0185. Updated for Windows Home Server V2.

  • GRAPHICS-0023. Restructured for clarity.

(Announcement Date: July 13, 2010)

Information on Windows Logo Kit 1.6

The Windows Logo Kit (WLK) 1.6 will ship in alignment with the release of Windows 7 Service Pack 1 (SP1). This release will enable new logo programs and enforce requirements with effective dates of December 2010. As part of this release, the Driver Test Manager (DTM) Controller will be installed on the Windows Server 2008 R2 operating system (64-bit) rather than Windows Server 2003 SP2. New and retiring logo programs will be announced in an upcoming newsletter.

(Announcement Date: July 6, 2010)

New Logo Program Category: Filter Drivers

The Windows Logo Program team would like inform our partners about a new logo category for filter drivers. The filter driver category is new in Windows Logo Kit (WLK) 1.6, and it is designed specifically for filter drivers operating in the Windows kernel. Common classes of these drivers are anti-virus filters. The filter category is comprised of the following requirements:

  • FILTER-001: A File System Filter Driver must be a Mini-Filter driver using the File Systems Filter Manager.

  • FILTER-002: A Network Filter Driver must make use of the Network Windows Filtering Platform (WFP).

  • FILTER-003: Kernel Mode Filter Drivers are architected to maximize reliability and functionality of Windows as well as interact accurately with the core components of the operating system.

These requirements are intended to help improve the quality of filter drivers by enforcing adherence to Windows recommended models, and detecting common driver bugs that may degrade the functionality, reliability, or performance of Windows.

Note that while the filter driver category is designed for those operating in the Windows kernel, it is not limited to drivers that support hardware or those that run kernel. For more information on these requirements, see LogoPoint, which can be accessed through your Winqual account at: https://winqual.microsoft.com/.

(Announcement Date: July 6, 2010)

DISPLAY-0113 Retired Immediately

DISPLAY-0113, "Network Enabled Projectors display basic connection information on the startup splash screen when no input signal is detected," has been retired in response to partner feedback. This requirement inadvertently restricted projectors failing to support two simultaneous input modes; however, it is acceptable for users to select the network mode before network projection is expected to function. There are no tests in Windows Logo Kit (WLK) for this requirement, so there will be no changes to testing.

(Announcement Date: July 6, 2010)

Errata Expiring Before November 1, 2010

Expiring July 13, 2010:

  • 30: PCIHCT: ASPM Capability Support test runs unconditionally on instead of as "Role-Based Error Reporting Capability"

  • 31: PCI Compliance test fails Advanced Error Reporting portion of the test with Assertion FB88100C-4655-42AF-87A4-857EDE0DE6D3

  • 33: PCI Compliance fails Cardbus Controllers on Assertion 6785AA02-FC90-444C-931D-9D4B120A0ED6

  • 35: PCI Hardware Compliance Test fails Device Capabilities register that do not always return

  • 36: PCI Hardware Compliance Test fails Device Capabilities register on Assertion 7788AEB9-8CFF-44D0-AA4F-898E05D9AE2A: FAILED

  • 38: PCI Compliance fails TYP2_IoBaseUpperHalf (68C54D92-6B38-4063-9B51-F5A4B9558147)

  • 61: PCI Compliance: TYP2_IoLimitUpperHalf (B6B64850-679D-4767-A17A-70DACA832CAD

  • 69: PCI Compliance: PWRM_PmData_DataSelect (5A75C8B5-3EBB-4836-8AF2-84A049AF808D)

  • 70: PCI Compliance: TYP1_PrimaryDiscardTimer (E06D175E-E56E-489A-96E2-02CA507EFDB9

  • 193: PCI Compliance test fails with advisory non-fatal mask error on PCIe 1.1 devices [52942EDA-0F18-46ED-82BD-91D6AA8BDDBC

  • 204: PCI Compliance test fails Assertion: 9CB9EE90-AF3F-40EC-8278-733F6DA9F Bit 5 in the Uncorrectable Error Severity register in the AERC table must be read-only and always return 1

  • 215: PCI Compliance test fails PCI-X devices that do not have MSI or MSI-X capability

  • 220: PCI Compliance - Test Header Log register of the Advanced Error Reporting Capability table must be read-only

  • 327: PCI Compliance - Endpoint Acceptable Latencies tested according to PCIe 1.1 and not 1.0a

  • 344: PCI Compliance - Interrupt Line register of the Header table must be read-writable

  • 351: PCI Compliance - Bit 17 (Receiver Overflow Error Severity) in the Uncorrectable Error Severity register (offset Ch) in the Advanced Error Reporting Capability table must be read-only and always return 1

  • 352: PCI Compliance - Bit 2 (Reserved_1) in the Link Control register (offset 10h) in the PCI Express Capability table must be read-only and always return 0

  • 354: PCI Compliance - Bit 20 (Data Link Layer Link Active Reporting Capable) in the Link Capabilities register (offset Ch) in the PCI Express Capability table must be read-only.

  • 355: PCI Compliance Message Upper Address register of the MSI Capability table must be read-writable for 64 bit address capable devices

  • 356: PCI Compliance - Bit range 11:10 (ASPM Support)in the Link Capabilities register (offset Ch) in the PCI Express Capability table must be read-only

  • 385: PCI Compliance - Header Log (1st DW) register of the Advanced Error Reporting Capability table must be read-only. Assertion: 6D047608-9AB2-4A28-AD3F-C60DFA7F4AD0

  • 395: PCI Compliance - Class Code register of the Header table must be read-only.

  • 396: PCI Compliance - Min_Gnt register of the Header table must be read-only and always return 0.

  • 403: PCI Compliance - Bit 0 (Correctable Error Detected) in the Device Status register (offset Ah) in the PCI Express Capability table must be clearable when it is set . Assertion B76FABD4-1C61-46FF-B6D9-155FCBB551EA

  • 430: PCI Compliance - Fails Assertion FBABE47C-6E20-4F1B-B7A1-6F073D77F8B2

  • 431: PCI Compliance - Fails Assertion D4D19854-F0B7-4952-835A-1270434648EC

  • 433: PCI Compliance - Fails Assertion 3AFC2E6D-326C-4A96-AC6B-987D4F809233

  • 452: PCI Compliance - Bit 0 (Correctable Error Detected) in the Device Status register (offset Ah) in the PCI Express Capability table must not change value on write of 0

  • 472: PCI Compliance - New table Virtual Channel Arbitration Table overlaps existing table Virtual Channel Capability (ID2)

  • 488: PCI Compliance - Bit 15 (PME_Status) in the Power Management Control/Status register (offset 4h) in the Power Management Capability table must default to 0 if PME# from D3 cold is not supported.

  • 490: PCI Compliance - Bit range 9:4 (Negotiated Link Width)in the Link Status register (offset 12h) in the PCI Express Capability table is 0h.Assertion CF68482E-9EEF-45B4-A8B8-1379AB6CF94A

  • 497: PCI Compliance - Bit range 1:0 (Reserved)in the Message Address register (offset 4h) in the MSI Capability table must be read-only and always return 0. Assertion A99A9B93-292B-457B-8CB6-0855447A8DF3

  • 520: PCI Compliance Capabilities Pointer register of the Header table must be read-only

  • 521: PCI Compliance Capabilities Pointer register of the Header table cannot have a value of 0h if the Status register indicates otherwise

  • 523: PCI Compliance Enhanced Capability Header Register of the Virtual Channel capability (ID2)

  • 524: PCI Compliance Bit range 31:28 (Reserved_2)in the Device Capabilities register (offset 4h) in the PCI Express Capability table must be read-only

  • 532: PCI Compliance - Bit range 25:18 (Captured Slot Power Limit Value)in the Device Capabilities register (offset 4h) in the PCI Express Capability table must be read-only and always return 0.

  • 538: PCI Compliance - New table Port Arbitration Table #0 overlaps existing table Virtual Channel Capability (ID2)

  • 576: PCI Compliance - A PCI-X device that generates interrupts must have an MSI or MSI-X capability. Assertion 24078F7D-D376-4557-9A43-4E4DC3AA3E63

  • 589: PCI Compliance - Bit range 19:16 (Capability Version)in the Enhanced Capability Header register (offset 0h) in the XYZ Capability table must be read-only

  • 590: PCI Compliance - Interrupt Pin register of the Header table must be read-only. Assertion 28AAA17F-22EB-4CB5-BD9F-28FDCE48088D

  • 605: PCI Compliance - Trying to write a value=0x** that can't fit in bit range=Port Arbitration Select (bit count=3)

  • 658: Bit 8 (Slot Implemented) in the PCI Express Capabilities register (offset 2h) in the PCI Express Capability table must be read-only

  • 659: Bit 6 (Presence Detect State) in the Slot Status register (offset 1Ah) in the PCI Express Capability table must be read-only and always return 1 for switch downstream ports and root ports which do not implement a slot

  • 680: PCI Compliance - Bit 0 (Load VC Arbitration Table) in the Port VC Control register (offset Ch) in the Virtual Channel Capability (ID2) table must be read-only and always return 0 even though it is technically read-write.

  • 681: PCI Compliance - Bit 16 (Load Port Arbitration Table) in the VC Resource Control #0 register (offset 14h) in the Virtual Channel Capability (ID2) table must be read-only and always return 0 for switch ports, root ports and RCRB, even though it is technically read-write.

  • 729: PCI Compliance - Unexpected Header Type = 255

  • 739: PCI Compliance - Bit range 14:12 (Max_Read_Request_Size)in the Device Control register (offset 8h) in the PCI Express Capability table must be read-writable if implemented.

  • 755: PCI Compliance Bit range 6:10 of the Slot Control register of the PCI Express capability is not correctly tested

  • 832: PCI Compliance - Operating mode bits of the class code register are not being tested properly

  • 833: PCI Compliance - Error Reporting Capable bits 4:0 of the Device Control Register in the PCI Express capability aren't tested correctly

  • 875: PCI Compliance - Slot Power Limit Value and Slot Power Limit Scale fields of the Slot Capabilities register shouldn't be tested

  • 934: PCI Compliance - Bit range 3:0 (Capability Version)in the PCI Express Capabilities register (offset 2h) in the PCI Express Capability table must be read-only . (Assertion B8334971-DD44-42C4-9DCB-0F58E512D0DF)

  • 960: PCI Compliance - Uncorrectable Error Mask and Severity Registers of the AERC are not being tested correctly. 3CDD17AF_FF8BC1A1_461CA4DE

  • 1167: PCIHCT - Bit range 23:21 (Reserved)in the Link Capabilities register (offset Ch) in the PCI Express Capability table must be read-only and always return 0

  • 1168: PCIHCT - Bit range 15:9 (Reserved_2)in the Link Control register (offset 10h) in the PCI Express Capability table must be read-only and always return 0

  • 1169: PCIHCT - Bit 11 (Electromechanical Interlock Control) in the Slot Control register (offset 18h) in the PCI Express Capability table must be read-writable . (Assertion 4976C48A-EAAE-4171-A890-16C1E5810B2D)

  • 1171: PCIHCT - Bit range 15:14 (Reserved)in the Link Status register (offset 12h) in the PCI Express Capability table must be read-only and always return 0 . (Assertion 2DF29F4E-C365-4B8D-9A72-0726AD8F53A6)

  • 1180: PCI Compliance - Data Link Layer Link Active bit is set but Link Active Reporting Capable is not. Assertion DC62767C-23C3-4668-9745-535E7B351382

  • 1221: PCI Compliance incorrectly tests the PCIe to Cardbus bridges. (Assertion 74266472-F9F0-4021-A418-A0DBB694336B

  • 1222: PCI Compliance - Bit 5 (VGA Palette Snoop) in the Command register (offset 4h) in the Header table must be read-only and always return 0 . It was found to be read-writeable. (Assertion CF73318D-AB13-4367-A15A-ABDCEB29E116)

  • 1223: PCI Compliance - Bit range 15:0 (Extended Capability ID)in the Enhanced Capability Header register (offset 0h) in the XYZ table must be read-only. (Assertion CBC6377A-5F74-44C6-9A32-053459F2112D0)

  • 1279: Reinstall with IO doesn't consider other methods of install/uninstall

  • 1594: ERRATA: USB: USB Host Controller Enable Disable Test: Allow more time for devices to re-enumerate after re-enabling all controllers - 2

  • 1617: USB Controller Power State Test fails due to controller reset on S4 resume

Expiring August 1, 2010:

  • 1806: ERRATA: HAL Timer test fails KeStallExecutionProcessor Backoff Test case due to test problem with processor implementation

  • 1811: ERRATA: USB Descriptor test incorrectly fails when device returns 'STALL' code

Expiring August 31, 2010:

  • 1338: UAA Test: PREVIEW Errata: This test enforces Low Power DCN requirement that D3 Cold support entails EPSS support

Expiring September 30, 2010:

  • 1198: UAA Test Preview errata: S/PDIF pin "Pin Sense" responses cannot use "Impedance" bits

(Announcement Date: July 6, 2010)

Original Equipment Manufacturers Can Continue to Ship Unclassified Biometric Fingerprint Readers

Beginning with the release of Windows Logo Kit version 1.6, the Windows Logo Program will have a category for biometric fingerprint readers. In addition to meeting all device fundamentals and applicable connectivity requirements, these readers will need to meet INPUT-0058, INPUT-0066, INPUT-0067, and INPUT-0069 in order to qualify for a Windows 7 logo.

In order to give the channel time to fill with logo-qualified biometric fingerprint readers, we will delay enforcement of these requirements for systems until December 1, 2012. We will post a clarification on Logopoint in the near future and we will notify you when the clarification has been posted.

(Announcement Date: June 29, 2010)

New Logo License Agreement 2011 Available for Signing on July 1

The new Logo License Agreement (LLA) 2011 will be available for signing on the Windows Quality Online Services (Winqual) website ( https://winqual.microsoft.com/) on July 1, 2010. The new LLA includes the following changes:

  • Smaller minimum size for the Windows 7 logo. Licensees now have the option to use a smaller minimum size (0.42") Windows 7 logo on systems where space on the casing is limited, for example, all-in-one PCs and smaller device form factors.

  • Logo on the back or bottom of mobile devices permitted under limited circumstances. When the smallest logo size permitted under the LLA does not fit in a visible location, we will now allow placement of the Windows logo on the back or bottom of mobile devices, provided that: The logo is comparable in size and placement to third-party logos.The logo is not placed on a removable component of the device.

  • Sublicense rights to logos. Original equipment manufacturers (OEMs) and independent hardware vendors (IHVs) who work with retailers to promote their products and who want retailers to be able to utilize Windows logos in promoting OEM and IHV products need sublicense rights to Windows logos. These rights have been added to LLA 2011.

(Announcement Date: June 22, 2010)

New Billing Service Features Go Live On July 1

The Microsoft Pay It Your Way website ( http://payityourway.com/  This link leaves the Microsoft.com site) is an online account receivable service. This service will go live on July 1, 2010. You can use this service to:

  • View transaction history.

  • Make a payment with a credit card.

  • Change the purchase order (PO) number on your invoice.

  • Edit PO numbers on your unbilled submissions.

Frequently Asked Questions

FAQ 1: How do I get my sign-in information?

Each billing contact associated with your account number will have access to this website. Your username is your email address. To activate your username, click this link https://www.payityourway.com/ForgotPassword.aspx and enter your email address. You will receive an email from webmaster@payityourway.com with your temporary password.

FAQ 2: I've received my invoice but the PO number is wrong. How do I change the PO number on my invoice?

To change the PO number on an invoice:

  1. Sign in to Pay It My Way and click View Transactions.

  2. In the Edit PO column, click the button for the invoice you want to change.

  3. On the Change Purchase Order Number screen, enter your new PO number.

  4. If you do not want to have a hard copy sent to you via the United States Postal Service (USPS), clear the corresponding checkbox.

  5. Click Proceed. A revised invoice will be emailed to you automatically.

Changing PO Numbers on Unbilled Submissions

Billing is done quarterly. At the end of each calendar quarter, submissions to be billed are loaded into the billing system. Invoices for the quarter are produced on the 16th day of the month following the end of the quarter ("billing month").

For example, on March 31, submissions from January 1 through March 31 are loaded into PayItYourWay.com. Edits to the PO numbers for the submissions are allowed during the first two weeks of April. On April 16, invoices are generated and no further edits are possible. Invoices are sent to you within five business days from the 16th. Payment on the invoices will be due on the 25th day of the month following the billing month. This due date provides you at least 30 days from the date you receive your invoice.

During the time that you are able to edit PO numbers on your submissions, there will be a button labeled Edit Pre-Bill PO Numbers on the Welcome page. This button is only available from the 1st through the 15th of the billing month. When you click this button, you will be presented with a screen that will allow you to make changes to the PO numbers on each of your submissions. The screen is self-explanatory but feel free to email us at whqlbill@microsoft.com with any questions.

In summary, the following steps are involved:

  1. Unbilled submissions are loaded into PayItYourWay.com on the last day of the calendar quarter.

  2. Email notices are sent to all billing contacts notifying them that they can edit submission PO numbers.

  3. Users can sign in to PayItYourWay.com and edit their PO numbers.

  4. On the 16th day of the billing month, invoices are generated. No further edits to submission PO numbers can be made after the close of business on the 15th.

  5. Invoices are prepared and mailed via USPS.

  6. Payment on invoices is due on the 25th day of the month following the billing month.

VERY IMPORTANT INFORMATION ******* PLEASE READ THIS SECTION

When we generate invoices, the submissions are grouped by account number and PO number. We generate a separate invoice for each unique combination of account number and PO number. For example, if you have one account number and two submissions and both submissions have the same PO number, you will receive one invoice with both submissions on it. If each submission has a different PO number, you will receive two invoices. If you have more than one account, you will receive at least one invoice for each account and possibly more than one invoice per account if the submissions for a given account have different PO numbers.

If one of your engineers made a submission under the wrong account, you will have 15 days to discover this and notify us. If you need an invoice split across two or more PO numbers, you will have 15 days to make the necessary adjustments. After invoices are generated, there is only one change that will be made to your invoice and that will be to change the PO number on the invoice (see FAQ 2 above). The billing team will NO LONGER MAKE INVOICE CHANGES. Your company has 15 days to identify and make the necessary adjustments to your submissions to ensure they are billed properly. Please take this notice of policy seriously as we will not honor requests to make changes to invoices.

(Announcement Date: June 22, 2010)

Retiring Windows Logo Program Categories

The following logo program categories and requirements will be retired when we release version 1.6 of the Windows Logo Kit (WLK):

  • Modem MODEM-0001 through MODEM-0025

  • Winsock Direct NETWORK-0141 through NETWORK-0143

  • ISDN NETWORK-0026NETWORK-0027NETWORK-0029NETWORK-0030NETWORK-0033NETWORK-0130 through NETWORK-0132

  • IrDA CONNECT-0025CONNECT-0027CONNECT-0029

Starting with WLK 1.6, any devices that previously submitted via these categories can use the Unclassified category to get a signature. Please use LogoPoint to send us any feedback you have about this announcement.

(Announcement Date: June 22, 2010)

Retirement Date Postponed for Tape Drive, Medium Changer, and Serial Port Adapters Categories

Previously we announced that we would retire the Tape Drive, Medium Changer, and Serial Port Adapters logo program categories in June 2010. We are postponing the retirement of these categories until Windows Logo Kit (WLK) 1.5 expires.

(Announcement Date: June 22, 2010)

Windows Logo Kit 1.5 QFE 002 Is Now Available on Connect

QFE 002 for Windows Logo Kit (WLK) 1.5 is now available for download on the WLK Connect site ( https://connect.microsoft.com/site/sitehome.aspx?SiteID=668). This QFE contains a fix to select Direct3D tests to significantly reduce log file sizes. (The affected tests are WGF11Shader5x.exe, WGF11Compute.exe, and WGFFilter.exe.) This change should make it significantly easier to comply with the 2-GB size limit for CAB files in logo program submission packages.

This QFE also includes:

  • Fix to the ConfigDisplay.exe utility so that it correctly enables secondary heads.

  • Fixes for the following errata: 1531: Display: WGF11 Compute Shader (FeatureLevel 10.0 and 10.1) has blocked test case1575: Display: WGF11 Compute Shader (Feature Level 10.0) has blocked test group when DX-compute is disabled. (dupe of 1531)1577: Display: The WGF11 Filter (Feature Level ??) fail test group filter\Aniso\2D (dupe to 1672)1578: Display: The WGF11 Filter (Feature Level 10.0, 10.1 and 11.0) test has several failures due to LOD Clamp1672: Display: WGF11 Filter (FeatureLevel 10.0, 10.1, and 11.0) test enforces LengthMinor clamping1842: Display: WGF11 Compute Shader (FeatureLevel 10.0 and 10.1) placeholder failure after the blocked test1959: Display:WGF11 Compute Shader (Feature Level 10.0, 10.1 and11.0) test has failures in Memory\Barrier\PS test cases

This QFE is required for Display tests for all operating systems. Even if you aren't affected by the 2-GB CAB limit, this QFE is required in order to to ensure that secondary heads are properly enabled. The reduction in log file size will also make it much easier to triage failures in these tests.

Note: Before applying the QFE, close all active DTM Studio sessions. Applying this QFE may affect any in-progress submission; please complete any submissions before applying the QFE. After installing this QFE, you will need to regenerate any affected submission that was generated before the QFE was installed.

(Announcement Date: June 22, 2010)

Windows Logo Kit 1.5 QFE 004 Is Now Available on Connect

Windows Logo Kit (WLK) 1.5 QFE 004 is now available on the WLK Connect site ( https://connect.microsoft.com/site/sitehome.aspx?SiteID=668). This fix mitigates issues with running the Rally PnP-X or Bluewire Vertical Pairing logo program tests, which report Function Discovery failures and often leave the test computer in a non-clean state.

This QFE is required for Rally PnP-X or Bluewire Vertical Pairing tests.

(Announcement Date: June 22, 2010)

Windows Summit 2010 Virtual Event: Device Track To Be Extended on June 30!

Windows Summit 2010 is a virtual event for software and hardware developers, designers, engineers, and testers, who build or want to build hardware and software solutions on the Windows 7 and Internet Explorer platforms.

On June 30 the Device track will be extended with a new set of Windows Summit 2010 sessions and virtual workshops. The workshops will focus on Device Stage for all types of devices, and will cover a new tool that simplifies implementation of Device Stage for your products. Session topics include:

  • Windows Connect Now

  • Uploading Device Metadata Packages

  • Play To

  • Windows Logo Program

Device, System, and Software Tracks

Specialized content for the Device, System, and Software tracks is now available online. You can access tools, resources, and information about building great products on Windows 7 and Internet Explorer, from the convenience of your computer, including information that addresses the Windows Logo Program - from what you need to know to certify your product to what's new in Windows Logo Kit (WLK) 1.5.

Here's a sampling of the sessions now available:

  • Device track, led by Mark Relph, Senior Director, Windows Developer and PC Ecosystem Team: The Windows Logo Program for Hardware and Devices: Getting StartedThe Windows Logo Kit: What's New in WLK 1.5Windows 7 Device Content and Web ResourcesDeveloping Your Device Experience Strategy

  • System track, led by Brad Brooks, Corporate Vice President, Windows Consumer Marketing and Product Management: Windows 7 Imaging and Deployment Tools OverviewUnderstanding the Windows Logo Program for SystemsBuilding TroubleshootersUsing the Mobile Broadband Platform in Windows 7

  • Software track, led by Dean Hachamovitch, General Manager, Internet Explorer Team: Developing Multi-Touch Applications for Natural ExperiencesUnleashing the Latest Innovations in Modern Graphics Hardware with Windows 7Windows 7 Ribbon: The Next Generation User Experience for Presenting Commands in Windows ApplicationsExtending Battery Life by Creating Energy-Efficient Applications

Track content is available 24x7. You can watch all the sessions or choose the ones that interest you the most. In addition to track content and the opening talks, you can view questions that were submitted to the experts along with the experts' answers.

To see a full list of sessions and to learn more, visit http://www.microsoft.com/windows/windows-summit/default.aspx?ocid=sum10_lognews.

(Announcement Date: June 22, 2010)

New Billing Service Features Go Live On July 1

The Microsoft Pay It Your Way website ( http://payityourway.com/  This link leaves the Microsoft.com site) is an online account receivable service. This service will go live on July 1, 2010. You can use this service to:

  • View transaction history.

  • Make a payment with a credit card.

  • Change the purchase order (PO) number on your invoice.

  • Edit PO numbers on your unbilled submissions.

Frequently Asked Questions

FAQ 1: How do I get my sign-in information?

Each billing contact associated with your account number will have access to this website. Your username is your email address. To activate your username, click this link https://www.payityourway.com/ForgotPassword.aspx and enter your email address. You will receive an email from webmaster@payityourway.com with your temporary password.

FAQ 2: I've received my invoice but the PO number is wrong. How do I change the PO number on my invoice?

To change the PO number on an invoice:

  1. Sign in to Pay It My Way and click View Transactions.

  2. In the Edit PO column, click the button for the invoice you want to change.

  3. On the Change Purchase Order Number screen, enter your new PO number.

  4. If you do not want to have a hard copy sent to you via the United States Postal Service (USPS), clear the corresponding checkbox.

  5. Click Proceed. A revised invoice will be emailed to you automatically.

Changing PO Numbers on Unbilled Submissions

Billing is done quarterly. At the end of each calendar quarter, submissions to be billed are loaded into the billing system. Invoices for the quarter are produced on the 16th day of the month following the end of the quarter ("billing month").

For example, on March 31, submissions from January 1 through March 31 are loaded into PayItYourWay.com. Edits to the PO numbers for the submissions are allowed during the first two weeks of April. On April 16, invoices are generated and no further edits are possible. Invoices are sent to you within five business days from the 16th. Payment on the invoices will be due on the 25th day of the month following the billing month. This due date provides you at least 30 days from the date you receive your invoice.

During the time that you are able to edit PO numbers on your submissions, there will be a button labeled Edit Pre-Bill PO Numbers on the Welcome page. This button is only available from the 1st through the 15th of the billing month. When you click this button, you will be presented with a screen that will allow you to make changes to the PO numbers on each of your submissions. The screen is self-explanatory but feel free to email us at whqlbill@microsoft.com with any questions.

In summary, the following steps are involved:

  1. Unbilled submissions are loaded into PayItYourWay.com on the last day of the calendar quarter.

  2. Email notices are sent to all billing contacts notifying them that they can edit submission PO numbers.

  3. Users can sign in to PayItYourWay.com and edit their PO numbers.

  4. On the 16th day of the billing month, invoices are generated. No further edits to submission PO numbers can be made after the close of business on the 15th.

  5. Invoices are prepared and mailed via USPS.

  6. Payment on invoices is due on the 25th day of the month following the billing month.

VERY IMPORTANT INFORMATION ******* PLEASE READ THIS SECTION

When we generate invoices, the submissions are grouped by account number and PO number. We generate a separate invoice for each unique combination of account number and PO number. For example, if you have one account number and two submissions and both submissions have the same PO number, you will receive one invoice with both submissions on it. If each submission has a different PO number, you will receive two invoices. If you have more than one account, you will receive at least one invoice for each account and possibly more than one invoice per account if the submissions for a given account have different PO numbers.

If one of your engineers made a submission under the wrong account, you will have 15 days to discover this and notify us. If you need an invoice split across two or more PO numbers, you will have 15 days to make the necessary adjustments. After invoices are generated, there is only one change that will be made to your invoice and that will be to change the PO number on the invoice (see FAQ 2 above). The billing team will NO LONGER MAKE INVOICE CHANGES. Your company has 15 days to identify and make the necessary adjustments to your submissions to ensure they are billed properly. Please take this notice of policy seriously as we will not honor requests to make changes to invoices.

(Announcement Date: June 15, 2010)

Retiring Windows Logo Program Categories

The following logo program categories and requirements will be retired when we release version 1.6 of the Windows Logo Kit (WLK):

  • Modem MODEM-0001 through MODEM-0025

  • Winsock Direct NETWORK-0141 through NETWORK-0143

  • ISDN NETWORK-0026NETWORK-0027NETWORK-0029NETWORK-0030NETWORK-0033NETWORK-0130 through NETWORK-0132

  • IrDA CONNECT-0025CONNECT-0027CONNECT-0029

Starting with WLK 1.6, any devices that previously submitted via these categories can use the Unclassified category to get a signature. Please use LogoPoint to send us any feedback you have about this announcement.

(Announcement Date: June 15, 2010)

New FAQs for the Windows 7 Software Logo Program

We would like to announce a new section on the Windows 7 Software Logo Program website. This new section answers some frequently asked questions that Microsoft has received since the start of the Windows 7 Software Logo Program. We have categorized the questions into three sections:

Please send any questions to winqual@microsoft.com.

(Announcement Date: June 15, 2010)

Windows Summit 2010 Virtual Event

Windows Summit 2010 is a virtual event for software and hardware developers, designers, engineers, and testers, who build or want to build hardware and software solutions on the Windows 7 and Internet Explorer (IE) platforms. Specialized content tracks for devices, systems, and software experts have been developed and are being released on a rolling schedule.

Device and System Track Content is Now Available

The Device and System tracks have kicked off and the content is now available online. You can access tools, resources, and information about building great products on Windows 7 and Internet Explorer from the convenience of your computer, including information that addresses the Windows Logo Program - from what you need to know to certify your product to what's new in the Windows Logo Kit (WLK) 1.5. To get started, simply sign in at http://www.microsoft.com/windows/windows-summit/default.aspx?ocid=sum10_lognews.

Software Track Begins June 16

The Software track of Windows Summit 2010 kicks off on June 16 with an opening talk by Dean Hachamovitch, General Manager of the Internet Explorer Team. Dean is responsible for the design, development, and release of Internet Explorer, the Microsoft RSS platform, and future versions of our web browser, as well as security and customer response for the currently supported versions of IE.

Here's a sampling of the sessions for the Software track:

  • Developing Multi-Touch Applications for Natural Experiences

  • Unleashing the Latest Innovations in Modern Graphics Hardware with Windows 7

  • Windows 7 Ribbon: The Next Generation User Experience for Presenting Commands in Windows Applications

  • Extending Battery Life by Creating Energy-Efficient Applications

Related track content goes live after the opening talk and will be available 24x7. You can watch all sessions or choose the ones that most interest you. There is also the opportunity to ask the experts questions and the answers will be posted to the site on a regular basis, viewable by everyone.

To see a full list of sessions and to learn more, visit http://www.microsoft.com/windows/windows-summit/default.aspx?ocid=sum10_lognews.

(Announcement Date: June 15, 2010)

Enforcement Delayed for NETWORK-0212 and NETWORK-0227

The Windows Logo Program team would like inform our partners about some requirement changes. We are delaying enforcement of NETWORK-0212 (Ethernet devices that implement network presence conform to the Power Management specification on the NDIS Program) and NETWORK-0227 (Ethernet devices must implement Wake on LAN patterns according to the specification on connect) until January 1, 2011 or 90 days after Windows Logo Kit (WLK) 1.6 is released, whichever is later. In order to give time for the ecosystem to fill the channel with compliant devices, we will also delay enforcement of these requirements for desktop and all-in-one system submissions until December 1, 2011. We will not require these features for any mobile platforms because Windows 7 does not enable the features by default on mobile platforms.

An errata filter will be in place in the device category until January 1, 2011 or 90 days after WLK 1.6 is released, whichever is later. We will have tests to validate these requirements in the systems kit starting with Windows Logo Kit (WLK) 1.6. There will be a preview filter for the new systems tests until the requirements go into effect on December 1, 2011.

(Announcement Date: June 8, 2010)

Link Layer Topology Discovery Will Not Be Required

CONNECT-0098, which takes effect June 1, 2010, originally would have required that network-enabled devices support Link Layer Topology Discovery (LLTD). In response to partner feedback, we are changing CONNECT-0098 from required to if-implemented. This means that we will not require network-enabled devices to support LLTD, but if a device does implement LLTD, we will require that the implementation conform to the protocol standards.

Imaging partners should note that IMAGING-0048 will require CONNECT-0098 only if the device implements LLTD. IMAGING-0048 will still require CONNECT-0099 and CONNECT-0100.

CONNECT-0098 will also apply to network media devices, network attached storage, and routers, but only if those devices implement LLTD.

(Announcement Date: June 1, 2010)

Preview Errata Currently in Effect

Preview errata are used to mask failures in new tests or sometimes test cases within tests. If a preview erratum is applied to your test run, you should examine the failures in question. Do not assume that these failures are bugs in the test. The failures are most likely problems with the device under test. These problems must be fixed before the preview erratum expires.

Listed below are the preview errata that are currently in effect and their expiration dates.

Preview errata that expire June 1, 2010:

Errata #: Errata Title

  • 1152: TCG TPM Integration test case Quote2Basic is Previewed until 1 June 2010

  • 1245: GlitchFree WMV HD 720p video playback quality test cases 2 & 3 Preview for 6 months post WLK1.4 release

  • 1288: UAA Test: preview filter for Encoded Packet Type validation

  • 1343: WLK DVD Spindown, WLK Optical Drive Streaming Mode, WLK CSS Negotiation Region Check, and WLK Aggressive Optical Drive tests are PREVIEW

  • 1348: UAA Test: PREVIEW Errata: digital converter channel to HDMI slot mapping failures

  • 1766: Preview filter for Input tests - Hot Key test, Scroll test, Winkey test

  • 1776: TPM TCG OS Interface Test - Preview Errata - Test should be preview initially for WLK 1.5

  • 1812: Preview: VWiFiStress is a preview test for WLK 1.5

  • 1851: 1394 Industry Certification Test ID Entry (MANUAL) test is in PREVIEW

  • 1859: KS Position Test: PREVIEW ERRATA: KSJACK_DESCRIPTION (AUDIO-0077) not required until 5/31/10

  • 1876: Preview Errata: Display Devices Verify Digital Connector

  • 1879: RoundTrip test: PREVIEW Errata: KSJACK_DESCRIPTION support is in preview mode

  • 1942: Optical Logo test: PREVIEW Errata: Dual Layer Write profile will not be required on 1 June 2009 for Blu-Ray drives of 9.5 mm height and smaller as well as DVD drives 7mm height and smaller

Preview errata that expire June 30, 2010:

Errata #: Errata Title

  • 1299: UAA Test: PREVIEW Errata: Some digital pin widgets incorrectly set Jack Detect Override

  • 1391: MTP Compliance test has mandatory requirement waived until June 30, 2010

Preview errata that expire August 09, 2010:

Errata #: Errata Title

  • 1608: NDIS: WLAN: Statistics_ext has been modified for WLK 1.5 some failures should be in PREVIEW mode

  • 1609: NDIS: WLAN: SoftAP_WPS_ext is a PREVIEW test

  • 1719: LOGO Wireless router WPS preview test errata WCN Wireless Default Configuration (Router Reset)

  • 1720: Wireless router WPS preview test errata WCN UPnP Configure And Connect to AP with WPA2PSK AES PassPhrase using PIN over Wireless

Preview errata that expire August 31, 2010:

Errata #: Errata Title

  • 1289: UAA Test: PREVIEW filter for HDMI LPCM CAD verb

  • 1338: UAA Test: PREVIEW Errata: This test enforces Low Power DCN requirement that D3 Cold support entails EPSS support

Preview errata that expire September 30, 2010:

Errata #: Errata Title

  • 1198: UAA Test Preview errata: S/PDIF pin "Pin Sense" responses cannot use "Impedance" bits

Preview errata that expire December 1, 2010:

Errata #: Errata Title

  • 125: PCI Compliance test failes when SSID/SSVID registers are writeable

  • 1315: PREVIEW: IO Cancellation with Direct IO: This test is preview in WLK 1.4 & 1.5

  • 1786: USB Host Controller Tramsfer Speed Test - PREVIEW 1789 USB DRIVER RE-ENUMERATION TEST - PREVIEW

  • 1796: Preview filter for the Storage Trim Test

  • 1818: DVD Spindown test: A condition in this Preview test results in erroneous failures

  • 1963: Sensor tests: PREVIEW Errata: Several Sensor tests new to WLK 1.5 are in preview mode

Preview errata that expire January 31, 2011:

Errata #: Errata Title

  • 1444: WaveTest: PREVIEW Errata: HDMI outputs that don't support 44.1kHz on Windows 7 or under third-party driver

  • 1801: Fidelity false failures in Render Power Transition Test

Preview errata that expire June 1, 2011:

Errata #: Errata Title

  • 1949: Preview: KSPROPERTY_JACK_SINK_INFO needs to be supported

  • 1799: Bluetooth Device Version Check Test- ExecSecondary test is in PREVIEW

  • 1799: Bluetooth Device Version Check Test- ExecPrimary test is in PREVIEW

Preview errata that expire July 1, 2011:

Errata # Errata Title

  • 1466: UAA Test: Preview Filter - Intel Low Power DCN says "EPSS implies KeepAlive, but only after July 1st 2011"

Preview errata that expire December 1, 2011:

Errata #: Errata Title

  • 1797: USB-IF Test Certification ID Check - PREVIEW

Preview errata that expire June 1, 2012:

Errata #: Errata Title

  • 1787: USB Host Controller Compliance - PREVIEW

(Announcement Date: June 1, 2010)

Errata That Will Expire Before October

The following Windows Logo Kit errata will expire before October 1, 2010.

Errata that expire June 30, 2010:

Errata #: Errata Title

  • 1299: UAA Test: PREVIEW Errata: Some digital pin widgets incorrectly set Jack Detect Override

  • 1390: GetObject errata filter

  • 1391: MTP Compliance test has mandatory requirement waived until June 30, 2010

  • 1445: ERRATA: MTP Compliance Test - Relax battery level device property for camera devices

  • 1448: WMDM_Compliance_InitializeStorage

  • 1452: PurchaseFlag is not applicable for abstract audio album

  • 1454: drmprotection property can only be set on DRM content even though it is read-write

  • 1622: The MTP Compliance Test - GetObjectPropList test 18 and 19 may fail due to incorrect method being used.

  • 1651: GetObjectPropList Test5 - verify storage id on devices with multiple storages

  • 1662: MtpComplianceTest_GetObjectPropList_Test 18 And 19 Fail Due To Incorrect Test Method Being Used

  • 1665: MtpComplianceTest_GetObjectPropValue_Tests 8 And 15 Incorrectly Expect The Same Value Returned For Name That Was Sent As FileName

  • 1702: MtpComplianceTest_GetObjectReferences References Are Not Persisted Across Sessions

  • 1703: MtpComplianceTest_NokiaErrata

  • 1705: WmdmCompliance_Re-InitializeStorage

  • 1718: MTP Compliance Test SetObjectPropValue

  • 1734: Wpd Compliance Test: Stress test is not required to pass.

Errata that expire July 13, 2010:

Errata #: Errata Title

  • 30: PCIHCT: ASPM Capability Support test runs unconditionally on instead of as "Role-Based Error Reporting Capability

  • 31: PCI Compliance test fails Advanced Error Reporting portion of the test with Assertion FB88100C-4655-42AF-87A4-857EDE0DE6D3

  • 33: PCI Compliance fails Cardbus Controllers on Assertion 6785AA02-FC90-444C-931D-9D4B120A0ED6

  • 35: PCI Hardware Compliance Test fails Device Capabilities register that do not always return

  • 36: PCI Hardware Compliance Test fails Device Capabilities register on Assertion 7788AEB9-8CFF-44D0-AA4F-898E05D9AE2A: FAILED

  • 38: PCI Compliance fails TYP2_IoBaseUpperHalf (68C54D92-6B38-4063-9B51-F5A4B9558147)

  • 61: PCI Compliance: TYP2_IoLimitUpperHalf (B6B64850-679D-4767-A17A-70DACA832CAD)

  • 69: PCI Compliance: PWRM_PmData_DataSelect (5A75C8B5-3EBB-4836-8AF2-84A049AF808D)

  • 70: PCI Compliance: TYP1_PrimaryDiscardTimer (E06D175E-E56E-489A-96E2-02CA507EFDB9)

  • 193: PCI Compliance test fails with advisory non-fatal mask error on PCIe 1.1 devices [52942EDA-0F18-46ED-82BD-91D6AA8BDDBC]

  • 204: PCI Compliance test fails Assertion: 9CB9EE90-AF3F-40EC-8278-733F6DA9F Bit 5 in the Uncorrectable Error Severity register in the AERC table must be read-only and always return 1

  • 215: PCI Compliance test fails PCI-X devices that do not have MSI or MSI-X capability

  • 220: PCI Compliance - Test Header Log register of the Advanced Error Reporting Capability table must be read-only

  • 327: PCI Compliance - Endpoint Acceptable Latencies tested according to PCIe 1.1 and not 1.0a

  • 344: PCI Compliance - Interrupt Line register of the Header table must be read-writable

  • 351: PCI Compliance - Bit 17 (Receiver Overflow Error Severity) in the Uncorrectable Error Severity register (offset Ch) in the Advanced Error Reporting Capability table must be read-only and always return 1

  • 352: PCI Compliance - Bit 2 (Reserved_1) in the Link Control register (offset 10h) in the PCI Express Capability table must be read-only and always return 0

  • 354: PCI Compliance - Bit 20 (Data Link Layer Link Active Reporting Capable) in the Link Capabilities register (offset Ch) in the PCI Express Capability table must be read-only.

  • 355: PCI Compliance Message Upper Address register of the MSI Capability table must be read-writable for 64 bit address capable devices

  • 356: PCI Compliance - Bit range 11:10 (ASPM Support)in the Link Capabilities register (offset Ch) in the PCI Express Capability table must be read-only

  • 385: PCI Compliance - Header Log (1st DW) register of the Advanced Error Reporting Capability table must be read-only. Assertion: 6D047608-9AB2-4A28-AD3F-C60DFA7F4AD0

  • 395: PCI Compliance - Class Code register of the Header table must be read-only.

  • 396: PCI Compliance - Min_Gnt register of the Header table must be read-only and always return 0.

  • 403: PCI Compliance - Bit 0 (Correctable Error Detected) in the Device Status register (offset Ah) in the PCI Express Capability table must be clearable when it is set. Assertion B76FABD4-1C61-46FF-B6D9-155FCBB551EA

  • 430: PCI Compliance - Fails Assertion FBABE47C-6E20-4F1B-B7A1-6F073D77F8B2

  • 431: PCI Compliance - Fails Assertion D4D19854-F0B7-4952-835A-1270434648EC

  • 433: PCI Compliance - Fails Assertion 3AFC2E6D-326C-4A96-AC6B-987D4F809233

  • 452: PCI Compliance - Bit 0 (Correctable Error Detected) in the Device Status register (offset Ah) in the PCI Express Capability table must not change value on write of 0

  • 472: PCI Compliance - New table Virtual Channel Arbitration Table overlaps existing table Virtual Channel Capability (ID2)

  • 488: PCI Compliance - Bit 15 (PME_Status) in the Power Management Control/Status register (offset 4h) in the Power Management Capability table must default to 0 if PME# from D3 cold is not supported.

  • 490: PCI Compliance - Bit range 9:4 (Negotiated Link Width)in the Link Status register (offset 12h) in the PCI Express Capability table is 0h. Assertion CF68482E-9EEF-45B4-A8B8-1379AB6CF94A

  • 490: Bit range 9:4 (Negotiated Link Width)in the Link Status register (offset 12h) in the PCI Express Capability table is 0h. Assertion CF68482E-9EEF-45B4-A8B8-1379AB6CF94A

  • 497: PCI Compliance - Bit range 1:0 (Reserved)in the Message Address register (offset 4h) in the MSI Capability table must be read-only and always return 0. Assertion A99A9B93-292B-457B-8CB6-0855447A8DF3

  • 520: PCI Compliance Capabilities Pointer register of the Header table must be read-only

  • 521: PCI Compliance Capabilities Pointer register of the Header table cannot have a value of 0h if the Status register indicates otherwise

  • 523: PCI Compliance Enhanced Capability Header Register of the Virtual Channel capability (ID2)

  • 524: PCI Compliance Bit range 31:28 (Reserved_2)in the Device Capabilities register (offset 4h) in the PCI Express Capability table must be read-only

  • 532: PCI Compliance - Bit range 25:18 (Captured Slot Power Limit Value)in the Device Capabilities register (offset 4h) in the PCI Express Capability table must be read-only and always return 0.

  • 538: PCI Compliance - New table Port Arbitration Table #0 overlaps existing table Virtual Channel Capability (ID2)

  • 576: PCI Compliance - A PCI-X device that generates interrupts must have an MSI or MSI-X capability. Assertion 24078F7D-D376-4557-9A43-4E4DC3AA3E63

  • 589: PCI Compliance - Bit range 19:16 (Capability Version)in the Enhanced Capability Header register (offset 0h) in the XYZ Capability table must be read-only

  • 590: PCI Compliance - Interrupt Pin register of the Header table must be read-only. Assertion 28AAA17F-22EB-4CB5-BD9F-28FDCE48088D

  • 605: PCI Compliance - Trying to write a value=0x** that can't fit in bit range=Port Arbitration Select (bit count=3)

  • 658: Bit 8 (Slot Implemented) in the PCI Express Capabilities register (offset 2h) in the PCI Express Capability table must be read-only

  • 659: Bit 6 (Presence Detect State) in the Slot Status register (offset 1Ah) in the PCI Express Capability table must be read-only and always return 1 for switch downstream ports and root ports which do not implement a slot

  • 680: PCI Compliance - Bit 0 (Load VC Arbitration Table) in the Port VC Control register (offset Ch) in the Virtual Channel Capability (ID2) table must be read-only and always return 0 even though it is technically read-write.

  • 681: PCI Compliance - Bit 16 (Load Port Arbitration Table) in the VC Resource Control #0 register (offset 14h) in the Virtual Channel Capability (ID2) table must be read-only and always return 0 for switch ports, root ports and RCRB, even though it is technically read-write.

  • 729: PCI Compliance - Unexpected Header Type = 255

  • 739: PCI Compliance - Bit range 14:12 (Max_Read_Request_Size)in the Device Control register (offset 8h) in the PCI Express Capability table must be read-writable if implemented.

  • 755: PCI Compliance Bit range 6:10 of the Slot Control register of the PCI Express capability is not correctly tested

  • 832: PCI Compliance - Operating mode bits of the class code register are not being tested properly

  • 833: PCI Compliance - Error Reporting Capable bits 4:0 of the Device Control Register in the PCI Express capability aren't tested correctly

  • 875: PCI Compliance - Slot Power Limit Value and Slot Power Limit Scale fields of the Slot Capabilities register shouldn't be tested

  • 934: PCI Compliance - Bit range 3:0 (Capability Version)in the PCI Express Capabilities register (offset 2h) in the PCI Express Capability table must be read-only . (Assertion B8334971-DD44-42C4-9DCB-0F58E512D0DF)

  • 960: PCI Compliance - Uncorrectable Error Mask and Severity Registers of the AERC are not being tested correctly. 3CDD17AF_FF8BC1A1_461CA4DE

  • 1167: PCIHCT - Bit range 23:21 (Reserved)in the Link Capabilities register (offset Ch) in the PCI Express Capability table must be read-only and always return 0

  • 1168: PCIHCT - Bit range 15:9 (Reserved_2)in the Link Control register (offset 10h) in the PCI Express Capability table must be read-only and always return 0

  • 1169: PCIHCT - Bit 11 (Electromechanical Interlock Control) in the Slot Control register (offset 18h) in the PCI Express Capability table must be read-writable . (Assertion 4976C48A-EAAE-4171-A890-16C1E5810B2D)

  • 1171: PCIHCT - Bit range 15:14 (Reserved)in the Link Status register (offset 12h) in the PCI Express Capability table must be read-only and always return 0 . (Assertion 2DF29F4E-C365-4B8D-9A72-0726AD8F53A6)

  • 1180: PCI Compliance - Data Link Layer Link Active bit is set but Link Active Reporting Capable is not. Assertion DC62767C-23C3-4668-9745-535E7B351382

  • 1221: PCI Compliance incorrectly tests the PCIe to Cardbus bridges. (Assertion 74266472-F9F0-4021-A418-A0DBB694336B)

  • 1222: PCI Compliance - Bit 5 (VGA Palette Snoop) in the Command register (offset 4h) in the Header table must be read-only and always return 0 . It was found to be read-writeable. (Assertion CF73318D-AB13-4367-A15A-ABDCEB29E116)

  • 1223: PCI Compliance - Bit range 15:0 (Extended Capability ID)in the Enhanced Capability Header register (offset 0h) in the XYZ table must be read-only. (Assertion CBC6377A-5F74-44C6-9A32-053459F2112D0)

  • 1594: ERRATA: USB: USB Host Controller Enable Disable Test: Allow more time for devices to re-enumerate after re-enabling all controllers - 2

  • 1617: USB Controller Power State Test fails due to controller reset on S4 resume

Errata that expire August 1, 2010:

Errata #: Errata Title

  • 1351: UAA Test false-fails codecs in D3 Cold that don't respond to both halves of double-function-group reset

  • 1806: ERRATA: HAL Timer test fails KeStallExecutionProcessor Backoff Test case due to test problem with processor implementation

  • 1811: ERRATA: USB Descriptor test incorrectly fails when device returns 'STALL' code

Errata that expire August 9, 2010:

Errata #: Errata Title

  • 192: PCI Compliance - Test does not correctly ID Hot-Pluggable capability - Serial Number not required [60BDF3F8-01D2-4B58-8A14-04DA4C1B694A]

  • 235: PCI Compliance Test does not correctly ID Hot-Pluggable capability - Serial Number not required [60BDF3F8-01D2-4B58-8A14-04DA4C1B694A]

  • 338: Bit 10 (Interrupt Disable) in the Command register (offset 4h) in the Header table must be read-writable if the device supports an interrupt

  • 339: Bit 8 (Extended Tag Field Enable) in the Device Control register (offset 8h) in the PCI Express Capability table must be read-writable if Extended Tag Field Support is indicated

  • 340: PCI Compliance - Bit 5 (Retrain Link) in the Link Control register (offset 10h) in the PCI Express Capability table must always return 0 on reads even though it is read-write.

  • 343: Bit range 15:8 (Bus Number) in the PCI-X Bridge Status register (offset 4h) in the PCI-X Capability table must be read-only

  • 347: PCI Compliance Header Type 1 Registers failure

  • 348: PCI Compliance Architecture Power Management Capability failure

  • 350: PCI Compliance Bit 3 (Read Completion Boundary) in the Link Control register (offset 10h) in the PCI Express Capability table must be read-only and always return 0 for switch ports

  • 365: PCI Compliance - SSVID register of the Subsystem ID and Subsystem Vendor ID Capability table must not change value after power state transitions.

  • 387: PCI Compliance - ATI/AMD graphics devices cause a system hang when being tested for power management capabilities.

  • 421: PCI Compliance - Function Level Reset initiated by out of specification bit functionality causes assertions to fail

  • 463: PCI Compliance - Capability ID register of the Unrecognized Capability ID 19 table is 13h. It must be in the range [0x1 - 0x12]. Assertion C58DF5F1-A565-491A-A776-B804DD494B55

  • 566: PCI Compliance - Bit range 1:0 (PowerState)in the Power Management Control/Status register (offset 4h) in the Power Management Capability table is 0h

  • 955: Optical Logo test fails Inquiry, Modesense, and Drive serial number test cases on SATA optical drives

  • 1087: Composite devices are not properly identified by the Tuner USB Serial Number Test (STREAM-0017)

  • 1104: PCIHCT - Bit range 10:9 (DEVSEL# Timing)in the Secondary Status register (offset 1Eh) in the Header table doesn't always return 1 as expected.

  • 1147: PCI Compliance - Capabilites pointer register is ovewritten by the test when it is RW and not RO. (Assertion 44D27133-2DA6-4B15-BF03-476FD1BFE0F0)

  • 1299: UAA Test: Some digital pin widgets incorrectly set Jack Detect Override

  • 1337: ERRATA: Optical test "command perfomance check" cannot be passed by most partners and is blocking logo

  • 1528: ERRATA: WHEA: The ERST vallidation test fails due to a valid NOOP instruction that has no physical address

  • 1608: NDIS: WLAN: Statistics_ext has been modified for WLK 1.5 some failures should be in PREVIEW mode

  • 1609: NDIS: WLAN: SoftAP_WPS_ext is a PREVIEW test

  • 1719: LOGO Wireless router WPS preview test errata WCN Wireless Default Configuration (Router Reset)

  • 1720: Wireless router preview test errata WCN UPnP Configure And Connect to AP with WPA2PSK AES PassPhrase using PIN over Wireless

  • 1727: WHEA HCT Logo: Incorrect instruction check while validating WHEA ERST ACPI Table

  • 1751: NDIS: WLAN: AdhocInterop_ext - Client fails to connect to IBSS due to multiple IBSS

  • 1754: NDIS: WWAN: CDMA Provider failure, ProviderId must be 0 or 5 digits in length for CDMA

  • 1755: NDS: WWAN: CDMA signal test failure.

  • 1759: NDIS: WLAN: Scan failure when joining an IBSS in AdhocInterop_ext

  • 1761: NDIS WLAN: Softap_WPS_Ext test has issues around capture packets and setting PHY

  • 1762: NDIS WLAN: vwifiinfrasoftap_ext - DUT-AP sent unsecure traffic when it is supposed to send only secure traffic

  • 1763: NDIS: WLAN: Statistics_ext test has issues on validating broadcast counters - ReceivededFrameCount

  • 1763: NDIS: WLAN: Statistics_ext test has issues on validating broadcast counters - ullTransmittedFrameCount

  • 1763: NDIS: WLAN: Statistics_ext test has issues on validating broadcast counters - ullWEPExcludedCount

  • 1763: NDIS: WLAN: Statistics_ext test fails with DUT failed to receive expected number of packets. Acutal=0, Expected=45 error

  • 1763: NDIS: WLAN: Statistics_ext ullReceivedFrameCount test fails with DUT failed to receive expected number of packets. Acutal=0, Expected=45 error

  • 1763: NDIS: WLAN: Statistics_ext MacMcastCounters DecryptSuccessCount test fails with ullReceivedFrameCount field in DOT11_STATISTICS/MacMcastCounters after data transmission completes is incorrect. Actual=0, Expected=50

  • 1907: Optical Logo test fails AudioMediaDAO with Failed to do raw reading on audio tracks Error

Errata that expire August 31, 2010:

Errata #: Errata Title

  • 1289: UAA Test: PREVIEW filter for HDMI LPCM CAD verb

  • 1338: UAA Test: PREVIEW Errata: This test enforces Low Power DCN requirement that D3 Cold support entails EPSS support

Errata that expire September 30, 2010:

Errata #: Errata Title

  • 1198: UAA Test Preview errata: S/PDIF pin "Pin Sense" responses cannot use "Impedance" bits

  • 1620: Device Capabilities - ObjectProperties-Audio - Support for AlbumArtist is not required for audio files

(Announcement Date: June 1, 2010)

Windows Summit 2010 Begins Today!

Windows Summit 2010 is for software and hardware developers, designers, engineers, and testers, who build or want to build hardware and software solutions on the Windows 7 and Internet Explorer platforms. From the convenience of your computer, this virtual event gives you access to content, tools, resources, and information about building great products on Windows 7 and Internet Explorer (IE), including information about the Windows Logo Program - from how to certify your product to what's new in Windows Logo Kit (WLK) 1.5.

Opening Talks

The Windows Summit 2010 virtual event begins today with an opening talk by Michael Angiulo, General Manager of Windows Planning and PC Ecosystem Teams. Michael is responsible for the product planning input that drives the Windows vision process as well as various partner engagement programs such as WinHEC.

Following Michael Angiulo's opening talk, Mark Relph, Senior Director of the Windows Developer and PC Ecosystem Team, leads off the Device track. Mark is responsible for building a rich ecosystem of hardware and software partners for Windows. This includes supporting world-class compatibility and showcasing the innovations from the ecosystem of Windows partners.

The System track begins June 2 and features Brad Brooks, Corporate Vice President for Windows Consumer Marketing and Product Management. Brad leads the consumer business for Windows client and oversees efforts to connect with consumers. In Brad's prior role as general manager of product marketing for the Windows Business Group, he led the global consumer and business marketing efforts.

Dean Hachamovitch, General Manager of the Internet Explorer Team, starts the Software track on June 16. Dean is responsible for the design, development, and release of Internet Explorer, the Microsoft RSS platform, and future versions of our web browser, as well as security and customer response for the currently supported versions of IE.

Specialized Content Tracks for Devices, Systems, and Software Experts

Content will be available 24x7, released on a rolling schedule so you can select the tracks you want to watch. You will have the opportunity to ask questions and the experts' answers will be posted to the site on a regular basis, viewable by everyone.

Each track launches with a high-profile opening speaker. Related track content goes live after the opening talk. Below you can find the speakers and a sampling of sessions by track or visit the website (http://www.microsoft.com/windows/windows-summit/default.aspx?ocid=sum10_lognews) for the complete schedule:

  • May 25 - Device track, led by Mark Relph, Senior Director, Windows Developer and PC Ecosystem Team: The Windows Logo Program for Hardware and Devices: Getting StartedThe Windows Logo Kit: What's New in WLK 1.5Windows 7 Device Content and Web ResourcesDeveloping Your Device Experience Strategy

  • June 2 - System track, led by Brad Brooks, Corporate Vice President, Windows Consumer Marketing and Product Management: Windows 7 Imaging and Deployment Tools OverviewUnderstanding the Windows Logo Program for SystemsBuilding TroubleshootersUsing the Mobile Broadband Platform in Windows 7

  • June 16 - Software track, led by Dean Hachamovitch, General Manager, Internet Explorer Team: Developing Multi-Touch Applications for Natural ExperiencesUnleashing the Latest Innovations in Modern Graphics Hardware with Windows 7Windows 7 Scenic Ribbon: The Next Generation User Experience for Presenting Commands in Windows ApplicationsExtending Battery Life by Creating Energy-Efficient Applications

To see a full list of sessions and to learn more, visit: http://www.microsoft.com/windows/windows-summit/default.aspx?ocid=sum10_lognews.

Register Now for Windows Summit 2010!

Let us help you succeed with Windows 7 and Internet Explorer. Register now: http://www.microsoft.com/windows/windows-summit/default.aspx?ocid=sum10_lognews.

(Announcement Date: May 25, 2010)

Windows Logo Kit 1.5 QFE 001 Is Now Available on Connect

QFE 001 for Windows Logo Kit (WLK) 1.5 is now available for download on the WLK Connect site ( https://connect.microsoft.com/site/sitehome.aspx?SiteID=668). WLK 1.5 QFE 001 updates USB device fundamentals tests to run USB 3 devices and also updates the USB Controller Power State test.

A number of USB device fundamentals tests are failing on USB 3 devices. Most of these failures are caused by a failing setup task, which is preventing the test from running. The fixes to get the USB device fundamentals tests to run on USB 3 devices are:

  • Allow the following tests to run on USB 3.0 devices: USB Address Description testUSB Descriptor testUSB Device Control Requests testUSB Device Framework testUSB Enable Disable testUSB Enumeration Stress testUSB HIDView testUSB Selective Suspend testUSB Specification Compliance testUSB System Suspend Resume test

  • USB Specification Compliance test update to accept SuperSpeed devices running at high speed to report a version number of 2.1.Increase timeout in the USB Controller Power State test to account for devices that take longer to come back from system resume.

  • Remove disable/enable of the host controller at the beginning of the USB Controller Power State test. Instead of removing the Force HCResetOnResume bit in Windows 7, the test now checks for its presence and fails if it is set. If it is not set the test moves on and will not enable/disable the host controller.

This QFE is needed only for USB 3 device submissions, USB controller submissions and system submissions that have USB controllers. You can download the QFE from the WLK Connect website.

(Announcement Date: May 25, 2010)

Network-Connected Printers Must Implement Windows Rally

This is a reminder that effective June 1, 2010, IMAGING-0048 will require that network-connected printers, scanners, and multi-function printers (MFPs) implement the Windows Rally technologies as described by CONNECT-0098, CONNECT-0099, CONNECT-0100, and IMAGING-0004. For more information, please refer to the referenced requirements, which are available on the Windows Quality Online Services (Winqual) website ( http://winqual.microsoft.com/), and the Windows 7 Logo Program for Printers FAQ ( http://msdn.microsoft.com/en-us/windows/hardware/gg463087.aspx).

(Announcement Date: May 25, 2010)

Clarifications to STORAGE-0026 for Optical Drives

When STORAGE-0026 takes effect on June 1, 2010, read-only optical drives will no longer be a device category in the Windows Logo Program. After June 1, systems with read-only optical drives must qualify such devices through the Unclassified category.

In response to partner feedback, we have made some clarifications in STORAGE-0026. These clarifications do not change the substance of the requirement and consequently there are no changes to the Windows Logo Kit (WLK) as a result of the clarifications. The new clarifications are described in detail below. You can read the full text of STORAGE-0026 on Logopoint ( https://winqual.microsoft.com/).

Description of Changes

The following changes were made in the table of Microsoft requirements:

  • In the Profiles section, "Removable Disc" changed to "Removable Disk" to keep spelling consistent with Mt. Fuji and MMC specifications.

  • In the Profiles section, "If Drive is recordable this profile must be implemented" changed to "Required" for the following profiles: CD-R, CD-RW, DVD-R Sequential Recording, DVD-RAM, DVD-RW Restricted Overwrite, DVD-R Dual Layer Sequential Recording, DVD+RW, DVD+R, DVD+R DL. This change is consistent with the elimination of read-only optical drives as a device category.

  • In the Features section, the requirement for Asynchronous Notification is changed to remove the phrase "if implemented for other buses".

The following changes were made to the footnotes:

  • In footnote 4, "50 000 msec" changed to "60 000 msec" to be consistent with change notes (change 2 for version 2) at the top of the requirement.

  • Footnote 5 removed because it was obsolete.

The following changes were made to the design and implementation notes:

  • "DTM" changed to "WLK".

  • Removed the reference to "A recordable drive must implement all of the following profiles" because this information is now reflected more concisely in the table.

(Announcement Date: May 25, 2010)

GPU Family Update Submissions Are Back Online

We are accepting GPU Family Update submissions through the Microsoft Connect website.

To submit log files from the GPU Family Update category:

  1. Log on to the Microsoft Connect website ( http://connect.microsoft.com/).

  2. Click Your Dashboard, and then click the Windows Logo Program connection.

  3. On the navigation menu, click Feedback.

  4. Click Submit Feedback.

  5. Click GPU family update category.

  6. Complete the survey form and click Submit.

  7. On the next page, under Repro Steps, click Attach files.

  8. Click Browse, select your CPK (one CPK file per feedback), and then click Submit.

(Announcement Date: May 18, 2010)

Expiration Dates for Preview Errata and Regular Errata

Preview errata are used to mask failures in new tests or sometimes test cases within tests. If a preview erratum is applied to your test run, you should examine the failures in question. Do not assume that these failures are bugs in the test. The failures are most likely problems with the device under test. These problems must be fixed before the preview erratum expires.

Listed below are the preview errata that are currently in effect and their expiration dates.

Preview errata that expire June 1, 2010:

Errata #: Errata Title

  • 1152: TCG TPM Integration test case Quote2Basic is Previewed until 1 June 2010

  • 1245: GlitchFree WMV HD 720p video playback quality test cases 2 & 3 Preview for 6 months post WLK1.4 release

  • 1288: UAA Test: preview filter for Encoded Packet Type validation

  • 1315: PREVIEW: IO Cancellation with Direct IO: This test is preview in WLK 1.4 & 1.5

  • 1343: WLK DVD Spindown, WLK Optical Drive Streaming Mode, WLK CSS Negotiation Region Check, and WLK Aggressive Optical Drive tests are PREVIEW

  • 1348: UAA Test: PREVIEW Errata: digital converter channel to HDMI slot mapping failures

  • 1766: Preview filter for Input tests - Hot Key test, Scroll test, Winkey test

  • 1776: TPM TCG OS Interface Test - Preview Errata - Test should be preview initially for WLK 1.5

  • 1786: USB Host Controller Tramsfer Speed Test - PREVIEW

  • 1796: Preview filter for the Storage Trim Test

  • 1812: Preview: VWiFiStress is a preview test for WLK 1.5

  • 1851: 1394 Industry Certification Test ID Entry (MANUAL) test is in PREVIEW

  • 1859: KS Position Test: PREVIEW ERRATA: KSJACK_DESCRIPTION (AUDIO-0077) not required until 5/31/10

  • 1876: Preview Errata: Display Devices Verify Digital Connector

  • 1879: RoundTrip test: PREVIEW Errata: KSJACK_DESCRIPTION support is in preview mode

  • 1942: Optical Logo test: PREVIEW Errata: Dual Layer Write profile will not be required on 1 June 2009 for Blu-Ray drives of 9.5 mm height and smaller as well as DVD drives 7mm height and smaller

  • 1949: Preview: KSPROPERTY_JACK_SINK_INFO needs to be supported

Preview errata that expire June 30, 2010:

Errata #: Errata Title

  • 1299: UAA Test: PREVIEW Errata: Some digital pin widgets incorrectly set Jack Detect Override

  • 1391: MTP Compliance test has mandatory requirement waived until June 30, 2010

Preview errata that expire July 02, 2010:

Errata #: Errata Title

  • 1963: Sensor tests: PREVIEW Errata: Several Sensor tests new to WLK 1.5 are in preview mode

Preview errata that expire August 09, 2010:

Errata #: Errata Title

  • 1608: NDIS: WLAN: Statistics_ext has been modified for WLK 1.5 some failures should be in PREVIEW mode

  • 1609: NDIS: WLAN: SoftAP_WPS_ext is a PREVIEW test

  • 1719: LOGO Wireless router WPS preview test errata WCN Wireless Default Configuration (Router Reset)

  • 1720: Wireless router WPS preview test errata WCN UPnP Configure And Connect to AP with WPA2PSK AES PassPhrase using PIN over Wireless

Preview errata that expire August 31, 2010:

Errata #: Errata Title

  • 1289: UAA Test: PREVIEW filter for HDMI LPCM CAD verb

  • 1338: UAA Test: PREVIEW Errata: This test enforces Low Power DCN requirement that D3 Cold support entails EPSS support

Preview errata that expire September 30, 2010:

Errata #: Errata Title

  • 1198: UAA Test Preview errata: S/PDIF pin "Pin Sense" responses cannot use "Impedance" bits

Preview errata that expire December 1, 2010:

Errata #: Errata Title

  • 125: PCI Compliance test failes when SSID/SSVID registers are writeable

  • 1789: USB DRIVER RE-ENUMERATION TEST - PREVIEW

Preview errata that expire January 31, 2011:

Errata #: Errata Title

  • 1444: WaveTest: PREVIEW Errata: HDMI outputs that don't support 44.1kHz on Windows 7 or under third-party driver

  • 1801: Fidelity false failures in Render Power Transition Test

Preview errata that expire June 1, 2011:

Errata #: Errata Title

  • 1799: Bluetooth Device Version Check Test- ExecSecondary test is in PREVIEW

Preview errata that expire July 1, 2011:

Errata #: Errata Title

  • 1466: UAA Test: Preview Filter - Intel Low Power DCN says "EPSS implies KeepAlive, but only after July 1st 2011"

Preview errata that expire December 1, 2011:

Errata #: Errata Title

  • 1797: USB-IF Test Certification ID Check - PREVIEW

Preview errata that expire June 1, 2012:

Errata #: Errata Title

  • 1787: USB Host Controller Compliance - PREVIEW

Regular Errata That Expire in June 2010

Listed below are the errata that will expire in June 2010.

Regular errata that expire June 1, 2010:

Errata #: Errata Title

  • 205: UsbCheckApp: Bad Descriptor Test Failure

  • 535: Display: WGF Shader 4.x may crash if multisample isn't supported

  • 582: Display: D3D:Present Validation2 not skipping correctly if driver doesn't support rotated modes

  • 670: WaveTest: "communications class" devices can support 16 kHz sample rates rather than required 44.1 kHz and 48 kHz

  • 828: Display: WGF Rasterizer not properly skipping on zero area triangle cases when running 10.1 feature level 10.0

  • 1234: HDMITest: codecs failed for setting HDMI Capable bit = 1 but not implementing ELD verb

  • 1244: System Partition Test should not fail on non-premium Vista SKUs

  • 1276: UAA Test: false failures in power state transition timings

  • 1287: The Monitor test Digital Link protection will fail when the monitor does not have a digital connection

  • 1298: Device specific errata for theMODEM- NDISTest 6.0 (Power Management) test (Local Modem calling remote) (Get Reference Modem) assertions on DTM Version 1.4.7100 on Windows 7.

  • 1300: UAA Test should ignore pin widgets whose Configuration Default has Port Connectivity = No Connection

  • 1326: Display: D3D Content Protection -CPAuthChannelAPI fail due to missing GUID 1330: Optical Logo Test: Real-Time Streaming test case only supports CLV speeds

  • 1346: WIA_IPS_THRESHOLD property inside WIA Flatbed driver is not correctly initialized. on Windows Vista

  • 1424: Lullaby fails on Bluetooth devices that removes a specific handle

  • 1567: Usb Host Controller test in any system category should only be checking for S4 support if supported

  • 1572: ChkInf Test reports failure when Include and Needs directives are used within DDInstall.Wdf section

  • 1593: Chkinf improperly fails drivers that are including sti.inf in multiple install sections per the DDK

  • 1916: Test for EDID Requirements failure with Serial Number test case

Regular errata that expire June 30, 2010:

Errata #: Errata Title

  • 1390: GetObject errata filter 1448: WMDM_Compliance_Initialize

  • 1454: drmprotection property can only be set on DRM content even though it is read-write

  • 1544: MTP Compliance Test - DeleteObject functional test 3 is failing when no objects are available on the device

  • 1622: The MTP Compliance Test - GetObjectPropList test 18 and 19 may fail due to incorrect method being used.

  • 1651: GetObjectPropList Test5 - verify storage id on devices with multiple storages

(Announcement Date: May 11, 2010)

Reminder About New Requirements for June 2010

The Windows Logo Program team would like to remind partners about new requirements that go into effect June 1, 2010. The tests that validate these new requirements are in Windows Logo Kit 1.5:

  • CONNECT-0091: Near Field Communication (NFC) radio is compliant with the publicly available Near Field Communication specification V1.0

  • CONNECT-0123: USB devices should allow the Operating System to load an alternate driver on device

  • CONNECT-0125: USB Host Controllers can achieve at least 60% of their transfer speeds as defined in the respective specification (USB 2.0 or 3.0 spec)

  • CONNECT-0126: All USB devices and host controllers work properly upon resume from sleep, hibernation or restart without a forced reset of the USB host controller

  • DEVFUND-0046: Windows Server device drivers which have configurable settings provide command line utility or function for device and driver management

  • DISPLAY-0111: Display device implements the EDID data structure

  • DISPLAY-0113: Network Enabled Projectors display basic connection information on the startup splash screen when no input signal is detected

  • DISPLAY-0114: Network Enabled Projectors automatically display network input on client connection when there is no existing input signal

  • IMAGING-0051: Scanners and multi-function printers with scanning ability are required to implement the WIA 2.0 driver architecture, on all local buses implemented on the device (USB, IEEE 1394, etc.) according to the guidelines set out in the Windows Driver Kit

  • INPUT-0051: The KVM Switchbox must correctly provide the Extended Display Identification Data (EDID) received from the connected monitor to all PCs connected to it

  • INPUT-0052: The KVM switchbox detects the presence or absence of a physical monitor connected to it

  • NETMEDIA-0036: Digital Media Servers (DMS) support for MP3 audio streaming

  • NETMEDIA-0037: DMS supports popular MP4 video formats

  • NETMEDIA-0039: Digital Media Servers (DMS) must support popular AVI video formats

  • NETMEDIA-0049: Digital Media Servers (DMS) must be able to stream JPG media profiles as specified in the DLNA 1.5 media formats specification.

  • NETMEDIA-0050: Digital Media Renderer (DMR) DIDL-Lite size requirements

  • NETMEDIA-0051: Digital Media Renderers (DMR) re-register with Windows Mediasupport for WMDRM-ND LINK PROTECTION SYSTEM

  • NETMEDIA-0057: Digital Media Renderer SetAVTansportURI Robustness

  • NETMEDIA-0062: Digital Media Renderer (DMR) playback requirement in stopped state

  • NETWORK-0212: Ethernet devices that implement network presence conform to the Power Management specification on the NDIS Program

  • NETWORK-0227: Ethernet devices must implement Wake on LAN patterns according to the specification on connect

  • NETWORK-0294: Ethernet devices that implement TCP Chimney must properly handle the Out Of Order data scenarios

  • NETWORK-0295: Host Firewalls must allow mobile broadband devices that are compliant with Windows mobile broadband driver model to function correctly

  • STORAGE-0024: ATA/ATAPI based devices meet Microsoft and ATA/ATAPI protocol requirements (Effective June 2010)

  • STORAGE-0026: Optical Drives meet Industry and Microsoft standards (Effective June 2010)

  • STREAM-0021: Digital TV Tuner uses the Broadcast Driver Architecture (BDA)

  • STREAM-0082: Video streaming communication device produces acceptable frame rate.

  • STREAM-0083: Video streaming communication device produces acceptable image geometry.

  • STREAM-0084: Video streaming communication device produces acceptable image radiometry.

  • STREAM-0085: Video streaming communication device produces acceptable image uniformity.

  • SYSFUND-0193: Systems that include Wireless USB radios use WHCI radios

  • SYSFUND-0218: Desktop systems must have at least one digital video connector

(Announcement Date: May 11, 2010)

Windows Summit 2010: Wherever You Are, Be Here

The Windows Summit 2010 just got easier to attend. It's now a virtual event so everyone interested in building for Windows 7 can participate. Just stay at your desktop to get the best insight about building great products on Windows 7 and Internet Explorer. Changing from an in-person event to a virtual event gives you 24x7 access to content from the convenience of your computer.

At Windows Summit 2010 you'll discover the robust customization features in Windows 7 that help hardware partners like you create richer, more usable experiences on PCs and devices.

Content will be released on a rolling schedule for three tracks: Systems, Devices, and Software. Track content includes existing scenarios and best practices, how to improve overall quality and extend your battery life, as well as information that addresses the Windows Logo Program - from what you need to know to certify your product to what's new in Windows Logo Kit (WLK) 1.5.

Select the specialized track representing the most value to you and your business, or view them all. Each track launches with a high-profile keynote and related content goes live after the keynote as follows:

  • May 25 - Device track: Discover the rich customization features in Windows 7 that enable partners to create a custom user experience for the PC or device. Targeted at software and device firmware engineers, this track will provide you with the direction and technical information to unlock the power of Windows 7 to create a great device experience.

  • June 2 - System track: Understand the features of Windows 7 that you can leverage to create and deliver the best system possible. You'll see how implementing a few fundamental techniques can dramatically improve overall system quality and key user experiences.

  • June 16 - Software track: The Windows 7 platform makes it easy for developers to create engaging, user-friendly applications by providing familiar tools and rich development features that allow them to take advantage of the latest PC capabilities. The sessions in this track will guide you through the key developer advances in fundamentals, richer application experiences, and the best of Windows and the Web.

You can learn more at http://www.microsoft.com/windows/windows-summit/default.aspx.

(Announcement Date: May 11, 2010)

Windows Summit 2010: Wherever You Are, Be Here

The Windows Summit 2010 just got easier to attend. It's now a virtual event. Just stay at your desktop to get the best insight about building great products on Windows 7 and Internet Explorer.

Specialized Content Tracks for Systems, Devices, and Software Experts

The schedule is available at http://www.microsoft.com/windows/windows-summit/default.aspx. Pick the specialized track representing the most value to you and your business. We're ready to help you excel. Join us.

  • May 25 - Device track: Discover the rich customization features in Windows 7 that enable partners to create a custom user experience for the PC or device. Targeted at software and device firmware engineers, this track will provide you with the direction and technical information to unlock the power of Windows 7 to create a great device experience.

  • June 2 - System track: Understand the features of Windows 7 that you can leverage to create and deliver the best system possible. You'll see how implementing a few fundamental techniques can dramatically improve overall system quality and key user experiences.

  • June 16 - Software track: The Windows 7 platform makes it easy for developers to create engaging, user-friendly applications by providing familiar tools and rich development features that allow them to take advantage of the latest PC capabilities. The sessions in this track will guide you through the key developer advances in fundamentals, richer application experiences, and the best of Windows and the Web.

Learn more: http://www.microsoft.com/windows/windows-summit/default.aspx.

(Announcement Date: May 4, 2010)

Windows Logo Kit 1.5 QFE 003 Is Now Available on Connect

Windows Logo Kit (WLK) 1.5 QFE 003 has been released on the WLK Connect site ( https://connect.microsoft.com/). This fix solves a problem where the test framework was overloading CPUs in certain cases. Most actual failures pertaining to the issue were with single-core CPU systems. However, if a system has more User-Mode Driver Framework (UMDF) drivers or user-mode applets offloading driver work than it has cores, this failure can occur on multi-core systems as well.

This fix resolves the CPU loading for all systems and should not adversely affect testing otherwise.

This fix solves the issue where the aforementioned devices end up with a (typically missing) problem code while running the system stress tests, including:

  • System - Common Scenario Stress With IO

  • System - Disable/Enable With IO

  • System - Sleep Stress With IO

This fix only solves problems where the device or drivers failed due to the CPU overloading, not due to other issues.

(Announcement Date: May 4, 2010)

Latest DTM Help Documentation Available for Download

The latest Device Test Manager (DTM) documentation update for the Windows Logo Kit (WLK) is now available from the Microsoft Connect WLK website. Here are the instructions for viewing the latest documentation:

  1. Go to https://connect.microsoft.com/site668/Downloads?wa=wsignin1.0.

  2. Sign in.

  3. Select the April 2010 documentation update.

  4. Click Download.

  5. After downloading, open DTM.chm.

(Announcement Date: May 4, 2010)

GPU Family Update Program Temporarily Suspended

At this time we are experiencing issues when uploading CPK files for the GPU Family Update program through the Connect Web site, so we are temporarily suspending this program. We ask that you continue to run the GPU Family Update category tests if you are swapping GPUs per POLICY-0004, but at this time you are not required to submit them through the Connect Web site.

(Announcement Date: April 27, 2010)

Windows Summit 2010 Session Update

Join us for Windows Summit 2010, an intimate event designed for people who engineer and test Windows 7-based PCs, devices, and software. This conference features sessions that will help speed your product to market while creating an end user experience that today's customer demands, from PC design considerations for Windows Touch, to developing your device experience strategy, to how to create rich Web experiences with Internet Explorer 9. Three tracks are offered: Systems, Devices, and Software. We'll discuss existing scenarios and best practices within each track, including how to improve overall quality and how to extend your battery life, as well as sessions that address the Windows Logo Program - from what you need to know to certify your product to what's new in Windows Logo Kit (WLK) 1.5.

In addition to networking with Microsoft technical experts and leaders at breakout sessions and chalk talks, we will have an Ask the Experts and social evening, all starting with an opening keynote by Michael Angiulo, General Manager of Windows Planning and PC Ecosystem Teams. Register soon because this event is filling quickly!

What: Windows Summit 2010

When: May 25-27, 2010

Where: Microsoft Conference Center, Microsoft Campus, Redmond, Washington

Learn more and register: http://www.microsoft.com/windows/windows-summit/default.aspx

Windows Summit 2010 Tracks and Breakout Sessions

Windows Summit 2010 features three technical tracks: Systems, Devices, and Software. Each track features ways the Windows 7 platform can help speed your products to market while delivering a rich user experience. You'll have the opportunity to exchange ideas and observations with the Microsoft experts behind Windows 7.

Systems Track

Learn fundamental techniques that can dramatically improve overall system quality and user experience.

System Track Breakout Sessions

  • System Track Kickoff and Value of Quality

  • Quality Starts Here: Key Considerations for Building Quality Windows-Based PCs

  • Windows Touch Overview and PC Design Considerations

  • Windows 7 Imaging and Deployment Tools Overview

  • Windows 7 Image Management and Best Practices

  • Understanding the Windows Logo Program for Systems

  • Building Troubleshooters

  • Connecting Next-Generation Storage to Windows

  • Using the Mobile Broadband Platform in Windows 7

  • Get the Most Out of Your Battery: Implementing Hardware for Windows Power Management

  • Chalk Talk: Diagnosing Platform Power Management Problems

  • Chalk Talk: Winning in the Marketplace: PCs That Deliver a Great Experience

Devices Track

Unleash the custom capabilities of Windows 7 to enable better device experiences.

Device Track Breakout Sessions

  • Device Track Kickoff

  • Windows 7 Device Experience Overview

  • The Windows Logo Program for Hardware and Devices: Getting Started (Part 1)

  • The Windows Logo Program for Hardware and Devices: Getting Started (Part 2)

  • The Windows Logo Kit: What's New in WLK 1.5

  • Windows 7 Device Content and Web Resources

  • Developing Your Device Experience Strategy

  • Extending the Device Experience

  • Metadata Authoring: Part 1- Devices and Printers

  • Metadata Authoring: Part 2- Device Stage

  • The Device Stage Roadmap

  • Winqual Device Metadata Submissions

  • Chalk Talk: Device Metadata Planning, Authoring, and Deploying

Software Track

Learn how Windows 7, offering developers a familiar platform plus new advances in key developer fundamentals, makes it easy to create custom software for a richer application experience.

Software Track Breakout Sessions

  • Software Track Kickoff

  • Developing Multi-Touch Applications for Natural Experiences

  • Creating Rich Web Applications with Internet Explorer 9

  • Integrate Your Applications with the Windows 7 Desktop to Simplify User Experiences

  • Windows Error Reporting as a Platform Advantage for Developers

  • Empower Users to Find, Visualize, and Organize Their Data with Libraries and the Explorer

  • Building Context-Aware Applications on the Sensor and Location Platform

  • Unleashing the Latest Innovations in Modern Graphics Hardware with Windows 7

  • Windows 7 Scenic Ribbon: The Next Generation User Experience for Presenting Commands in Windows Applications

  • Extending Battery Life by Creating Energy-Efficient Applications

  • Improving System Performance by Creating Efficient Background Activities

  • Building High-Performing Windows Applications by Using the Windows Performance Toolkit

  • Panel: Windows 7 Touch Applications

  • Panel: Building Innovative Windows Client Software

Learn more and register for Windows Summit 2010 today: http://www.microsoft.com/windows/windows-summit/default.aspx or follow us on Twitter (@winsummit2010) and Facebook (Windows Summit 2010).

(Announcement Date: April 20, 2010)

Reminder About New Requirements for June 2010

The Windows Logo Program team would like to remind partners about new requirements which go into effect June 1, 2010. The tests that validate these new requirements are in Windows Logo Kit 1.5:

  • CONNECT-0091: Near Field Communication (NFC) radio is compliant with the publicly available Near Field Communication specification V1.0

  • CONNECT-0123: USB devices should allow the Operating System to load an alternate driver on device

  • CONNECT-0125: USB Host Controllers can achieve at least 60% of their transfer speeds as defined in the respective specification (USB 2.0 or 3.0 spec)

  • CONNECT-0126: All USB devices and host controllers work properly upon resume from sleep, hibernation or restart without a forced reset of the USB host controller

  • DISPLAY-0111: Display device implements the EDID data structure

  • DISPLAY-0113: Network Enabled Projectors display basic connection information on the startup splash screen when no input signal is detected

  • DISPLAY-0114: Network Enabled Projectors automatically display network input on client connection when there is no existing input signal

  • IMAGING-0051: Scanners and multi-function printers with scanning ability are required to implement the WIA 2.0 driver architecture, on all local buses implemented on the device (USB, IEEE 1394, etc.) according to the guidelines set out in the Windows Driver Kit

  • INPUT-0051: The KVM Switchbox must correctly provide the Extended Display Identification Data (EDID) received from the connected monitor to all PCs connected to it

  • INPUT-0052: The KVM switchbox detects the presence or absence of a physical monitor connected to it

  • NETMEDIA-0036: Digital Media Servers (DMS) support for MP3 audio streaming

  • NETMEDIA-0037: DMS supports popular MP4 video formats

  • NETMEDIA-0039: Digital Media Servers (DMS) must support popular AVI video formats

  • NETMEDIA-0049: Digital Media Servers (DMS) must be able to stream JPG media profiles as specified in the DLNA 1.5 media formats specification

  • NETMEDIA-0050: Digital Media Renderer (DMR) DIDL-Lite size requirements

  • NETMEDIA-0051: Digital Media Renderers (DMR) re-register with Windows Mediasupport for WMDRM-ND LINK PROTECTION SYSTEM

  • NETMEDIA-0057: Digital Media Renderer SetAVTansportURI Robustness

  • NETMEDIA-0062: Digital Media Renderer (DMR) playback requirement in stopped state

  • NETWORK-0294: Ethernet devices that implement TCP Chimney must properly handle the Out Of Order data scenarios

  • NETWORK-0295: Host Firewalls must allow mobile broadband devices that are compliant with Windows mobile broadband driver model to function correctly

  • STORAGE-0024: ATA/ATAPI based devices meet Microsoft and ATA/ATAPI protocol requirements (Effective June 2010)

  • STORAGE-0026: Optical Drives meet Industry and Microsoft standards (Effective June 2010)

  • STREAM-0021: Digital TV Tuner uses the Broadcast Driver Architecture (BDA)

  • STREAM-0082: Video streaming communication device produces acceptable frame rate

  • STREAM-0083: Video streaming communication device produces acceptable image geometry

  • STREAM-0084: Video streaming communication device produces acceptable image radiometry

  • STREAM-0085: Video streaming communication device produces acceptable image uniformity

  • SYSFUND-0193: Systems that include Wireless USB radios use WHCI radios

  • SYSFUND-0218: Desktop systems must have at least one digital video connector

(Announcement Date: April 13, 2010)

Register for Windows Summit 2010!

Windows Summit 2010 is a special opportunity to learn—straight from the Windows team—how you can best use Windows 7 and Internet Explorer to enable great solutions for your customers. This three-day event takes place May 25-27 at the Microsoft Conference Center in Redmond, WA, and is designed for people who engineer and test Windows 7-based PCs and solutions. Take advantage of this uniquely intimate event on the Microsoft campus to network with Microsoft technical experts and leaders at breakout sessions, chalk talks, and an “ask the experts” evening and social event. Michael Angiulo, General Manager of the Windows Planning and PC Ecosystem team, will give the opening keynote to provide a view of the Windows business and the exciting opportunities in front of us.

Experts from Windows are designing three technical tracks–System, Device, and Software–to help you create the best systems, devices, and software using Windows 7 and Internet Explorer.

The System track includes sessions on:

  • Optimizing performance and energy efficiency

  • Implementing touch-enabled PCs

  • Designing effective user experiences

  • Understanding the Windows Logo Program for systems

  • Creating and deploying system images

The Device track includes sessions on:

  • Overviews and demos of the Windows 7 device experience

  • Understanding the Windows Logo Program for devices

  • Using the Windows 7 platform to create custom device experiences

The Software track includes sessions on:

  • Developing touch-enabled applications

  • Supporting the Windows Libraries feature

  • Building on the Windows Sensors and Location platform

  • Utilizing Windows Error Reporting

  • Developing rich Web applications using Internet Explorer

For more information and to register, visit http://www.microsoft.com/windows/windows-summit. We look forward to seeing you in May!

(Announcement Date: April 13, 2010)

New Windows Error Reporting Agreement Version 1.3 Now Available

The new Windows Error Reporting Agreement version 1.3 is now available for signing on the Winqual Web site ( https://winqual.microsoft.com/). The new agreement addresses two sections of the previous agreement. It eliminates the six-month time period for use of information that is not personally identifiable; and also adds the ability for companies to submit public symbol files to enhance problem identification and prioritization.

Note: You must sign the new Windows Error Reporting Agreement version 1.3 by May 1, 2010, in order to access Windows Error Reporting (WER) data after that date.

(Announcement Date: April 13, 2010)

Register for Windows Summit 2010!

Windows Summit 2010 is a special opportunity to learn—straight from the Windows team—how you can best use Windows 7 and Internet Explorer to enable great solutions for your customers. This three-day event takes place May 25-27 at the Microsoft Conference Center in Redmond, WA, and is designed for people who engineer and test Windows 7-based PCs and solutions. Take advantage of this uniquely intimate event on the Microsoft campus to network with Microsoft technical experts and leaders at breakout sessions, chalk talks, and an “ask the experts” evening and social event. Michael Angiulo, General Manager of the Windows Planning and PC Ecosystem team, will give the opening keynote to provide a view of the Windows business and the exciting opportunities in front of us.

Experts from Windows are designing three technical tracks–System, Device, and Software–to help you create the best systems, devices, and software using Windows 7 and Internet Explorer.

The System track includes sessions on:

  • Optimizing performance and energy efficiency

  • Implementing touch-enabled PCs

  • Designing effective user experiences

  • Understanding the Windows Logo Program for systems

  • Creating and deploying system images

The Device track includes sessions on:

  • Overviews and demos of the Windows 7 device experience

  • Understanding the Windows Logo Program for devices

  • Using the Windows 7 platform to create custom device experiences

The Software track includes sessions on:

  • Developing touch-enabled applications

  • Supporting the Windows Libraries feature

  • Building on the Windows Sensors and Location platform

  • Utilizing Windows Error Reporting

  • Developing rich Web applications using Internet Explorer

For more information and to register, visit http://www.microsoft.com/windows/windows-summit. We look forward to seeing you in May!

(Announcement Date: April 6, 2010)

New Windows Error Reporting Agreement Version 1.3 Now Available

The new Windows Error Reporting Agreement version 1.3 is now available for signing on the Winqual Web site ( https://winqual.microsoft.com/). The new agreement addresses two sections of the previous agreement. It eliminates the six-month time period for use of information that is not personally identifiable; and also adds the ability for companies to submit public symbol files to enhance problem identification and prioritization.

Note: You must sign the new Windows Error Reporting Agreement version 1.3 by May 1, 2010, in order to access Windows Error Reporting (WER) data after that date.

(Announcement Date: April 6, 2010)

Your Last Chance to Change the Windows Client Software Logo Program!

We’re almost at the end of the survey period. Please take our quick Windows Client Software Logo Program survey at http://www.zoomerang.com/Survey/?p=WEB22AC5Z28EFX  This link leaves the Microsoft.com site by April 9, 2010. The logo program team takes your feedback very seriously and this is your opportunity to tell us what you like, what you don’t, and the changes you’d like us to make.

Thanks for your participation!

(Announcement Date: April 6, 2010)

Some Preview Errata Have Been Converted to Regular Errata

Preview errata are applied in two ways. In one case, all failures that occur in a test are allowed; this is a preview erratum that applies to the entire test. In the other case, the erratum only allows specific assertions within the test to fail; this is a preview erratum that applies only to test cases.

An example of a preview erratum that applies only to a test case is Errata 1338. This erratum applies only to the test case described, not the entire test. Errata 1338 is described below.

Errata Title:

UAA Test: PREVIEW Errata: This test enforces Low Power DCN requirement that D3 Cold support entails EPSS support

Errata Issue Description:

Errata 1338

Preview Errata - D3 Cold support advertised but EPSS not advertised. AUDIO-0062, effective June 1 2009, requires that any HD Audio codec that advertises EPSS support comply with the Intel HD Audio Low Power DCN. The D3 Cold bit is reserved on codecs that do not advertise support for the Low Power DCN.

Errata Resolution Description:

When this Errata expires, the issue described will be considered a valid failure.

Based on the large amount of partner feedback on the preview errata process, preview errata that apply to test cases will be converted to regular errata. Preview errata that apply to entire tests will be left in place. Preview Errata for test cases will have the word preview in their title and have messaging in the issue statement emphasizing what is being previewed. When these errata expire, failure of the described test cases will be considered a valid failure.

This is a short term solution to immediately address partner feedback. We are investigating other solutions for the long term. We believe it is important to differentiate preview errata from regular errata in order to highlight new points of failure for a period of time before they are enforced.

Below is a list of the preview errata for test cases that have been converted to regular errata.

Bug #-->Erratum Title

  • 1198-->UAA Test Preview errata: S/PDIF pin "Pin Sense" responses cannot use "Impedance" bits

  • 1289-->UAA Test: PREVIEW filter for HDMI LPCM CAD verb

  • 1338-->UAA Test: PREVIEW Errata: This test enforces Low Power DCN requirement that D3 Cold support entails EPSS support

  • 1348-->UAA Test: PREVIEW Errata: digital converter channel to HDMI slot mapping failures

  • 1444-->WaveTest: PREVIEW Errata: HDMI outputs that don't support 44.1kHz on Windows 7 or under third-party driver

  • 1859-->KS Position Test: PREVIEW ERRATA: KSJACK_DESCRIPTION (AUDIO-0077) not required until 5/31/10

  • 1608-->NDIS: WLAN: Statistics_ext has been modified for WLK 1.5 some failures should be in PREVIEW mode

  • 1942-->Optical Logo test: PREVIEW Errata: Dual Layer Write profile will not be required on 1 June 2009 for Blu-Ray drives of 9.5 mm height and smaller as well as DVD drives 7mm height and smaller

  • 1879-->RoundTrip test: PREVIEW Errata: KSJACK_DESCRIPTION support is in preview mode

(Announcement Date: March 30, 2010)

Your Chance to Change the Windows Client Software Logo Program!

If you haven’t done so already, we would like to get your feedback on the Windows 7 Software Logo Program. Please take our quick Windows Client Software Logo Program survey at http://www.zoomerang.com/Survey/?p=WEB22AC5Z28EFX  This link leaves the Microsoft.com site by April 9, 2010. The logo program team takes your feedback very seriously and this is your opportunity to tell us what you like, what you don’t, and the changes you’d like us to make.

Thanks for your participation!

(Announcement Date: March 30, 2010)

Release Schedule for Windows Logo Kit 1.6

The Windows Logo Program would like to inform our partners that Windows Logo Kit (WLK) 1.6 will not release on the traditional six-month cadence. Although we are relaxing the release date, we will still provide the usual notice and opportunity for beta testing and partner feedback. We will announce the beta release in future editions of this newsletter.

Program requirements that are due to take effect in June 2010 are already covered by WLK 1.5 and will be enforced by expiration of the preview filters. In order to allow adequate time for partners to implement WLK 1.6 after it is released, we may postpone enforcement of program requirements that are currently due to take effect in December 2010.

(Announcement Date: March 23, 2010)

Your Chance to Change the Windows Client Software Logo Program!

If you haven’t done so already, we would like to get your feedback on the Windows 7 Software Logo Program. Please take our quick Windows Client Software Logo Program survey at http://www.zoomerang.com/Survey/?p=WEB22AC5Z28EFX  This link leaves the Microsoft.com site by April 2, 2010. The logo program team takes your feedback very seriously and this is your opportunity to tell us what you like, what you don’t, and the changes you’d like us to make.

Thanks for your participation!

(Announcement Date: March 23, 2010)

Your Chance to Change the Windows Client Software Logo Program!

We would like to get your feedback on the Windows 7 Software Logo Program. Please take our quick Windows Client Software Logo Program survey at http://www.zoomerang.com/Survey/?p=WEB22AC5Z28EFX  This link leaves the Microsoft.com site by April 2, 2010. The logo program team takes your feedback very seriously and this is your opportunity to tell us what you like, what you don’t, and the changes you’d like us to make.

(Announcement Date: March 16, 2010)

Device Metadata Announces Bulk Upload Functionality

Device metadata is now accepting bulk uploads! Users can upload as many as fifty (50) device metadata packages into a single experience at one time. All packages will be uploaded into the same experience, and will be marked as Preview or not Preview according to the option selected. You can upload Device metadata packages in bulk into either a new experience or an existing experience, and you can also upload PC metadata packages can in bulk.

Uploading is easy! When creating a new experience, enter an Experience Name, use the browse button to select multiple packages, designate whether to upload all the packages as Preview or not Preview, select the proper logo option, and click Upload. When updating an existing experience, navigate to the experience, use the browse button to select multiple packages, fill out any other required information, and click Upload.

Note: The Friendly Name option is not available when uploading multiple packages.

You must follow the rules listed in the help documents at https://winqual.microsoft.com/member/DeviceMetadata/default.aspx for all device metadata packages. Additionally, all device metadata packages uploaded to Windows Quality Online Services (Winqual) must be signed with the certificate your company has on file with Winqual.

(Announcement Date: March 16, 2010)

Device Metadata Announces Bulk Upload Functionality

Device metadata is now accepting bulk uploads! Users can upload as many as fifty (50) device metadata packages into a single experience at one time. All packages will be uploaded into the same experience, and will be marked as Preview or not Preview according to the option selected. You can upload Device metadata packages in bulk into either a new experience or an existing experience, and you can also upload PC metadata packages can in bulk.

Uploading is easy! When creating a new experience, enter an Experience Name, use the browse button to select multiple packages, designate whether to upload all the packages as Preview or not Preview, select the proper logo option, and click Upload. When updating an existing experience, navigate to the experience, use the browse button to select multiple packages, fill out any other required information, and click Upload.

Note: The Friendly Name option is not available when uploading multiple packages.

You must follow the rules listed in the help documents at https://winqual.microsoft.com/member/DeviceMetadata/default.aspx for all device metadata packages. Additionally, all device metadata packages uploaded to Windows Quality Online Services (Winqual) must be signed with the certificate your company has on file with Winqual.

(Announcement Date: March 9, 2010)

MPIO Test Removed from Hardware-Based RAID (Storage Array) Test Category

The Microsoft Multipath I/O (MPIO) test was removed from the Hardware-based RAID (Storage Array) test category in Windows Logo Kit (WLK) 1.5. This test had many issues which resulted in support calls, errata, and in some cases missed test coverage. A new version of this test is under development and will be released in a future version of the WLK. WLK 1.5 has no specific MPIO testing for RAID systems. The current process for testing hardware-based RAID systems that support MPIO is to check the MPIO box in the submission wizard and run all the tests that are exposed in the Driver Test Manager (DTM). RAID systems will get the same test report they have received in the past for MPIO submissions as long as the MPIO box is checked.

(Announcement Date: March 9, 2010)

Devices Must Support x64-Based Versions of Windows

Because notebook computers in today’s market support both 32-bit and 64-bit instruction sets, devices that can be installed on a system that runs an x64-based version of Windows must have an x64 driver in order to qualify for a logo.

(Announcement Date: March 2, 2010)

Windows Vista SP2 Deadline Extension

Based on feedback from original equipment manufacturer (OEM) partners, we are extending the deadline for testing with Windows Vista Service Pack 2 (SP2) by two months. All Windows Vista logo program submissions must be tested with Windows Vista SP2 by May 1, 2010.

(Announcement Date: March 2, 2010)

Rate: