Mattiwatti
commented
5 years ago Hi,
VS 2019 (non-preview) has been released for a while and is in fact already at version 16.1, could this be the cause of the problem?
The project is set to require WDK version $(LatestTargetPlatformVersion), which means as much as 'whatever the highest locally installed version is'. This is because the project does not depend on any specific WDK version other than requiring 10.0 at minimum (8.1 might actually work but I have never tested this). MSBuild evaluates this macro to create an actual version number from it, which in your case apparently is 10.0.17763.0.
With an updated VS 2019 and the 19H1 WDK installed, $(LatestTargetPlatformVersion) should evaluate to 10.0.18362.0, not 10.0.17763.0. Not that the WDK version matters per se; as I said it should theoretically compile with any version >= 10.0. But it does indicate that something might be wrong with your VS or WDK installation.
Besides installing the preview instead of the release version of VS 2019, it's also possible that you have SDK 10.0.17763.0 installed next to WDK 10.0.18362.0, and that the macro is incorrectly evaluating to 10.0.17763.0 due to this. Because the SDK is a Visual Studio component and the WDK is not, you have to modify this using the Visual Studio installer (VS 2019 -> Modify -> Individual components -> scroll all the way down and ensure 'Windows 10 SDK (10.0.18362.0)' is checked.)
This is what my installation looks like:
zoand
I downloaded and installed the VS 2019 preview and the WDK there after. I loaded the solution then ran into an error saying that the WDK version 10.0.17763.0 is not available.
The WDK version is in fact 10.0.17763.1 and the solution wants 10.0.17763.0 ... any idea of how to work around this problem? Any way to relax version requirements in the solution to handle this situation?