Download the latest drivers, software, firmware, and diagnostics for your HP products from the official HP Support website. Your Canon account is the way to get the most personalized support resources for your products. Already have an account?-->
Applies to: Configuration Manager (current branch)
Configuration Manager provides a driver catalog that you can use to manage the Windows device drivers in your Configuration Manager environment. Use the driver catalog to import device drivers into Configuration Manager, to group them in packages, and to distribute those packages to distribution points. Device drivers can be used when you install the full OS on the destination computer and when you use Windows PE in a boot image. Windows device drivers consist of a setup information (INF) file and any additional files that are required to support the device. When you deploy an OS, Configuration Manager obtains the hardware and platform information for the device from its INF file.
When you import device drivers, you can assign the device drivers to a category. Device driver categories help group similarly used device drivers together in the driver catalog. For example, set all network adapter device drivers to a specific category. Then, when you create a task sequence that includes the Auto Apply Drivers step, specify a category of device drivers. Configuration Manager then scans the hardware and selects the applicable drivers from that category to stage on the system for Windows Setup to use.
Group similar device drivers in packages to help streamline OS deployments. For example, create a driver package for each computer manufacturer on your network. You can create a driver package when importing drivers into the driver catalog directly in the Driver Packages node. After you create a driver package, distribute it to distribution points. Then Configuration Manager client computers can install the drivers as required.
Consider the following points:
When you create a driver package, the source location of the package must point to an empty network share that's not used by another driver package. The SMS Provider must have Full control permissions to that location.
When you add device drivers to a driver package, Configuration Manager copies it to the package source location. You can add to a driver package only device drivers that you've imported and that are enabled in the driver catalog.
You can copy a subset of the device drivers from an existing driver package. First, create a new driver package. Then add the subset of device drivers to the new package, and then distribute the new package to a distribution point.
When you use task sequences to install drivers, create driver packages that contain less than 500 device drivers.
Create a driver package
To create a driver package, you must have an empty network folder that's not used by another driver package. In most cases, create a new folder before you start this procedure.
In the Configuration Manager console, go to the Software Library workspace. Expand Operating Systems, and then select the Driver Packages node.
On the Home tab of the ribbon, in the Create group, select Create Driver Package.
Specify a descriptive Name for the driver package.
Enter an optional Comment for the driver package. Use this description to provide information about the contents or the purpose of the driver package.
In the Path box, specify an empty source folder for the driver package. Each driver package must use a unique folder. This path is required as a network location.
The site server account must have Full control permissions to the specified source folder.
The new driver package doesn't contain any drivers. The next step adds drivers to the package.
If the Driver Packages node contains several packages, you can add folders to the node to separate the packages into logical groups.
Additional actions for driver packages
You can do additional actions to manage driver packages when you select one or more driver packages from the Driver Packages node.
Create prestage content file
Creates files that you can use to manually import content and its associated metadata. Use prestaged content when you have low network bandwidth between the site server and the distribution points where the driver package is stored.
Delete (driver package)
Removes the driver package from the Driver Packages node.
Distributes the driver package to distribution points, distribution point groups, and distribution point groups that are associated with collections.
Export (driver package)
Start the Export Driver Package Wizard to save associated drivers and content to a file. Use this process to move driver packages between hierarchies.
Import driver package
Start the Import Driver Package Wizard to create a driver package from a previously exported package.
Starting in version 2010, when you import an object in the Configuration Manager console, it now imports to the current folder. Previously, Configuration Manager always put imported objects in the root node.
Manage access accounts
Adds, modifies, or removes access accounts for the driver package.
For more information about package access accounts, see Accounts used in Configuration Manager.
Move (driver package)
Moves the driver package to another folder in the Driver Packages node.
Properties (driver package)
Opens the Properties window. Review and change the content and properties of the driver. For example, change the name and description of the driver, enable or disable it, and specify on which platforms it can run.
Driver packages have metadata fields for Manufacturer and Model. Use these fields to tag driver packages with information to assist in general housekeeping, or to identify old and duplicate drivers that you can delete. On the General tab, select an existing value, or enter a string to create a new entry.
In the Driver Packages node, these fields display in the list as the Driver Manufacturer and Driver Model columns. They can also be used as search criteria.
Starting in version 1906, use these attributes to pre-cache content on a client. For more information, see Configure pre-cache content.
View all the drivers in the selected driver package.
Update distribution points
Updates the driver package on all the distribution points where the site stores it. This action copies only the content that has changed after the last time it was distributed.
You can install drivers on destination computers without including them in the OS image that is deployed. Configuration Manager provides a driver catalog that contains references to all the drivers that you import into Configuration Manager. The driver catalog is located in the Software Library workspace and consists of two nodes: Drivers and Driver Packages. The Drivers node lists all the drivers that you've imported into the driver catalog.
Import device drivers into the driver catalog
Before you can use a driver when you deploy an OS, import it into the driver catalog. To better manage them, import only the drivers that you plan to install as part of your OS deployments. Store multiple versions of drivers in the catalog to provide an easy way to upgrade existing drivers when hardware device requirements change on your network.
As part of the import process for the device driver, Configuration Manager reads the following properties about the driver:
- Supported hardware
- Supported platform information
By default, the driver is named after the first hardware device that it supports. You can rename the device driver later. The supported platforms list is based on the information in the INF file of the driver. Because the accuracy of this information can vary, manually verify that the driver is supported after you import it into the catalog.
After you import device drivers into the catalog, add them to driver packages or boot image packages.
You can't import device drivers directly into a subfolder of the Drivers node. To import a device driver into a subfolder, first import the device driver into the Drivers node, and then move the driver to the subfolder.
Process to import Windows device drivers into the driver catalog
In the Configuration Manager console, go to the Software Library workspace. Expand Operating Systems, and select the Drivers node.
On the Home tab of the ribbon, in the Create group, select Import Driver to start the Import New Driver Wizard.
On the Locate Driver page, specify the following options:
Import all drivers in the following network path (UNC): To import all the device drivers in a specific folder, specify its network path. For example:
If there are a lot of subfolders and a lot of driver INF files, this process can take time.
Import a specific driver: To import a specific driver from a folder, specify the network path to the Windows device driver INF file.
Specify the option for duplicate drivers: Select how you want Configuration Manager to manage driver categories when you import a duplicate device driver
- Import the driver and append a new category to the existing categories
- Import the driver and keep the existing categories
- Import the driver and overwrite the existing categories
- Do not import the driver
When you import drivers, the site server must have Read permission to the folder, or the import fails.
On the Driver Details page, specify the following options:
Hide drivers that are not in a storage or network class (for boot images): Use this setting to only display storage and network drivers. This option hides other drivers that aren't typically needed for boot images, such as a video driver or modem driver.
Hide drivers that are not digitally signed: Microsoft recommends only using drivers that are digitally signed
In the list of drivers, select the drivers that you want to import into the driver catalog.
Enable these drivers and allow computers to install them: Select this setting to let computers install the device drivers. This option is enabled by default.
If a device driver is causing a problem or you want to suspend the installation of a device driver, disable it during import. You can also disable drivers after you import them.
To assign the device drivers to an administrative category for filtering purposes, such as 'Desktops' or 'Notebooks', select Categories. Then choose an existing category, or create a new category. Use categories to control which device drivers are applied by the Auto Apply Drivers task sequence step.
On the Add Driver to Packages page, choose whether to add the drivers to a package.
Select the driver packages that are used to distribute the device drivers.
If necessary, select New Package to create a new driver package. When you create a new driver package, provide a network share that's not in use by other driver packages.
If the package has already been distributed to distribution points, select Yes in the dialog box to update the boot images on distribution points. You can't use device drivers until they're distributed to distribution points. If you select No, run the Update Distribution Point action before using the boot image. If the driver package has never been distributed, you must use the Distribute Content action in the Driver Packages node.
On the Add Driver to Boot Images page, choose whether to add the device drivers to existing boot images.
Add only storage and network drivers to the boot images.
Select Yes in the dialog box to update the boot images on distribution points. You can't use device drivers until they're distributed to distribution points. If you select No, run the Update Distribution Point action before using the boot image. If the driver package has never been distributed, you must use the Distribute Content action in the Driver Packages node.
Configuration Manager warns you if the architecture for one or more drivers doesn't match the architecture of the boot images that you selected. If they don't match, select OK. Go back to the Driver Details page, and clear the drivers that don't match the architecture of the selected boot image. For example, if you select an x64 and x86 boot image, all drivers must support both architectures. If you select an x64 boot image, all drivers must support the x64 architecture.
- The architecture is based on the architecture reported in the INF from the manufacturer.
- If a driver reports it supports both architectures, then you can import it into either boot image.
Configuration Manager warns you if you add device drivers that aren't network or storage drivers to a boot image. In most cases, they aren't necessary for the boot image. Select Yes to add the drivers to the boot image, or No to go back and modify your driver selection.
Configuration Manager warns you if one or more of the selected drivers aren't properly digitally signed. Select Yes to continue, and select No to go back and make changes to your driver selection.
Complete the wizard.
Manage device drivers in a driver package
Use the following procedures to modify driver packages and boot images. To add or remove a driver, first locate it in the Drivers node. Then edit the packages or boot images with which the selected driver is associated.
In the Configuration Manager console, go to the Software Library workspace. Expand Operating Systems, and then select the Drivers node.
Select the device drivers that you want to add to a driver package.
On the Home tab of the ribbon, in the Driver group, select Edit, and then choose Driver Packages.
To add a device driver, select the check box of the driver packages to which you want to add the device drivers. To remove a device driver, clear the check box of the driver packages from which you want to remove the device driver.
If you're adding device drivers that are associated with driver packages, you can optionally create a new package. Select New Package, which opens the New Driver Package dialog box.
If the package has already been distributed to distribution points, select Yes in the dialog box to update the boot images on distribution points. You can't use device drivers until they're distributed to distribution points. If you select No, run the Update Distribution Point action before using the boot image. If the driver package has never been distributed, you must use the Distribute Content action in the Driver Packages node. Before the drivers are available, you must update the driver package on distribution points.
Select OK when finished.
Manage device drivers in a boot image
You can add to boot images Windows device drivers that have been imported into the catalog. Use the following guidelines when you add device drivers to a boot image:
Add only storage and network drivers to boot images. Other types of drivers aren't usually required in Windows PE. Drivers that aren't required unnecessarily increase the size of the boot image.
Add only device drivers for Windows 10 to a boot image. The required version of Windows PE is based on Windows 10.
Make sure that you use the correct device driver for the architecture of the boot image. Don't add an x86 device driver to an x64 boot image.
Process to modify the device drivers associated with a boot image
In the Configuration Manager console, go to the Software Library workspace. Expand Operating Systems, and then select the Drivers node.
Select the device drivers that you want to add to the driver package.
On the Home tab of the ribbon, in the Driver group, select Edit, and then choose Boot images.
To add a device driver, select the check box of the boot image to which you want to add the device drivers. To remove a device driver, clear the check box of the boot image from which you want to remove the device driver.
If you don't want to update the distribution points where the boot image is stored, clear the Update distribution points when finished check box. By default, the distribution points are updated when the boot image is updated.
Configuration Manager warns you if the architecture for one or more drivers doesn't match the architecture of the boot images that you selected. If they don't match, select OK. Go back to the Driver Details page and clear the drivers that don't match the architecture of the selected boot image. For example, if you select an x64 and x86 boot image, all drivers must support both architectures. If you select an x64 boot image, all drivers must support the x64 architecture.
- The architecture is based on the architecture reported in the INF from the manufacturer.
- If a driver reports it supports both architectures then you can import it into either boot image.
Configuration Manager warns you if you add device drivers that aren't network or storage drivers to a boot image. In most cases, they aren't necessary for the boot image. Select Yes to add the drivers to the boot image or No to go back and modify your driver selection.
Configuration Manager warns you if one or more of the selected drivers aren't properly digitally signed. Select Yes to continue or select No to go back and make changes to your driver selection.
Additional actions for device drivers
You can do additional actions to manage drivers when you select them in the Drivers node.
Clears, manages, or sets an administrative category for the selected drivers.
Removes the driver from the Drivers node and also removes the driver from the associated distribution points.
Prohibits the driver from being installed. This action temporarily disables the driver. The task sequence can't install a disabled driver when you deploy an OS.
This action only prevents drivers from installing using the Auto Apply Driver task sequence step.
Lets Configuration Manager client computers and task sequences install the device driver when you deploy the OS.
Moves the device driver to another folder in the Drivers node.
Opens the Properties dialog box. Review and change the properties of the driver. For example, change its name and description, enable or disable it, and specify which platforms it can run on.
Use task sequences to install drivers
Use task sequences to automate how the OS is deployed. Each step in the task sequence can do a specific action, such as installing a driver. You can use the following two task sequence steps to install device drivers when you deploy an OS:
Auto Apply Drivers: This step lets you automatically match and install device drivers as part of an operating system deployment. You can configure the task sequence step to install only the best matched driver for each detected hardware device. Alternatively, specify that the step installs all compatible drivers for each detected hardware device, and then let Windows Setup choose the best driver. You can also specify a driver category to limit the drivers that are available for this step.
Apply Driver Package: This step lets you make all device drivers in a specific driver package available for Windows Setup. In the specified driver packages, Windows Setup searches for the device drivers that are required. When you create stand-alone media, you must use this step to install device drivers.
When you use these task sequence steps, you can also specify how the drivers are installed on the computer where you deploy the OS. For more information, see Manage task sequences to automate tasks.
You can use several reports in the Driver Management reports category to determine general information about the device drivers in the driver catalog. For more information about reports, see Introduction to reporting.
Starting with Windows 10, release 1703, a USB Audio 2.0 driver is shipped with Windows. It is designed to support the USB Audio 2.0 device class. The driver is a WaveRT audio port class miniport. For more information about the USB Audio 2.0 device class, see https://www.usb.org/documents?search=&type%5B0%5D=55&items_per_page=50.
The driver is named: usbaudio2.sys and the associated inf file is usbaudio2.inf.
Drivers Control Play 3
The driver will identify in device manager as 'USB Audio Class 2 Device'. This name will be overwritten with a USB Product string, if it is available.
The driver is automatically enabled when a compatible device is attached to the system. However, if a third-party driver exists on the system or Windows Update, that driver will be installed and override the class driver.
usbaudio2.sys fits within the wider architecture of Windows USB Audio as shown.
Related USB specifications
The following USB specifications define USB Audio and are referenced in this topic.
- USB-2 refers to the Universal Serial Bus Specification, Revision 2.0
- ADC-2 refers to the USB Device Class Definition for Audio Devices, Release 2.0.
- FMT-2 refers to the Audio Data Formats specification, Release 2.0.
The USB-IF is a special interest group that maintains the Official USB Specification, test specifications and tools.
The driver supports the formats listed below. An alternate setting which specifies another format defined in FMT-2, or an unknown format, will be ignored.
Type I formats (FMT-2 2.3.1):
- PCM Format with 8..32 bits per sample (FMT-2 220.127.116.11.1)
- PCM8 Format (FMT-2 18.104.22.168.2)
- IEEE_FLOAT Format (FMT-2 22.214.171.124.3)
Type III formats (FMT-2 2.3.3 and A.2.3):
This section describes the features of the USB Audio 2.0 driver.
Audio function topology
The driver supports all entity types defined in ADC-2 3.13.
Each Terminal Entity must have a valid clock connection in compatible USB Audio 2.0 hardware. The clock path may optionally include Clock Multiplier and Clock Selector units and must end in a Clock Source Entity.
The driver supports one single clock source only. If a device implements multiple clock source entities and a clock selector, then the driver will use the clock source that is selected by default and will not modify the clock selector’s position.
A Processing Unit (ADC-2 3.13.9) with more than one input pin is not supported.
An Extension Unit (ADC-2 3.13.10) with more than one input pin is not supported.
Cyclic paths in the topology are not allowed.
The driver supports the following endpoint synchronization types (USB-2 126.96.36.199):
- Asynchronous IN and OUT
- Synchronous IN and OUT
- Adaptive IN and OUT
For the asynchronous OUT case the driver supports explicit feedback only. A feedback endpoint must be implemented in the respective alternate setting of the AS interface. The driver does not support implicit feedback.
There is currently limited support for devices using a shared clock for multiple endpoints.
For the Adaptive IN case the driver does not support a feedforward endpoint. If such an endpoint is present in the alternate setting, it will be ignored. The driver handles the Adaptive IN stream in the same way as an Asynchronous IN stream.
The size of isochronous packets created by the device must be within the limits specified in FMT-2.0 section 188.8.131.52. This means that the deviation of actual packet size from nominal size must not exceed +/- one audio slot (audio slot = channel count samples).
An audio function must implement exactly one AudioControl Interface Descriptor (ADC-2 4.7) and one or more AudioStreaming Interface Descriptors (ADC-2 4.9). A function with an audio control interface but no streaming interface is not supported.
The driver supports all descriptor types defined in ADC-2, section 4. The following subsections provide comments on some specific descriptor types.
Class-Specific AS interface descriptor
For details on this specification, refer to ADC-2 4.9.2.
An AS interface descriptor must start with alternate setting zero with no endpoint (no bandwidth consumption) and further alternate settings must be specified in ascending order in compatible USB Audio 2.0 hardware.
An alternate setting with a format that is not supported by the driver will be ignored.
Each non-zero alternate setting must specify an isochronous data endpoint, and optionally a feedback endpoint. A non-zero alternate setting without any endpoint is not supported.
The bTerminalLink field must refer to a Terminal Entity in the topology and its value must be identical in all alternate settings of an AS interface.
The bFormatType field in the AS interface descriptor must be identical to bFormatType specified in the Format Type Descriptor (FMT-2 184.108.40.206).
For Type I formats, exactly one bit must be set to one in the bmFormats field of the AS interface descriptor. Otherwise, the format will be ignored by the driver.
To save bus bandwidth, one AS interface can implement multiple alternate settings with the same format (in terms of bNrChannels and AS Format Type Descriptor) but different wMaxPacketSize values in the isochronous data endpoint descriptor. For a given sample rate, the driver selects the alternate setting with the smallest wMaxPacketSize that can fulfill the data rate requirements.
Type I format type descriptor
For details on this specification, refer to FMT-2 220.127.116.11.
The following restrictions apply:
|Format||Subslot size||Bit resolution|
|Type I PCM format:||1 <= bSubslotSize <= 4||8 <= bBitResolution <= 32|
|Type I PCM8 format:||bSubslotSize 1||bBitResolution 8|
|Type I IEEE_FLOAT format:||bSubslotSize 4||bBitResolution 32|
|Type III IEC61937 formats:||bSubslotSize 2||bBitResolution 16|
Class-Specific AS isochronous audio data endpoint descriptor
For details on this specification, refer to ADC-2 18.104.22.168.
The MaxPacketsOnly flag in the bmAttributes field is not supported and will be ignored.
The fields bmControls, bLockDelayUnits and wLockDelay will be ignored.
Class requests and interrupt data messages
The driver supports a subset of the control requests defined in ADC-2, section 5.2, and supports interrupt data messages (ADC-2 6.1) for some controls. The following table shows the subset that is implemented in the driver.
|Entity||Control||GET CUR||SET CUR||GET RANGE||INTERRUPT|
|Clock Source||Sampling Frequency Control||x||x||x|
|Clock Selector||Clock Selector Control||x|
|Clock Multiplier||Numerator Control||x|
|Mixer Unit||Mixer Control||x||x||x|
|Selector Unit||Selector Control||x||x|
|Feature Unit||Mute Control||x||x||x|
|Automatic Gain Control||x||x|
Additional information on the controls and requests is available in the following subsections.
Clock source entity
For details on this specification, refer to ADC-2 22.214.171.124.
At a minimum, a Clock Source Entity must implement Sampling Frequency Control GET RANGE and GET CUR requests (ADC-2 126.96.36.199.1) in compatible USB Audio 2.0 hardware.
The Sampling Frequency Control GET RANGE request returns a list of subranges (ADC-2 5.2.1). Each subrange describes a discrete frequency, or a frequency range. A discrete sampling frequency must be expressed by setting MIN and MAX fields to the respective frequency and RES to zero. Individual subranges must not overlap. If a subrange overlaps a previous one, it will be ignored by the driver.
A Clock Source Entity which implements one single fixed frequency only does not need to implement Sampling Frequency Control SET CUR. It implements GET CUR which returns the fixed frequency, and it implements GET RANGE which reports one single discrete frequency.
Clock selector entity
For details on this specification, refer to ADC-2 188.8.131.52
The USB Audio 2.0 driver does not support clock selection. The driver uses the Clock Source Entity which is selected by default and never issues a Clock Selector Control SET CUR request. The Clock Selector Control GET CUR request (ADC-2 184.108.40.206.1) must be implemented in compatible USB Audio 2.0 hardware.
For details on this specification, refer to ADC-2 220.127.116.11.
The driver supports one single volume range only. If the Volume Control GET RANGE request returns more than one range, then subsequent ranges will be ignored.
The volume interval expressed by the MIN and MAX fields should be an integer multiple of the step size specified in the RES field.
If a feature unit implements single channel controls as well as a master control for Mute or Volume, then the driver uses the single channel controls and ignores the master control.
Additional Information for OEM and IHVs
OEMs and IHVs should test their existing and new devices against the supplied in-box driver.
There is not any specific partner customization that is associated with the in-box USB Audio 2.0 driver.
This INF file entry (provided in a update to Windows Release 1703), is used to identify that the in-box driver is a generic device driver.
The in-box driver registers for the following compatible IDs with usbaudio2.inf.
See the USB audio 2.0 specification for subclass types.
USB Audio 2.0 Devices with MIDI (subclass 0x03 above) will enumerate the MIDI function as a separate multi-function device with usbaudio.sys (USB Audio 1.0 driver) loaded.
The USB Audio 1.0 class driver registers this compatible ID with wdma_usb.inf.
And has these exclusions:
An arbitrary number of channels (greater than eight) are not supported in shared mode due to a limitation of the Windows audio stack.
IHV USB Audio 2.0 drivers and updates
For IHV provided third party driver USB Audio 2.0 drivers, those drivers will continue to be preferred for their devices over our in-box driver unless they update their driver to explicitly override this behavior and use the in-box driver.
Audio Jack Registry Descriptions
Starting in Windows 10 release 1703, IHVs that create USB Audio Class 2.0 devices having one or more jacks have the capability to describe these jacks to the in-box Audio Class 2.0 driver. The in-box driver uses the supplied jack information when handling the KSPROPERTY_JACK_DESCRIPTION for this device.
Jack information is stored in the registry in the device instance key (HW key).
The following describes the audio jack information settings in the registry:
<tid> = terminal ID (As defined in the descriptor)
<n> = Jack number (1 ~ n).
Convention for <tid> and <n> is:
- Base 10 (8, 9, 10 rather than 8, 9, a)
- No leading zeros
- n is 1-based (first jack is jack 1 rather than jack 0)
T1_NrJacks, T1_J2_ChannelMapping, T1_J2_ConnectorType
For additional audio jack information, see KSJACK_DESCRIPTION structure.
These registry values can be set in various ways:
By using custom INFs which wrap the in-box INF for the purpose to set these values.
Directly by the h/w device via a Microsoft OS Descriptors for USB devices (see example below). For more information about creating these descriptors, see Microsoft OS Descriptors for USB Devices.
Microsoft OS Descriptors for USB Example
The following Microsoft OS Descriptors for USB example contains the channel mapping and color for one jack. The example is for a non-composite device with single feature descriptor.
The IHV vendor should extend it to contain any other information for the jack description.
If the driver does not start, the system event log should be checked. The driver logs events which indicate the reason for the failure. Similarly, audio logs can be manually collected following the steps described in this blog entry. If the failure may indicate a driver problem, please report it using the Feedback Hub described below, and include the logs.
For information on how to read logs for the USB Audio 2.0 class driver using supplemental TMF files, see this blog entry. For general information on working with TMF files, see Displaying a Trace Log with a TMF File.
For information on 'Audio services not responding' error and USB audio device does not work in Windows 10 version 1703 see, USB Audio Not Playing
If you run into a problem with this driver, collect audio logs and then follow steps outlined in this blog entry to bring it to our attention via the Feedback Hub.
This USB Audio 2.0 class driver was developed by Thesycon and is supported by Microsoft.