To target Windows 8.1, Windows 8, and Windows 7, install an older WDK and an older version of Visual Studio either on the same machine or on a separate machine. For links to older kits, see Other WDK downloads.
Join the Windows Insider Program to get WDK Insider Preview builds. For installation instructions for the Windows Insider Preview builds, see Installing preview versions of the Windows Driver Kit (WDK).
The WDK NuGet package consists of essential libraries, headers, DLL, tools, and metadata used for building Windows drivers that can be shared and supported by modern CI/CD pipelines. Users can access and consume the NuGet packages directly from nuget.org within Visual Studio. Using NuGet with the WDK provides a convenient solution for WDK acquisition and updates. It manages dependencies such as the SDK, to help keep the driver development tool chain up to date. For more information, see Install the latest WDK using NuGet - Step by Step.
Starting with WDK version 10.0.26100.1, the WDK now supports development, testing and deployment of drivers on ARM64 machines. The WDK/EWDK can be installed and run natively on ARM64 hardware, in addition to the previously supported emulation of x86 KMDF/UMDF2 drivers on ARM64 hardware. There is also support for debugging and deployment of drivers to an ARM64 target machine from both ARM64 and x64 host machines. The process of installing WDK/EWDK on ARM64 machines will automatically identify and install all the necessary dependencies including build tools, binaries, and libraries.
The provided links for the SDK and the WDK have matching build numbers, which is always required for the kits to work together. If you decide to install your own SDK/WDK pair, perhaps for a different Windows version, ensure that the build numbers match. For more details, see Kit versioning.
As an alternative to downloading Visual Studio, the SDK, and the WDK, you can download the EWDK, which is a standalone, self-contained command-line environment for building drivers. It includes Visual Studio Build Tools, the SDK, and the WDK.
You can optionally use the Visual Studio interface with the build tools provided in the EWDK. To do this, ensure that the Visual Studio major version matches the version of the Visual Studio Build Tools in the EWDK. For example, Visual Studio 2022 works with the EWDK that contain VS17.X build tools. For a list of Visual Studio 2022 version numbers, see Visual Studio 2022 Releases.
To build a driver, the build number of your SDK installation must match the build number of your WDK installation. The QFE values does not need to match unless your driver uses functionality that is only available in the headers included with a later QFE.
A quick way to see the full build string for locally installed kits is to go to Windows settings (Win+I), navigate to Apps, then Installed apps, and in the Search box type kit. The full build string appears to the right of the kit name. If you navigate to C:\Program Files (x86)\Windows Kits\10\Include, note that the QFE shown there is hardcoded to .0, so this is not a reliable way to check your QFE identifier. Also note that when you install a kit, the new installation replaces any previously existing installation of the same build number. When you install Visual Studio with the Desktop development with C++ workload, if the installation payload includes the Windows SDK, the right-hand Summary pane also shows a hardcoded .0 for QFE.
Driver updates for Windows, along with many devices, such as network adapters, monitors, printers, and video cards, are automatically downloaded and installed through Windows Update. You probably already have the most recent drivers, but if you'd like to manually update or reinstall a driver, here's how:
I've done it on Windows 10. After plugging the USB blaster II then go to Install Drivers and navigate to the install directory and there is a drivers directory. I've done it twice on this machine and it's worked.
I tried one option for eliminating driver signing (command line) and tried the advanced restart settings suggestion above but that ended with a bricked computer and a call to IT to get a bitlocker key. I'm not trying it again.
I tried both. The first didn't seem to work though I'll try again. The second bricked my computer. If you have an encrypted drive you need the encryption key to use option 2. IT fixed it but I'm not doing it again.
Excellent instructions. First my new Eval kit didn't blink lights on first power up like it was supposed to, then the first run of Quartus Lite V20 required Admin permission (Run as Administrator), then the driver was not signed and this helped. What a mess trying to get a demo going on my latest Win 10 with their latest software but I now have blinky lights (on to real code).
Intel does not verify all solutions, including but not limited to any file transfers that may appear in this community. Accordingly, Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade.
I see that the GPIB-USB-B compatibility ended with version NI 488.2 version 17.6. I have 20 installed so the 17.6 install doesn't fully run since a higher version is installed. Do I have to uninstall 20 to use my NI hardware?
Why yes. It turns out that's exactly what I have to do. I uninstalled 20 and installed 17.6 and it works. Does that mean it will keep that driver if I upgrade to 20 now or will it kill the device? I guess I'll see when I add a device that isn't compatible with 17.6.
I have two devices to be operated simultaneously. But one device was not supportet in v17.6 yet the other is the GPIB-USB-B. So I had to find a way to get them both running in the latest environment as I had no option to uninstall v20.0.
We are trying to communicate between an Agilent light meter via a Keysight software through GPIB-USB-B. I see that the GPIB-USB-B is supported by NI 488.2 v17.6 and older drivers. I get a runtime Engine error of LabVIEW.
Driver Booster will quickly spot broken and outdated drivers and finds the exact up-to-date match for the system and devices. The driver database supports more than 6.5 million devices & drivers from 1200+ major brands. Besides, driver sources are all officially from the original hardware manufacturers and have passed the Microsoft WHQL test and IObit test.
Driver issues will bring painful inconveniences to your life. Crashing, freezing, no sound, keyboard stuck, or frequent network drops, you name it. Driver booster provides free built-in tools to resolve these common Windows issues such as sound, video, graphic, and Wi-Fi connectivity issues once and for all, as well as speed up browsing and downloading for smoother system performance.
Driver Booster provides a safe and stable display driver uninstaller to completely uninstall AMD/NVIDIA/INTEL graphics card drivers, and remove all traces of display driver leftovers. If you want entirely new driver installation, delete drivers that are causing issues, or upgrade GPU from AMD to Nvidia, this driver removal is a must-have.
"Iobit's Driver Booster is the best software available. I have been using all the Iobit Driver Boosters and other Iobit software for many years now. Driver Booster finds outdated drivers for my laptop's and along with using other Iobit software keeps my systems running smoothly. As usual Iobit does it again with a great software that is innovated with new technology to keep my laptop's running at their best."
"One scan a day keeps outdated drivers away. Instead of looking individually for drives updates; just one click on Driver Booster can keep all of my pc's drivers up-to-date! Driver Booster improved my gaming experience especially when it comes to demanding games that needs the latest updates. IObit products showed me the true capability of my pc."
"I was having all sorts of problems with my laptop, finally realizing that it was caused by the drivers. Despite going through all the channels my laptop brand provides I was still having problems. One click of Driver Booster and it found 17 (long) outdated drivers and fixed them just as quickly. My driver problems have disappeared and my laptop is running much better! I will use no other program for my driver needs."
Excellent option for budget/conscious peeps who need a useful driver update utility, beats most of the competition when it comes to extra features and services, such as a game booster, updating game components, and offline driver updates* A solid performer providing consistency and reliability!
I always keep it running while playing because of its "Game Boost" feature, which actually helps in performance, mainly so that your computer focuses its resources on the game you're playing. It's also useful for updating your drivers every few weeks, which you could do manually, but why would you?
1. Was able to get it to upload the patch. Then, the driver up did upload. I was able to print one photo and scan one doc. Didn't use the printer for several days, then it would not work at all--not to print or scan. The printer hardware is still in excellent condition, but the message reads that the PC does not recognize that the printer is plugged in, or attached by USB port.
7fc3f7cf58