On my Win10 system, at least, the install-filter, intstall-filter-win and zadig programs do not copy the files to the windows folder and therefore the devices stop functioning(at least windows device manager reports them as not functioning).
Not a bug for install-filter and install-fiter-win -- you are supposed to have libusb-win32 device driver/dll installed first. Zadig is not part of libusb-win32 project but if you install just the filter, you need to have libusb-win32 device driver and dll installed first.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hmm... alright, but that seems like a fairly large gap in logic: install libusb as a full driver before you can use it as a filter driver.
Presumably, the choice to use filter driver mode is because you want to augment an already functioning, non-libusb device(also presumably, microsoft doesn't install libusb for you...)
In this case you don't want to install libusb as a full driver which is the requirement? What's the recommended workflow on a customers system?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
You do not install libusb as a full driver. You need to install the base package (libusb installer or libusbk installer) to install libusb0.sys into the system. You are not install libusb0.sys as any device's driver yet (device driver or filter driver) by doing that.
It is the same for other filter driver like usbdk. By installing the filter driver, it is just modifying the registry to add to the driver stack.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Not a bug for install-filter and install-fiter-win -- you are supposed to have libusb-win32 device driver/dll installed first. Zadig is not part of libusb-win32 project but if you install just the filter, you need to have libusb-win32 device driver and dll installed first.
Hmm... alright, but that seems like a fairly large gap in logic: install libusb as a full driver before you can use it as a filter driver.
Presumably, the choice to use filter driver mode is because you want to augment an already functioning, non-libusb device(also presumably, microsoft doesn't install libusb for you...)
In this case you don't want to install libusb as a full driver which is the requirement? What's the recommended workflow on a customers system?
You do not install libusb as a full driver. You need to install the base package (libusb installer or libusbk installer) to install libusb0.sys into the system. You are not install libusb0.sys as any device's driver yet (device driver or filter driver) by doing that.
It is the same for other filter driver like usbdk. By installing the filter driver, it is just modifying the registry to add to the driver stack.
BTW, please do not use Sourcefore for futher support requests. Please subscribe to libusb-win32 mailing list for futher discussions. Thanks.