libwdi: Windows Driver Installer library for usb devices
The aim of this project is to provide Windows application developers and driver makers, with a convenient way of extracting and installing USB drivers on end-users systems. Such drivers can then be used with, but not limited to, libusb applications using libusb 1.0 or libusb-win32.
If you have a question that cannot be answered in these pages, please send an e-mail to email@example.com.
Make sure you have '[libwdi]' in the e-mail subject so that your question is dealt with appropriately. Or you can also try to mail the developers directly.
- Automated driverless device detection
- Automated inf creation, using the name reported by the USB device
- Automated driver files extraction, for both 32 and 64 bit platforms
- Automated driver installation, including UAC elevation where necessary
- A single library, embedding all the required files. Can be statically or dynamically linked to an application, so that driver installation can be taken care automatically of when required.
- Ability to produce a single library that runs and can install drivers on any platform from Windows 2000 to Windows 7
- Ability to produce a single library that runs and can install drivers on both 32 and 64 bit versions of Windows
- Allows the embedding and selection of WinUSB, libusb0.sys (from libusb-win32) or your own USB driver (eg. WHQL drivers)
- Allows the installation of your code signing certificate as a Trusted Publisher
- Full locale support. All API strings are UTF-8, and the generated inf is UTF-16
- Open Source, with a proprietary application friendly license (LGPL v2.1)
- v1.0.4 (released 2011.01.22)
- v1.0.3 (released 2010.10.07)
- v1.0.2 (released 2010.09.15)
- v1.0.1 (released 2010.09.01)
- For Zadig, the WinUSB and libusb-win32 driver installer, you can either click the previous link or visit the Driver Installation section of the libusb Windows backend page.
- Using Zadig (the GUI driver installer application)
- Library Installation & Configuration
- Library API Documentation & Usage
- Signed driver installation walkthrough
The following development environments are currently supported for libwdi on Windows:
- MinGW (32 bit) or MinGW-w64. To compile a library that is both 32 and 64 bit compatible, you should use a version of MinGW-w64 that supports both -m32 and -m64 (a.k.a. "multilib"). TDM64 is a good MinGW-w64 distribution under Windows which fulfills this requirement.
- Microsoft Visual C++ (Visual Studio) 2008. Only the full version will allow you to produce 64 bit or or 32+64 bit binaries.
- Windows DDK build environment, which is freely available, through the use of the 'ddk_build.cmd' file. This will also produce all of 32, 64 or 32+64 bits binaries. Note that if you want to produce libwdi applications that are compatible with all supported platforms from XP onwards, you will need to use the Windows XP WDK build environment for the 32bit builds and Windows Server 2003 build environment for the 64bit build. Take note the WDK versions after 7600.16385.0 drop the support for Windows 2k. If you want to support Windows 2k, then you may have to use the 6001.18002 version (the last WDK version to support Windows 2k). However, please take note Microsoft recommends to use the latest WDK so using WDK 6001.18002 is not officially supported.
- cygwin (32 bit only).
The recommended development environment to compile the library/apps is the latest Windows DDK as it allows the building of a 32+64 bit compatible library, and ensures that the required WinUSB DLL files are available. If you need Windows 2000 compatibility you may have to use MinGW.org (32bit only) or the older version of WDK 6001.18002. You can also use multilib MinGW-w64, which appears to work fine, but be mindful that Windows 2000 targets are not officially supported by the MinGW-w64 team.
The current development tree is available from our SourceForge repository.
For those not familiar with git, here are the git commands you can use retrieve and compile the Windows branch:
git clone git://libwdi.git.sourceforge.net/gitroot/libwdi/libwdi ; retrieve development branch (this only needs to be done once) git pull ; for further updates, once the clone has been done
If you don't want to use git from the commandline, you can use TortoiseGit or Git Extensions to access and keep in sync with the git repository. Git Extensions comes ready to use, but note that before you can install TortoiseGit you need to install MSysGit.
Also note that, for MinGW and cygwin, as with the libusb development tree, you need to run
./autogen.sh in order to have configure and Makefile created for you.
To create projects relying on libwdi, please refer to how the sample executables zadic (console) and zadig (GUI) are compiled.
- Because the driver installation requires administrative privileges, but enumeration does not, the library compiled and embeds a 32/64 bit installer, that requires UAC elevation on platforms supporting UAC (Windows Vista and later).
- The project also uses a customer embedder to include the required driver resources (DLLs, 32 and 64 bit installer) along with any files you want to add (eg. signed inf). Note that since most of the DLLs are already compressed, there's not much space to be gained in using compression in the embedder.
- The reliance on DifXAPI.dll was dropped in w20, as the DLL is not available by default on XP and would increase the binary size.
- It is possible to produce a 32 bit library that is 32+64 bit compatible, but the opposite is not true. As such, when compiling for 64 bit, 32 bit compatibility will be removed to make the library smaller.
- downloading vs embedding of the driver files
- libusbK support
- trusted publisher certificate installation for promptless install
- cross-compilation & embedder improvements
- GUI sample application (zadig)
- allow the editing of the device name
- libusb0.sys driver support
- MinGW/cygwim/MSVC/DDK support
- 32 and 64 bit support and compilation time detection
- UAC elevation
- retrieval of device name
- automated inf generation
- Writing a Device Installation Application
- Determining Whether a Device Is Plugged In and removal of phantom devices
- Installer Detection for 32 bit applications
- Embedding manifests (for UAC elevation) with the DDK build environment
- Troubleshooting Device Installation with the SetupAPI Log File
- Debugging Device Installation in Windows Vista
- How To Browse for Folders from the Current Directory
- UI design guidelines from MSDN
- Setting Visual Styles
- Creating Status Bars
- How Windows elects the driver to use against a newly plugged device
- Using INX Files to Create INF Files
- Summary of INF Sections
Reusable Code Parts: Can our code solve your problems?
As a FOSS developer, there's nothing more frustrating than having to reinvent the wheel while harbouring a strong suspicion that someone, somewhere, might already have solved a similar issue.BR On the other hand, googling around and looking through scores of FOSS code listings to find that particular section of code which might be of interest to you is quite time consuming. Wouldn't it be just swell if the developers simply gave an detailed, high level overview of the problems they solved, whose solutions they think you can reuse?
The following page does just that and goes through a list of the features we implemented, which you might be interested in (provided your license is compatible with LGPL v2):