Windows Logo Program Requirement Updates - Archives
Updated: April 5, 2009
Note: The Requirement Updates listed here are generally older than the current 6-months release window. Current Requirement Updates can be viewed here.
On This Page
Windows Logo Program Requirement Updates - December 23, 2008
Windows Logo Program Requirement Updates - December 04, 2008
Windows Logo Program Requirement Updates - October 14, 2008
Windows Logo Program Requirement Updates - October 7, 2008
Windows Logo Program Requirement Updates - September 30, 2008
Windows Logo Program Requirement Updates - September 16, 2008
Windows Logo Program Requirement Updates - September 9, 2008
Windows Logo Program Requirement Updates - September 2, 2008
Windows Logo Program Requirement Updates - August 19, 2008
Windows Logo Program Update - Version 3.09
Windows Logo Program Update - Version 3.08
Windows Logo Program Update - Version 3.07
Premium Logo Requirement for Keyboard and Pointing and Drawing Devices
Windows Vista Logo Compliance Level Clarification
Windows Logo Program Update - Version 3.06
New Hardware Start Button Specification Released
Windows Logo Program Update - Version 3.05
Engage with the Serial ATA International Organization for SATA Device Testing
Microsoft Releases New Logo Program Requirements for RFID Devices and Printers
Windows Logo Program 3.0 Update - Version 3.03
Clarification on the Windows Logo Program Requirements for Vista - Final
Older Windows Logo Program Requirement Updates
Windows Logo Program Requirement Updates - December 23, 2008
The Windows Logo Program would like to inform partners of the following requirement updates. You can find complete details on LogoPoint.
DEVFUND-0001 - Added the exception clause and details on how this requirement is validated.
DEVFUND-0006 - Added testing details. Also added the exemption statement for HDMI devices to clause 2.
DEVFUND-0014 - Added details on how this requirement is tested during submission.
DEVFUND-0016 - Updated the testing details.
DEVFUND-0018 - Added the test details in the Design Notes.
DEVFUND-0027 - This requirement is being replaced by POLICY-0030 as this requirement is applicable through the lifecycle of the product and cannot be measured at the time of submission. This requirement will be removed January 1, 2009.
DEVFUND-0029 - Added the test details in the Design Notes.
DEVFUND-0039 - Reworded the details section to clarify the requirement.
DEVFUND-0043 - Added test information in Design Notes.
SYSFUND-0040 - This requirement is being replaced by POLICY-0030 at this requirement is applicable through the lifecycle of the product and cannot be measured at the time of submission. This requirement will be removed January 1, 2009.
PORTABLE-0051 - Retiring this requirement as it is no longer applicable.
STORAGE-0001 - Removed the SATA-IO requirement.
STORAGE-0002 - Changed a sentence from basic functionality to physical device drive.
STORAGE-0013 - Sections of the requirement are not going into effect until December 2009. Please see the requirement for complete details.
STORAGE-0017 - This requirement has been reorganized and streamlined.
STORAGE-0018 - Clarification. An optical drive (peripheral device type 5 as defined by the SCSI primary command set) is a device that complies with the following standards defined by MMC 6, Mt. Fuji 7, and Microsoft.
STORAGE-0022 - Replaced "basic functionality" with "physical disk drive." Added the sentence "Storage Miniports must comply with all miniport interface definitions as defined in the WDK".
INPUT-0037 - Deleted reference in Design notes to a white paper. it has been determined that a white paper is not necessary.
INPUT-0048 - Changed the If-Implemented Notes to: "If a Sensor or Location device interfaces with the Sensor Platform, it must meet this requirement".
INPUT-0049 - Changed the If-Implemented Notes to: "If a Location Sensor device interfaces with the Sensor Platform, it must meet this requirement".
INPUT-0050 - Changed If-Implemented Notes to: "If an Ambient Light Sensor device interfaces with the Sensor Platform, it must meet this requirement".
BUSPORT-0012 - Expire this requirement on 1 June 2009, Merging Device details into DEVFUND-0043 and System details into SYSFUND-0124.
BUSPORT-0024 - This requirement is being dropped.
CONNECT-0118 - Changed title and added link in the design notes below.
Removed the list below and replaced with: "Devices which interact with WSDAPI must populate the Metadata as defined in the Device Profile for Web Services Specification.
Wsdp:ThisDevice
Wsdp:ThisModel
Wsdp:Host
Any Wspd:HostedServiceEndpointReference)"
CONNECT-0065 - Requirement is being removed from LogoPoint.
CONNECT-0066 - Requirement is being removed from LogoPoint.
CONNECT-0067 - Requirement is being removed from LogoPoint.
CONNECT-0068 - Requirement is being removed from LogoPoint.
CONNECT-0083 - Requirement is being removed from LogoPoint.
CONNECT-0085 - Requirement is being removed from LogoPoint.
CONNECT-0089 - Requirement is being removed from LogoPoint.
CONNECT-0106 - Requirement is being removed from LogoPoint.
CONNECT-0107 - Requirement is being removed from LogoPoint.
CONNECT-0108 - Requirement is being removed from LogoPoint.
CONNECT-0110 - Requirement is being removed from LogoPoint.
CONNECT-0112 - Requirement is being removed from LogoPoint.
The following are new requirements and policies that we are proposing. Please provide feedback in LogoPoint.
POLICY-0030 - PREVIEW: All drivers and systems must maintain a high quality, measured by the Driver Quality Rating (DQR) metric, throughout the life of the product.
(Announcement Date: December 23, 2008)
Windows Logo Program Requirement Updates - December 04, 2008
The Windows Logo Program would like to inform partners of the following requirement updates. You can find complete details on LogoPoint.
POLICY-0004 - Added GPU family definition.
POLICY-0017 - Added new note for June 2009 requirement. If swapping a GPU that spans device families as stated in Policy-0004, this would require a new system submission.
SYSFUND-0042 - Requirement regarding IR learning and emitting has been clarified. Add notes about requirements for Windows Media Center Additional Clarification. Also made notes about requiring remotes for mobile system.
SYSFUND-0043 - Reactivated this requirement. It was erroneously removed from the site.
SYSFUND-0046 - Clarified the requirement for Direct X10 for Windows Vista Premium and Windows 7 logo.
SYSFUND-0120 - This requirement will be retired January 1, 2009.
The following are new requirements and policies that we are proposing.
SYSFUND-0218 - Desktop systems must have at least one digital video connector.
(Announcement Date: December 16, 2008)
New Windows Logo Program Testing Agreement Now Available
The new Windows Logo Program Testing Agreement, Version 2.2.1, is now available for signing. In this version, clarifications have been added to section 3ii.
Immediate signature of Version 2.2.1 is not required. However, please note that this version will be required for those new to the logo program or when a previously completed version expires.
This and all versions of the Windows Logo Program testing agreement are available on the WinQual Web site. See the "Helpful Links" area and click on "Legal Agreements".
(Announcement Date: December 04, 2008)
Windows Logo Program Requirement Updates - October 14, 2008
The Windows Logo Program would like to inform partners of the following requirement updates. You can find complete details on LogoPoint. Please provide any feedback by November 14, 2008.
BUSPORT-0030 Merging of BUSPORT-0012 and BUSPORT-0014.
INPUT-0048 Reference in details for SENSOR_DATA_TYPE_COUNTRY_REGION data field changed from RFC 1766 to ISO 3166.
POLICY-0003 Add final two paragraphs that clarify our expectations about having all drivers of a multi-function device installed during testing.
(Announcement Date: October 14, 2008)
Windows Logo Program Requirement Updates - October 7, 2008
The Windows Logo Program would like to inform partners of the following requirement updates. You can find complete details on LogoPoint. Please note that updated requirements in the IMAGING and PORTABLE categories will be available in early November 2008.
AUDIO-0011 Combination jacks that have both a speaker and a microphone are also able to provide a connect that supports microphone and speaker jack.
CONNECT-0048 Changed section 3 and changing full-speed to full speed or high-speed.
GRAPHICS-0013 Clarified resolutions that need to be supported.
GRAPHICS-0025 Added Windows 7 as a form factor.
GRAPHICS-0029 Removed Windows Vista-specific language as it applies to both Windows Vista and Windows 7.
GRAPHICS-0052 Added last bullet of the requirement.
GRAPHICS-0057 Added notes for Windows Vista basic logo.
GRAPHICS-0068 Added Windows 7 fields.
GRAPHICS-0071 Clarified Windows 7 and Direct3D version 11 requirements.
STORAGE-0019 Any place that said devices was changed to volumes.
SYSFUND-0059 Removed hybrid specific requirements based on feedback. This has been moved to SYSFUND-0215.
SYSFUND-0139 Combination jacks that have both a speaker and a microphone are also able to provide a connect that supports microphone and speaker jack.
SYSFUND-0195 Removed Windows 7-specific requirements based on feedback. Windows 7 hybrid requirements can be found in SYSFUND-0212.
The following are new requirements and policies that we are proposing. Please provide any feedback on new and updated requirements by November 14.
DEVFUND-0039 Windows Driver Framework (WDF) drivers are packaged to contain the latest RTM free versions of redistributables.
DEVFUND-0041 All drivers must operate normally and execute without errors with Data Execution Prevention (DEP) enabled.
DEVFUND-0043 All devices and drivers must support S3 and S4 sleep states of the system they are integrated on or connected to.
GRAPHICS-0027 StretchRect support YUV to RGB conversions.
GRAPHICS-0032 Display WDDM driver support the DirectX VA 2.0 Video Processor DDI.
GRAPHICS-0076 If Display adapter or chipset supports Direct3D 11, it must comply with Direct3D 11 and DXGI feature sets.
SYSFUND-0212 Windows 7 systems with Multiple GPUs must meet all GRAPHICS and System Fundamental requirements and must pass all tests in all available GPU operating modes.
SYSFUND-0214 Systems support S3 and S5 states
(Announcement Date: October 7, 2008)
Windows Logo Program Requirement Updates - September 30, 2008
The Windows Logo Program would like to inform partners of the following requirement updates. You can find complete details on LogoPoint.
STREAM-0053 USB stream video camera complies with USB Video Class specifications
STREAM-0060 Digital TV tuners requiring protected streams must use Protected Broadcast Driver Architecture
STREAM-0062 TV tuners must be able to scan for services multiple times
STREAM-0063 ISDB-t Digital TV tuners must support BML
STREAM-0065 TV tuners must be able to record programs
STREAM-0066 TV tuners must support 500 channel changes
STREAM-0067 Digital TV tuners must support surprise removal of Conditional Access Systems smartcard
STREAM-0068 Devices with multiple TV tuners must support simultaneous use of all tuner streams (including homogeneous & heterogeneous broadcast types)
STREAM-0071 TV tuners must support at least six hours of uptime
STREAM-0072 TV tuners must be able to record programs
STREAM-0074 TV tuner must complete First Run and play Live TV within Windows Media Center
NETMEDIA-0001 Decoder requirements for Digital Media Renderers (DMR)
NETMEDIA-0002 Digital Media Servers pass DLNA 1.5 certification
NETMEDIA-0003 Digital Media Renderers pass DLNA 1.5 certification
NETMEDIA-0004 DLNA 1.5 certification for Digital Media Controllers
NETMEDIA-0008 Digital Media Server DMS support Device Description Document
NETMEDIA-0009 Digital Media Renderer is discoverable as a DMR via PnP-X settings
NETMEDIA-0010 Digital Media Controllers must include metadata from Device Description Document for Digital Media Controllers
NETMEDIA-0011 Digital Media Server support wake on LAN
NETMEDIA-0012 Wake on LAN requirements for Digital Media Renderers
NETMEDIA-0017 Digital Media Server support renaming the DMS Friendly Name
NETMEDIA-0018 Digital Media Renderers support changing the friendly name
NETMEDIA-0020 Digital Media Renderers support Windows Media Digital Rights Management
NETMEDIA-0021 Digital Media Server supports Windows Media Video Profile
NETMEDIA-0022 Digital Media Servers support Windows Media Audio Profile
NETMEDIA-0023 Digital Media Renderers support Windows Media Video Profile
NETMEDIA-0024 Digital Media Renderers support Windows Media Audio Profile
NETMEDIA-0025 Digital Media Renderers meet resource element selection requirements
NETMEDIA-0026 Digital Media Servers support the following DLNA search queries
NETMEDIA-0027 If the Digital Media Renderer implements a Media Server Control Point, then the DMR must either support search locally, or support sending search requires in response to user action.
NETMEDIA-0029 Album art requirements for Digital Media Servers
NETMEDIA-0032 Metadata requirements for Digital Media Servers
NETMEDIA-0041 Skipping file that cannot be played
NETMEDIA-0042 Digital Media Renderers accept streams without user input
NETMEDIA-0047 Digital Media Servers streams continuously
NETMEDIA-0048 Digital Media Renderer plays media continuously
NETMEDIA-0053 Digital Media Servers stream high definition content
NETMEDIA-0054 Digital Media Servers support multiple HTTP connections
NETMEDIA-0059 Digital Media Server meets album art requirements
NETMEDIA-0060 Digital Media Server meets thumbnail image requirements
NETMEDIA-0061 Digital Media Server support video thumbnails
NETMEDIA-0066 Digital Media Server support media seek
NETMEDIA-0070 Time-based seeking in Digital Media Renderers
NETMEDIA-0071 Digital Media Renderer supports pausing a stream as specified in UPnP AVTransport specification
NETMEDIA-0072 Digital Media Renderer supports Volume Control as specified under DLNA requirement 7.3.108MM
NETMEDIA-0074 Digital Media Controllers support wake on LAN
NETMEDIA-0075 Digital Media Renderer support for metadata update object
NETMEDIA-0076 Digital Media Renderers support wake on LAN
NETMEDIA-0077 Digital Media Renderers support Device Description Document
NETMEDIA-0078 Digital Media Servers that implement sleep mode support Device Description Document
DEVFUND-0034 All PnP devices must properly implement the CM_DEVCAP_REMOVABLE capability
DEVFUND-0035 Drivers must operate correctly on servers that have processors configured into multiple processor groups
DEVFUND-0036 User Mode Driver Framework drivers must be secure, stable, reliable and not have application compatibility issues
DEVFUND-0037 Kernel Mode Driver Framework drivers are architected to maximize reliability and stability and do not leak resources such as memory or KMDF objects
DEVFUND-0038 Kernel modem Driver Framework drivers are designed to handle DDI gracefully
DEVFUND-0040 Windows Driver Framework driver INF files are properly structured.
The following is a new requirement that we are proposing. Please provide any feedback on new and updated requirements by November 14.
INPUT-0046 Add clarification around expectations for each finger and touchable surface.
(Announcement Date: September 30, 2008)
Windows Logo Program Requirement Updates - September 16, 2008
The Windows Logo Program would like to inform partners of the following requirement updates. You can find complete details on LogoPoint.
GRAPHICS-0020 - Display adapter or chipset complies with Direct3D 10 and DXGI feature sets. Added performance target metrics for AeroAT testing on Direct3D 10
STORAGE-0013 - Optical Drives meet Industry and Microsoft standards. Deleted "future" from the title.
The following are new requirements and policies that we are proposing. Please provide any feedback on these new requirements by October 21, 2008.
SYSFUND-0200 - Embedded devices in a system must report the removable/non-removable capability appropriately.
STREAM-0060 - Digital TV Tuners requiring protected streams use PBDA.
STREAM-0062 - TV Tuners must be able to scan for services times.
STREAM-0063 - ISDB-T Digital TV Tuners must support BML.
STREAM-0064 - TV Tuners must support closed captioning.
STREAM-0065 - TV Tuners must support 500 channel changes.
STREAM-0071 - TV tuners must support time-shifted playback.
(Announcement Date: September 16, 2008)
Windows Logo Program Requirement Updates - September 9, 2008
The Windows Logo Program would like to inform partners of the following requirement updates. You can find complete details on LogoPoint.
GRAPHICS-0020 - Display adapter or chipset complies with Direct3D 10 and DXGI feature sets. Updated with performance target metrics for AeroAT testing on Direct3D 10.
SYSFUND-0072 - Remote boot support for PXE complies with BIOS Boot Specification 1.01 or EFI boot manager. Updated requirement for new June 1, 2009, logo refresh.
SYSFUND-0007 - System meets minimum memory requirements. Removed incorrect variable.
The following are new requirements and policies that we are proposing. Please provide any feedback on these new requirements by October 14, 2008.
SYSFUND-0204 Systems enable a firewall solution by default.
AUDIO-0054 WaveRT drivers support pull-mode audio streaming technology by implementing the IMiniportWaveRTStreamNotification interface.
AUDIO-0057 Bluetooth audio devices to expose Major/Minor Class of Device identifier and accurately reflect form factor/primary usage.
AUDIO-0059 BT Audio devices must be compliant with the Bluetooth connectivity requirements.
AUDIO-0060 Bluetooth Audio Device needs to support at least one of the below profiles.
AUDIO-0061 Bluetooth Audio Devices must complete an HCIDisconnect before powering down.
AUDIO-0062 If HD Audio codec supports HD Audio Low-Power DCN then it needs to implements the Low-Power specification correctly in hardware, firmware and 3rd party software (driver).
AUDIO-0077 HD audio drivers must support specific properties to describe state of jack/connector.
AUDIO-0078 If HDMI or DisplayPort supports multi-channel HD audio, the audio subsystem needs to be be compliant with HD audio HDMI DCNs.
AUDIO-0079 Audio drivers using HD audio specification and exposing HDMI or DisplayPort endpoint must support the KSPROPERTY_JACK_SINK_INFO property.
AUDIO-0080 An audio device that is appropriate for communication scenarios only or wants to be certified in the Communications Device Logo program exposes itself as a Default Communications Device to Windows.
AUDIO-0083 Communication device does not use undiscoverable and/or uncontrollable non-linear audio processing that is on by default.
AUDIO-0087 Bluetooth Audio Device Driver Requirements.
STREAM-0060 Digital TV Tuners requiring protected streams use PBDA.
STREAM-0061 All TV Tuners must resume from hibernation multiple times.
STREAM-0062 All TV Tuners must be able to scan for services multiple times.
STREAM-0063 ISDB-T Digital TV Tuners must support BML.
STREAM-0064 All TV Tuners must support closed captioning.
STREAM-0065 All TV Tuners must support 500 channel changes.
STREAM-0066 All TV Tuners must support 500 channel changes.
STREAM-0071 All Devices must support time-shifted playback.
STREAM-0072 All Devices must be able to record programs.
STREAM-0074 All Devices must complete First Run and play LiveTV within Media Center for Premium Logo.
STREAM-0076 All scheduled recording must wake up a Device.
STREAM-0077 Devices must support playback during the transition from Windows to Full-Screen modes.
STREAM-0081 All Devices must support parental ratings.
Correction from last week's Windows Logo Program newsletter:
In last week's newsletter, we incorrectly identified GRAPHICS-0072 as a new logo requirement. This requirement was combined with GRAPHICS-0071. We apologize for any confusion.
(Announcement Date: September 9, 2008)
Windows Logo Program Requirement Updates - September 2, 2008
The Windows Logo Program would like to inform partners of the following requirement updates. You can find complete details on LogoPoint.
BUSPORT-0001 - HD Audio controller implements additional requirements not specified in the Intel HD Audio specification: Added Server Device form factor
BUSPORT-0002 - HD Audio bus controllers follow applicable Plug and Play guidelines: Added Server Device form factor
BUSPORT-0006 - CardBus controller complies with industry standards and Windows-compatible configuration: Added Server Device form factor
BUSPORT-0008 - Open HCI controller support IEEE 1394a -1999: Added Server Device form factor
BUSPORT-0011 - Secure Digital I/O (SDIO) host controllers comply with industry standards and Windows KMDF requirements: Added Server Device form factor
BUSPORT-0013 - USB host controller that supports USB functionality complies with the appropriate specification: Added Server Device form factor
BUSPORT-0014 - USB host controller successfully enumerates new devices upon resume from suspend: Added Server Device form factor
BUSPORT-0017 - USB host controller maintains device state on resume from S1 or S3: Added Server Device form factor
BUSPORT-0027 - 1394b host controllers must provide at least one customer accessible nine pin 'bilingual' port: Added Server Device form factor
BUSPORT-0033 - 1394 host controllers pass all required 1394 Trade Assocation compliance tests: Added Server Device form factor
BUSPORT-0034 - USB Host Controller is USB IF certified: Added Server Device form factor
CONNECT-0012 - CardBus card is configured correctly: Added Server Device form factor
CONNECT-0017 - A single ExpressCard module that supports both USB and PCI Express interfaces implements a common serial number: Added Server Device form factor
CONNECT-0020 - Descriptors are implemented for Vendor_ID and Model_ID entries in the configuration status register (CSR) space: Added Server Device form factor
CONNECT-0021 - 1394 device configuration ROM is correctly implemented: Added Server Device form factor
CONNECT-0023 - Vendor and model leaf supports textual descriptor leaf format for 1394 devices: Added Server Device form factor
CONNECT-0024 - SBP-2-capable 1394 device complies with SBP-2-related requirements: Added Server Device form factor
CONNECT-0033 - Configuration space for PCI device is correctly populated: Added Server Device form factor
CONNECT-0034 - PCI Express requirement: Added Server Device form factor
CONNECT-0037 - PCI and PCI-X devices, that are PCI 2.3 compliant, support the interrupt-disable bit: Added Server Device form factor
CONNECT-0038 - PCI-X and PCI Express devices that use prefetchable memory BARs, implement 64-bit prefetchable memory base address registers (BARs): Added Server Device form factor
CONNECT-0042 - PCI device that reports PCI-X capability in the PCI configuration space and that generates interrupts may support MSI or MSI-X but is not required to do so: Added Server Device form factor
CONNECT-0044 - USB device complies with implementation details from the USB specification: Added Server Device form factor
CONNECT-0045 - USB serial numbers are implemented for specific device classes and are unique across specific device models: Added Server Device form factor
CONNECT-0046 - USB hub correctly identifies and reports the number of ports that the user can access: Added Server Device form factor
CONNECT-0048 - Isochronous USB device and driver requirement: Added Server Device form factor
CONNECT-0049 - USB hub or device that implements USB functionality complies with the related specification: Added Server Device form factor
CONNECT-0050 - USB hub with exposed ports is self-powered: Added Server Device form factor
CONNECT-0052 - USB device can be configured to any USB address: Added Server Device form factor
CONNECT-0054 - USB device responds to all string requests that the host sends to indexes: Added Server Device form factor
CONNECT-0056 - USB peripheral operates in function mode when connected to a computer host controller: Added Server Device form factor
CONNECT-0058 - Third-party INF files include the class “USB” only if the device is a USB host controller, a root, or an external hub: Added Server Device form factor
CONNECT-0059 - USB device responses to host requests are limited in size by the wLength field: Added Server Device form factor
CONNECT-0061 - USB device that uses the iSerialNumber field ensures unique serial numbers across devices of the same model: Added Server Device form factor
CONNECT-0062 - USB device that implements manufacturer-defined serial numbers contains valid characters: Added Server Device form factor
CONNECT-0069 - PCI and PCI-X devices, at a minimum, are PCI 2.1 compliant: Added Server Device form factor
CONNECT-0071 - USB Transfer Cable requirements: Added Server Device form factor
CONNECT-0093 - USB device is USB IF certified: Added Server Device form factor
CONNECT-0094 - All Bus powered USB devices support USB Selective Suspend after periods of inactivity: Added Server Device form factor
CONNECT-0104 - USB device that signals device-attach responds after at least 100 ms: Added Server Device form factor
CONNECT-0109 - Attached USB devices must be functional after resuming from system power states: Added Server Device form factor
CONNECT-0121 - IEEE 1394 devices meet Industry requirements: Added Server Device form factor
INPUT-0001 - Digitizers provide a high quality input experience: Added Server Device form factor
INPUT-0002 - Input gaming device are HID-compliant and use Direct Input APIs: Added Server Device form factor
INPUT-0008 - All HIDs meet USB HID specifications: Added Server Device form factor
INPUT-0016 - Windows Logo flag key is implemented on all keyboards supporting more than 50 keys, the Windows Vista Start Button design is required after June 30th 2007: Added Server Device form factor
INPUT-0018 - Smart card driver does not stop the system if required resources are not available: Added Server Device form factor
INPUT-0019 - Smart card driver can support multiple instances of the same device on a system: Added Server Device form factor
INPUT-0020 - Reader supports direct and inverse-convention smart cards: Added Server Device form factor
INPUT-0021 - Reader supports 258-byte packets in T=0 and 259-byte packets in T=1: Added Server Device form factor
INPUT-0022 - Reader supports smart card insertion and removal monitor: Added Server Device form factor
INPUT-0023 - Reader supports negotiable and specific modes according to the ISO/IEC specification: Added Server Device form factor
INPUT-0024 - Reader supports 3.5795-MHz minimum clock frequency: Added Server Device form factor
INPUT-0025 - Reader supports minimum data rate of 9600 bps: Added Server Device form factor
INPUT-0026 - Reader supports Reset command: Added Server Device form factor
INPUT-0027 - USB smart card CCID reader complies with USB Device Class Specification for USB Chip/Smart Card Interface Devices: Added Server Device form factor
INPUT-0028 - USB CCID reader issues NAK on interrupt pipe if device has no interrupt data to transmit: Added Server Device form factor
INPUT-0029 - Input device that implements a PIN data-entry keyboard complies with ISO: Added Server Device form factor
INPUT-0030 - Windows Smart Card Minidrivers meet Windows Smart Card Minidriver Version 5 Specifications and Certification Criteria: Added Server Device form factor
INPUT-0036 - Windows Smart Card Minidrivers meet Windows Smart Card Minidriver Version 6 Specifications and Certification Criteria: Added Server Device form factor
INPUT-0037 - Dynamic Keyboards meet the requirements listed here: Added Server Device form factor
STORAGE-0013 - Optical Drives meet Industry and Microsoft standards: Deleted "(Future Requirement)" from title and changed from factor from Future Requirement to Required.
The following are new requirements and policies that we are proposing. Please provide any feedback on these new requirements by October 14, 2008.
SYSFUND-0211 - Display adapter or Chipset for graphics solution on Server is based on WDDM: New
GRAPHICS-0075 - Graphics driver components comply with Application Verifier test criteria: New
GRAPHICS-0071 - Display adapter or Chipset complies with WDDM v1.1 required feature set: New
GRAPHICS-0072 - If the Display adapter or chipset implements the optional WDDM v1.1 video playback features they must follow the respective specifications: New
GRAPHICS-0073 - Display Driver designed for Display adaptor or chipset that contains an HD Audio interface supporting multi-channel HDMI or DisplayPort audio consistent with HD Audio must comply with HD Audio HDMI #& DisplayPort DCN's: New
GRAPHICS-0075 - Graphics driver components comply with Application Verifier test criteria: New
(Announcement Date: September 2, 2008)
Windows Logo Program Requirement Updates - August 19, 2008
The Windows Logo Program would like to inform partners of the following requirement updates. For complete details, review LogoPoint.
SYSFUND-0064 -Requirement updated for June 2009 logo refresh.
SYSFUND-0065 - Requirement merged with SYSFUND-0064.
SYSFUND-0042 -Requirement updated for June 2009 logo refresh.
SYSFUND-0060 -Requirement updated for June 2009 logo refresh.
SYSFUND-0061 -Requirement updated for June 2009 logo refresh.
CONNECT-0093 -Enforcement date changed from June 2009 to June 2010.
BUSPORT-0034 -Enforcement date changed from June 2009 to June 2010.
(Announcement Date: August 19, 2008)
Windows Logo Program Update - Version 3.09
Client System Document
-
SYSFUND-0032 - Fixed typo in effective date, which should be June 1, 2007
-
Clarified motherboard requirement description
Server System Document
-
SYSFUND-0115 - Clarified wording
-
Clarified wording about requirements for server device logo
-
SYSFUND-0129 - Added reference to future requirement SYSFUND-0115
-
Clarified text of "supported" program
-
Added DP and virtualization requirements SYSFUND-0140, SYSFUND-0141, SYSFUND-0142, and SYSFUND-0143
-
Clarified WHEA requirements SYSFUND-0012, SYSFUND-0013, SYSFUND-0014, SYSFUND-0015, SYSFUND-0016, removed SYSFUND-0017
-
Removed SYSFUND-0119 (Windows Compatibility Implementation Guide)
Device Requirements Document
-
Clarified wording about server device logo
-
Clarified GRAPHICS-0007 exception for ultra mobile form factor
-
Added Wireless USB requirements CONNECT-78 through CONNECT-0093
-
Added INPUT-0030 for smart card minidrivers
-
Added Premium option for NETWORK-0004
(Announcement date: January 4, 2007)
Windows Logo Program Update - Version 3.08
Client System Document
-
Modified motherboard requirements section to clarify requirements.
-
SYSFUND-0004 S3 resume time requirement has updated details section with clarification regarding systems with USB hubs.
-
SYSFUND-0007 Updated details section with clarification on Premium minimum system memory based on partner feedback. Included Design and Implementation Notes section to clarify additional question received regarding this requirement.
-
SYSFUND-0049 Updated details section with the following, "For front panel audio jacks on a desktop or the side/front panel jacks on a mobile platform, at least one of the jacks must be defined as a Headphone output in the HD Audio codec's pin configuration register by the system BIOS and function as such as the default behavior."
-
SYSFUND-0118 Added the following text to note 6 that refers to Full scale output voltage of the Analog Headphone Out Jack: Smaller output voltages (>=150mVrms) are permitted when required by regulatory and safety standards. Removed R* from requirement header in document under the UMPC Form Factor.
-
SYSFUND-0127 Added the following text to note 6 that refers to Full scale output voltage of the Analog Headphone Out Jack: Smaller output voltages (>=150mVrms) are permitted when required by regulatory and safety standards.
-
SYSFUND-0139 Created system level requirement to complement AUDIO-0011 from the Audio devices section. Added to address partner clarification requests.
Server System Document
Device Requirements Document
Device Connectivity - PCI and PCI Express Devices
Graphics Device
Display Device
Network Devices
Audio Device
-
AUDIO-0006 Added the following text to note 6 that refers to Full scale output voltage of the Analog Headphone Out Jack: Smaller output voltages (>=150mVrms) are permitted when required by regulatory and safety standards.
-
AUDIO-0025 Added the following text to note 6 that refers to Full scale output voltage of the Analog Headphone Out Jack: Smaller output voltages (>=150mVrms) are permitted when required by regulatory and safety standards.
Input Devices - Keyboard
-
INPUT-0031 Added note indicating that buttons that support Windows Media Center functionality comply with the Windows Vista Remote control documentation. This requirement does not apply to keyboards that are integrated in either a Mobile PC or All-in-one PC form factors.
-
INPUT-0032 This requirement does not apply to keyboards that are integrated in either a Mobile PC or All-in-one PC form factors.
Input Devices - Pointing and Drawing
-
INPUT-0033 This requirement does not apply to pointing devices that are integrated in either Mobile PC or All-in-one PC form factors.
-
INPUT-0034 This requirement does not apply to pointing devices that are integrated in either Mobile PC or All-in-one PC form factors.
Storage Devices
(Announcement date: November 16, 2006)
Windows Logo Program Update - Version 3.07
Network Infrastructure Devices Requirements
All requirements in this device category have been updated to remove the entry for the Server Devices form factor. There is currently no certification program of Network Infrastructure Devices in the Windows Vista Logo Program for Hardware. This update has been made to the following requirements:
|
NETWORK-0050
NETWORK-0051
NETWORK-0052
NETWORK-0053
NETWORK-0054
NETWORK-0065
|
NETWORK-0066
NETWORK-0067
NETWORK-0068
NETWORK-0069
NETWORK-0070
NETWORK-0071
|
NETWORK-0073
NETWORK-0075
NETWORK-0076
NETWORK-0077
NETWORK-0078
NETWORK-0079
|
NETWORK-0080
NETWORK-0081
NETWORK-0082
NETWORK-0083
NETWORK-0086
|
Other Requirement Updates for Version 3.07
-
AUDIO-0003 Removed "If-Implemented definition" section; this is required "R" for Windows Vista Logo.
-
AUDIO-0006 Incorrectly listed this requirement as a FUTURE requirement for Audio devices. Audio device and driver must still pass the audio fidelity tests in the DTM today; system submissions will be required to pass these tests after June 1, 2007.
-
AUDIO-0025 Incorrectly listed this requirement as a FUTURE requirement for Audio devices. Audio device and driver must still pass the audio fidelity tests in the DTM today; system submissions will be required to pass these tests after June 1, 2007.
-
CONNECT-0077 Updated formatting to be consistent with other requirements in the document.
-
CONNECT-0076 Updated formatting to be consistent with other requirements in the document.
-
DISPLAY-0085 Extra text in the "If-Implemented Definition" was removed.
-
INPUT-0001 Reformatted details section to be consistent with other requirements.
-
INPUT-0031 New input keyboard device requirement; introduced to promote a Premium logo program for this device category.
-
INPUT-0032 New input keyboard device requirement; introduced to promote a Premium logo program for this device category.
-
INPUT-0033 New input pointing and drawing device requirement; introduced to promote a Premium logo program for this device category.
-
INPUT-0034 New input pointing and drawing device requirement; introduced to promote a Premium logo program for this device category.
-
NETWORK-0050 Clarified the "If-Implemented definition" based on partner feedback.
-
STORAGE-0005 Updated note on Premium mobile systems; required as of June 1, 2008. Changed from "R*" in Premium field of spreadsheet to "I" since this requirement is specific to the hard drive and not a system.
-
SYSFUND-0032 Updated with FUTURE effective date of June 1, 2007.
-
SYSFUND-0033 Updated Server document to be consistent with language in Client for this requirement.
-
SYSFUND-0044 Updated table to reflect the FUTURE enforcement date of Hybrid Hard Disk Drives for Premium Mobile systems to June 1, 2008.
-
SYSFUND-0047 Updated "If-Implemented definition" for current system audio solutions that support multi-streaming audio scenarios.
-
SYSFUND-0070 Added "If-Implemented definition."
-
SYSFUND-0072 Added "If-Implemented definition." Updated details section to make implementation as defined in the BIOS Boot Specification, Version 1.01, Appendix C recommended. PXE support is still required for Business systems. This requirement is also exempt for systems that have Wireless LAN only.
-
SYSFUND-0075 Created "Design and Implementation Note" section to add note that was previously part of the details.
-
SYSFUND-0119 Updated "Design and Implementation Note" section with information on future Draft release milestones of the Windows Compatibility Implementation Guide. Updated title to be consistent with the title of the guide.
-
SYSFUND-0130 Updated title and details to remove AH - AES-GCM and SHA-1 and is Server specific.
-
SYSFUND-0131 This requirement does not apply to All-in-one form factor type systems; requirement title and details updated.
-
SYSFUND-0132 This requirement does not apply to All-in-one form factor type systems; requirement title and details updated. Moved details from the notes section to the body of the requirement.
-
SYSFUND-0135 Updated requirement with FUTURE "If-Implemented" date.
(Announcement date: October 26, 2006)
Premium Logo Requirement for Keyboard and Pointing and Drawing Devices
Premium level requirements do not exist for all device categories that are supported in the Windows Logo Program for Windows Vista. Some device categories include requirements for Basic logo level only, therefore no Premium logo can be obtained for those categories. Based on consistent feedback from our partners the Windows Logo Program will introduce new Premium requirements to allow for differentiation of Premium products from Basic products in the marketplace.
The first two device categories to be updated to introduce Premium logo requirements are Keyboard and Pointing and Drawing devices. Version 3.07 of the Windows Logo Program Suite will include the new set of Premium logo requirements for Keyboard and Pointing and Drawing categories for Windows Vista.
New requirements will be available for review with the release of Version 3.07, available on October 2, 2007 on Windows Logo Program Requirements V. 3.0. The new requirements have been included here for your immediate review.
Input Devices - Keyboard
The following requirements are NEW and are being introduced to justify the creation of a Premium logo program for the Keyboard category.
A Premium keyboard must implement at least one hot key that is mapped to a Windows function. Examples of possible functions that could be mapped to include, but are not limited to, the following:
These media keys must use the registry keys associated with the WM_APPCOMMAND API to access those functions as described in the Windows Driver Kit. Registry keys can be programmed by using INF files to install special entries as defaults or through a customized interface provided to the user.
Design and Implementation Note
See Key Support, Keyboard Scan Codes, and Windows.
Microsoft has defined extended scan codes for PS/2-compatible multimedia keyboards, and the USB HID Device Working Group has defined the consumer controls page. Hardware vendors must comply with these defined values and use their default functionality to ensure a good user experience following an upgrade or if the user doesn't install any supplemental software. Additional software or drivers can be written to provide software remapping functionality. See also the Microsoft Platform SDK and Windows Driver Kit, "WM_APPCOMMAND."
A Premium keyboard must include the following media keys:
These media keys must use the registry keys associated with the WM_APPCOMMAND API to access those functions as described in the Windows Driver Kit. Registry keys can be programmed by using INF files to install special entries as defaults or through a customized interface provided to the user.
Design and Implementation Note
See Key Support, Keyboard Scan Codes, and Windows.
Microsoft has defined extended scan codes for PS/2-compatible multimedia keyboards, and the USB HID Device Working Group has defined the consumer controls page. Hardware vendors must comply with these defined values and use their default functionality to ensure a good user experience following an upgrade or if the user doesn't install any supplemental software. Additional software or drivers can be written to provide software remapping functionality. See also the Microsoft Platform SDK and Windows Driver Kit, "WM_APPCOMMAND."
Input Devices - Pointing and Drawing
A Premium pointing device (mouse or other) must not use mechanical parts, such as a track ball, to track position. Examples of acceptable position tracking technologies include, but are not limited to, optical and laser.
A Premium pointing device (mouse or other) must support scrolling. Scroll capability can be implemented in a number of different ways; some common implementations include scroll wheel and touch pad. Other implementations are also acceptable.
(Announcement date: September 21, 2006)
Windows Vista Logo Compliance Level Clarification
The Windows Logo Program explicitly identifies the compliance level and the versions of the operating system for which the product (system or device) passed compliance testing. After the manufacturer completes the self-test process and submits test logs to Microsoft, Windows Hardware Quality Labs (WHQL) validates this compliance.
For the Windows Vista Client Operating System, a product (system or device) can obtain one of two levels of compliance, as described below. The following table provides guidelines for how the compliance levels map to Windows Vista client SKUs and which logo can be used on each SKU.
|
Windows Vista SKU
|
Basic Systems
|
Premium Systems
|
| Ultimate |
Yes |
Yes |
| Enterprise |
Yes |
Yes |
| Business |
Yes |
Yes |
| Home Premium |
Yes |
Yes |
| Home Basic |
Yes |
No |
Compliance Levels for Windows Logo Program
"Windows Vista BASIC" and "Works with Windows Vista" logo level
A system or device being tested is deemed compliant when it meets the basic logo requirements (previously known as "silver" or "standard" logo level) as defined in the Windows Logo Program Requirements Suite Version 3. This level of compliance indicates to a customer that the product works well with Windows. The basic logo requirements ensure reliability, stability, security, and proper installation, as well as implements functionality that take advantage of some of the latest Windows innovations.
The "Windows Vista Basic" logo for systems and the "Works with Windows Vista" logo for devices ensure hardware and devices have been tested to Microsoft standards and proven to work. Certified hardware partners can distribute device driver software on Windows Update and take action on device driver performance feedback from Windows Vista customers.
An example is no stop errors, proper installation, and proper removal. For audio devices, it would mean that it implements Universal Audio Architecture (UAA) and other functional requirements in Windows Logo Program Requirements Suite.
Note that for device categories defined in the Windows Logo Program documentation that have Basic logo requirements but no Premium logo requirements defined can only qualify for the "Works with Windows Vista" Basic logo. Though the requirement headers may have an 'R' in both Basic and Premium level, unless there is only an 'R' in the Premium, the device will only qualify for a Basic logo.
"Windows Vista" and "Certified for Windows Vista" Premium logo level
A product being tested is deemed compliant when it meets the premium logo requirements (previously known as "gold" logo level) as defined in the Windows Logo Program Requirements Suite. This level of compliance indicates to a customer that the product enables additional or enhanced capability with Windows, thereby enabling a premium experience.
For audio devices, although the basic logo includes requirements for basic audio support, the premium logo includes requirements to support high fidelity to enhance the audio experience.
Unclassified Program
Devices from device categories that are not currently defined as part of the Windows Logo Program requirements are allowed to submit drivers for signatures under the Unclassified Program. The driver will be validated against a core set of driver tests to validate stability under Windows Vista. For more information, see Unclassified Signature Program.
Windows Codenamed "Longhorn" Server Logo Program
For the Windows Longhorn Server operating system, a product meets the logo compliance level as described below:
A system or device being tested is deemed logo'd when it meets the logo requirements as defined in the Windows Logo Program Requirements Suite. The logo requirements ensure reliability, stability, security, and proper installation, as well as implements functionality that take advantage of some of the latest Windows innovations.
A separate submission is required with the necessary test logs if any device must be logo'd for client and server.
(Announcement date: September 20, 2006)
Windows Logo Program Update - Version 3.06
-
Clarified TCP Chimney and RSS networking requirements. In each case, all relevant requirements are required if implemented.
-
Clarified server document to consistently refer to PCI 2.3.
-
Definition of motherboard category with list of relevant requirements.
-
AUDIO-0006; Updated with FUTURE implementation date of June 1, 2007; test logs are still required to be submitted but they are not required to pass. Values relaxed for Line Out crosstalk and updated notes section.
-
AUDIO-0008; Updated with FUTURE implementation date of June 1, 2007.
-
AUDIO-0025; Updated with FUTURE implementation date of June 1, 2007; test logs are still required to be submitted but they are not required to pass.
-
DISPLAY-0068. DISPLAY-0072, DISPLAY-0073, DISPLAY-0074, DISPLAY-0078, DISPLAY-0082, DISPLAY-0083, DISPLAY-0084, DISPLAY-0086, DISPLAY-0087, DISPLAY-0088; Relaxed DDC/CI to be required for Premium only for Display Devices. If Implemented for Basic.
-
DISPLAY-0071; Relaxed DDC/CI to be required for Premium only for Display Devices. Relaxed list of required VCP codes.
-
DISPLAY-0075; Relaxed DDC/CI to be required for Premium only for Display Devices. Relaxed list of required VCP codes. If Implemented for Basic.
-
DISPLAY-0076, DISPLAY-0077, DISPLAY-0079, DISPLAY-0080, DISPLAY-0081; Relaxed DDC/CI to be required for Premium only for Display Devices.
-
DISPLAY-0085; Clarified body of requirement to be consistent with If Implemented language.
-
GRAPHICS-0002; Updated with tables to clarify minimum graphics memory values.
-
GRAPHICS-0068; Updated range IDs for DirectX 9.0 and DirectX 10.0-compatible drivers.
-
NETWORK-0014 and NETWORK-0015; Clarified "if-implemented" for Basic.
-
NETWORK-0033; Removal of ISDN modem requirement.
-
STORAGE-0002 and STORAGE-0006; Clarifications based on industry feedback.
-
SYSFUND-0007; Updated with FUTURE requirement date for all Premium systems to ship with 1 GB of system memory by June 1, 2007.
-
SYSFUND-0033; Clarification of watchdog timer requirement.
-
SYSFUND-0044 and STORAGE-0005; future storage requirement has been updated as "Premium Storage offering" and includes option of either Hybrid Disk Drive or Solid State HDD. The effective date has been set as June 1 2008.
-
SYSFUND-0046; Updated with FUTURE implementation date of June 1, 2007 for Premium systems that ship with 512 MB of dedicated system memory; these systems are not required to ship with the Aero Theme enabled, however they are required to demonstrate that the Aero Theme can be supported during system testing. Tables updated with clarifications based on partner feedback.
-
SYSFUND-0047; FUTURE requirement date for Desktop Consumer and Business systems was incorrect, updated to June 1, 2007; Mobile date unchanged.
-
SYSFUND-0048, SYSFUND-0050; Updated with FUTURE implementation date of June 1, 2007.
-
SYSFUND-0057; Updated with a note on pre-OS boot behavior of exposed audio volume control.
-
SYSFUND-0118; Updated with FUTURE implementation date of June 1, 2007; test logs are still required to be submitted but they are not required to pass. Values relaxed for Line Out crosstalk and updated notes section.
-
SYSFUND-0118; Clarified reference to future logo requirements.
-
SYSFUND-0127; Updated with FUTURE implementation date of June 1, 2007; test logs are still required to be submitted but they are not required to pass.
-
SYSFUND-0137; Relaxed requirement for integrated auxiliary displays to support S4.
-
SYSFUND-0163; Clarified language based on industry feedback.
(Announcement date: September 6, 2006)
New Hardware Start Button Specification Released
Version 1.01 of the Windows Vista Hardware Start Button Specification has been released. It is available on the Windows Logo Program Requirements page.
(Announcement date: September 6, 2006)
Windows Logo Program Update - Version 3.05
New requirement clarifications and modifications have been published in Version 3.05 of the Windows Logo Program Suite, now available for download from the WHDC Web site.
-
SYSFUND-0007 - Updated with table to clarify intent of details for minimum memory requirements on a system
-
SYSFUND-0035; SYSFUND-0135 - Clarified wording to specify operating system installation
-
SYSFUND-0042 - Added "or DVB-S" to requirement details to allow for DVB-S regions, clarified title to be specific to systems that expose Windows Media Center and ship a Premium Logo TV tuner
-
SYSFUND-0043 - Moved Ultra-Mobile system to "if-implemented"; these systems are not required to have an exposed USB port
-
SYSFUND-0137 - Updated to include details for Basic auxiliary displays; they are not required to support functionality while system is in S5 (power off)
-
AUDIO-0048 - Updated with link to documentation
-
AUDIO-0051 - Updated with additional "Design and Implementation Notes" details
-
GRAPHICS-0001 - Clarified details text regarding S-Video and composite video output interfaces and expected support for proprietary connectors
-
GRAPHICS-0007 - Added note to requirement for Ultra-Mobile PC solutions, which have effective date of June 1, 2007 in the Client system document
-
IMAGING-0013; IMAGING-0004 - Updated Excel spreadsheet to reflect what is in the logo document
-
INPUT-0006; INPUT-0007 - Added "or DVB-S" to requirement details to allow for DVB-S regions
-
NETWORK-0052; NETWORK-0057; NETWORK-0060; NETWORK-0064 - Updated Excel spreadsheet to reflect what is in the logo document
-
NETWORK-0092-0119 - TCP Chimney requirements updated to "if-implemented" for server form factors
-
NETWORK-0120-0124 - RSS NIC requirements updated to "if-implemented" for server form factors
-
STREAM-0010 - Clarified details section for a small buffer size to be used for compressed video streams; this does not apply to uncompressed video
-
STREAM-0014 - Clarified title and details for a graph to support multiple instances while in stop mode
(Announcement date: August 8, 2006)
Engage with the Serial ATA International Organization for SATA Device Testing
Microsoft is partnering with the Serial ATA International Organization (SATA-IO) group for pretesting of Serial ATA (SATA) hard drives, SATA optical drives, and SATA controllers for the Windows Logo Program. Manufacturers are strongly encouraged to immediately engage with this standards organization and begin testing devices and controllers. Moving to this third-party testing model has many benefits, including shorter testing time, requirements that stay current as technology advances, experts at SATA IO who can help debug issues with hardware and, most of all, end users benefiting from high-quality components that "just work."
What is SATA?
-
SATA is an evolutionary replacement for the Parallel ATA physical storage interface. SATA-IO is the group that develops, manages, and drives adoption of the Serial ATA specifications. Users of the SATA interface benefit from greater speed, simpler upgradeable storage devices, and easier configuration.
-
The goal of SATA-IO is to drive industry adoption by defining, developing, and delivering standardized specifications for the SATA interface.
What type of testing does SATA-IO do, and when is logo pretesting required?
-
Bus-level testing can be accomplished only by trained personnel who are using sophisticated and expensive bus analyzers. SATA-IO provides electrical, mechanical, protocol, and system interoperability testing. Microsoft storage tests cannot test for electrical behavior of the device in Windows.
-
SATA-IO handles issues with test problems, has committed to having bi-annual interoperability workshops, and has year-round test facilities. Testing programs have started for devices and will begin in the third quarter of 2006 for controllers.
-
SATA-IO testing will be required for SATA devices on June 1, 2007. However, Driver Test Manager (DTM) will ask manufacturers of SATA devices for the SATA-IO certificate file at Windows Vista launch. Partners that do not perform SATA-IO testing will fail the test; however, the storage team will incorporate an errata cleaner to remove the failure until June 1, 2007.
(Announcement date: July 25, 2006)
Microsoft Releases New Logo Program Requirements for RFID Devices and Printers
Microsoft has released two requirements for Radio Frequency Identification (RFID) devices and printers for Microsoft Windows Vista. These newly created requirements are being released for the first time, and we encourage partners to review and provide feedback to Microsoft. The logo program for RFID devices and printers is expected to begin in 2007 when the tests will be added to the Windows Driver Kit (WDK). The new requirements are in version 3.04 of the Windows Logo Program Device Requirements for Windows Vista Client and Windows Server code named "Longhorn," which is available for download on Windows Logo Program Requirements V. 3.0.
(Announcement date: July 25, 2006)
Windows Logo Program 3.0 Update - Version 3.03
These Logo Program requirement clarifications and modifications can be reviewed in the revised release of the Windows Logo Program Suite 3.03, published on WHDC Web:
-
GRAPHICS-0034 - Clarification and reduction to list of entries that the Windows Display Driver Model (WDDM) driver must populate in the registry and INF
-
DISPLAY-0023 - Removed from Windows Logo Program
-
DISPLAY-0024; DISPLAY-0025 - Removed reference to enhanced auxiliary display
-
DISPLAY-0026 - Removed from Windows Logo Program
-
DISPLAY-0028 - Updated to reflect language in the Windows Driver Kit (WDK)
-
DISPLAY-0029 - Removed from Windows Logo Program
-
INPUT-0007 - Updated text to clarify expected behavior of IR receiver and transceiver
-
NETWORK-0046 - Text updated for clarification
-
SYSFUND-0090 - Updated in server document to match system document
-
IMAGING-0004; IMAGING-0010 - Relaxed to "if implemented" until June 1, 2007
-
NETWORK-0045 - Text clarified to allow secondary network adapter to be 10/100
-
STREAM-0010 - Updated text to clarify intent of requirement
-
STREAM-0014 - Updated title and text to be specific to TV tuner filters
-
STREAM-0023 - Updated text to note either UYVY or YUY2, and removed design note
(Announcement date: July 13, 2006)
Clarification on the Windows Logo Program Requirements for Vista--Final
In May 2006, we released the Windows Logo Program Requirements Version 3.0, Revision 1.0 suite of documents for Client, Server, and Devices. Based on feedback from partners and customers testing on Beta 2 of Windows Vista, we have subsequently released two updates to the requirements. The primary intent for these revisions is to keep the industry aware of changes to the requirements as soon as possible based on feedback from Beta 2. To date, the updates to the Windows Logo Program requirements have addressed the following:
-
Clarifications of the intent through additional information provided as a part of the requirement.
-
Relaxation of some or part of the requirements where appropriate, based on the feedback and where the relaxation does not materially impact the quality and customer experience scenarios in any significant manner.
-
Corrections of typographical errors.
-
Introduction of new requirements for future implementation (these are not effective for Windows Vista).
It is difficult to predict how many more such changes could occur before the release of Windows Vista, but please note the following:
-
In the recent updates, no new hardware requirements have been introduced that impact Windows Vista.
-
Partners who have planned their product designs based on Windows Logo Program Suite 3.0, Revision 1.0 should be able to continue with their plans because any updates only relaxed the requirements. Products designed for Windows Logo Program Suite 3.0, Revision 1.0 should meet the test criteria.
-
We do not anticipate any changes to the requirements that impact Windows Vista after Release Candidate 1 (RC1), at which time you should be able to begin making the submissions for logo.
If you have feedback or concerns, please contact the Windows Hardware Logo Program team at logofb@microsoft.com.
(Announcement date: July 13, 2006)
Older Windows Logo Program Requirement Updates
To view Requirement Update releases older than those shown here, please go the the Windows Logo Program Newsletter Archive and review announcements included in the archived newsletters.
