KMDF 1.17 and UMDF 2.17 versions not available in Visual Studio 2015 Driver Model selection.

NTDEV
1

KMDF 1.17 and UMDF 2.17 are supposed to be available with V1511 of the WDK
and OS. I have Visual Studio 2015 V14.0.24720.00 Update 1, WDK
V10.0.10586.0 and OS V10.0.10586, Build 10586.122 which should include
these versions of KMDF and UMDF. However, the Driver Model selections
available under Project Properties/Driver Settings only include minor
versions 15. Does anyone know how to make these versions available in
Visual Studio 2015?

2

Randy Lewis wrote:

KMDF 1.17 and UMDF 2.17 are supposed to be available with V1511 of the
WDK and OS. I have Visual Studio 2015 V14.0.24720.00 Update 1, WDK
V10.0.10586.0 and OS V10.0.10586, Build 10586.122 which should include
these versions of KMDF and UMDF. However, the Driver Model selections
available under Project Properties/Driver Settings only include minor
versions 15. Does anyone know how to make these versions available in
Visual Studio 2015?

The 10586 WDK has TMF files for 1.17, but that’s it. No include files,
no libraries, and no co-installers.

Since there are so few public details, allow me to theorize. It looks
like there are no API changes in 1.17, and it looks like 1.17 ONLY works
on the TH2 1511 release of Windows 10. You can’t load it on earlier
systems. If you target 1.15, you’ll get 1.15 on original Windows 10,
and 1.17 on Windows 10 1511, and that’s the best you can do. Thus,
there is no point to targeting 1.17 in your project file.

It’s a little hard to answer questions today because of MSDN problems.
I wonder if they are under a denial-of-service attack.

–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.

3

Thanks Tim. There are few new methods available with UMDF 2.17 that intrigued me but nothing I can’t live without for now. I assume that eventually with future updates to Visual Studio, the WDK and Windows 10 that these minor updates should automatically appear in the Driver Model selection box without me having to do anything special.

4

Tim Roberts wrote:

It’s a little hard to answer questions today because of MSDN problems.
I wonder if they are under a denial-of-service attack.

Randy keeps searching for “hidclass white paper” over and over, hoping something will appear.

5

This is a known oversight and will be corrected in the next WDK release. Sorry for the inconvenience.