Error while building driver "The build tools for WindowsKernelModeDriver10.0 Can not be found"

microsoft / Windows-driver-samples

This repo contains driver samples prepared for use with Microsoft Visual Studio and the Windows Driver Kit (WDK). It contains both Universal Windows Driver and desktop-only driver samples.

Microsoft Public License

6.79k stars 4.89k forks source link

Error while building driver "The build tools for WindowsKernelModeDriver10.0 Can not be found" #1068

Closed HBTest13 closed 1 month ago

HBTest13 commented 6 months ago

While i build the Sample "Windows-driver-samples\audio\simpleaudiosample" i am getting Error "The build tools for WindowsKernelModeDriver10.0 Can not be found, to build using the WindowsKernelModeDriver 10.0 build tools ,Please install WindowsKernelModeDriver 10.0 build tool, Alternatively, you may upgrade to the current visual studio tools by selecting the Project menu or right -click the solution "Retarget solution"."

I have checked all the possible ways like checked in Win11, update WDK and SDK with compatible version.

And currently i am using VS 2022 and Windows 11 OS to build this project.

Can you please help out to solve this error.

### Tasks

### Tasks

hhhheying commented 3 months ago

Hello,

I encountered a similar issue and was able to resolve it. Here are some steps you might find helpful:

Verify SDK and WDK Versions: Ensure that you have the correct versions of the Windows SDK and Windows Driver Kit (WDK) installed. Compatibility with your version of Visual Studio is crucial.
Integration with Visual Studio: If you haven't already, integrate the Windows SDK and WDK with Visual Studio:

Navigate to the directory where the Windows Kits are installed, typically located at C:\Program Files (x86)\Windows Kits\10.
Look for the Vsix within the Windows Kits directory.
Find the file named WDK.vsix and double-click to run the installer. Make sure to close Visual Studio before doing this to avoid any conflicts.

I hope this helps!

NeoAdonis commented 1 month ago

@HBTest13: It seems like an issue with your WDK installation. Following the steps hhhheying suggested might help you with it.

I'm closing the issue for now but please let me know if the issue was resolved or if you encountered more problems.

tikonen commented 1 week ago

Putting this here In case somebody googles this problem. My issue was that somehow the target had changed to ARM when driver kit was installed for x64.