- Get List of connected USB Devices
- 8 Answers 8
- USB device class drivers included in Windows
- USB Device classes
- Device setup classes
- Microsoft-provided USB device class drivers
- Windows. Devices. Usb Namespace
- Device Support
- USB Device Capabilities
- Troubleshooting
- Classes
- Enums
- USBDeview v3.01
- Leave a Reply Cancel reply
- Standard USB Identifiers
- Single-Interface USB Devices
- Multiple-Interface USB Devices
Get List of connected USB Devices
How can I get a list of all the connected USB devices on a windows computer?
8 Answers 8
Add a reference to System.Management for your project, then try something like this:
I know I’m replying to an old question, but I just went through this same exercise and found out a bit more information, that I think will contribute a lot to the discussion and help out anyone else who finds this question and sees where the existing answers fall short.
The accepted answer is close, and can be corrected using Nedko’s comment to it. A more detailed understanding of the WMI Classes involved helps complete the picture.
Win32_USBHub returns only USB Hubs. That seems obvious in hindsight but the discussion above misses it. It does not include all possible USB devices, only those which can (in theory, at least) act as a hub for additional devices. It misses some devices that are not hubs (particularly parts of composite devices).
Win32_PnPEntity does include all the USB devices, and hundreds more non-USB devices. Russel Gantman’s advice to use a WHERE clause search Win32_PnPEntity for a DeviceID beginning with «USB%» to filter the list is helpful but slightly incomplete; it misses bluetooth devices, some printers/print servers, and HID-compliant mice and keyboards. I have seen «USB\%», «USBSTOR\%», «USBPRINT\%», «BTH\%», «SWD\%», and «HID\%». Win32_PnPEntity is, however, a good «master» reference to look up information once you are in possession of the PNPDeviceID from other sources.
As a bonus, it appears that under the hood, WMI walks the Device Tree when responding to the Win32_USBControllerDevice query, so the order in which these results are returned can help identify parent/child relationships. (This is not documented and is thus only a guess; use the SetupDi API’s CM_Get_Parent (or Child + Sibling) for definitive results.) As an option to the SetupDi API, it appears that for all the devices listed under Win32_USBHub they can be looked up in the registry (at HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\ + PNPDeviceID ) and will have a parameter ParentIdPrefix which will be the prefix of the last field in the PNPDeviceID of its children, so this could also be used in a wildcard match to filter the Win32_PnPEntity query.
In my application, I did the following:
In summary, Win32USBControllerDevice Dependents are a complete list of USB Devices on a system (other than the Controllers themselves, which are the Antecedents in that same query), and by cross-referencing these PNPDeviceId pairs with information from the registry and from the other queries mentioned, a detailed picture can be constructed.
USB device class drivers included in Windows
This topic is for programmers. If you are a customer experiencing USB problems, see Troubleshoot common USB problems
This topic lists the Microsoft-provided drivers for the supported USB device classes.
If you are installing USB drivers: You do not need to download USB device class drivers. They are installed automatically. These drivers and their installation files are included in Windows. They are available in the \Windows\System32\DriverStore\FileRepository folder. The drivers are updated through Windows Update.
If you are writing a custom driver: Before writing a driver for your USB device, determine whether a Microsoft-provided driver meets the device requirements. If a Microsoft-provided driver is not available for the USB device class to which your device belongs, then consider using generic drivers, Winusb.sys or Usbccgp.sys. Write a driver only when necessary. More guidelines are included in Choosing a driver model for developing a USB client driver.
USB Device classes
USB Device classes are categories of devices with similar characteristics and that perform common functions. Those classes and their specifications are defined by the USB-IF. Each device class is identified by USB-IF approved class, subclass, and protocol codes, all of which are provided by the IHV in device descriptors in the firmware. Microsoft provides in-box drivers for several of those device classes, called USB device class drivers. If a device that belongs to a supported device class is connected to a system, Windows automatically loads the class driver, and the device functions with no additional driver required.
Hardware vendors should not write drivers for the supported device classes. Windows class drivers might not support all of the features that are described in a class specification. If some of the device’s capabilities are not implemented by the class driver, vendors should provide supplementary drivers that work in conjunction with the class driver to support the entire range of functionality provided by the device.
For general information about USB-IF approved device classes see the USB Common Class Specification
The current list of USB class specifications and class codes is documented in the USB-IF Defined Class Code List.
Device setup classes
Windows categorizes devices by device setup classes, which indicate the functionality of the device.
Microsoft defines setup classes for most devices. IHVs and OEMs can define new device setup classes, but only if none of the existing classes apply. For more information, see System-Defined Device Setup Classes.
Two important device setup classes for USB devices are as follows:
USBDevice <88bae032-5a81-49f0-bc3d-a4ff138216d6>: IHVs must use this class for custom devices that do not belong to another class. This class is not used for USB host controllers and hubs.
USB <36fc9e60-c465-11cf-8056-444553540000>: IHVs must not use this class for their custom devices. This is reserved for USB host controllers and USB hubs.
The device setup classes are different from USB device classes discussed earlier. For example, an audio device has a USB device class code of 01h in its descriptor. When connected to a system, Windows loads the Microsoft-provided class driver, Usbaudio.sys. In Device Manager, the device is shown under is Sound, video and game controllers, which indicates that the device setup class is Media.
Microsoft-provided USB device class drivers
| USB-IF class code | Device setup class | Microsoft-provided driver and INF | Windows support | Description |
|---|---|---|---|---|
| Audio (01h) | Media | Usbaudio.sys |
Note Supports Subclass 02h (ACM)
Starting with Windows Vista, you can enable CDC and Wireless Mobile CDC (WMCDC) support by setting a registry value, as described in Support for the Wireless Mobile Communication Device Class.
NoteВ В Usbprint.sys enumerates printer devices under the device set up class: Printer
The driver is loaded when a SuperSpeed hub is attached to an xHCI controller. See USB host-side drivers in Windows.
Note that for Windows Server 2003, Windows XP, and Windows 2000, special instructions are required for loading this driver because it might have been released later than the operating system.
Note Usbccid.sys driver has been replaced by UMDF driver, WUDFUsbccidDriver.dll.
Usbvideo.inf
WindowsВ Vista
Note that for Windows XP, special instructions are required for loading this driver because it might have been released later than the operating system.
Note В В Supports Subclass 01h and Protocol 01h
Bth.inf
NoteВ В Supports SubClass 04h and Protocol 01h
Note Microsoft recommends that hardware vendors build USB NCM compatible devices instead. USB NCM is a public USB-IF protocol that offers better throughput performance.
Windows. Devices. Usb Namespace
This namespace defines Windows Runtime classes that a UWP app can use to communicate with WinUSB devices. These devices are handled by the inbox winusb.sys driver and are identified by a specific Microsoft OS Descriptor.
A valid WinUSB device will have a compatible id of USB\MS_COMP_WINUSB
Device Support
This namespace supports most WinUSB devices. However, it does not provide access to USB devices with device classes of the following:
USB Device Capabilities
A UWP app that accesses a USB device must include specific device capability data in the capabilities node of its manifest. This data identifies the device and its purpose (or function). Note that some devices may have multiple functions.
Since Windows 10, version 1809 (October 2018 Update)
Before Windows 10, version 1809 (October 2018 Update)
Since 1809, the VendorId/ProductId and function-type no longer need to be specified and will be ignored on newer systems. If targeting systems below 1809, then see legacy USB device capabilities.
Troubleshooting
Classes
The endpoint descriptor for a USB bulk IN endpoint. The descriptor specifies the endpoint type, direction, number and also the maximum number of bytes that can be read from the endpoint, in a single transfer.
Represents the pipe that the underlying USB driver opens to communicate with a USB bulk IN endpoint of the device. The app can get an input stream from the pipe and access data is being read from the endpoint.
The endpoint descriptor for a USB bulk OUT endpoint. The descriptor specifies the endpoint type, direction, number and also the maximum number of bytes that can be written to the endpoint, in a single transfer.
Represents the pipe that the underlying USB driver opens to communicate with a USB bulk OUT endpoint of the device. The object provides access to an output stream to which the app can write data to send to the endpoint.
Provides information about a USB configuration, its descriptors and the interfaces defined within that configuration. For an explanation of a USB configuration, see Section 9.6.3 in the Universal Serial Bus (USB) specification.
Derives information from the first 9 bytes of a USB configuration descriptor. The information includes the power capabilities of the device when the configuration is active and the number of interfaces included in that configuration. For an explanation of a configuration descriptor, Section 9.6.3 Universal Serial Bus Specification. For information about descriptor fields, see:
Provides information about the USB control transfer, the type of control request, whether the data is sent from or to the host, and the recipient of the request in the device.
Provides information about the type of descriptor, its size (in bytes), and gets the descriptor data.
Represents a USB device. The object provides methods and properties that an app can use to enumerate WinUSB devices and send IN and OUT control transfers.
Provides a way for the app to get an Advanced Query Syntax (AQS) string by specifying the class code, subclass code, and the protocol code defined by the device. The properties in this class are passed in the call to GetDeviceClassSelector.
Provides a way for you to retrieve a UsbDeviceClass object based on the USB device class of a device. The properties defined in this class represent the supported USB device classes, and they return UsbDeviceClass objects.
For information about USB device classes, see the official USB Website for Approved Class Specification Documents.
Derives information from the USB device descriptor of the device. For an explanation of the device descriptor, see Table 9.8 in the Universal Serial Bus Specification.
Derives information from the USB endpoint descriptor of the endpoint, such as type, direction, and endpoint number. This object also gets the specific endpoint descriptors based on the type of endpoint. For an explanation of an endpoint descriptor, see Section 9.6.5 in the Universal Serial Bus Specification:
Provides information about the USB interface including its endpoints, the number of alternate settings the interface supports, and gets the entire descriptor set for those settings. It also obtains pipes associated with the endpoints that the interface supports.
Describes a USB alternate setting (of an interface) in an interface descriptor. For an explanation of an interface descriptor, see Section 9.6.5 in the Universal Serial Bus Specification:
Provides information about an alternate setting and select that setting. The app can get the USB interface descriptors for the setting and its endpoints, and determine whether this setting is currently selected.
The endpoint descriptor for a USB interrupt IN endpoint. The descriptor specifies the endpoint type, direction, number and also the maximum number of bytes that can be read from the endpoint, in a single transfer. The app can also get information about how often the host polls the endpoint for data.
Represents the object that is passed as a parameter to the event handler for the DataReceived event.
Represents the pipe that the underlying USB driver opens to communicate with a USB interrupt IN endpoint of the device. The object also enables the app to specify an event handler. That handler that gets invoked when data is read from the endpoint.
The endpoint descriptor for a USB interrupt OUT endpoint. The descriptor specifies the endpoint type, direction, number and also the maximum number of bytes that can be written to the endpoint, in a single transfer. The app can also get information about how often the host polls the endpoint to send data.
Represents the pipe that the underlying USB driver opens to communicate with a USB interrupt OUT endpoint of the device. The object provides access to an output stream to which the app can write data to send to the endpoint.
Describes the setup packet for a USB control transfer. For an explanation of the setup packet, see Table 9.2 in the Universal Serial Bus (USB) specification.
Enums
Defines constants that indicate the recipient of a USB control transfer. The recipient is defined in the setup packet of the control request. See Table 9.2 of section 9.3 of the Universal Serial Bus (USB) specification (www.usb.org).
Defines constants that indicate the type of USB control transfer: standard, class, or vendor.
Defines constants that indicate the type of USB endpoint: control, bulk, isochronous, or interrupt.
Defines constants for configuration flags that can be set for a USB pipe that the host opens for a USB bulk IN endpoint.
Defines constants that indicate the direction of USB transfer: IN or OUT transfers.
Defines constants for configuration flags that can be set for a USB pipe that the host opens for a USB OUT endpoint.
USBDeview v3.01
Утилита от NirSoft, сообщит о всех подключенные к компьютеру USB устройствах. Показывает VID, PID и другую информацию о USB устройствах. Также, отображаются информация о всех ранее подключенные устройств. Есть возможность выборочной деинсталляции USB устройств.
Дистрибутив объединяет в себе x86 и x64-редакции:
USBDeview.exe – для 32 битных систем;
USBDeview_x64.exe – для 64 битных ОС.
Для того, чтобы отключить / включить USB-устройства на x64 системах, необходимо использовать 64-разрядную версию USBDeview.
В архив с утилитой добавлен русскоязычный модуль USBDeview_lng.ini, который при желании можно удалить и язык интерфейса автоматически вернется на нормальный английский язык.
USBDeview v3.01 ; USBDeview.rar; size: 164 169 bytes
| Имя устройства | Описание | Тип устройства | Подключено | Безопасное извлечение | Запрещено | USB-концентратор | Буква диска |
| USB Flash Drive | Lenovo USB Flash Drive USB Device | Устройство хранения данных | Да | Нет | Нет | Нет | I: |
| Серийный номер | Первое подключение | Переподключение | Код поставщика | Код продукта | Версия прошивки | Класс USB | Подкласс USB |
| AA04012700010693 | 11/3/2015 11:45:15 PM | 11/3/2015 11:45:20 PM | 17ef | 3818 | 11.00 | 08 | 06 |
| Протокол USB | Концентратор, порт | Поставщик | Продукт | Префикс ParentId | Служба | Описание службы | Файл драйвера |
| 50 | 7&240d8652&3 | USBSTOR | USB Mass Storage Driver | USBSTOR.SYS | |||
| Класс устройства | Производитель устройства | Мощность (ток) | Версия USB | Описание драйвера | Версия драйвера | Код экземпляра устройства | Возможности |
| USB | Compatible USB storage device | 500 mA | 2.00 | USB Mass Storage Device | 5.1.2600.0 | USB\Vid_17ef&Pid_3818\AA04012700010693 | Removable, UniqueID |
Leave a Reply Cancel reply
This site uses Akismet to reduce spam. Learn how your comment data is processed.
Standard USB Identifiers
The set of identifiers generated for USB devices depends on whether the device is a single-interface device or a multiple-interface device.
Single-Interface USB Devices
When a new USB device is plugged in, the system-supplied USB hub driver composes the following device ID by using information extracted from the device’s device descriptor:
v(4) is the 4-digit vendor code that the USB committee assigns to the vendor.
d(4) is the 4-digit product code that the vendor assigns to the device.
r(4) is the revision code.
The hub driver extracts the vendor and product codes from the idVendor and idProduct fields of the device descriptor, respectively.
An INF model section can also specify the following hardware ID:
and the following compatible IDs:
c(2) is the device class code taken from the device descriptor.
s(2) is the device subclass code.
p(2) is the protocol code.
The device class code, subclass code, and protocol code are determined by the bDeviceClass, bDeviceSubClass, and bDeviceProtocol fields of the device descriptor, respectively. These are 2-digit numbers.
Multiple-Interface USB Devices
Devices with multiple interfaces are called composite devices. Starting with Windows 2000, when a new USB composite device is plugged into a computer, the USB hub driver creates a physical device object (PDO) and notifies the operating system that its set of child devices has changed. After querying the hub driver for the hardware identifiers associated with the new PDO, the operating system searches the appropriate INF files to find a match for the identifiers. If it finds a match other than USB\COMPOSITE, it loads the driver indicated in the INF file. However, if no other match is found, the operating system uses the compatible ID USB\COMPOSITE, for which it loads the USB Generic Parent driver. The Generic Parent driver then creates a separate PDO and generates a separate set of hardware identifiers for each interface of the composite device.
Each interface has a device ID of the following form:
v(4) is the 4-digit vendor code that the USB committee assigns to the vendor.
d(4) is the 4-digit product code that the vendor assigns to the device.
z(2) is the interface number that is extracted from the bInterfaceNumber field of the interface descriptor.
An INF model section can also specify the following compatible IDs:
d(2) is the device class code taken from the device descriptor.
s(2) is the subclass code.
p(2) is the protocol code.
The device class code, subclass code, and protocol code are determined by the bInterfaceClass, bInterfaceSubClass, and bInterfaceProtocol fields of the interface descriptor, respectively. These are 2-digit numbers.
detector