Determining WDK version from driver binary

NTDEV
1

Yeah, you heard me right.
Is there a mechanism to analyze a driver binary package (.inf, .sys, .cat, etc.) to determine what WDK was used to build it?

Thanks.

2

No, there is not. I tried to answer the same question five years ago. What bigger problem are you trying to solve?

d

Bent from my phone

From: xxxxx@intel.commailto:xxxxx
Sent: ?1/?17/?2015 12:18 PM
To: Windows System Software Devs Interest Listmailto:xxxxx
Subject: [ntdev] Determining WDK version from driver binary

Yeah, you heard me right.
Is there a mechanism to analyze a driver binary package (.inf, .sys, .cat, etc.) to determine what WDK was used to build it?

Thanks.

—
NTDEV is sponsored by OSR

Visit the list at: http://www.osronline.com/showlists.cfm?list=ntdev

OSR is HIRING!! See http://www.osr.com/careers

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer</mailto:xxxxx></mailto:xxxxx>

3

Thanks. Not an unexpected answer.

My workgroup is deploying systems to a well-known company in Washington. In preparation for the next major OS release from this company, certain folks are mandating that platform drivers are built with the WDK belonging to this next major OS release.

Without discussing the fine points of that mandate, I’m trying to determine the technical feasibility of that request.

4

So you are looking to see if we will catch you lying?

d

Bent from my phone

From: xxxxx@intel.commailto:xxxxx
Sent: ?1/?17/?2015 6:57 PM
To: Windows System Software Devs Interest Listmailto:xxxxx
Subject: RE:[ntdev] Determining WDK version from driver binary

Thanks. Not an unexpected answer.

My workgroup is deploying systems to a well-known company in Washington. In preparation for the next major OS release from this company, certain folks are mandating that platform drivers are built with the WDK belonging to this next major OS release.

Without discussing the fine points of that mandate, I’m trying to determine the technical feasibility of that request.

—
NTDEV is sponsored by OSR

Visit the list at: http://www.osronline.com/showlists.cfm?list=ntdev

OSR is HIRING!! See http://www.osr.com/careers

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer</mailto:xxxxx></mailto:xxxxx>

5

Basically.
Trying to catch which of our driver ingredients are really using the Win10 WDK before those drivers get deployed on systems.

6

Like Doron, I too have spent some considerable time looking at this issue.

If you just want a way to do a quick screening, I seem to recall that there’s linker version information that is present in the binary executable. While that tells you the version of the linker (and not the version of the WDK), that might at least give you a clue which version of VS the driver was built with. So, if you’re building your Windows V.Next drivers with the Visual Studio Next and your older drivers were build with VS 2013 (for example) that should give you a clue.

Peter
OSR
@OSRDrivers

7

Thanks folks. I’ll check into that.