Overview of Microsoft-provided USB drivers

This topics in this section describe the class drivers, generic client driver, and the parent composite driver that are provided by Microsoft.

Microsoft-provided USB drivers for controllers and hubs

Microsoft provides these set of drivers:

• For USB host controllers and hubs. For more information, see USB host-side drivers in Windows. You can develop a custom host controller driver that communicates with the USB host controller extension (UCX) driver. For more information, see Developing Windows drivers for USB host controllers.
• For handling common function logic for USB devices. For more information, see USB device-side drivers in Windows.
• For supporting Type-C connectors. For more information, see USB connector manager class extension (UcmCx).

Other Microsoft-provided USB drivers

Microsoft supports USB biometric devices (fingerprint readers) by providing the Windows Biometric Framework. See the Windows Biometric Framework.

Windows Server 2008

Windows Server 2003

Starting in Windows 7, Microsoft has replaced the kernel mode component of the Windows Vista USB driver stack (Wpdusb.sys) for Windows Portable Devices (WPD) with the generic Winusb.sys.

Microsoft provides the Wpdusb.sys driver to manage portable devices that support the Media Transfer Protocol. See WPD Design Guide.

Windows XP with Service Pack 2 (SP2)

Device setup class	Microsoft-provided driver and INF	Windows support	Description
USB	Usbccgp.sys is a parent driver for composite devices that supports multiple functions. For more information, see USB Generic Parent Driver (Usbccgp.sys).
Biometric
Media Transfer Protocol Devices	Wpdusb.sys (Obsolete)	Winusb.sys can be used as the USB device’s function driver instead of implementing a driver. See WinUSB.

Microsoft-provided USB device class drivers

Microsoft provides drivers for several USB device classes approved by USB-IF. These drivers and their installation files are included in Windows. They are available in the \Windows\System32\DriverStore\FileRepository folder.

Драйвер расширяемого хост-контроллера Intel® USB 3.0 Intel® 8/9/100 серии и Intel® C220/C610 Chipset семьи

Доступные загрузки

Intel(R)_USB_3.0_eXtensible_Host_Controller_Driver_5.0.4.43_v2.zip

Windows* 7, 32-разрядная версия
Windows* 7, 64-разрядная версия
Windows Server 2008 R2*

Подробное описание

Примечание: Драйвер контроллера Драйвер расширяемого хост-контроллера Intel® USB 3.0 не поддерживается на Windows XP и Windows Vista.

Это новая версия релиза: 5.0.4.43v2.

Не уверены, что это правильный драйвер или Программное обеспечение для вашего набора микросхем Intel® Запустите Приложение Intel® Driver & Support Assistant (Intel® DSA) для автоматического обнаружения драйверов или обновлений Программное обеспечение

О программном Программное обеспечение и драйверах Intel®

Драйвер или программное Программное обеспечение для компонента Intel могли быть изменены или заменены производителем компьютеров. Мы рекомендуем вам работать с производителем компьютера перед установкой нашего драйвера, чтобы вы не потеряли функции или настройки.

Загрузка документации

Данный файл для загрузки также подходит для перечисленных ниже видов продукции.

Лицензия на использование программного обеспечения Intel

Использование Вами программного обеспечения регулируется условиями лицензионного соглашения, входящего в комплект всех загружаемых программ.

INTEL SOFTWARE LICENSE AGREEMENT

IMPORTANT — READ BEFORE COPYING, INSTALLING OR USING.

Do not use or load this software and any associated materials (collectively,

the «Software») until you have carefully read the following terms and

conditions. By loading or using the Software, you agree to the terms of this

Agreement. If you do not wish to so agree, do not install or use the Software.

LICENSES: Please Note:

— If you are a network administrator, the «Site License» below shall

— If you are an end user, the «Single User License» shall apply to you.

— If you are an original equipment manufacturer (OEM), the «OEM License»

shall apply to you.

SITE LICENSE. You may copy the Software onto your organization’s computers

for your organization’s use, and you may make a reasonable number of

back-up copies of the Software, subject to these conditions:

1. This Software is licensed for use only in conjunction with Intel

component products. Use of the Software in conjunction with non-Intel

component products is not licensed hereunder.

2. You may not copy, modify, rent, sell, distribute or transfer any part

of the Software except as provided in this Agreement, and you agree to

prevent unauthorized copying of the Software.

3. You may not reverse engineer, decompile, or disassemble the Software.

4. You may not sublicense or permit simultaneous use of the Software by

more than one user.

5. The Software may include portions offered on terms in addition to those

set out here, as set out in a license accompanying those portions.

SINGLE USER LICENSE. You may copy the Software onto a single computer for

your personal, noncommercial use, and you may make one back-up copy of the

Software, subject to these conditions:

1. This Software is licensed for use only in conjunction with Intel

component products. Use of the Software in conjunction with non-Intel

component products is not licensed hereunder.

2. You may not copy, modify, rent, sell, distribute or transfer any part

of the Software except as provided in this Agreement, and you agree to

prevent unauthorized copying of the Software.

3. You may not reverse engineer, decompile, or disassemble the Software.

4. You may not sublicense or permit simultaneous use of the Software by

more than one user.

5. The Software may include portions offered on terms in addition to those

set out here, as set out in a license accompanying those portions.

OEM LICENSE: You may reproduce and distribute the Software only as an

integral part of or incorporated in Your product or as a standalone

Software maintenance update for existing end users of Your products,

excluding any other standalone products, subject to these conditions:

1. This Software is licensed for use only in conjunction with Intel

component products. Use of the Software in conjunction with non-Intel

component products is not licensed hereunder.

2. You may not copy, modify, rent, sell, distribute or transfer any part

of the Software except as provided in this Agreement, and you agree to

prevent unauthorized copying of the Software.

3. You may not reverse engineer, decompile, or disassemble the Software.

4. You may only distribute the Software to your customers pursuant to a

written license agreement. Such license agreement may be a «break-the-

seal» license agreement. At a minimum such license shall safeguard

Intel’s ownership rights to the Software.

5. The Software may include portions offered on terms in addition to those

set out here, as set out in a license accompanying those portions.

NO OTHER RIGHTS. No rights or licenses are granted by Intel to You, expressly

or by implication, with respect to any proprietary information or patent,

copyright, mask work, trademark, trade secret, or other intellectual property

right owned or controlled by Intel, except as expressly provided in this

OWNERSHIP OF SOFTWARE AND COPYRIGHTS. Title to all copies of the Software

remains with Intel or its suppliers. The Software is copyrighted and

protected by the laws of the United States and other countries, and

international treaty provisions. You may not remove any copyright notices

from the Software. Intel may make changes to the Software, or to items

referenced therein, at any time without notice, but is not obligated to

support or update the Software. Except as otherwise expressly provided, Intel

grants no express or implied right under Intel patents, copyrights,

trademarks, or other intellectual property rights. You may transfer the

Software only if the recipient agrees to be fully bound by these terms and if

you retain no copies of the Software.

LIMITED MEDIA WARRANTY. If the Software has been delivered by Intel on

physical media, Intel warrants the media to be free from material physical

defects for a period of ninety days after delivery by Intel. If such a defect

is found, return the media to Intel for replacement or alternate delivery of

the Software as Intel may select.

EXCLUSION OF OTHER WARRANTIES. EXCEPT AS PROVIDED ABOVE, THE SOFTWARE IS

PROVIDED «AS IS» WITHOUT ANY EXPRESS OR IMPLIED WARRANTY OF ANY KIND

INCLUDING WARRANTIES OF MERCHANTABILITY, NONINFRINGEMENT, OR FITNESS FOR A

PARTICULAR PURPOSE. Intel does not warrant or assume responsibility for the

accuracy or completeness of any information, text, graphics, links or other

items contained within the Software.

LIMITATION OF LIABILITY. IN NO EVENT SHALL INTEL OR ITS SUPPLIERS BE LIABLE

FOR ANY DAMAGES WHATSOEVER (INCLUDING, WITHOUT LIMITATION, LOST PROFITS,

BUSINESS INTERRUPTION, OR LOST INFORMATION) ARISING OUT OF THE USE OF OR

INABILITY TO USE THE SOFTWARE, EVEN IF INTEL HAS BEEN ADVISED OF THE

POSSIBILITY OF SUCH DAMAGES. SOME JURISDICTIONS PROHIBIT EXCLUSION OR

LIMITATION OF LIABILITY FOR IMPLIED WARRANTIES OR CONSEQUENTIAL OR INCIDENTAL

DAMAGES, SO THE ABOVE LIMITATION MAY NOT APPLY TO YOU. YOU MAY ALSO HAVE

OTHER LEGAL RIGHTS THAT VARY FROM JURISDICTION TO JURISDICTION.

TERMINATION OF THIS AGREEMENT. Intel may terminate this Agreement at any time

if you violate its terms. Upon termination, you will immediately destroy the

Software or return all copies of the Software to Intel.

APPLICABLE LAWS. Claims arising under this Agreement shall be governed by the

laws of California, excluding its principles of conflict of laws and the

United Nations Convention on Contracts for the Sale of Goods. You may not

export the Software in violation of applicable export laws and regulations.

Intel is not obligated under any other agreements unless they are in writing

and signed by an authorized representative of Intel.

GOVERNMENT RESTRICTED RIGHTS. The Software is provided with «RESTRICTED

RIGHTS.» Use, duplication, or disclosure by the Government is subject to

restrictions as set forth in FAR52.227-14 and DFAR252.227-7013 et seq. or its

successor. Use of the Software by the Government constitutes acknowledgment

of Intel’s proprietary rights therein. Contractor or Manufacturer is Intel

2200 Mission College Blvd., Santa Clara, CA 95052.

Загрузка файла начата. Если загрузка не началась, нажмите здесь для повторной инициации загрузки.

Add and Remove Drivers to an offline Windows Image

You can use DISM to install or remove driver (.inf) files in an offline Windows or WinPE image. You can either add or remove the drivers directly by using the command prompt, or apply an unattended answer file to a mounted .wim, .ffu, .vhd, or .vhdx file.

When you use DISM to install a device driver to an offline image, the device driver is added to the driver store in the offline image. When the image is booted, Plug and Play (PnP) runs and associates the drivers in the store to the corresponding devices on the computer.

To add drivers to a WindowsВ 10 image offline, you must use a technician computer running WindowsВ 10, Windows ServerВ 2016, or Windows Preinstallation Environment (WinPE) for WindowsВ 10. Driver signature verification may fail when you add a driver to a WindowsВ 10 image offline from a technician computer running any other operating system.

To learn how to add a driver on a running Windows PC, see Add a driver online in audit mode or Install a plug and play device. To learn how to add a driver to a PC running WinPE, see Drvload command line options.

Driver types

• .inf-style drivers: Many drivers include an information file (with an .inf extension) to help install the driver. These can be installed using tools described in this topic.
• .exe-style drivers: Drivers without an .inf file often must be installed like typical Windows desktop applications. To learn how to add these, see Add a driver online in Audit Mode
• Boot-critical drivers: Graphics and storage drivers may sometimes need to be added to the Windows image (as shown in this topic), as well as the Windows PE image, and in the Windows recovery (WinRE) image.

Add drivers to an offline Windows image

To add drivers to an offline image, you have to mount an image prior to adding drivers.

If you’re adding drivers to a WinPE image, you can add them to the WinPE image in the output folder you specified when you ran copype, for example: C:\WinPE_amd64\media\sources\boot.wim . This ensures that drivers will be included in WinPE each time you build WinPE media from that folder.

1. Mount a Windows image. For example:

1. Add a driver to the image.

To install all of the drivers from a folder and all its subfolders, point to the folder and use the /Recurse option.

To see all DISM driver servicing command line options, see DISM driver servicing command-line options.

Using /Recurse can be handy, but it’s easy to bloat your image with it. Some driver packages include multiple .inf driver packages, which often share payload files from the same folder. During installation, each .inf driver package is expanded into a separate folder. Each individual folder has a copy of the payload files. We’ve seen cases where a popular driver in a 900MB folder added 10GB to images when added with the /Recurse option.

To install an unsigned driver, use /ForceUnsigned to override the requirement that drivers installed on X64-based computers must have a digital signature.

1. Check to see if the driver was added. Drivers added to the Windows image are named Oem*.inf. This guarantees unique naming for newly added drivers. For example, the files MyDriver1.inf and MyDriver2.inf are renamed Oem0.inf and Oem1.inf.

1. Commit the changes and unmount the image.

Remove drivers from an offline Windows image

1. At an elevated command prompt, mount the offline Windows image:

1. Remove a specific driver from the image. Multiple drivers can also be removed on one command line.

Removing a boot-critical driver package can make the offline Windows image unbootable. For more information, see DISM Driver Servicing Command-Line Options. пїЅ

1. Commit the changes and unmount the image.

Add drivers to an offline Windows image by using an unattended answer file

1. Gather the device driver .inf files that you intend to install on the Windows image.

All drivers in the directory and subdirectories that are referenced in the answer file are added to the image. You should manage the answer file and these directories carefully to address concerns about increasing the size of the image with unnecessary driver packages.

1. Use WindowsВ System Image Manager (WindowsВ SIM) to create an answer file that contains the paths to the device drivers that you want to install.

• Add the Microsoft-Windows-PnpCustomizationsNonWinPE\DriverPaths\PathAndCredentials\Credentials component to your answer file in the offlineServicing configuration pass.

For each location that you intend to access, add a separate PathAndCredentials list item by right-clicking on DriverPaths in the Answer File pane and clicking Insert New PathAndCredentials.

See Configure components and settings in an answer file for information on how to modify an answer file.

1. For each path in Microsoft-Windows-PnpCustomizationsNonWinPE , specify the path to the device driver and the credentials that are used to access the file, if the file is on a network share.

When you include multiple device driver paths by adding multiple PathAndCredentials list items, you must increment the value of Key for each path. For example, you can add two separate driver paths where the value of Key for the first path is equal to 1 and the value of Key for the second path is equal to 2.

1. Save the answer file and exit WindowsВ SIM. The answer file must resemble the following sample.

1. Mount the Windows image that you intend to install the drivers to by using DISM:

If you’re working with a VHD or FFU, specify /Index:1 .

1. Apply the answer file to the mounted Windows image:

For more information about how to apply an answer file, see DISM Unattended Servicing Command-Line Options.

The .inf files referenced in the path in the answer file are added to the Windows image.

1. Check to see if the driver was added. Drivers added to the Windows image are named Oem*.inf. This guarantees unique naming for newly added drivers. For example, the files MyDriver1.inf and MyDriver2.inf are renamed Oem0.inf and Oem1.inf.

For example, type:

1. Unmount the .wim file and commit the changes. For example, type:

If you need drivers for WinPE to see the local hard disk drive or a network, you must use the windowsPE configuration pass of an answer file to add drivers to the WinPE driver store and to reflect boot-critical drivers required by WinPE. For more information, see Add Device Drivers to Windows During Windows Setup.