libwdi | Windows Driver Installer library for USB devices

by pbatard C Version: v1.5.0 License: GPL-3.0

X-Ray Key Features Code Snippets Community Discussions(2)Vulnerabilities Install Support

kandi X-RAY | libwdi Summary

libwdi is a C library. libwdi has no bugs, it has no vulnerabilities, it has a Strong Copyleft License and it has medium support. You can download it from GitHub.

Windows Driver Installer library for USB devices

Support

Quality

Security

License

Reuse

Support

libwdi has a medium active ecosystem.

It has 1468 star(s) with 422 fork(s). There are 107 watchers for this library.

It had no major release in the last 12 months.

There are 0 open issues and 256 have been closed. On average issues are closed in 62 days. There are no pull requests.

It has a neutral sentiment in the developer community.

The latest version of libwdi is v1.5.0

Quality

libwdi has 0 bugs and 0 code smells.

Security

libwdi has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

libwdi code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

libwdi is licensed under the GPL-3.0 License. This license is Strong Copyleft.

Strong Copyleft licenses enforce sharing, and you can use them when creating open source projects.

Reuse

libwdi releases are available to install and integrate.

Installation instructions are available. Examples and code snippets are not available.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of libwdi

Get all kandi verified functions for this library.

libwdi Key Features

No Key Features are available at this moment for libwdi.

libwdi Examples and Code Snippets

No Code Snippets are available at this moment for libwdi.

Community Discussions

Trending Discussions on libwdi

Can I use SetupDiEnumDeviceInterfaces to get a DevicePath from SetupDiGetDeviceInterfaceDetail when no InterfaceClassGUID is known?

Why isn't windows loading the WINUSB Driver?

QUESTION

Can I use SetupDiEnumDeviceInterfaces to get a DevicePath from SetupDiGetDeviceInterfaceDetail when no InterfaceClassGUID is known?

Asked 2021-May-14 at 14:11

Overview...

I have read How to get device interface GUID for a device? and How to open a handle to a device using its Device Instance ID?, but I'm still confused about how I am to (or whether I should even) use SetupDiEnumDeviceInterfaces paired with SetupDiGetDeviceInterfaceDetail to get a DevicePath that can be opened with CreateFile to access the device when no device interface class GUID is known. My question is based on the MSDN article here and here which rely on these functions.

More details...

The high level of my problem is I've got an audio USB device I need to send control transfer commands. To do so, I want to use WinUSB's API, and to do that I need to get a handle to the device via CreateFile. Unfortunately, there is no .inf file associated with the device and so there is no known device interface class GUID. If one plugs the device in, Windows associates with it usbaudio.sys as the driver. To start talking over WinUSB, I use libwdi to install WinUSB as the device driver so that I can communicate with it via the WinUSB API. To accomplish the install of WinUSB, libwdi dynamically creates a self-signed .cat and .inf file pair, which unfortunately has no device interface class defined. In fact, the INF file has the following in it:

...

ANSWER

Answered 2021-May-14 at 00:32

Yes, first you need to get a device information set for devices that implement the interface via SetupDiGetClassDevs, then pick one of the devices and read its device interface data, and use that to get the device interface detail that contains the device path.

Example:

Source https://stackoverflow.com/questions/67527315

QUESTION

Why isn't windows loading the WINUSB Driver?

Asked 2020-Nov-03 at 01:07

I'm developing a USB Device containing a couple of USB Functions (CDC-ACM and DFU as of now), using windows provided drivers.

The device descriptor indicates the device uses IAD (Interface Association Descriptor) and the configuration descriptor reflects that, containing all the descriptors for the CDC function as well as the DFU Function. This configuration works right out of the box on non-windows platforms, with both drivers correctly assigned.

Due to WCID (Windows Compatible ID) requirements, I have setup the following descriptor indicating that windows should load WINUSB for the DFU Interface.

...

ANSWER

Answered 2020-Sep-08 at 03:02

You don't need to use Zadig to see what drivers Windows is using. The list of SYS files is shown in the Device Manager when you double-click on your device and go to the "Driver" tab.

At some point, possibly through software like Zadig, you might have loaded an INF file on your computer that tells it to use libusb0 with your device. You can inspect your device in the Device Manager and look at the "Inf Name" field to find out what INF file is responsible for this, if that is the case.

I recommend that you right-click on your device and select "Uninstall Device..." to remove your device's association with libusb0. You should also click the "Uninstall driver software" checkbox as you are doing this to remove the unwanted INF file (if it exists).

Source https://stackoverflow.com/questions/63774162

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install libwdi

You can download it from GitHub.

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: