Wdk 10

Previous WDK versions and other downloads – Windows drivers

Wdk 10

  • 05/07/2018
  • 6 minutes to read
    • E
    • C
    • D
    • m
    • g

This topic contains information about earlier versions of the Windows Driver Kit (WDK),Enterprise WDK (EWDK), and additional downloads for support purposes. To develop drivers,use the latest public versions of the Windows Driver Kit (WDK) and tools, available fordownload on Download the Windows Driver Kit (WDK).

The Windows Driver Kit (WDK) is used to develop, test, and deployWindows drivers. To develop drivers, use the latest public versions ofthe Windows Driver Kit (WDK) and tools, available for download onDownload the Windows Driver Kit (WDK).

This topic contains information about earlier versions of the WDK, theEnterprise WDK (EWDK), and additional downloads for support purposes. Touse these earlier versions, you must first install the version ofVisual Studio that is appropriate for your targeted platform.

Runtime requirements

You can run the Windows 10, version 1903 WDK on Windows 7 and later, and use it to develop drivers for these operating systems:

Client OSServer OS
Windows 10Windows Server 2019, Windows Server 2016
Windows 8.1Windows Server 2012 R2
Windows 8Windows Server 2012
Windows 7Windows Server 2008 R2 SP1

Step 1: Install Visual Studio

The WDK requires Visual Studio. For more information about system requirements for Visual Studio, see Visual Studio 2019 System Requirements.

The following table indicates which Visual Studio version is required for the different releases of the WDK.

Configure Visual Studio for Windows 10, versions 1709, 1803, 1809 and 1903

When you install Visual Studio, select the Desktop development withC++ workload. The Windows 10 Software Development Kit (SDK) isautomatically included and is displayed in the right-hand Summarypane.

To develop drivers for ARM/ARM64, choose Individual components andunder Compilers, build tools, and runtimes select Visual C++compilers and libraries for ARM/ARM64.

Install the Windows SDK to target Windows 10, versions 1607 and 1703

If your development targets systems that run Windows 10, version 1607 or Windows 10, version 1703, you should install Visual Studio 2015, and then also download and install the version of the Windows SDK for the targeted version of Windows 10, as identified in the following table.

The Windows SDK was not included in Visual Studio 2015, so you must install the SDK separately. Later versions of Visual Studio include the Windows SDK.

Step 2: Install the WDK

The WDK is integrated with Visual Studio and Debugging Tools for Windows(WinDbg). This integrated environment gives you the tools you need todevelop, build, package, deploy, test, and debug drivers.

Note

Starting with Windows 10, version 1709, installing the WDKwill by default install the WDK extensions for Visual Studio. Theseextensions are required for integration of the WDK with Visual Studio.

Versions of WindowsWDK and related downloads
Windows 10, version 2004WDK for Windows 10, version 2004 (10.1094.1)* See Note below
Windows 10, version 1903WDK for Windows 10, version 1903
Windows 10, version 1809WDK for Windows 10, version 1809
Windows 10, version 1803WDK for Windows 10, version 1803
Windows 10, version 1709WDK for Windows 10, version 1709
Windows 10, version 1703WDK for Windows 10, version 1703
Windows 10, version 1607WDK for Windows 10, version 1607
Windows 8.1 UpdateWDK 8.1 Update (English only) – temporarily unavailableWDK 8.1 Update Test Pack (English only) – temporarily unavailable WDK 8.1 Samples
Windows 8WDK 8 (English only) WDK 8 redistributable components (English only) WDK 8 Samples
Windows 7WDK 7.1.0

Important

If you have installed the WDK for Windows 10, version 1703 on a system that had the WDK for Windows 10, version 1607 installed, some files from the earlier version of the WDK might have been removed. To restore these files:

  1. On the Start menu, enter Apps & features in the search box, and select Apps & features from the results.
  2. Find Windows Driver Kit – Windows 10.0.15063.0 in the list of Apps & Features, and then select the program.
  3. Select Modify, select Repair, and then follow the directions on the screen.
  4. The files will be restored.

Optional: Install the EWDK

The Enterprise WDK (EWDK) is a standalone, self-contained, command-line environment forbuilding drivers and basic Win32 test applications. It includes theVisual Studio Build Tools, the SDK, and the WDK. This environmentdoesn't include all the features available in Visual Studio, such asthe integrated development environment (IDE).

Using the EWDK requires .NET Framework 4.6.1. For more information about which systems run this version of the framework, see .NET Framework system requirements. For links to download the .NET Framework, see Install the .NET Framework for developers.

For more information about the EWDK, seeUsing the Enterprise WDK 10.

Note

Starting in Windows 10 version 1709, the EWDK is ISO-based. To get started, download and mount the ISO, and then run LaunchBuildEnv.

To work with HAL Extensions, prepare your development system, running Windows 10, version 1709 or a later version of Windows 10. Also install the WDK or the EWDK, and then install the updated version of the Windows OEM HAL Extension Test Cert 2017 (TEST ONLY), available for download as a ZIP file: HAL_Extension_Test_Cert_2017.zip.

For more information about using this updated certificate, see Update for “Windows OEM HAL Extension Test Cert 2017 (TEST ONLY)” test certificate on Windows Support.

Optional: Install WinDbg Preview

WinDbg Preview is a new version of WinDbg with more modern visuals, faster windows, a full-fledged scripting experience, built with the extensible debugger data model front and center. WinDbg Preview supports debugging every version of Windows 10.

For download links and more information about WinDbg Preview, see Download WinDbg Preview.

If you're debugging Windows XP, Windows Server 2003, Windows Vista, orWindows Server 2008 (or using one of these operating systems to runDebugging Tools for Windows), you need to use the Windows 7 release ofthe debugging tools. It's included in the SDK for Windows 7 and .NETFramework 4.0.

Get the standalone debugging tools for Windows XP by first downloadingthe Windows 7 SDK:Microsoft Windows SDK for Windows 7 and .NET Framework 4.

To install the Debugging Tools for Windows as a standalone component,start the SDK installer, and in the installation wizard, selectDebugging Tools for Windows, and clear all other components.

Submit and view feedback for

Источник: https://docs.microsoft.com/en-us/windows-hardware/drivers/other-wdk-downloads

Download the Windows Driver Kit (WDK) – Windows drivers

Wdk 10

  • 08/17/2020
  • 4 minutes to read
    • E
    • C
    • D
    • k
    • p

The WDK is used to develop, test, and deploy Windows drivers.

  • Learn what's new in driver development
  • Review known issues

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).

Step 1: Install Visual Studio 2019

The WDK requires Visual Studio. For more information about system requirements for Visual Studio, see Visual Studio 2019 System Requirements.

The following editions of Visual Studio 2019 support driver development for this release:

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. Note that the version of the SDK that is compatible with the WDK for Windows 10, version 2004 may not be the default SDK. To select the correct SDK:

In Visual Studio Installer, on the Individual components tab, search for Windows 10 SDK (10.0.19041.0), select this version and continue with install. Note that Visual Studio will automatically install Windows 10 SDK (10.0.19041.1) on your machine.

If you already have Visual Studio 2019 installed, you can install the Windows 10 SDK (10.0.19041.1) by using the Modify button in Visual Studio install.

WDK has Spectre mitigation enabled by default but requires spectre mitigated libraries to be installed with Visual Studio for each architecture you are developing for.

Additionally, developing drivers for ARM/ARM64 require the build tools for these architectures to also be installed with Visual Studio.

To locate these items you will need to know the latest version of MSVC installed on your system.

To find the latest version of MSVC installed on your system, in Visual Studio Installer go to workload page, on the right pane under installation details, expand Desktop development with C++ and locate the MSVC v142 – VS 2019 C++ x64/x86 build tools (V14.xx) – note where xx should be the highest version available.

With this information (v14.xx), go to Individual components and search for v14.xx. This will return the tool sets for all architectures, including Spectre mitigated libs. Select the driver architecture you are developing for.

For example, searching for v14.25 returns the following:

MSVC v142 – VS 2019 C++ ARM build tools (v14.25)MSVC v142 – VS 2019 C++ ARM Spectre-mitigated libs (v14.25)MSVC v142 – VS 2019 C++ ARM64 build tools (v14.25)MSVC v142 – VS 2019 C++ ARM64 Spectre-mitigated libs (v14.25)MSVC v142 – VS 2019 C++ x64/x86 build tools (v14.25)MSVC v142 – VS 2019 C++ x64/x86 Spectre-mitigated libs (v14.25)

Step 1.5 Install Refreshed Windows SDK 10.0.19041.16385 for Windows 10, version 2004

  • Download SDK for Windows 10, version 2004

This SDK is strongly recommended and will eventually be made available thru Visual Studio

Step 2: Install Refreshed WDK for Windows 10, version 2004

  • Download WDK for Windows 10, version 2004

The WDK Visual Studio extension is included in the default WDK installation.

Enterprise WDK (EWDK) for Windows 10, version 2004

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.7.0 and MSVC toolset v14.23. To get started, mount the ISO and run LaunchBuildEnv.

The EWDK also requires the .NET Framework version 4.7.2. For more information about other requirements for the .NET Framework, see .NET Framework system requirements.

  • Download the EWDK for Windows 10, version 2004

You can use the Visual Studio interface with the build tools provided in the EWDK.

  1. Mount the EWDK ISO.
  2. Run LaunchBuildEnv.cmd.
  3. In the environment created in step 2, type SetupVSEnv, and then press Enter.
  4. Launch devenv.exe from the same environment, using the full file path.Example: C:\Program Files (x86)\Microsoft Visual Studio\2019\\%Community|Professionial|Enterprise%\Common7\IDE\devenv.exe

Note that the Visual Studio major version should match with the version in the EWDK. For example, Visual Studio 2019 works with the EWDK that contain VS16.X build tools.

Driver samples for Windows 10

To download the driver samples, do one of the following:

Источник: https://docs.microsoft.com/en-us/windows-hardware/drivers/download-the-wdk

Provision a computer for driver deployment and testing (WDK 10) – Windows drivers

Wdk 10

  • 05/08/2020
  • Чтение занимает 3 мин
    • E
    • D
    • D
    • d
    • n

Provisioning a target or test computer is the process of configuring a computer for automatic driver deployment, testing, and debugging. To provision a computer, use Microsoft Visual Studio.

A testing and debugging environment has two computers: the host computer and the target computer. The target computer is also called the test computer. You develop and build your driver in Visual Studio on the host computer. The debugger runs on the host computer and is available in the Visual Studio user interface. When you test and debug a driver, the driver runs on the target computer.

The host and target computers must be able to ping each other by name. This might be easier if both computers are joined to the same workgroup or the same network domain. If your computers are in a workgroup, we recommend that you connect the computers with a router rather than a hub or switch.

Tip

For the latest information on the WDK and known issues, see the WDK support forum.

Prepare the target computer for provisioning

  1. On the target computer, install the operating system that you'll use to run and test your driver.

  2. Install the WDK. You do not need to install Visual Studio, however, unless you plan on doing driver development on the target computer.

  3. If Secure Boot is enabled on an x86 or x64 target computer, disable it. For information about Unified Extensible Firmware Interface (UEFI) and Secure Boot, see UEFI Firmware.

    If the target computer uses an ARM processor, install the Windows Debug Policy. This can be done only by Microsoft or the manufacturer of the target computer. You do not need to disable Secure Boot.

  4. On the target computer, run the WDK Test Target Setup MSI that matches the platform of the target computer. You can find the MSI in the Windows Driver Kit (WDK) installation directory under Remote.

    Example: C:\Program Files (x86)\Windows Kits\10\Remote\x64\WDK Test Target Setup x64-x64_en-us.msi

  5. If the target computer is running an N or KN version of Windows, install the Media Feature Pack for N and KN versions of Windows:

  6. If your target computer is running Windows Server, find the DriverTest folder that was just created by WDK Test Target Setup MSI. (Example: c:\DriverTest).

    Select and hold (or right-click) the DriverTest folder, and choose Properties.

    On the Security tab, give Modify permission to the Authenticated Users group.

Verify that the host and target computers can ping each other. Open a Command Prompt window, and enter ping ComputerName.

If the host and target computers are joined to a workgroup and are on different subnets, you might have to adjust some firewall settings so that the host and target computers can communicate. Follow these steps:

  1. On the target computer, in Control Panel, go to Network and Internet > Network Sharing Center. Note your active network. This will be Public network, Private network, or Domain.
  2. On the target computer, in Control Panel, go to System and Security > Windows Firewall > Advanced settings > Inbound Rules.
  3. In the list of inbound rules, find all Network Discovery rules for your active network. (For example, find all Network Discovery rules that have a Profile of Private.) Double click each rule and open the Scope tab. Under Remote IP address, select Any IP address.
  4. In the list of inbound rules, locate all File and Printer Sharing rules for your active network. For each of those rules, double click the rule, and open the Scope tab. Under Remote IP address, select Any IP address.

Provision the target computer

Now you're ready to provision the target computer from the host computer in Visual Studio.

  1. On the host computer, in Visual Studio, select the Extensions menu, point to Driver, point to Test, and select Configure Devices.

  2. In the Configure Devices dialog, select Add new device.

  3. For Network host name, enter the name or local IP address of your target computer. Select Provision device and choose debugger settings.

  4. Select Next.

  5. Select a type of debugging connection, and enter the required parameters.

    For more information about setting up debugging over various types of connections, see Setting Up Kernel-Mode Debugging Manually in the CHM or online documentation for Debugging Tools for Windows.

  6. The provisioning process takes several minutes and might automatically reboot the target computer once or twice. When provisioning is complete, select Finish.

Note

Provisioning virtual machines through the WDK's automatic provisioning process is not supported. However, you can test drivers on a VM by setting up the target VM manually as described in the step by step echo lab.

See Also

Deploying a Driver to a Test Computer

Отправить и просмотреть отзыв по

Этот продукт Эта страница Просмотреть все отзывы по странице

Источник: https://docs.microsoft.com/ru-ru/windows-hardware/drivers/gettingstarted/provision-a-target-computer-wdk-8-1

Поделиться:
Нет комментариев

    Добавить комментарий

    Ваш e-mail не будет опубликован. Все поля обязательны для заполнения.