Forus USB Devices Driver
-->
- Forus USB Devices Driver
- Forus Usb Devices Driver Updater
- Forus Usb Devices Driver Vga
- Forus Usb Devices Drivers
- Usb Device Drivers Windows 10
Plug in your device to the host system. Open Device Manager and locate the device. Select and hold (or right-click) the device and select Update driver software. From the context menu. In the wizard, select Browse my computer for driver software. The package provides the installation files for Microsoft USB Input Device Driver version 10.0.4. If the driver is already installed on your system, updating (overwrite-installing) may.
UMDF provides device driver interfaces (DDIs) that a client driver can use to integrate with Windows components such as the Plug and Play Manager and Power Manager. UMDF also provides specialized target objects for USB devices, which abstract the hardware in. The driver is loaded based on a compatible ID match similar to other USB device class drivers included in Windows. USB Class02&SubClass02. If you want to load Usbser.sys automatically, set the class code to 02 and subclass code to 02 in the Device Descriptor. For more information, see USB communications device class. Locate Universal Serial Bus Controllers Apple Mobile Device USB Driver. It is also possible the device may show under Imaging Devices, Portable Devices or Other Devices or as an MTB USB Device. Right-click and select Update Driver Software. Click Browse my computer for driver software.
Summary
- Registry keys that must be set by OEMs to define USB descriptors.
Applies to:
- Windows 10
Last updated:
- November 2015
OEMs must set several registry values to make sure that their device enumerates with the correct metadata when connected to a computer. These values specify device and configuration descriptors for the USB device-side drivers in Windows. OEMs that create and include their own interfaces must set additional registry values in order for their interfaces to be loaded and used.
Registry keys related to the device-side USB drivers are under:
HKEY_LOCAL_MACHINESystemCurrentControlSetControlUSBFN
This topic describes settings for the preceding key and subkeys that define the device, configuration, and interface descriptors for the device.
USBFN registry key
Configuration information for the USB device are under:
HKEY_LOCAL_MACHINESystemCurrentControlSetControlUSBFN
This table describes its subkeys. Some of them can be modified by OEMs. More information about the supported values for each subkey is provided in sections below.
| Subkey | Description |
|---|---|
| Alternates | This subkey contains additional subkeys that describe an interface that has one or more alternate settings. |
| Associations | This subkey defines Interface Association Descriptors (IADs). Each IAD allows multiple interfaces to be grouped into a single function. Each subkey represents a different IAD and OEMs can modify the values for those subkeys. |
| Default | This subkey contains default values that are used to describe device-specific settings such as the VID and PID. This is a Microsoft-owned subkey whose values are overridden by those in the parent key. |
| Configurations | This subkey contains additional subkeys that contain configuration descriptor values that are used during USB enumeration. For example, the standard test configuration might exist under HKEY_LOCAL_MACHINESystemCurrentControlSetControlUSBFNConfigurationsTestConfig. |
| ConfigurationsDefault | This is a Microsoft-owned subkey. It contains values for the default configuration. The interfaces in the default configuration are added before the current configuration present when the IncludeDefaultCfg value is set to 1 under the HKEY_LOCAL_MACHINESystemCurrentControlSetControlUSBFN key. |
| Interfaces | This subkey contains additional subkeys that describe specific interface descriptors. For example, the IP over USB interface may reside under HKEY_LOCAL_MACHINESystemCurrentControlSetControlUSBFNInterfacesIpOverUsb. The name of the interface subkey is also used as the hardware ID of the USBFN child device for loading the USBFn class driver. In the IP over USB example, the hardware ID of the USBFN child device will be USBFNIpOverUsb. |
This table describes the values that OEMs can define in the HKEY_LOCAL_MACHINESystemCurrentControlSetControlUSBFN key. Values that are not defined in this key assume the default values defined by Microsoft under HKEY_LOCAL_MACHINESystemCurrentControlSetControlUSBFNDefault.
All OEMs must set the idVendor, idProduct, ManufacturerString, and ProductString values. OEMs that create and add their own interfaces must also set CurrentConfiguration to the name of the subkey under HKEY_LOCAL_MACHINESystemCurrentControlSetControlUSBFNConfigurations that includes their interfaces in the InterfaceList.
| Value | Type | Owner | Description |
|---|---|---|---|
| IncludeDefaultCfg | REG_DWORD | OEM | Set to 1 when OEMs want to include the interfaces of the Default configuration such as IpOverUsb or MTP. |
| idVendor | REG_DWORD | OEM | The vendor identifier for the device descriptor that is sent to the host during enumeration. |
| idProduct | REG_DWORD | OEM | The product identifier for the device descriptor that is sent to the host during enumeration. |
| ManufacturerString | REG_SZ | OEM | The manufacturer string that is sent to the host to identify the manufacturer of the device. |
| ProductString | REG_SZ | OEM | A string that describes the device as a product. The default value is Windows 10 Mobile Device. This value is used as the display name of the device in the connected computer's user interface. OEMs should make sure that this value matches the value of the PhoneModelName value under the DeviceTargetingInfo subkey. |
| iSerialNumber | REG_DWORD | OEM | If this value is set to 0, then the device does not have a serial number. If this value is non-zero or does not exist, then the serial number is generated uniquely per device. |
| CurrentConfiguration | REG_SZ | OEM | This string must correspond to the name of a configuration subkey. This string determines which configuration to use to build a configuration descriptor for USB device enumeration. |
USBFNConfigurations registry key
This table describes the values that OEMs can define for subkeys under HKEY_LOCAL_MACHINESystemCurrentControlSetControlUSBFNConfigurations. Each subkey represents a different USB configuration. If the OEM wants to create their own interface, the OEM must define a new configuration which contains the interfaces to be used. To do this, create a subkey under HKEY_LOCAL_MACHINESystemCurrentControlSetControlUSBFNConfigurations that uses the name of the configuration and populate the subkey with the values in this table. Additionally, for the USB driver to use the new configuration, the CurrentConfiguration value (described in the preceding table) must be set to the name of the configuration subkey.
| Value | Type | Owner | Description |
|---|---|---|---|
| InterfaceList | REG_MULTI_SZ | OEM or Microsoft | Contains a list of interface names that correspond to interface subkeys under HKEY_LOCAL_MACHINESystemCurrentControlSetControlUSBFNInterfaces, the IAD associations defined under HKEY_LOCAL_MACHINESystemCurrentControlSetControlUSBFNAssociations, and the alternate interfaces defined under HKEY_LOCAL_MACHINESystemCurrentControlSetControlUSBFNAlternates. Those keys determine the interfaces that are used to describe the composite configuration descriptor. If the IncludeDefaultCfg value under the HKEY_LOCAL_MACHINESystemCurrentControlSetControlUSBFN key is set to 1, this list is appended to the Microsoft-owned default interface list to create the complete interface list that the device will use to enumerate. |
| MSOSCompatIdDescriptor | REG_BINARY | OEM or Microsoft | Optional. Defines an Extended Compat ID OS Feature Descriptor for the configuration. If the IncludeDefaultCfg value under the HKEY_LOCAL_MACHINESystemCurrentControlSetControlUSBFN key is set to 1, the functions in this descriptor are appended to the functions and interfaces in the default configuration. |
USBFNInterfaces registry key
This table describes the values that OEMs can modify for subkeys under HKEY_LOCAL_MACHINESystemCurrentControlSetControlUSBFNInterfaces.
Each subkey represents a different USB interface. To define an interface, create a subkey under HKEY_LOCAL_MACHINESystemCurrentControlSetControlUSBFNInterfaces using the name of the interface, and populate it with the values in the table below. Additionally, an interface will only be included if the interface is part of the InterfaceList of the CurrentConfiguration.
| Value | Type | Owner | Description |
|---|---|---|---|
| InterfaceDescriptor | REG_BINARY | OEM or Microsoft | A binary representation of an interface descriptor to send to the host during USB enumeration. The bInterfaceNumber and iInterface values are automatically populated by the USB function stack after compiling a full configuration descriptor to avoid conflicts with other interface descriptors. |
| InterfaceGUID | REG_SZ | OEM or Microsoft | A GUID that uniquely identifies an interface on the bus. |
| InterfaceNumber | REG_DWORD | OEM or Microsoft | Optional. This value is used to assign a fixed interface number to a function. Interface numbers 0-1F are reserved for legacy functions, 20-3F are reserved for Microsoft, and 40-5F are reserved for use by OEMs. |
| MSOSExtendedPropertyDescriptor | REG_BINARY | OEM or Microsoft | Optional. Defines an Extended Property OS Feature Descriptor for the interface. |
USBFNAlternates registry key
The alternates subkey is used to define a single interface that has one or more alternate interfaces. This table describes the values that OEMs can modify for subkeys under HKEY_LOCAL_MACHINESystemCurrentControlSetControlUSBFNAlternates.
Each subkey represents a different interface. To define an interface with alternate settings, create a subkey under HKEY_LOCAL_MACHINESystemCurrentControlSetControlUSBFNAlternates by using the name of the interface, and populate it with the values in the table below.
| Value | Type | Owner | Description |
|---|---|---|---|
| InterfaceList | REG_MULTI_SZ | OEM or Microsoft | A list of two of more interface names that correspond to interfaces defined under HKEY_LOCAL_MACHINESystemCurrentControlSetControlUSBFNInterfaces. That key collectively defines an interface with alternate settings. The first interface corresponds to alternate setting 0, the second interface corresponds to alternate setting 1, and so on. |
| InterfaceNumber | REG_DWORD | OEM or Microsoft | Optional. This value is used to assign a fixed interface number to a function. Interface numbers 0-1F are reserved for legacy functions, 20-3F are reserved for Microsoft, and 40-5F are reserved for use by OEMs. |
| MSOSExtendedPropertyDescriptor | REG_BINARY | OEM or Microsoft | Optional. Defines an Extended Property OS Feature Descriptor for the interface. |
USBFNAssociations registry key
OEMs can specify associations by defining Interface Association Descriptors (IADs). Each IAD allows multiple interfaces to be grouped into a single function. This table describes the values that OEMs can modify for subkeys under HKEY_LOCAL_MACHINESystemCurrentControlSetControlUSBFNAssociations.
Each subkey represents a different IAD. To define an association, create a subkey under HKEY_LOCAL_MACHINESystemCurrentControlSetControlUSBFNAssociations by using the name of the IAD, and populate it with the values in the table below.
| Value | Type | Owner | Description |
|---|---|---|---|
| InterfaceList | REG_MULTI_SZ | OEM or Microsoft | A list of interfaces or alternate interfaces that are associated with a USB function. If the size of the list is less than 2, then the function driver stack fails to load. Other functions or interfaces continue to load. |
| bFunctionClass | REG_DWORD | OEM or Microsoft | The class code of the function, set to 02. |
| bFunctionSubClass | REG_DWORD | OEM or Microsoft | The subclass code of the function, set to 0d. |
| bFunctionProtocol | REG_DWORD | The protocol code of the function, set to 01. | |
| MSOSExtendedPropertyDescriptor | REG_BINARY | OEM or Microsoft | Optional. Defines an Extended Property OS Feature Descriptor for the interface. |
Use case: Enabling MirrorLink
MirrorLink is an interoperability standard that allows integration between mobile devices and car infotainment systems. The device must expose a USB CDC NCM interface to the MirrorLink client. As a Communications Device Class (CDC) device, it is required to describe the data interfaces by using either an Interface Association Descriptor (IAD) and/or a CDC Function Union Descriptor.
To enable MirrorLink connectivity on Windows 10 Mobile Device, OEM must make these changes to expose an IAD.
Create an association for the communication and data interfaces by using an Interface Association Descriptor (IAD) by setting registry values shown in the preceding table.
In addition to the registry settings, set this registry value to a non-zero value.
Value Type Owner Description MirrorLink REG_DWORD OEM or Microsoft A non-zero value indicates the interface supports MirrorLink. The USB function stack does not stall the MirrorLink USB command. Class-specific descriptors can be included in the interface descriptor set that is defined in the registry. The size field must be set in those descriptors so that USB function driver stack can parse them accurately.
Alternatively, a CDC Function Union Descriptor can also be defined as a Class-Specific Interface Descriptor; however, the interface numbers specified by the Union descriptor are static and are not be assigned by the USB function driver stack, and the presence of a Union descriptor does not cause the interfaces described by it to be associated with a single child PDO. An IAD is required for that association.
Related topics
USB device-side drivers in Windows
Developing Windows drivers for USB function controllers
-->For certain Universal Serial Bus (USB) devices, such as devices that are accessed by only a single application, you can install WinUSB (Winusb.sys) in the device's kernel-mode stack as the USB device's function driver instead of implementing a driver.
This topic contains these sections:
Automatic installation of WinUSB without an INF file
As an OEM or independent hardware vendor (IHV), you can build your device so that the Winusb.sys gets installed automatically on Windows 8 and later versions of the operating system. Such a device is called a WinUSB device and does not require you to write a custom INF file that references in-box Winusb.inf.
When you connect a WinUSB device, the system reads device information and loads Winusb.sys automatically.
For more information, see WinUSB Device.
Installing WinUSB by specifying the system-provided device class
When you connect your device, you might notice that Windows loads Winusb.sys automatically (if the IHV has defined the device as a WinUSB Device). Otherwise follow these instructions to load the driver:
- Plug in your device to the host system.
- Open Device Manager and locate the device.
- Select and hold (or right-click) the device and select Update driver software... from the context menu.
- In the wizard, select Browse my computer for driver software.
- Select Let me pick from a list of device drivers on my computer.
- From the list of device classes, select Universal Serial Bus devices.
- The wizard displays WinUsb Device. Select it to load the driver.
If Universal Serial Bus devices does not appear in the list of device classes, then you need to install the driver by using a custom INF.The preceding procedure does not add a device interface GUID for an app (UWP app or Windows desktop app) to access the device. You must add the GUID manually by following this procedure.
Load the driver as described in the preceding procedure.
Generate a device interface GUID for your device, by using a tool such as guidgen.exe.
Find the registry key for the device under this key:
HKEY_LOCAL_MACHINESYSTEMCurrentControlSetEnumUSB<VID_vvvv&PID_pppp>
Under the Device Parameters key, add a String registry entry named DeviceInterfaceGUID or a Multi-String entry named DeviceInterfaceGUIDs. Set the value to the GUID you generated in step 2.
Disconnect the device from the system and reconnect it to the same physical port.Note If you change the physical port then you must repeat steps 1 through 4.
Writing a custom INF for WinUSB installation
As part of the driver package, you provide an .inf file that installs Winusb.sys as the function driver for the USB device.
The following example .inf file shows WinUSB installation for most USB devices with some modifications, such as changing USB_Install in section names to an appropriate DDInstall value. You should also change the version, manufacturer, and model sections as necessary. For example, provide an appropriate manufacture's name, the name of your signed catalog file, the correct device class, and the vendor identifier (VID) and product identifier (PID) for the device.
Also notice that the setup class is set to 'USBDevice'. Vendors can use the 'USBDevice' setup class for devices that do not belong to another class and are not USB host controllers or hubs.
If you are installing WinUSB as the function driver for one of the functions in a USB composite device, you must provide the hardware ID that is associated with the function, in the INF. You can obtain the hardware ID for the function from the properties of the devnode in Device Manager. The hardware ID string format is 'USBVID_vvvv&PID_pppp'.
The following INF installs WinUSB as the OSR USB FX2 board's function driver on a x64-based system.
Starting in Windows 10, version 1709, the Windows Driver Kit provides InfVerif.exe that you can use to test a driver INF file to make sure there are no syntax issues and the INF file is universal. We recommened that you provide a universal INF. For more information, see Using a Universal INF File.
Only include a ClassInstall32 section in a device INF file to install a new custom device setup class. INF files for devices in an installed class, whether a system-supplied device setup class or a custom class, must not include a ClassInstall32 section.
Except for device-specific values and several issues that are noted in the following list, you can use these sections and directives to install WinUSB for any USB device. These list items describe the Includes and Directives in the preceding .inf file.
USB_Install: The Include and Needs directives in the USB_Install section are required for installing WinUSB. You should not modify these directives.
USB_Install.Services: The Include directive in the USB_Install.Services section includes the system-supplied .inf for WinUSB (WinUSB.inf). This .inf file is installed by the WinUSB co-installer if it isn't already on the target system. The Needs directive specifies the section within WinUSB.inf that contains information required to install Winusb.sys as the device's function driver. You should not modify these directives.Note Because Windows XP doesn't provide WinUSB.inf, the file must either be copied to Windows XP systems by the co-installer, or you should provide a separate decorated section for Windows XP.
USB_Install.HW: This section is the key in the .inf file. It specifies the device interface globally unique identifier (GUID) for your device. The AddReg directive sets the specified interface GUID in a standard registry value. When Winusb.sys is loaded as the device's function driver, it reads the registry value DeviceInterfaceGUIDs key and uses the specified GUID to represent the device interface. You should replace the GUID in this example with one that you create specifically for your device. If the protocols for the device change, create a new device interface GUID.
Note User-mode software must call SetupDiGetClassDevs to enumerate the registered device interfaces that are associated with one of the device interface classes specified under the DeviceInterfaceGUIDs key. SetupDiGetClassDevs returns the device handle for the device that the user-mode software must then pass to the WinUsb_Initialize routine to obtain a WinUSB handle for the device interface. For more info about these routines, see How to Access a USB Device by Using WinUSB Functions.
Forus USB Devices Driver
The following INF installs WinUSB as the OSR USB FX2 board's function driver on a x64-based system. The example shows INF with WDF coinstallers.
Forus Usb Devices Driver Updater
USB_Install.CoInstallers: This section, which includes the referenced AddReg and CopyFiles sections, contains data and instructions to install the WinUSB and KMDF co-installers and associate them with the device. Most USB devices can use these sections and directives without modification.
The x86-based and x64-based versions of Windows have separate co-installers.
Note Each co-installer has free and checked versions. Use the free version to install WinUSB on free builds of Windows, including all retail versions. Use the checked version (with the '_chk' suffix) to install WinUSB on checked builds of Windows.
Each time Winusb.sys loads, it registers a device interface that has the device interface classes that are specified in the registry under the DeviceInterfaceGUIDs key.
Note If you use the redistributable WinUSB package for Windows XP or Windows Server 2003, make sure that you don't uninstall WinUSB in your uninstall packages. Other USB devices might be using WinUSB, so its binaries must remain in the shared folder.
How to create a driver package that installs Winusb.sys
To use WinUSB as the device's function driver, you create a driver package. The driver package must contain these files:
- WinUSB co-installer (Winusbcoinstaller.dll)
- KMDF co-installer (WdfcoinstallerXXX.dll)
- An .inf file that installs Winusb.sys as the device's function driver. For more information, see Writing an .Inf File for WinUSB Installation.
- A signed catalog file for the package. This file is required to install WinUSB on x64 versions of Windows starting with Vista.
Note Make sure that the driver package contents meet these requirements:
Forus Usb Devices Driver Vga
- The KMDF and WinUSB co-installer files must be obtained from the same version of the Windows Driver Kit (WDK).
- The co-installer files must be obtained from the latest version of the WDK, so that the driver supports all the latest Windows releases.
- The contents of the driver package must be digitally signed with a Winqual release signature. For more info about how to create and test signed catalog files, see Kernel-Mode Code Signing Walkthrough on the Windows Dev Center - Hardware site.
Forus Usb Devices Drivers
Download the Windows Driver Kit (WDK) and install it.
Create a driver package folder on the machine that the USB device is connected to. For example, c:UsbDevice.
Copy the WinUSB co-installer (WinusbcoinstallerX.dll) from the WinDDKBuildNumberredistwinusb folder to the driver package folder.
The WinUSB co-installer (Winusbcoinstaller.dll) installs WinUSB on the target system, if necessary. The WDK includes three versions of the co-installer depending on the system architecture: x86-based, x64-based, and Itanium-based systems. They are all named WinusbcoinstallerX.dll and are located in the appropriate subdirectory in the WinDDKBuildNumberredistwinusb folder.
Copy the KMDF co-installer (WdfcoinstallerXXX.dll) from the WinDDKBuildNumberredistwdf folder to the driver package folder.
The KMDF co-installer (WdfcoinstallerXXX.dll) installs the correct version of KMDF on the target system, if necessary. The version of WinUSB co-installer must match the KMDF co-installer because KMDF-based client drivers, such as Winusb.sys, require the corresponding version of the KMDF framework to be installed properly on the system. For example, Winusbcoinstaller2.dll requires KMDF version 1.9, which is installed by Wdfcoinstaller01009.dll. The x86 and x64 versions of WdfcoinstallerXXX.dll are included with the WDK under the WinDDKBuildNumberredistwdf folder. The following table shows the WinUSB co-installer and the associated KMDF co-installer to use on the target system.
Use this table to determine the WinUSB co-installer and the associated KMDF co-installer.
WinUSB co-installer KMDF library version KMDF co-installer Winusbcoinstaller.dll Requires KMDF version 1.5 or later Wdfcoinstaller01005.dll
Wdfcoinstaller01007.dll
Wdfcoinstaller01009.dll
Winusbcoinstaller2.dll Requires KMDF version 1.9 or later Wdfcoinstaller01009.dll Winusbcoinstaller2.dll Requires KMDF version 1.11 or later WdfCoInstaller01011.dll Write an .inf file that installs Winusb.sys as the function driver for the USB device.
Create a signed catalog file for the package. This file is required to install WinUSB on x64 versions of Windows.
Attach the USB device to your computer.
Open Device Manager to install the driver. Follow the instructions on the Update Driver Software wizard and choose manual installation. You will need to provide the location of the driver package folder to complete the installation.
Related topics
Usb Device Drivers Windows 10
WinUSB Architecture and Modules
Choosing a driver model for developing a USB client driver
How to Access a USB Device by Using WinUSB Functions
WinUSB Power Management
WinUSB Functions for Pipe Policy Modification
WinUSB Functions
WinUSB