Windows Logo Program for Hardware FAQ

To correct this error, update the digital certificate that you have on file by following the directions at:

https://winqual.microsoft.com/help/default.htm#Updating_your_Digital_Certificate.htm

After you update your VeriSign ID, close all Internet Explorer browser windows, and then revisit the Winqual Web site. You will now be able to upload your submission.

All legal agreements must be signed online.

Note: You are no longer required to send the agreement copy to Microsoft by fax.

To sign the agreement online at any time:

If you do not see the Legal Agreements link or a text box for signing a particular agreement, the appropriate permissions might not be enabled for your account.

To receive permission to sign legal agreements, ask your company's administrator to do the following:

DUA means Driver Update Acceptable submission.

For an already-approved submission, this type of submission lets you make changes only to the INF file. You cannot change the driver binaries (such as .sys, .dll, and so on).

No test log files, and therefore no Readme.doc file, are required for a DUA submission. The Winqual Submission Tool (WST) tests some of the same things that ChkINF does. On the back end, the Winqual site performs a Windiff to make sure that no binaries have changed.

The charge for a DUA submission is $250 for each operating system family. We do not charge per driver package. For example, if you submit for Windows XP x86 and Windows XP x64, the charge is $250. If you submit for Windows Vista and Windows Server 2008 x86, the charge is $500.

The Reseller Submission Policy lets a company that purchases a product from a manufacturer resell the hardware as its own and receive a listing in the Windows Vista Compatibility Center and Windows Logo’d Product List. To repackage and re-label a device that previously earned the Windows logo, you must make a reseller submission. This submission does not require testing and has a reduced processing fee.

A reseller submission must meet the following requirements:

You can resell a submission to any third-party vendor who has an established Winqual account.

For directions on how to resell a submission, go to:

https://winqual.microsoft.com/Help/default.htm#How_to_Resell_.htm

For directions on how to accept a resold submission, go to:

https://winqual.microsoft.com/Help/default.htm#How_to_Accept_Resold_Submission.htm

For directions on how to decline a resold submission, go to:

https://winqual.microsoft.com/Help/default.htm#How_to_Reject_Resold_Submisson.htm

You can change the company name associated with your Winqual account as long as the ownership of the company has not changed.

Have the administrator log on to your Winqual account and navigate to Member Services > Billing Groups > Change: Billing Group Name.

If company ownership changes, you must establish a new Winqual account. You can establish an account on the Winqual site by going to:

https://winqual.microsoft.com/signup

You can add or remove your submissions to Windows Update through the Driver Distribution Center by following these steps:

You must sign the submission package with a VeriSign certificate before you upload the submission to Winqual.

A new signing tool (signtool.exe) has replaced the previous tool (signcode.exe). Note that signtool.exe is available as part of the Windows Device Kit (WDK) and that Microsoft no longer supports signcode.exe.

You can download the WDK and signtool.exe tool, along with many other useful code-signing tools at:

http://www.microsoft.com/whdc/DevTools/WDK/WDKpkg.mspx

For instructions on how to sign code by using signtool.exe, go to:

https://winqual.microsoft.com/Help/code-sign_files_with_your_verisign_id.htm

To prepare a system to use test-signed drivers when that system is currently running a Windows operating system:

Note: In Windows Vista, you must be logged on to the local administrator account.

VeriSign Organizational Certificate Digital ID ($99 USD) is available at:

http://www.verisign.com/code-signing/msft-organizational-certificates/index.html

This digital ID is used only by Winqual and is valid only for establishing an account for your company in Winqual. You cannot use this digital ID for hardware submissions.

VeriSign Microsoft Authenticode Code Signing Digital ID ($399 USD) is available at:

http://www.verisign.com/code-signing/msft-partner-code-signing/index.html

This digital ID is more versatile and is the accepted standard for establishing ownership of code.

Some applications in Winqual (such as hardware logo and driver reliability signatures) require a Class 3 code signing certificate. Using a code signing certificate enables you to digitally sign your 32-bit or 64-bit .exe (PE files), .cab, .dll, and .ocx files.

You can find additional information at:

https://winqual.microsoft.com/help/default.htm#obtaining_a_verisign_class_3_digital_id.htm

The information is filled in after the agreement has been signed.

After your submission is complete, you can view the agreement by logging on to your Winqual account and navigating to Member Services > Legal Agreements. Use the submission ID search on the right side of the page.

Unfortunately, certificates that VeriSign did not provide are not compatible with the Winqual site. A VeriSign ID is required to establish an account and to upload any files to the site so that we can accurately verify that it is from your company.

You can find additional information at:

https://winqual.microsoft.com/help/default.htm#obtaining_a_verisign_class_3_digital_id.htm

Winqual tries to provide a two-business-day turnaround. However, we are closed on the weekends, and submissions are not considered late until after seven days. More information is available at: Windows Logo Program Requirements and Policies.

To obtain help with the WLK, open a support case with CSS. They will provide technical support.

Customers who have a Premier support contract should work with their Technical Account Manager (TAM) to open support incidents.

For customers who do not have a Premier support contract, professional support options, including telephone numbers and pricing information, are available at:

http://support.microsoft.com/oas/default.aspx?&prid=11880

If we determine that the support issue is related to Microsoft, you will not be charged for the services. We either do not charge for the service or credit your account if a charge has been made. Some examples of Microsoft-related issues are a test issue, errata being processed or errata filter not working, a documentation issue, or a WLK product issue.

A logo-certified, Winqual-signed driver does not expire. Only a test-signed driver has an expiration date.

The code that checks the digital signature examines the time stamp and verifies that the signature was applied during the valid time period of the certificate. If no time stamp exists, the code uses the expiration date of the certificate.

The .cat file remains valid as long as you do not modify the .inf file.

If the Driver Test Manager (DTM) support team identifies a failure in your submission but informs you that we will overlook the failure, use the following process:

A signed catalog file (.cat) is used as a digital signature for an arbitrary collection of files. A .cat file contains a collection of hashes or thumbprints that correspond to a file in the collection.

Device installation recognizes the signed .cat file of a driver package as the digital signature for the driver package. Each thumbprint in the .cat file corresponds to a file that the driver package installed, regardless of the intended operating system.

The Purchase Order field has no restrictions or format. The field is for your use only to help you identify individual submissions.

Here is a list for your use.

We use the Announcement Date to know when to announce your product in HCL. If you do not want to announce your product in HCL, leave this field blank.

You can check announced products at:

https://winqual.microsoft.com/HCL

Firmware Version is an optional field, but you can determine the version from one of the devices in the .inf file.

The charge for a standard submission is $250 for each operating system family. For example, if you submit for Windows Vista x86 and Windows Vista x64, the charge is $250. If you submit for Windows XP x86 and Windows Server 2003 x86, the charge is $500. Note that there is no logo program for Windows 2000.

More information about billing policies is available at:

http://www.microsoft.com/whdc/winlogo/hwrequirements.mspx

You should not place an incident ID or DTM errata ID number in the README file unless a DTM support staff person gave it to you for submission purposes. Referenced ID numbers are only for incidents that will become errata or for errata filters that are not working correctly.

It might be because you do not have the required permissions.

To download signed .cat files:

To view which folder corresponds to which operating system, double-click the .cat file in the driver folder and, on the Security Catalog tab, click a hash. Under Entry details, you will find the OSAttr, which means the following:

2:5.0 = Windows 2000
2:5.1 = Windows XP
2:5.2 = Windows Server 2003
2:6.0 = Windows Vista and Windows Server 2008

The Windows Logo Program for hardware helps partners design, build, and sell compelling Windows-compatible products. The Windows logo helps customers to identify systems and peripherals that meet comprehensive standards for platform features, compatibility, and quality to ensure a great computing experience for end users.

Participating in the Windows Logo Program for hardware will help partners meet customer needs and expectations by delivering a product that meets Microsoft Windows standards for compatibility, reliability, and quality. Qualifying for a Windows logo will enable you to differentiate your products with the clear, trusted promise of a great Microsoft Windows computing experience.

Partners that produce products that work with Windows are eligible for the logo program and/or a digital signature on a driver, including original equipment manufacturers (OEMs), original design manufacturers (ODMs), independent hardware vendors (IHVs), independent software vendors (ISVs), and system builders.

Participation in the logo program means that you can:

Yes, the Windows Logo Program for hardware is worth Microsoft Partner Program points.

The Windows Vista Logo Program is structured to provide two distinct, clearly defined tiers of customer promise and partner benefits. The two tiers provide partners more value in differentiating their high-end products.

Basic Certification
Logos	Customer Promises	Benefits
Hardware	• A cost-effective, quality product that offers a familiar and easy-to-use Windows experience. • Devices that meet basic Microsoft standards for compatibility, reliability, and security. • Ongoing support via digitally signed drivers, downloaded from Windows Update.	• Download artwork for the logo to feature on product packaging and marketing materials. • Product listing in the Windows Vista Compatibility Center. • Digital signatures for drivers, indicating tested compatibility with Windows Vista. • Eligibility for free driver distribution on Windows Update. • Access to Windows Error Reporting data to improve the quality of signed drivers and to target fixes.

No, the tiered logo program applies only to Windows Vista.

Yes, hardware that qualifies for the premium logo running on Windows Vista will have a great foundation for enabling the best user experiences that a Windows-based PC can offer. A premium Windows Vista system is the right hardware to deliver premium experiences and is expected to run demanding software applications for productivity and gaming. The exact set of features and underlying hardware in a system will shape the experiences on a specific PC.

The Windows Vista Compatibility Center is a Web site that lists the compatibility status of thousands of products. The site offers links to the latest drivers and software upgrades and encourages visitors to leave feedback to help us improve the compatibility experience.

To get your product listed and to be included as a logo-qualified product on the in the Windows Vista Compatibility Center, visit our partner page for more information. can also click the Feedback link and fill in the Suggest an additional product form.

To secure the rights to use the Windows logo, partners must first complete these steps:

Partners then follow this process to license the logo for each product:

Partners can use the logo specifications and sample artwork to produce compliant logos. Microsoft does not provide stickers and does not endorse any particular sticker manufacturer.

Partners can download the logo artwork files (after their products have passed logo program testing and they have signed the Logo License Agreement) by signing in to Winqual with an administrator-level account, clicking Member Services in the upper-right corner, and then clicking the Logo Artwork link.

No.

Yes, a device logo is associated with the test logs that are submitted. If you have a device that meets the requirements for both client and server logo programs and you desire to get both logos, you can submit the test results for both operating systems and then license both logos.

All logo submissions will continue to use Winqual at https://winqual.microsoft.com. Some process notes to be aware of:

There is a nominal fee to review the testing logs that you submit. See the Testing Fee Schedules and Payment Instructions in the Logo Policies information available in LogoPoint on the Winqual site (https://winqual.microsoft.com/).

It depends. 32-bit editions of Windows Vista will load unsigned drivers if you sign in with an account that has administrator permissions on the computer or use administrator credentials during driver installation. 64-bit versions of Windows Vista will require all kernel-mode code to be digitally signed before it will load.

Yes, Windows Vista will load Windows XP and Windows Server 2003 drivers without a warning.

Yes, Windows Vista will load Authenticode-signed drivers without a warning as long as the certificate you created is added to the certificate store.

Yes, the Windows Driver Kit includes documentation and tools to build catalogs and sign them.

No, there will be no change in behavior. Certificates made with Makecert.exe or received from a trusted CA must be added to the certificate store for the system to respect drivers signed with that signature certificate.

No. The set of tests required for each device type and logo level will be clearly defined and selected in the Windows Logo Kit (WLK). When making a submission to Winqual, vendors will be asked to indicate the logo being targeted for the hardware.

Yes. However, drivers that ship with the operating system will also support hardware that does not meet the premium logo program requirements. Depending on the exact set of hardware components installed in your system, the drivers shipped with the operating system may or may not deliver certain experiences or qualify the system for a premium logo.

The logo requirements lead to tests and test cases that validate the requirements. Microsoft collects the tests and places them into suites of jobs that can be launched from the Device Test Manager (DTM). After passing the tests for your device type and logo designation, you can package the test results and submit them for review, sign the logo license, and begin using the logo on product packaging and other materials.

The specific guidelines and limitations for what can be changed after the system passes logo program testing are defined in the Windows Hardware Logo Program Policies, which are maintained in LogoPoint on the Winqual site (https://winqual.microsoft.com/).

For information about the overall process, see Logo Program Testing: Getting Started. To understand the specific steps for running each test, check the Device Test Manager (DTM) test procedures when they are released with the WLK.

No, all premium systems must ship with a premium Windows Vista edition to enable the premium experiences that users expect.

Refer to the Windows Logo Program requirements page at http://www.microsoft.com/whdc/winlogo/hwrequirements.mspx

You can sign up for ongoing updates through the Windows Hardware Developer Central newsletters on http://www.microsoft.com/whdc/newsreq.mspx

The definitions for desktop and mobile systems are contained in POLICY-0027, available in LogoPoint on the Winqual site (https://winqual.microsoft.com/).

Yes, there are requirements specific to x64 and independent hardware vendors (IHVs) submitting drivers for the logo program must submit an x64 version when they submit any 32-bit version. OEMs using x64 implementations must have signed drivers available to end users if shipping a 32-bit version of Windows Vista on the system.

The Windows Vista basic logo represents stability. Windows Display Driver Model (WDDM) drivers deliver a much more robust driver infrastructure to deliver stability and reliability in a tear-free desktop. The premium logo represents enhanced capability, which includes a composite desktop that uses the Aero-Express or Aero-Glass theme capability.

Microsoft Windows XP Display Driver Model (XPDM) drivers cannot get a Windows logo.

The Windows System Assessment Tool (WinSAT) is a benchmarking tool designed into Windows that generates scores based on system performance. It will analyze the graphics subsystem, the processor, the memory, the hard disk drive, and other critical components of the system and then calculate a total score. You can use this score to compare your system performance to that of any other Windows-based system.

The Windows System Assessment Tool (WinSAT) helps specify requirements in a way that is most relevant to actual performance when running Windows and is accurately measurable and testable with tools that are in the Windows operating system. WinSAT assesses the performance of the CPU, graphics system, and memory and storage devices. It is important to note that a Windows-based system benefits by good performance in each of these critical areas, because no component area can compensate for a lower performing component area. For example, a high performing hard disk drive cannot make up for a lesser performing graphics system. WinSAT is used in the logo requirements to specify minimum performance thresholds for these critical areas to ensure that key Windows features will perform well.

Yes. Desktop and workstation systems must support the S3, S4, and S5 states as defined in the ACPI 1.0b specification. Systems with more than 4 GB of memory are not required to support the S3 and S4 states. Every system must support wake from all implemented sleep states, except S4 and S5, for all wake-capable devices and buses.

Most Windows Driver Model (WDM) drivers should just work, but the latest driver models – including Windows Driver Foundation (WDF) and Windows Display Driver Model (WDDM) – are recommended, will save coding time, will reduce errors in power management, and are more robust and secure.

WLK 1.4 is the only kit supported for Windows Server 2008 R2 and the only kit supported for use after July 9, 2009.

As of May 5, 2009.

WLK 1.4 is officially released and no longer in beta. The beta support alias will be open until July 9, 2009; after then, all support issues should be filed with Microsoft support. You can also file support cases directly with Microsoft at any time.

The Windows Server 2008 Logo Program for 32-bit systems continues to exist and partners can continue to make submissions for that program with WLK 1.4, provided that the system is also submitted at the same time for the Windows Server 2008 R2 Logo Program for 64-bit systems.

The Windows Server 2008 Logo Program for 64-bit systems is superseded by the Windows Server 2008 R2 Logo Program for 64-bit systems. Beginning July 9, 2009, all 64-bit Windows Server 2008 systems must meet the Windows Server 2008 R2 Logo Program requirements.

Microsoft has not yet determined when the Windows Server 2003 Logo Program will end. Partners can continue to use WLK 1.2 for logo program submissions until July 9, 2009. At that point Winqual will require all submissions to use WLK 1.4. The Windows Server 2003 Logo Program tests are included in WLK 1.4 and are unchanged from WLK 1.2.

The Windows Server 2008 Failover Cluster Configuration Program (FCCP) is a certification program built on the Windows Server 2008 Logo Program for hardware. For more information, see Failover Cluster Configuration Program.

No. For more information about cluster certification, see Failover Cluster Configuration Program.

Yes. It will continue to exist through the lifecycle of the Windows Server 2003 Logo Program.

Yes. This program is intended for platforms that meet the Windows Server 2008 Logo Program requirements but cannot meet the Windows Server 2008 R2 requirements. Platforms submitted for the Windows Server 2008 R2 Supported program must have earned the Windows Server 2008 logo and must be able to run Windows Server 2008 R2 and pass basic driver testing for Windows Server 2008 R2.

No. Any system that can pass Windows Server 2008 and Windows Server 2008 R2 testing can meet the Windows Server 2003 logo requirements, and must be tested for that operating system in order to qualify for the logo.

No, the Windows Server 2008 Supported Program has closed.

There is no 32-bit system or device logo for Windows Server 2008 R2, because there is no 32-bit version of the operating system. Systems can continue to qualify for the 32-bit system logo for Windows Server 2008 using WLK 1.4, provided that they also qualify at the same time for the Windows Server 2008 R2 64-bit system logo.

A driver that is signed for Windows Server 2008 will load on a Windows Server 2008 R2 system without a popup warning. Logo testing, however, requires that all drivers on Windows Server 2008 R2 systems be qualified for a Windows Server 2008 R2 logo.

SVVP is a validation program built on the Windows Server 2008 R2 Logo Program for hardware. It is intended to validate that a virtualization product provides a stable virtual implementation of a server system. Testing is done on Windows Server 2008 R2. For more information, see Windows Server Virtualization Validation Program.

Yes. The two logo programs have different requirements and tests.

WLK 1.4 supports 32-bit and 64-bit Windows Server 2008 device testing.

The AQs for Windows Server 2008 R2 are:

All editions of Windows Server 2008 R2 are covered by the logo program. This includes, but is not limited to:

The program also covers Windows Small Business Server 2008 and Windows Essential Business Server 2008.

Device Fundamental requirements apply to all device categories for Windows Vista and all later operating systems. All submissions for any device category and any qualification level must meet all Device Fundamental requirements in addition to their category-specific requirements.

Yes. All submissions under the Unclassified category must meet all of the Device Fundamental requirements and must pass the Driver Reliability Tests in the WLK.

Yes. DEVFUND-0014 applies to all submissions. The only exemption is for devices that are physically embedded in a system that can support only x86 architecture. For details, refer to the DEVFUND-0014 requirements on the LogoPoint tool.

Yes. When you use inbox driver for your device, you must also test it for x64 architecture and include the test results in your submission package. Failure to do so results in the submission failing the Winqual checks and you being charged for this submission.

After the release of Windows Vista, Microsoft previously allowed partners 60 days to develop and submit x64 drivers and test results after the submission of x86 drivers and test results. This helped partners ramp up on x64 architecture. Currently, all partners must submit x64 drivers and test results at the same time as the x86 submissions. Failure to do so is considered noncompliance with the DEVFUND-0014 requirement, and such submissions are canceled immediately.

Microsoft is committed to providing consumers a seamless experience if they choose to upgrade from x86 architecture to x64 architecture for Windows Vista and later operating systems. Any device that is certified and logo'd for Windows Vista or any driver that is signed to work with Windows Vista on x86 architecture must also work with Windows Vista on x64 architecture. This is also applicable to later operating systems. This requirement ensures that we jointly meet that commitment to our customers.

You can find details on developing x64 driver in the WDK. Some of the valuable links are as follows:

The submission process involves multiple steps on the backend. One of these steps checks the various Hardware IDs in the driver files to ensure that they meet the Device Fundamental requirement (DEVFUND-0014). If you did not include all of the valid Hardware IDs for your device for x86 architecture also on the x64 architecture, then your submission fails this check and is marked as "Failed". For more specifics, refer to the DEVFUND-0014 requirement on LogoPoint.

No. If you previously made a submission for x64 driver and test results, then you can update only your x86 drivers at this time. Ensure that you do not include any additional Hardware IDs in your driver files for x86 at this time, or the submission might fail.

Yes, you can select the I am not providing an INF or Driver Package check box when you make an Unclassified submission. In this case, testing of your unclassified device is completed by using the operating system's inbox drivers. You are not permitted to upload a driver package when you upload the submission to Winqual. Also, you do not qualify for either a signed driver package or a logo to use with your device. You receive only a Logo Verification report to indicate that your device was successfully tested with this kit for the Unclassified category. IHVs might want to use this option to test their devices before they integrate the device into an OEM's system.

In WLK 1.2, the check box previously titled No INF File is renamed I am not providing an INF or Driver Package.

The No INF File title was causing confusion among partners and testers. To clearly explain the purpose of this check box, we renamed it I am not providing an INF or Driver Package. When you select this check box, the Windows Logo Kit understands that you do not want to provide a driver package or an INF file. Therefore, the kit selects the most appropriate INF and driver files from the operating system's inbox drivers to operate and test the device. When the test results of this submission are uploaded to Winqual, you cannot upload a driver package.

When you select the I am not providing an INF or Driver Package check box, device testing is completed by using the operating system's inbox drivers. Therefore, during this submission to Winqual you cannot qualify for a signed driver package and you cannot upload a driver package.