Windows Driver Kit (WDK) 8.1 Release Notes
These release notes contain information about the Windows Driver Kit (WDK) 8.1 release. The Windows Driver Kit (WDK) is being delivered "as is" and might contain content that is missing, incomplete, or temporarily not functioning correctly. It might also contain content that will be removed in a later WDK release. The information in these notes can change without notice.
Issue: A driver project that was previously converted to use the Windows Driver Kit (WDK) 8 tool set does not load in WDK 8.1
Workaround: Users must upgrade a WDK 8 driver project to use the WDK 8.1 tool set to successfully build the driver. To upgrade the project, follow these steps:
- Open a Microsoft Visual Studio Command Prompt window.
...\tools\x86\ProjectUpgradetool.exefrom the command line.
Issue: Running level-1 ARM driver tests from the command line does not work.
Workaround: Use the UI version of the driver tests available in Visual Studio. For further information, see How to run the HCK Test Suites in WDK 8.1
Issue: When installing the WDK tests pack, The Wi-Fi test file Wlan1tests.dllis placed incorrectly at ..\Program Files (x86)\Windows Kits\8.1\Testing\Tests\HCK Tests\Basic\Device.Network.WLAN\arm\nttest\nettest\Wireless\hck.
Workaround: Move Wlan1tests.dll from \Program Files (x86)\Windows Kits\8.1\Testing\Tests\HCK Tests\Basic\Device.Network.WLAN\arm\nttest\nettest\Wireless\hck to the correct location, which is ..\Program Files (x86)\Windows Kits\8.1\Testing\Tests\HCK Tests\Basic\Device.Network.WLAN\arm\.
The Wlan1tests.dll file should be moved and not copied or the test harness will try to run both copies of the file.
Issue: When using the driver test feature, the host might occasionally connect to the target computer before the debug service is ready. This results in the following error: Could not start debugging session, error 80004005.
Workaround: If you hit this error, you should try to connect again.
Issue: The GetVersion and GetVersionEx functions are deprecated starting with Windows 8.1.
Workaround: Use the IsWindowsXxx macros defined in Versionhelpers.h to get Windows version information.
Issue: User projects do not build correctly using Microsoft Visual Studio 2012.
Workaround: For the initial installation of WDK 8.1, follow these steps:
- Follow the setup instructions to install the WDK and SDK.
Before starting Visual Studio, open a Command Prompt window as Administrator, and enter the following command to run the VsRegCopy.ps1 script:
powershell –executionpolicy bypass –file VSRegCopy.ps1
Issue: The x86 version of Inf2cat.exe does not run correctly on a host machine that is running Windows 7. You'll get an "Unable to get the length of the indirect data" error, and signing will fail.
Workaround: Either install the WDK on a host machine that is running Windows 8 or Windows 8.1, or use the x64 version of Inf2cat.exe.
To override the default $(Inf2CatToolPath) and $(Inf2CatToolArchitecture) settings, run the following command in the Visual Studio command-line environment (and replace <solution> with the name of your solution file):
Msbuild <solution> /p:Inf2CatToolPath="C:\Program Files (x86)\Windows Kits\8.1\bin\x64" /p:Inf2CatToolArchitecture=Native64Bit
Issue: To install and use the WDK headless feature on a system that is running Windows 7 or Windows Server 2008 R2, you must have .NET 4.5 installed. For more information, see Installing the WDK Build Environment in a Lab.
Issue: You might find that you can't build a Windows Vista target after migrating a WDK 8 project to WDK 8.1. This problem can occur if you use WDK 8 and Visual Studio 2012 to create a project, and then use the ProjectUpgradeTool tool to upgrade the project/solution to WDK 8.1 and Microsoft Visual Studio 2013.
Workaround: For instructions on how to work around this issue, see Migrate a Windows Vista target from WDK 8 to WDK 8.1