Install Libusb Windows 10

I have a custom composite USB device with usbser, winusb, usbstor interfaces. We have a few hundred devices running for three ish years now, with billions of libusb operations. (Thanks folks!) on win7,8,10. The unit has a feature in which I send a command to the winusb interface to reconfigure it's usb serial#. The device soft disconnects from the USB bus, changes part of it's descriptor (the serial number), waits 500ms (or 2seconds, doesn't help the issue) and then reconnects. Under windows 7, and the virus known as windows 8, this works fine.

Jul 2, 2018 - libusb-win32 is a port of libusb-0.1 under Windows. Digital transformation platform, enables teams to build powerful applications 10x faster.

Under windows 10, I get a duplicate entry of the old device in my libusb_get_device_list structure. Below is a data dump. I have libusb debugging turned on (hence the first 3 lines) The first line (VID 046D) is a USB flash drive that was unplugged during a PRIOR power cycle of the box. Where or why libusb is complaining about this device is a mystery to me.

At the same time it may likely be a clue to the what is going on. Using usbdview, all 3 errant devices are not present. The second 2 lines (VID 2B2A) refer to the winusb and msc interfaces on my composite device, and the parent id of 17AD5DBB is the old parent from the previous enumeration of my device.

(with the old serial number). 2B2A is a private USB VID. Finally, the 0), 1), 2), is a simple crawl of the libusb_get_device_list with libusb_get_devicedescriptor There should be only one VID 2B2A in this list (as there is on win7/8); there is only 1 device attached to the PC. If I reboot, there is in fact only 1 device present, and things work. However, rebooting isn't really an option for the actual use case of the product. (but I still get the gripe about the USB flash drive) libusb: error [init_device] device '.

Devid.info is not responsible in any way for the performance of or issues caused by any third-party drivers.Drivers may also be available for free directly from manufacturers' websites. Any other third-party products, brands or trademarks listed above are the sole property of their respective owner. Drivers are the property and the responsibility of their respective manufacturers, and may also be available for free directly from manufacturers' websites. Microsoft and Windows are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.

USB#VID_046D&PID_C080&MI_01#6&33F61665&0&0001' is no longer connected! Libusb: error [init_device] device '. USB#VID_2B2A&PID_0156&MI_02#6&17AD5DBB&1&0002' is no longer connected! Libusb: error [init_device] device '. USB#VID_2B2A&PID_0156&MI_03#6&17AD5DBB&1&0003' is no longer connected! • VID 1B21 PID 1242 CLS 0000 PROT 00 • VID 1B1C PID 1B15 CLS 0000 PROT 00 • VID 1B1C PID 1B15 CLS 0000 PROT 00 • VID 046D PID C080 CLS 0000 PROT 00 • VID 2B2A PID 0156 CLS 00EF PROT 01 • VID 2B2A PID 0156 CLS 00EF PROT 01 • VID 8086 PID A12F CLS 0000 PROT 00 Any suggestions are welcome. I unload libusb as soon as possible after firing off the call that causes the disconnect/modification of the serial number/reconnect.

I am confident that I have unloaded the libusb default context, closed libusb, and exited my program before the USB endpoint device performs the soft-disconnect. The errant behavior happens on 3 different windows 10 Pro boxes. In all cases, the device is connected to the root hub embedded in the Intel chipset.

(USB xHCI ) -Steve. ' USB endpoint device performs the soft-disconnect.' Disconnect is not end point but device related and even if s/w driven it is h/w, So what you mean here? Even by f/w what must be done is to disconnected the device Pull up /dow on, the D+/D- line to get host view a device disconnect and reconnection (force re-enumeration). But i guess that is what you do as device is re-enumerating somehow A similar common issue i see often is with 'usb serial' device disconnect/reconnect or 'f/w reset' not found by host of failing to work.

It's because at reconnect time the application (terminal emulator) is stilll holding and using the first 'dead' usb device instance so it can be re-created and connected to newly replug (maybe reusign the first zombi one again). To solve this ensure all app are close (double check in program manager if the app is not still their in a kind of zombi state), then only un/re-plug device. Recheck device list. No reboot is needed. Can you try the same? In the past i did some re-enum test with an stm32 f/w doing usb disconnect (10ms) and changing one string the host app was not even closing simply closing handle calling libusb_exit / init again.