WLP Policies

Policies for Windows Hardware Logo Program
June 22, 2007
Logo Policy
Abstract
This paper lists Windows Hardware Logo policies related to PC system or device testing, legal agreements, and billing.
These policies are intended for testers and account administrators who run Microsoft compatibility tests and submit
packages to Microsoft for the Windows Hardware Logo Program. These policies apply to submissions made using the
Hardware Compatibility Tests (HCT), the Display Compatibility Tests (DCT) and the Driver Test Manager (DTM), part of
the Windows Driver Kit (WDK).
This information applies for the following operating systems:

Windows Vista™
Contents
Audit Policies...................................................................................................................................................................................... ..........2
Billing Policies..................................................................................................................................................................... .........................3
Hardware Refresh Policies................................................................................................................................................................. ..........6
Legal Agreement Policies.................................................................................................................................................................... .........9
Product Listing Policies.......................................................................................................................................................... ....................10
Product Naming Policies............................................................................................................................................................................ .11
Reseller Submission Policies.................................................................................................................................................. ...................13
Testing and Submission Policies.................................................................................................................................................. ..............14
Disclaimer
This is a preliminary document and may be changed substantially prior to final commercial release of the software described herein.
The information contained in this document represents the current view of Microsoft Corporation on the issues discussed as of the date of publication.
Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft
cannot guarantee the accuracy of any information presented after the date of publication.
This White Paper is for informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE
INFORMATION IN THIS DOCUMENT.
Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of this document may be
reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording,
or otherwise), or for any purpose, without the express written permission of Microsoft Corporation.
Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document.
Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give you any license to these
patents, trademarks, copyrights, or other intellectual property.
Unless otherwise noted, the example companies, organizations, products, domain names, e-mail addresses, logos, people, places and events depicted
herein are fictitious, and no association with any real company, organization, product, domain name, email address, logo, person, place or event is
intended or should be inferred.
© 2007 Microsoft Corporation. All rights reserved.
Microsoft, Windows, Windows NT, Windows Server, and Windows Vista are either registered trademarks or trademarks of Microsoft Corporation in the
United States and/or other countries.
The names of actual companies and products mentioned herein may be the trademarks of their respective owners.
Policies for Windows Hardware Logo Program - 2
Audit Policies
Logo Requirements - Logo Policy - Audit Policies
POLICY-0009 Version 1 Audit Policy
Effective Date: 01-Jun-2007 Consumer Business
All- All-
Ultra Ultra Ultra Ultra
Expiration Date: Client Desktop Mobile in- Desktop Mobile in-
Portable Mobile Portable Mobile
Device PC PC one PC PC one
PC PC PC PC
PC PC
Basic R* R* R* R* R* R* R* R* R* R* R*
Status: Approved Premium R* R* R* R* R* R* R* R* R* R* R*
Audit Selection
Any device (any hardware ID) included in a device or system submission, reseller, or marketing name submission can be
selected for an audit. If a product is selected for an audit it may be purchased at retail by Microsoft, or it may be requested
to be shipped from the submitter, at the submitter's expense, including all shipping charges.
Microsoft reserves the right to specify the exact product name or hardware ID of the product to be submitted for audit.
Audited hardware will be returned to the submitting company if requested by the company and all packaging and shipping
charges are paid. Microsoft assumes no liability for returned hardware that is damaged during testing.
In all instances when an audit is requested the product must be provided as configured for shipping to the consumer
(retail packaging). In the case of system audits, the retail package and retail BIOS must be provided. Any special
instructions required to configure the device or system for testing using the test manager should also be included with the
audit hardware.
Audit Failures Not Corrected

Microsoft will notify partners what fixes are required to bring the product back into compliance and the timeline that those
updates must be made. If the requested changes are not made in the prescribed timeline, then the product is removed
immediately from the Microsoft Catalogs or Tested Products Lists. The Microsoft Windows logo must be removed from the
product and all packaging and promotional materials associated with that product. Microsoft will send official notification of
the action required by the audited company.
Billing Policies
Logo Requirements - Logo Policy - Billing Policies
POLICY-0010 Version 2 Submission Fee, Invoices, and Billing Policy
All- All-
PC PC PC PC
PC PC
Submission Fee
The minimum fee per submission is $250 for a device or system submission. Fees must be paid in U.S. funds by check or
wire transfer. Submissions under $750.00 (U.S.) are allowed to use credit cards. Fees are charged on a per-submission
basis, each submission will be billed according to the number of OS-families included in the submission. Localized driver
packages may be included with any submissions without any extra charge.
Operating Systems Accepted Testing fee OS Family Group Price
Windows Vista x86 $250.00 One fee if submitted together
Windows Vista x64 $250.00
Windows XP x86 $250.00 One fee if submitted together
Windows XP x64 $250.00
Windows Server 2003 x86 $250.00 One fee if submitted together
Windows Server 2003 x64 $250.00
Windows Server 2003 IA-64 $250.00
Windows 2000* (client or server) $0.00 Must be an integrated driver and
submitted with another OS at
the same time.
Enterprise Qualification Program (EQP) $100.00 $100.00
Reseller program test submissions ** $100.00 $100.00
* Must be submitted with another Operating System

**$100.00 per submission regardless of the number of operating system families submitted.
EXAMPLE 1: Windows Vista System Submissions, Business and Consumer test suites (testing logs may be
created separately or simultaneously)
A single submission including Charge
Windows Vista x86 $250.00
Windows Vista x64 No additional fee
Total $250.00
EXAMPLE 2: Windows XP, all OS families and Windows 2000 Server

Windows XP Professional x86 $250.00
Windows XP Professional x64 $0.00
Windows 2000 Server $0.00
Total $250.00
EXAMPLE 3: Windows Vista and Windows 2003 Server, multiple-OS families

Windows Vista x86 $250
Windows Vista x64 $0
Windows Server 2003, x86 $250
Windows Server 2003, x64 Enterprise Edition $0
Windows Server 2003, IA-64 Enterprise Edition $0
Total $500.00
Invoice Details
Invoices are mailed once a quarter (four times per year) shortly after the following dates:
• First quarter invoices are mailed after March 31.
• Second quarter invoices are mailed after June 30.
• Third quarter invoices are mailed after September 30.
• Fourth quarter invoices are mailed after December 31.
All invoices are due 30 days from the date of the invoice.
Non-Payment
If there is a dispute with a charge the partner needs to contact whqlbill@microsoft.com immediately. The undisputed
portion of the bill should be paid in the 30 day window, with the resolved disputed portion paid within 30 days of resolving
the dispute. Delinquent accounts are blocked from further submissions. Non-payment is grounds to terminate the Logo
License agreement and close the Winqual account.
Billing Information
Billing information will be sent to the contacts listed in the billing section of the Winqual Web site.
Invoices are billed to the division referred to as the “billing group” on the Winqual site for each organization. We use the
billing group contact email and physical address for all invoices, along with the email addresses of the individuals that
initiated the submission.
Companies that want billing information to be sent to more than one person may enter multiple addresses inside the
billing group’s e-mail address field, separated by a semicolon, for example:
“someone@example.com;tester@example.com”. Invoices are mailed to the physical address listed in this section
(invoices are not sent by E-mail).
To update the billing group information on Winqual, follow these steps:
1. Winqual Administrator may login to the Winqual account
2. Click Member Services
3. Click Billing Groups
4. Change: Billing Group Information
Fee Payment Instructions
Testing fees for submissions made during each quarter are billed at the end of the quarter by Microsoft (there are no
ongoing membership fees). Fees are for reviewing your submission, this work is done regardless of whether the
submission passes or fails; therefore, a fee will be charged in either case. You must pay for all test submissions
regardless of the final test result. Please send any questions regarding billing to whqlbill@microsoft.com.
Use the following information to pay invoices:
Send checks to:
Microsoft Corp.
PO Box 198208
Atlanta, GA 30384-8208
If you use a service that requires a signature on delivery (such as FedEx), send checks to:
Microsoft - Lock box 198208
6000 Feldwood Rd
Atlanta, GA 30349-3652
Send wire transfers to:
Microsoft Corporation
Account# 3751385314
ABA# 11100001-2
Tax ID: 91-1144442
c/o Bank of America
901 Main Street
Dallas, TX 75202
United States
Purchase Orders
Winqual does not require purchase order (PO) numbers. If your company requires a PO number to be referenced on your
invoice, the person making the submission must enter the number when the submission is made. PO numbers that are
entered will appear on the invoice. PO numbers are referenced for convenience only. Microsoft is not responsible for
ensuring that the correct number is entered. Companies that require a PO to be completed for internal processes may
make purchase orders payable to the Windows Logo Program for Hardware, as listed below:
Microsoft Corporation
Windows Logo Program for Hardware
One Microsoft Way
Redmond, WA 98052
Fax (425) 936-7329
Partners should not mail or fax copies of purchase orders to Microsoft. Purchase orders that are sent to this address or
faxed to the Microsoft fax number will be discarded and no tracking will be done.
Hardware Refresh Policies

Logo Requirements - Logo Policy - Hardware Refresh Policies
POLICY-0016 Version 2 Logo Life Span
All- All-
PC PC PC PC
PC PC
Basic R R R R R R R R R R R
Status: Approved Premium R R R R R R R R R R R
A device or system that has received the Windows logo may continue to display that logo as long as the partner and
Microsoft support the product and operating system respectively.
The product must be tested for each OS for which the product would be authorized to display the logo based on such
qualification.
The terms of the Logo License Agreement and Test Agreement will govern the overall validity on the usage of the
logo.
Design and Implementation Notes
POLICY-0017 Version 1 Acceptable system updates for client systems

All- All-
PC PC PC PC
PC PC
Systems are allowed to update components without resubmitting for the logo as long as they meet the system update
criteria defined below.
Allowable System Update Criteria

• Components on the motherboard may not be replaced without resubmission. A motherboard may be de-featured
without a resubmission.
• Changing processor of the same architecture (vendor, pin config, instruction set) is acceptable.
• Changing memory configuration, as long as the minimum requirements for memory are met, is acceptable.
• Changing disk capacity is acceptable.

• Plug-in components covered with a valid logo program can be swapped with other logo’d components of the same
category as long as they correspond to and have qualified for the same logo level (for example switching a “Certified
for” graphics card with another “Certified for” logo’d graphics card).
• Devices swapped out in a system must be logo-qualified and capable of passing the logo standard from the same
period as the system or later.
o For example, a system that is logo qualified under the 1 June 2008 requirements must be shipped with devices
and drivers that meet the 1 June 2008 requirements or later. They may not ship with devices that were logo
qualified under the previous 2006 or 2007 logo requirement refresh period and could not pass the current
standard.
o A device which was logoed the previous year but is in a category where the logo standards did not change, and
therefore would be capable for passing the current standard is acceptable
o In the case of new requirements previously untested the device is still expected to meet the new requirements if
subjected to an audit.
Allowable Performance Range on Acceptably Updated Premium Systems

• Acceptably changed premium systems must show similar or better performance than the originally submitted system.
Microsoft is defining the performance metric as memory bandwidth throughput performance, measured using the
AeroAT test tool.
• The updated system cannot fall below 1600 Mb/s and continue to be labeled premium.
• There is no upper limit to performance improvement over the originally submitted system.
Updates NOT Permitted

The following updates trigger a resubmission:
• Motherboard, Firmware or BIOS updates except for string, splash screen or minor bug fixes. Specifically disallowed are
changes to ACPI, Plug and Play, and power management functionality.
• Swapping of components that are not covered under a logo program (for example, components that have qualified
under unclassified cannot be swapped).
System updates that require re-submission

When resubmission is triggered by BIOS changes or changes in unclassified components, the system may still be
considered an update if the motherboard is unchanged. As an update, the original requirements at the time of the original
submission are still the standards to be met. This means the submission must be tested using the current test kit, but
failures caused by not meeting the new requirements since the original submission, are waived. Any contingencies or
errata waiving conditions that were in effect at the original submission will be applied to the resubmission.
The submission should be accompanied by a README file containing the original submission ID. The failures will trigger
a manual review, comparing the motherboard devices to the original and reviewing the failures to determine if they are
exclusively caused by the higher standard. Partners should expect a significantly longer turn-around time because of the
nature of these reviews.

See also POLICY-0015, POLICY-0016 and POLICY-0018 for related information.
Legal Agreement Policies

Logo Requirements - Logo Policy - Legal Agreement Policies
POLICY-0012 Version 1 Legal Agreement Policy
All- All-
PC PC PC PC
PC PC
Submissions on the Winqual Web site require certain legal agreements to allow Microsoft to test, or list products on
Microsoft catalogs and distribute drivers on Windows Update.
There are three main types of legal agreements that are required before creating submissions:
1. Testing agreements: To participate in the logo program, a company must have a valid testing agreement on file with
Microsoft.
2. Logo license agreements: To license the logo on a product, product packaging, or in related marketing materials, a
company must have a valid logo license agreement on file and a corresponding product exhibit with Microsoft must
be signed during each submission. Contingencies granted as considered as addendums to the Logo License
Agreement.
3. Technology specific agreements: To license the Windows flag on a keyboard, a company must have a valid
Windows Start Button Logo License Agreement in place. To receive a digital signature for Audio solutions, a valid
WHQL Testing Agreement for Digital Rights Management (DRM) must be in place. Other license agreements may
apply.
Companies participating in the logo program for hardware must review the specific terms of each legal agreement.
All agreements may be downloaded for review purposes from the menu on the Winqual Website.
To accept the legal agreements, establish a Winqual account and designate a director from the company to accept legal
agreements on the company’s behalf. Users with the “Sign Master Legal Agreements” permission can accept legal
agreements for an organization
Questions about the legal agreements should be sent to WHQLegal@microsoft.com.
To see the latest agreements on Winqual please visit https://winqual.microsoft.com/member/LAC.

Product Listing Policies

Logo Requirements - Logo Policy - Product Listing Policies
POLICY-0013 Version 2 Product Listing Policy
All- All-
PC PC PC PC
PC PC
Status: Approved Premium R* R* R* R* R* R* R* I R* R* R*
For logo-qualified products to be listed in the Windows Marketplace, Windows Server Catalog, Windows Tested Products
List or the Hardware Compatibility List the product must meet the following requirements:
• Pass logo testing.
• Submitting company must accept the logo license agreement.
• Product will be listed after the announcement date provided by the submitter.
Previously announced products will be removed for the Windows Marketplace, Windows Server Catalog, Windows Tests
Products List or Hardware Compatibility List if the product fails audit, trademark violations, product does not go to market,
or if the Logo License Agreement is terminated.
Note that products submitted under the “Unclassified” submission category are not eligible to receive a product listing or
use a Microsoft logo. Specific verbiage is also reserved for products that meet the above criteria, if a product has not been
"Certified for Windows" logo-qualified then language such as "Certified", "Certified for", or "Certified with" may not be used
on promotional materials or product packaging.

See Windows Quality Online Services at https://winqual.microsoft.com/Default.aspx.
Product Naming Policies

Logo Requirements - Logo Policy - Product Naming Policies
POLICY-0014 Version 2 Product Naming Policy
All- All-
PC PC PC PC
PC PC
The product name of a device or system must uniquely identify one specific device or system. If a company produces
several distinctly different products under a given name, the most distinct product name should be used. Microsoft
recommends including a model name or number to uniquely identify the individual device or system. After a submission
has passed testing, additional marketing names may be added. Any marketing name listed may be subject to audit by
Microsoft.
End User Customers use the Microsoft Windows Server Catalog or the Windows Marketplace Tested Products List to
readily identify and find products licensed to use the Microsoft Designed for Windows logo. These databases are also
used for other purposes within and external to Microsoft. For example, Microsoft uses the Windows Server Catalog or
Windows Marketplace Tested Products List when U.S. Customs verifies with Microsoft that products coming into the
country are licensed to use the Designed for Windows logo. For these reasons as well as others, Microsoft requires that
the product name(s) listed on the Microsoft Windows Server Catalog or the Windows Marketplace Tested Products List be
detailed and accurate.
Product Name Requirements:
• A company may submit products only for itself and may not submit products on behalf of a third party.
For example, an independent testing lab that is used to test products for an OEM may not submit such products on
behalf of the OEM. The product must be submitted under the OEM account, and the OEM must accept any or all
agreements that apply to that product.
• At the time the submission is made, only a single product name can be entered.
• After the submission has passed testing, additional marketing names may be added by using the Product Listing
Wizard if all names meet the allowable change requirements posted for the category.
• The product name of a device or system must uniquely identify one specific device or system and must not be a
generic name.
For example, "Laser Printer" cannot be used as the product name of a laser printer. However, "Laser printer model
5003," "Laserprint 2893," and "QuickLine 2" are acceptable names.
• If a series name is included in the product name, then the product name must also include a model name or number
to uniquely identify that individual device or system. This requirement prevents confusion with other products in the
Windows Catalog.
For example, "Laserprint series" cannot be used as the product name of a laser printer. However, "Laserprint series
model 5003" and "Laserprint 2893" are acceptable names.
• The product name can include only the marketed product name, model number, and/or version number.
For example, a keyboard submitted with the product name "Quick-key" is acceptable. However, a submission that
includes multiple product names such as "Quick-key/Quick-key mobile, Quick-key 5000" is not allowed. The additional
names must be entered by using the Product Listing Wizard after the submission for "Quick-key" has passed testing.
• The product name cannot include any marketing slogans or tag lines.
• The product name cannot include any Microsoft trademarks.
• V.92 text can be included in the product name for modem device submissions only
In response to vendor feedback and testing concerns, WHQL now allows the text “V.92” to be used in modem device
product names. The submitter must fulfill one requirement, a support statement such as “this product meets all V.92
requirements” must be included in the readme file that accompanies the modem submission. If the submitter includes
V.92 in the product name and fails to include a support statement in the readme file included with the submission, the
submission will fail.
If a component in a system changes that does not meet the System Update Criteria, but the same product name is used,
the new motherboard and processor combination must be submitted separately and assigned a unique identifier that
should be placed somewhere on the machine to uniquely identify the submission and the corresponding hardware.

See "System Update Criteria", at POLICY-0017.
Reseller Submission Policies

Logo Requirements - Logo Policy - Reseller Submission Policies
POLICY-0008 Version 1 Reseller Submission Policy
All- All-
PC PC PC PC
PC PC
Status: Approved Premium R* R* R* R* R* R* R* I R* I R*
The Reseller Submission Policy allows companies that purchase a product from a manufacturer to resell the hardware as
their own and receive a listing in the Microsoft catalog and Hardware Compatibility List. Devices that have previously
earned the Windows logo under the original manufacturer's name can be repackaged and relabeled for the purchasing
company. Reseller submissions do not require testing and have a reduced processing fee. A reseller submission is
dependent on the parent submission. If the parent submission fails an audit, the reseller submission also fails.
Products submitted as a reseller submission must meet the following requirements:
• The reselling company cannot change the hardware or software when relabeling or repackaging the product, except for
branding or splash screen changes to identify the product under the new company name.
• If a reseller wants to change the driver, a new submission must be made. If the reselling company changes the INF file,
an entirely new driver submission package must be made for driver signing and Windows Update distribution.
• All reseller submissions are subject to audit.
See "How to Resell a Submission" in Winqual Help at https://winqual.microsoft.com/Help.
See the "Audit Policy", POLICY-0009.

Testing and Submission Policies

Logo Requirements - Logo Policy - Testing and Submission Policies
POLICY-0001 Version 1 General Logo Testing Policy
All- All-
PC PC PC PC
PC PC
Basic R R* R R* R* R R* R R* R* R
Status: Approved Premium R R* R R* R* R R* R R* R* R
Testing must be completed by the hardware manufacturer using the Windows Logo Kit (WLK).
Device submissions must include test logs and the corresponding device drivers with each submission. Devices that
utilize in-box drivers (drivers that are included with Windows) must be tested for compliance, but the drivers do not need
to be included in the submission package.
System submissions must include test logs with each submission.
The logo specifically applies to the hardware firmware and/or BIOS that were tested. To maintain the logo, the product
must be retested if the hardware, firmware or BIOS changes, with certain exceptions outlined in POLICY-0017.
Note The Driver Test Manager (DTM), which is part of the downloadable Windows Driver Kit (WDK), will be replaced by
the WLK. HCT/DCT submissions will not be supported by Microsoft after March 1, 2007 and HCT/DCT test results will not
be accepted after June 1, 2007.
POLICY-0002 Version 1 Windows Version Under Test Policy

Effective Date: 09-Mar-2007 Consumer Business
All- All-
PC PC PC PC
PC PC
The latest version of the Windows operating system must be used for logo testing unless an interim version is designated.
After release to manufacture (RTM) versions are available, release candidates or beta versions are not acceptable and
may result in failure of the submission. Submissions must be made with the latest available service pack within 90 days
after the public release of that Windows service pack. This policy applies to any version of Windows supported by the logo
program.
POLICY-0003 Version 2 Multifunction Device Test and Submission Policy

All- All-
PC PC PC PC
PC PC
Basic R R* R R* R* R R* R R* R* R
Status: Approved Premium R R* R R* R* R R* R R* R* R
Multi-function devices must pass testing for each functional unit contained in that device to qualify for the logo. Each
functional unit must test at the same qualification level or higher that the multi-function device is being submitted for, with
the following limitations when the functional units does not have matching qualification levels defined.
A "Certified for Windows" multi-function device must contain at least one "Certified for Windows" component, and all
components must pass testing at the highest logo level available for that component. For a "Works with Windows" multi-
function device there must be at least one "Works with Windows" component, all components must pass either "Certified
for Windows" or "Works with Windows" logo level testing. If a logo category is not defined or available for a given
component, it must qualify and be submitted for the unclassified signature.
For example, a "Certified for Windows" multi-function printer that supports scan and print functionality and has USB, IEEE
1394, and Network (Ethernet) connectivity meets the requirements for each functional unit on each connectivity type as
"Certified for Windows", unless a "Certified for Windows" qualification level is not defined for that technology, in which
case qualification as "Works with Windows" or Unclassified is acceptable.
Multi-function devices that include multiple interfaces or bus technologies must meet the qualification level of the device
for each interface or bus supported.
Each functional unit and connectivity type in a multi-function device must be tested and submitted for as a single
submission.
POLICY-0004 Version 2 Device Family Testing Policies

All- All-
PC PC PC PC
PC PC
The logo program policy requires that each family of devices be tested and submitted to Microsoft, even if the driver is
identical for each submission. If your INF contains devices that are considered different device families, but you do not
intend to test them, they should be removed from the INF.
What is a family?
A device product family is defined as a set of devices in which all the devices in the family would expose the same
functionality or a subset of functionality and would be tested in the same manner. In all cases, the most fully-featured
member of a device family must be the “tested representative” for the family. All devices that are a subset of the most fully
featured products must meet all logo requirements for its functionality.
How do I know when I need to treat a group of devices as a separate family?

Evaluate each device that is supported by the driver. If any of the following conditions apply, include in its own family:
1. If a device is manufactured by a different company.

2. If a device uses a different device class, PCI class and subclass, or vendor ID (VID).
3. If a device uses different driver binaries or uses a separate INF file.
4. If a device has different firmware.
5. If a device supports different bus protocols. If multiple protocols are supported, such as SCSI, iSCSI, or Fibre,
these protocols must be tested separately and are considered separate families.
6. If a device supports different media or drive types.
7. If a device supports multiple protocols, media, and drive types they must be tested separately and are
considered separate families.
The following devices have additional characteristics to classify families:
South Bridge SATA and ATA/ATAPI Controller Families

Controllers that are integrated into a South Bridge chipset must support the same base logic. If the driver supports an
add-in controller, the add-in must be tested as a separate family device.
RAID Controller, iSCSI Adapter, and Fibre Channel Adapter Families

Controllers that have identical core BIOS code and ASIC firmware may be tested as a single family. String changes to the
BIOS code are allowed between family members. If the BIOS code and/or firmware are updated, another family
submission is required.
Medium Changer Families

• Qualification for medium changers is specific to the drive type that is tested and submitted. Qualification with one drive
type does not qualify it with another drive type. If multiple drive types are supported and qualifications for these drive
types are required, these must be tested separately and are considered separate families.
• Medium changers may contain the following equipment changes and still qualify as a single family:
o Modules: If the library supports multiple frames or modules, only one frame or module is required.
o Drives: If four or fewer drives can be populated, the maximum number of drives is required. If more than four drives
can be populated, 25% of the changer's drive-carrying capacity is required to be filled with a minimum number of
four drives required.
o Buses: If multiple buses are supported, drives must be populated on each bus.
o Media: If 20 or less media can be populated, the maximum number of media supported is required. If more than 20
media can be populated, 10% of the media-carrying capacity is required to be filled with a minimum number of 20
media required.
RAID System and RAID JBOD Families

• The number of controller modules within the same family may differ.
• Controller hardware and firmware must be the same for a given family.
• If the controller hardware or firmware is virtual (consists of just software), any major revision of this software for added
functionality (such as bus speed) requires a new family group.
• Non multi-path or non-Microsoft MPIO drivers: A complete RAID System test must be completed against each RAID
System device included in the INF.
• Third Party multi-path and Microsoft MPIO driver implementations: A scaled test procedure is available to test
multiple families; see the corresponding section of the Multi-path test procedure for more information. This does not
grant base qualification or logo to these additional subsystems.

Device drivers often support more than one device, such as a printer driver that supports 10 different models of printers,
or a display driver that supports 25 different plug and play IDs. Microsoft recommends that vendors test each and every
device that is supported by a given driver to assure quality.
Microsoft recognizes that in a given device category there are cases where testing a model that is the most fully-featured,
or one that is physically and electrically identical to another model offers no increase in test coverage and no additional
hardware or driver flaws would be exposed by doing an additional test pass for logo qualification.
In an effort to simplify and reduce the amount of testing that is required to achieve a logo on each and every
hardware/driver combination, the following rules may be applied to your device testing coverage plan. Devices that are
considered equal to each other are referred to as a family of devices. A particular driver may have 100 unique plug and
play IDs in the INF, but after applying these device testing policies, you may find that there are only 10 devices that need
to be tested to achieve full test coverage for your device/driver combinations.
POLICY-0005 Version 2 Digital Signature and Windows Update Policy

All- All-
PC PC PC PC
PC PC
All submitted products, if shipped with Windows, must ship with Microsoft-signed device drivers or use inbox drivers.
Driver submissions are eligible to obtain digitally signed catalog files if they pass the test criteria defined by Microsoft and
they install using an INF file.
Logo-qualified device drivers are allowed to be distributed on Windows Update. Drivers submitted through the
Unclassified program may be distributed after consultation with Microsoft and with Microsoft's approval.
Microsoft strongly recommends that partners specify which driver is the best version to distribute on Windows Update.
The Winqual website has been revised to allow granular control of driver posting associated with each Plug and Play ID.
Microsoft may select specific drivers for each device to be distributed on Windows Update if required to ensure a better
customer experience on Windows or if there is no driver submitted by the partner.
See Driver Signing Requirements for Windows at http://www.microsoft.com/whdc/winlogo/drvsign/drvsign.mspx.
See Driver Installation at http://www.microsoft.com/whdc/driver/install/default.mspx.
See Specification for Use of PCI IDs with Windows Operating Systems at
http://www.microsoft.com/whdc/system/bus/PCI/pciidspec.mspx.
POLICY-0006 Version 2 Test Failures with Errata Policy

All- All-
PC PC PC PC
PC PC
Testing failures encountered during testing that are identified as a test failure, rather than hardware or driver failures,
should be brought to Microsoft’s attention by opening a service request with Customer Support Services (CSS). Once the
issue is researched and found to be a test error, an errata filter will be created and the filter can be used to clean the
Windows Logo Kit (WLK) test logs before submitting the results to the Winqual Web site.

Errata cannot be created for some test failures and will appear as a failure on automated review. If you encounter this
issue when submitting, CSS or Winqual support will provide details on how to properly document the failure for a manual
review.
DTM and WLK support is available via standard Microsoft product support channels. Details of available Microsoft
Services support options can be found at http://www.microsoft.com/services/microsoftservices/srv_support.mspx.
Customers with a Premier support contract should work with their TAM to open support incidents.
For non-Premier customers, Professional Support Options are listed at:

http://support.microsoft.com/default.aspx?scid=fh;EN-US;OfferProPhone including phone numbers and pricing
information.
For additional information see http://www.microsoft.com/whdc/whql/resources/support.mspx.
POLICY-0007 Version 2 Test Failure Contingency Policy

All- All-
PC PC PC PC
PC PC
A Contingency Agreement may be requested when a test failure has been determined to be caused by a problem with the
device or driver being submitted for logo, but the submitting partner believes it is in the best interest of the partner and
Microsoft to waive the requirement until it can be remedied. Contingencies may be granted for a limited period based on
an assessment of the technical issue and the related business needs after fully considering the customer impact and the
firm commitment from the affected partner to resolve the issues. Not all contingencies are approved.
The typical contingency review process takes 4 to 6 weeks, please plan in advance prior to making any requests.
Once a contingency is approved by Microsoft, a legal agreement is signed and a contingency filter is created which in
most cases will reverse a failure on submission (some may require manual review, depending on the nature of the failure).
Approved Contingencies are not covered under Non-Disclosure Agreement (NDA). Microsoft reserves the right to publish
the information regarding the affected hardware products.
To request a contingency for a failing submission, follow the procedures in the “Windows Logo Program Procedures and
Information” document. Requests for a contingency must include all the information detailed in the "How to request a
contingency" section of the document. Missing or incomplete information will cause a delay in the evaluation of the
request.
See "Windows Logo Program Procedures and Information" at TBD.
POLICY-0015 Version 2 Acceptable Device and Driver Update Policy

All- All-
PC PC PC PC
PC PC
During the time window between when a device/driver submission is originally made and the next logo refresh
date, certain changes are allowed to the driver package and submitted for signing without a retest. These are
changes to driver packages which add, remove, or modify files that do not interoperate with or otherwise
affect driver functionality or reliability. The files that may be added, modified, removed or replaced include .txt,
.htm, .doc, .rtf, .chm, .hlp, .INF, .jpg, .bmp, .cpl, .pdf, .mht ,or txtsetup.oem files. It is permissible to add new
hardware IDs in the INF as part of these updates, provided they meet the family policies.
Partners may change the name of the original manufacturer's driver files if the device hardware or driver
software has not changed. Full testing and submission is required if any files in the driver have been
recompiled.
The INF file itself may be modified and renamed. Partners must include a delta sheet of each file name
change and include a WinDiff log file for each renamed file in the Readme.doc. This WinDiff log will be
independently verified by comparing it to the original submission. Additionally INFtest must be run and the log
included in the submission (WinDiff and INFtest can be obtained from the WDK.)
Silicon chipset size reductions (die shrinks) are allowed, provided the device ID or subsystem device IDs are
unchanged, and no functionality is added or modified and the drivers are unchanged. If the die shrink would
impact other logo requirements, such as S3 resume time, the device requires a full retest and submission.
Changes that would require full testing and cannot be submitted under the Acceptable Device and Driver
Update policy include:
– Changes where driver binaries are modified and recompiled.
– Changes in device components, firmware or BIOS, with exceptions as noted in POLICY-0017.
– Changes in supported operating systems or I/O interfaces (also known as buses) not found in the original
submission.
The Winqual site changes to allow the return of driver updates should come online this summer.
See also POLICY-0016, POLICY-0017 and POLICY-0018 for related policies.
POLICY-0018 Version 1 Maintenance Signing

All- All-
PC PC PC PC
PC PC
Microsoft recognizes the need to maintain and improve drivers for devices after logo program expiration. A new
submission type is defined to allow drivers to be tested and submitted for signing after logo program expiration.
For a maintenance submission the original logo submission id is referenced. Any test assertions failed under the new kit
will be reviewed to assess if the original bar was met. If, on review, the failures are acceptable, the driver will be signed.
Restrictions:
• No PnP ids may be added to the INF.
• Driver may not be used with new product.
• No new product names will be entered into the catalog.
POLICY-0021 Version 1 Unclassified Program


All- All-
PC PC PC PC
PC PC
The Unclassified Program is designed to enhance system security and the overall customer experience by signing drivers
that:
• Pass the basic Windows driver reliability and stability tests

• Are submitted by partners that are registered with the Windows Logo Program
Device and drivers submitted through the Unclassified Program:
• Are not eligible to use the "Certified for Windows..." or "Works with Windows..." logo artwork.
• Are not automatically eligible to be posted to Windows Update without Microsoft approval.
• Will not be listed in the Windows Marketplace or the Windows Hardware Compatibility List.
• Must submit symbol files to assist in crash analysis.
• Will have Windows Error Reporting driver crash data available.
The Unclassified Program does not validate device or driver functionality. The Unclassified Program may not be used to
obtain a signature for a driver if a Basic or Premium logo program is defined for that device or driver category. Filters and
other application drivers are eligible for the Unclassified Program if the install using an INF file.

WLP Policies

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

WLP Policies

Uploaded by

Copyright:

Available Formats

Policies for Windows Hardware Logo Program

June 22, 2007

This information applies for the following operating systems:

© 2007 Microsoft Corporation. All rights reserved.

Audit Failures Not Corrected

* Must be submitted with another Operating System

A single submission including Charge

Windows Vista x86 $250.00

Windows Vista x64 No additional fee

EXAMPLE 2: Windows XP, all OS families and Windows 2000 Server

A single submission including Charge

Windows XP Professional x86 $250.00

Windows XP Professional x64 $0.00

Windows 2000 Server $0.00

EXAMPLE 3: Windows Vista and Windows 2003 Server, multiple-OS families

Windows Vista x86 $250

Windows Vista x64 $0

Windows Server 2003, x86 $250

Windows Server 2003, x64 Enterprise Edition $0

Windows Server 2003, IA-64 Enterprise Edition $0

Hardware Refresh Policies

Design and Implementation Notes

POLICY-0017 Version 1 Acceptable system updates for client systems

Allowable System Update Criteria

• Changing disk capacity is acceptable.

Allowable Performance Range on Acceptably Updated Premium Systems

Updates NOT Permitted

System updates that require re-submission

Design and Implementation Notes

Legal Agreement Policies

Design and Implementation Notes

Questions about the legal agreements should be sent to WHQLegal@microsoft.com.

To see the latest agreements on Winqual please visit https://winqual.microsoft.com/member/LAC.

Product Listing Policies

Design and Implementation Notes

Product Naming Policies

Product Name Requirements:

Design and Implementation Notes

Reseller Submission Policies

Design and Implementation Notes

See "How to Resell a Submission" in Winqual Help at https://winqual.microsoft.com/Help.

See the "Audit Policy", POLICY-0009.

Testing and Submission Policies

POLICY-0002 Version 1 Windows Version Under Test Policy

POLICY-0003 Version 2 Multifunction Device Test and Submission Policy

Design and Implementation Notes

POLICY-0004 Version 2 Device Family Testing Policies

How do I know when I need to treat a group of devices as a separate family?

1. If a device is manufactured by a different company.

South Bridge SATA and ATA/ATAPI Controller Families

RAID Controller, iSCSI Adapter, and Fibre Channel Adapter Families

Medium Changer Families

RAID System and RAID JBOD Families

Design and Implementation Notes

POLICY-0005 Version 2 Digital Signature and Windows Update Policy

Design and Implementation Notes

See Driver Signing Requirements for Windows at http://www.microsoft.com/whdc/winlogo/drvsign/drvsign.mspx.

See Driver Installation at http://www.microsoft.com/whdc/driver/install/default.mspx.

POLICY-0006 Version 2 Test Failures with Errata Policy

Design and Implementation Notes

For non-Premier customers, Professional Support Options are listed at:

For additional information see http://www.microsoft.com/whdc/whql/resources/support.mspx.

POLICY-0007 Version 2 Test Failure Contingency Policy