And, yes… as long as that works, that is a possible way forward. Microsoft would have us continue to use the “old” Windows 11 WDK hosted on VS 2019 to build drivers for the platforms that are no longer supported.

That means there are lots of companies that need to be able to update the drivers for their hardware or software (I’m looking at you, file system minifilter people) on those systems. Remember that only a couple of years ago (2020) Microsoft was still building, releasing, and supporting 32-bit version of Windows 10. Microsoft can wish what they want, but it is beyond question that there is still a significant installed base of Windows 7 and 32-bit Windows systems. These new restrictions will come as unwelcome news to many in the driver development community. No support for building 32-bit drivers, for any platform, x86 or ARM, or for any OS version including 32-bit Windows 10.

This means that it’s no longer possible to use the latest WDK to build drivers that support Windows 7 or Windows 8, or Windows 8.1.

No support for building drivers that target any Windows version before Windows 10.

There are some nice new features in VS 2022, including native 64-bit support (for the IDE itself) and support for C++ 20.īut, alas, there are a few surprises lurking in this most recent WDK release. Given that many (if not most) Windows driver developers these days often also write some sort of application code, having one tool chain that supports both jobs is both useful and most welcome. This new version of the WDK is only support on VS 2022. This version is referred to as the Windows 11 Version 22H2 WDK. It took “a while” but, without any fanfare, sometime in May of 2022, Microsoft released a version of the Windows Driver Kit (WDK) that supports Visual Studio (VS) 2022.

Visual studio 2022 64 bit download