Windows Driver Kit (WDK) for Windows 7 RC Release Notes
Please see Windows Driver Kit Version 7 Release Notes for the most recent version of the WDK Release Notes.
On This Page
 | Changes Since the WDK Release for Windows 7 Beta |
| Issues |
Changes Since the WDK Release for Windows 7 Beta
The WDK Now Has a Version Number
The Windows Driver Kit team plans to start service releases of the WDK after the version for Windows 7 RTM is released. To identify the WDK releases, we have given the WDK a version number. This version number will change with each service update, which may not be synchronous with a service pack release for a given operating system. The first number will increase with each major Windows client operating system release. The second and third numbers will identify WDK updates.
Debugger Installation Changed
If you install Debugging Tools for Windows by using Kitsetup, the debugging tools are installed in a folder called Debugger in the installation path that you selected. If you install the debugging tools along with other WDK components, they all have the same root installation path. If you do not want the debugging tools to be installed in the same root path as the other WDK components, you can do one of the following:
| • | Run the Debugger MSI file (located on the WDK media) directly. |
| • | Run Kitsetup and install only the debugging tools. Then rerun Kitsetup to install the other WDK components, choosing a different installation path for the other WDK components. To select a different root for the debugging tools, you must install the debugger before the rest of the WDK components. |
TargetPath Supported
In the Windows 7 Beta version of the WDK, TARGETPATH was not supported. It is supported in the Windows 7 RC version (WDK 7.0.0).
Header Files Restored
The following header files were removed in the Windows 7 Beta version of the WDK, but have been restored for the Windows 7 RC version (WDK 7.0.0):
| • | Comdef.h |
| • | Comip.h |
ATL 2.1 and ATL 3.0 Removed
The header files for ATL 2.1 and ATL 3.0 have been removed. ATL 7.1 header files have changed location from …\inc\crt\atl71 to …\inc\atl71. Changes were made to the build environment to use the ATL 7.1 header files in the new location. If your Sources file contains ATL_VER, the value should be 70 or 71.
All Support for Windows 2000 Build Environment Removed
The libraries for Windows 2000 have been removed from the WDK. _NT_Target_Version=$(NT_TARGET_VERSION_WIN2K) will result in an error. _NT_Target_Version must be Windows XP or a later version of Windows.
WinUSB Co-installer Added
The Windows 7 Beta version of the WinUSB 1.9 co-installer was provided through the Microsoft Connect Web site. The Windows 7 RC version is now in the WDK as WinUsbCoinstaller2.dll.
Samples Changed
Time Sensor Sample Added
A new sample was added under src\sensorsandlocation\timesensor.
Registry Filtering Sample Added
A new sample was added under src\general\registry\regfltr.
Toaster Sample Extended
The toaster sample now includes support for User-Mode Driver Framework (UMDF) RemoteTarget and RemoteInterface. The change can be found at src\general\toaster\umdf\toastmon.
Signing Sample Moved
The signing sample, Selfsign_example.cmd, has been moved from …\bin\selfsign to …\src\general\build\driversigning.
Tool Added
The Driver Coverage Kit was added to the WDK. It is located in tools\drvCov. The Driver Coverage Kit analyzes the test coverage of a test. For more information, see the WDK documentation.
Issues
Signtool sign /ac switch may create invalid signatures
The version of signtool that shipped in the Windows 7 SDK Beta and RC releases may create invalid signatures when signing with the /ac switch. Signatures will appear correct when signtool verifies the signed file with the /kp switch, but signatures will contain unexpected certificates and the file may fail to load. This issue occurs when additional certificates are present in the same certificate store or PFX file as the signing certificate.
Workaround
Remove all certificates from the certificate store or PFX file other than the signing certificate.
PREfast for Drivers (PFD) Installation Notes
To be fully functional, PREfast for Drivers (\tools\pfd\Prefast.exe) requires that both the build environments component and the tools component be installed with the WDK.
The core components of PFD are installed by the build environment option of the WDK installer. Many of the components are shared with the OACR (Auto Code Review) tool that is bundled with all of the build environments. With only the build environments component installed, PFD's scanning capabilities are fully functional, but the viewer is not. With only the tools component installed, the viewer is functional as long as the build environments component is also installed.
PFD is non-functional if only the tools component is installed. The directory structure is created but the binary files are not present. For PFD to be functional, the build environments component must be installed.
Workaround
Install both the build environments and tools components in the WDK installer to ensure full functionality.
If you want to install only the build environments, you can enable the full functionality of the stand-alone PFD viewer by copying Mscomctl.cab and Mscomctl.lpk from WDKRoot\bin\x86\OACR\viewer\scripts\defectui\frame to WDKRoot\tools\pfd\scripts\DefectUI\frames.
OSRUsbFx2 Sample Requires MSXML 6.0
On systems running Windows Server 2003 with Service Pack 2 (SP2) or a version of Windows XP earlier than Service Pack 3 (SP3), an upgrade to MSXML 6.0 is required to correctly build samples that use the OSRUsbFx2 library. The build of any code that uses this library will fail, and the build log will show "error : Failed to load msxml6.dll. Please ensure that MSXML 6.0 is installed on your system and try again."
Workaround
Install MSXML 6.0 from http://go.microsoft.com/fwlink/?LinkID=133943.
OS Version Check Error in WDK Copywia.cmd Tool
When run on Windows 7, the Copywia.cmd tool does not copy all the appropriate Windows Image Acquisition (WIA) files due to an OS Version Check error.
Workaround
To fix the tool, edit the Copywia.cmd file in a text editor as follows.
Replace the following:
if /I "%DDK_TARGET_OS%" EQU "WinLH" ( copy wiadriverex\usd\obj%build_alt_dir%\%cpu_samples%\wiadriverex.dll %1wiabins\drivers copy wiadriverex\segfilter\obj%build_alt_dir%\%cpu_samples%\segfilter.dll %1wiabins\drivers copy wiadriverex\imgfilter\obj%build_alt_dir%\%cpu_samples%\imgfilter.dll %1wiabins\drivers copy wiadriverex\errhandler\obj%build_alt_dir%\%cpu_samples%\errhandler.dll %1wiabins\drivers copy wiadriverex\uiext2\obj%build_alt_dir%\%cpu_samples%\uiext2.dll %1wiabins\drivers copy wiadriverex\wiadriver.inf %1wiabins\drivers copy wiadriverex\sample.bmp %1wiabins\drivers ) copy %basedir%\tools\wia\%cpu_tools%\wiatest.exe %1wiabins copy %basedir%\tools\wia\%cpu_tools%\wiainfo2.exe %1wiabins copy %basedir%\tools\wia\%cpu_tools%\wiatrcvw.exe %1wiabins copy %basedir%\tools\wia\%cpu_tools%\wiadbgcfg.exe %1wiabins copy %basedir%\tools\wia\%cpu_tools%\wialogcfg.exe %1wiabins copy %basedir%\tools\wia\%cpu_tools%\wiapreview.exe %1wiabins
With the following:
copy %basedir%\tools\wia\%cpu_tools%\wiatest.exe %1wiabins if /I "%DDK_TARGET_OS%" EQU "WinXP" ( copy %basedir%\tools\wia\%cpu_tools%\wialogcfg.exe %1wiabins goto end ) if /I "%DDK_TARGET_OS%" EQU "WinNET" ( copy %basedir%\tools\wia\%cpu_tools%\wiadbgcfg.exe %1wiabins goto end ) copy wiadriverex\usd\obj%build_alt_dir%\%cpu_samples%\wiadriverex.dll %1wiabins\drivers copy wiadriverex\segfilter\obj%build_alt_dir%\%cpu_samples%\segfilter.dll %1wiabins\drivers copy wiadriverex\imgfilter\obj%build_alt_dir%\%cpu_samples%\imgfilter.dll %1wiabins\drivers copy wiadriverex\errhandler\obj%build_alt_dir%\%cpu_samples%\errhandler.dll %1wiabins\drivers copy wiadriverex\uiext2\obj%build_alt_dir%\%cpu_samples%\uiext2.dll %1wiabins\drivers copy wiadriverex\wiadriver.inf %1wiabins\drivers copy wiadriverex\sample.bmp %1wiabins\drivers copy %basedir%\tools\wia\%cpu_tools%\wiainfo2.exe %1wiabins copy %basedir%\tools\wia\%cpu_tools%\wiatrcvw.exe %1wiabins copy %basedir%\tools\wia\%cpu_tools%\wiapreview.exe %1wiabins
WinUSB Co-installer Fails to Load on Windows Vista SP2
Winusbcoinstaller2.dll fails when installing WinUSB on Windows Vista Service Pack 2 (SP2). This is due to a build irregularity that we discovered after the Windows 7 RC build was completed. We expect to fix the problem soon, in an upcoming build. Please contact us at wdfinfo@microsoft.com if you would like to be notified about the availability of the fix. We apologize for the inconvenience.