Windows Update Hardware-Related Software Content Policy - 1

Windows Update Hardware-Related Software Content Policy - 1

Windows Update Hardware-Related Software Content Policy

January 13, 2012

Abstract

This document provides information about distributing hardware-related third-party software on the Microsoft Windows Update Web site for the Microsoft Windows family of operating systems. It provides general guidelines to help hardware and PC manufacturers understand the Business, Eligibility and Removal Policies.

This information applies to the following operating systems:
Windows Server 2008 R2
Windows7

Windows Server 2008
Windows Vista
Windows Server 2003
Windows XP
Windows 2000

The current version of this specification is maintained on the Web at:

Disclaimer: This document is provided “as-is”. Information and views expressed in this document, including URL and other Internet Web site references, may change without notice. You bear the risk of using it.

This document does not provide you with any legal rights to any intellectual property in any Microsoft product. You may copy and use this document for your internal, reference purposes.

Document History

Date / Change
July 29, 2005 / First publication
January 13, 2012 / Updated template, legal disclaimer, and contact email. No other changes.

Contents

1.Content Business Policy

2.Content Eligibility Policy

2.1Standard Content

2.2Non-standard Content

2.3Critical Content

3.Content Removal Policy

1.Content Business Policy

1.1At the present time, there is no charge to OEM and IHV partners for the hosting or distribution of content through Windows Update. Microsoft believes that the ability to improve system stability through the use of this update mechanism is fundamental to ensuring customers’ trustworthy PC experience.

1.2The policies that govern distribution of content from OEM and IHV partners through Windows Update may be updated at Microsoft’s sole discretion. Microsoft will provide at least 60 days’ notice for any change of policy, and at least 270 days’ advance notice for any change of policy related to recovery of Microsoft’s costs associated with this program.

1.3As used in this document, the term “hardware” refers to peripheral devices that interoperate with the basic computer system in order to expand the functionality it supports. Some examples of such devices are network controllers, graphics adapters, printers, mice, digital cameras, and cell phones.

2.Content Eligibility Policy

2.1Standard Content

2.1.1.This program is open to content provided by an OEM or IHV partner through the submission services provided at

2.1.1.1.Partner must provide standard IP and Open Source warranties and provide unlimited indemnification through the execution of the WHQL Testing or substantively similar agreement

2.1.2.To qualify for this program, content to be distributed through Windows Update must be hardware related and required for the proper and feature-compete functioning of the hardware (for example, drivers and hardware-related software only) on a Windows OS.

2.1.3.Microsoft subsidizes this distribution mechanism in order to improve end user experiences with Windows Operating Systems. Hardware-related software must meet all of the following requirements:

2.1.3.1.The software or substantially feature-equivalent software is distributed “in the box” with the hardware or already embedded with the hardware.

2.1.3.2.The software is only useful in conjunction with the hardware and the software’s sole purpose is to make the hardware optimally functional on a Windows OS; software not intended primarily for use in conjunction with a Windows OS does not qualify for this program.

2.1.3.3.The sole purpose of any software UI, APIs or other interfaces is to allow a user to manage and configure a hardware device on a Windows OS.

2.1.3.4.The software is associated specifically with unique hardware or specific hardware consumables through Windows Plug and Play as defined by the appropriate BUS specifications (examples: PCI, USB, IP Connected, SMBIOS fields, MS Virtual BUS drivers)

2.1.4.Content must be digitally signed by Microsoft and must meet all relevant Microsoft content quality and Windows interoperability guidelines such as the Designed for Windows (DFW) and/or other Microsoft digital signature programs.

2.1.4.1.Hardware-related software that is distributed on Windows Update must support Microsoft software stacks and protocols to the extent defined by the Windows Logo requirements.

2.1.5.Installation package must:

2.1.5.1.adequately install needed components via an INF-based installation or follow the process outlined below in 3.2,

2.1.5.2.be readily uninstallable by the user,

2.1.5.3.install only on specific hardware configurations,

2.1.5.4.fully complete without requiring user input, and

2.1.5.5.not require a reboot if the Operating System supports installation without rebooting.

2.1.6.Content must clearly describe any changes to end user settings that might be associated with use of the software, and must prompt for end user affirmation and consent prior to any change of settings.

2.1.7.Content must provide customers full control of how their personal information is collected, used, and communicated to others and must not generate unwanted communications.

2.1.8.Content must not delete or alter any Windows OS component, alter access to or functionality of any Windows OS component, or make use of non-public Windows interfaces, data-structures, or other non-public mechanisms.

2.1.9.Content must not engage in malicious activity (for example, viruses, worms, security exploits, bots, ad-ware, spyware).

2.2Non-standard Content

2.2.1.Microsoft currently provides a mechanism to support legacy content that fails to comply with 3.1.5 above (INF-based installation). To request participation in this program submit a request by email to ith “WU Non-Standard Driver Content Request” in the subject line. This content must meet the following requirements in addition to the Standard Content requirements.

2.2.2.The content provider must prove to Microsoft that an INF-based installation is insufficient to address the stability issues that the package is intended to solve.

2.2.3.The content must meet the requirements for Critical Content (2.3).

2.3Critical Content

2.3.1.Microsoft provides a mechanism for content providers to utilize the critical update and automatic download features of Windows Update. To request participation in this program submit a request by email to ith “WU Critical Content Request” in the Subject line. This content must meet the following requirements in addition to the Standard Content requirements:

2.3.1.1.The driver is among the top 20 Online Crash Analysis (OCA) driver issues report for an OEM’s systems over the last 90 days; or

2.3.1.2.The previous version of the code causes 10% or 10,000 (whichever is lower) of an OEM's systems to stop unexpectedly during driver installation over a two-week period or lose basic device or system functionality. Examples of this include: sound cards no longer emit sounds; a mouse cannot move the cursor; a storage unit cannot be accessed; or

2.3.1.3.At the sole discretion of Microsoft, the existing code results in excessive product support calls by OEMs, IHVs, or Microsoft.

3.Content Removal Policy

Reasons for immediate removal of content from the Windows Update Web site and/or the Automatic Update service include but are not limited to the following:

3.1.Installation failure rate of 5% or greater as measured by the Windows Update installation client.

3.2.The content is found to cause computers to stop unexpectedly during non-exceptional usage.

3.3.Removal request by the content provider who submitted the content, or is requested by the content provider’s designated proxy.

3.4.PSS or Help-Desk volume and/or customer complaints as reported by Microsoft or a third party.

3.5.Excessive Windows Error Reports.

3.6.High Uninstall rates.

3.7.Exceptionally large download size.

3.8.Discovery of a material violation of any policies described in this document, the WHQL testing agreement or the Logo license agreement.

------End of document------