-->![Download Debugging Drivers For Windows 7 Download Debugging Drivers For Windows 7](/uploads/1/2/6/4/126430621/681797352.jpg)
![Debugging Debugging](/uploads/1/2/6/4/126430621/714020473.png)
Installs Intel® Network Adapter drivers release 23.2 for Windows* 7. Network Adapter Driver for Windows 7*. For Windows 7*. Which file should you download? Installs Intel® Network Adapter drivers release 23.2 for Windows* 7. Network Adapter Driver for Windows 7*. For Windows 7*. Which file should you download?
The WDK is used to develop, test, and deploy Windows drivers. The latest public version of WDK is available below.
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).
WDK for Windows 10, version 1903
Step 1: Install Visual Studio 2019
The following editions of Visual Studio 2019 support driver development:
When you install Visual Studio 2019, select the Desktop development with C++ workload. The Windows 10 Software Development Kit (SDK) is automatically included, and is displayed in the right-hand Summary pane. However, the version of the SDK that is compatible with the WDK for Windows 10, version 1903 is not currently the default SDK. To select the correct SDK:
![Download Debugging Drivers For Windows 7 Download Debugging Drivers For Windows 7](/uploads/1/2/6/4/126430621/681797352.jpg)
- In Visual Studio Installer, on the Workloads tab, under Installation Details, expand Universal Windows Platform development.
- Under Optional, select Windows 10 Preview SDK (10.0.18362.0).
- Continue with the install.
If you already have Visual Studio 2019 installed, you can install the Windows 10 Preview SDK (10.0.18362.0) by using the Modify button in Visual Studio install.
Download Adb Drivers For Windows 7 64 Bit
For ARM/ARM64 driver development, choose Individual components and under Compilers, build tools, and runtimes select Visual C++ compilers and libraries for ARM/ARM64.
For each architecture you intend to build drivers for, install the Spectre mitigated libraries thru Individual Components -> Compilers, build tools, and runtimes -> MSVC v142 - VS 2019 C+ x64/x86 Spectre-mitigated libs (v14.21).
Step 2: Install WDK for Windows 10, version 1903
New as of 1709 release: The WDK installation will by default install the WDK Visual Studio extension. This must be done in order for WDK VS integration to work.
Enterprise WDK for Windows 10, version 1903 (EWDK)
The EWDK is a standalone self-contained command-line environment for building drivers. It includes the Visual Studio Build Tools, the SDK, and the WDK. The latest public version of the EWDK contains Visual Studio 2019 Build Tools 16.0.0. To get started, mount the ISO and run LaunchBuildEnv.
EWDK with Visual Studio Build Tools
Additional information
Release notes and run-time requirements
WDK requires Visual Studio, for more information more info on system requirements for Visual Studio please review Visual Studio 2019 System Requirements.
EWDK will additionally need .NET 4.7.2, for more information on what .NET runs on please review .NET Framework system requirements.
You can use the WDK to develop drivers for these operating systems:
Client OS | Server OS |
---|---|
Windows 10 | Windows Server 2019, Windows Server 2016 |
Windows 8.1 | Windows Server 2012 R2 |
Windows 8 | Windows Server 2012 |
Windows 7 | Windows Server 2008 R2 SP1 |
Universal Windows driver samples
To get universal Windows driver samples, do one of the following:
- Go to the driver samples page on GitHub and click Clone or download > Download ZIP on the right side of the page.
- Download the GitHub Extension for Visual Studio to connect to the GitHub repositories.
- Browse the driver samples on the Microsoft Samples portal.
Related downloads
-->Start here for an overview of Debugging Tools for Windows. This tool set includes WinDbg and other debuggers.
Install Debugging Tools for Windows
You can get Debugging Tools for Windows as part of a development kit or as a standalone tool set:
- As part of the WDKDebugging Tools for Windows is included in the Windows Driver Kit (WDK). To get the WDK, see Download the Windows Driver Kit (WDK).
- As part of the Windows SDKDebugging Tools for Windows is included in the Windows Software Development Kit (SDK). To download the installer or an ISO image, see Windows 10 SDK on Windows Dev Center.
- As a standalone tool setYou can install the Debugging Tools for Windows alone, without the Windows SDK or WDK, by starting installation of the Windows SDK and then selecting only Debugging Tools for Windows in the list of features to install (and clearing the selection of all other features). To download the installer or an ISO image, see Windows 10 SDK on Windows Dev Center.
Get started with Windows Debugging
To get started with Windows debugging, see Getting Started with Windows Debugging.
To get started with debugging kernel-mode drivers, see Debug Universal Drivers - Step by Step Lab (Echo Kernel-Mode). This is a step-by-step lab that shows how to use WinDbg to debug Echo, a sample driver that uses the Kernel-Mode Driver Framework (KMDF).
Debugging environments
If your computer has Visual Studio and the WDK installed, then you have six available debugging environments. For descriptions of these environments, see Debugging Environments.
All of these debugging environments provide user interfaces for the same underlying debugging engine, which is implemented in the Windows Symbolic Debugger Engine (Dbgeng.dll). This debugging engine is also called the Windows debugger, and the six debugging environments are collectively called the Windows debuggers.
Note
Visual Studio includes its own debugging environment and debugging engine, which together are called the Visual Studio debugger. For information on debugging in Visual Studio, see Debugging in Visual Studio. For debugging managed code, such as C#, using the Visual Studio debugger is often the easiest way to get started.
Windows debuggers
![Debugging Debugging](/uploads/1/2/6/4/126430621/714020473.png)
The Windows debuggers can run on x86-based, x64-based, or ARM-based processors, and they can debug code that is running on those same architectures. Sometimes the debugger and the code being debugged run on the same computer, but other times the debugger and the code being debugged run on separate computers. In either case, the computer that is running the debugger is called the host computer, and the computer that is being debugged is called the target computer. The Windows debuggers support the following versions of Windows for both the host and target computers.
- Windows 10 and Windows Server 2016
- Windows 8.1 and Windows Server 2012 R2
- Windows 8 and Windows Server 2012
- Windows 7 and Windows Server 2008 R2
Symbols and symbol files
Symbol files store a variety of data that are not required when running the executable binaries, but symbol files are very useful when debugging code. For more information about creating and using symbol files, see Symbols for Windows debugging (WinDbg, KD, CDB, NTSD).
Blue screens and crash dump files
If Windows stops working and displays a blue screen, the computer has shut down abruptly to protect itself from data loss and displays a bug check code. For more information, see Bug Checks (Blue Screens). You analyze crash dump files that are created when Windows shuts down by using WinDbg and other Windows debuggers. For more information, see Crash dump analysis using the Windows debuggers (WinDbg).
Tools and utilities
In addition to the debuggers, Debugging Tools for Windows includes a set of tools that are useful for debugging. For a full list of the tools, see Tools Included in Debugging Tools for Windows.
Additional documentation
For additional information related to Debugging Tools for Windows, see Debugging Resources. For information on what's new in Windows 10, see Debugging Tools for Windows: New for Windows 10.