If you haven’t joined the OSRHINTS mailing list yet, I recommend that you do.
Why? This list, NTDEV, is a place for folks to post questions and get answers. It’s not a place for us to post general notices of interest to the Windows Driver Development Community. Bringing issues, hints, tips, and ideas to the attention of members of the Windows Driver Development Community is what OSRHINTS is for.
For example, WDK 14393 was released today… and we found an issue with it that we think is important. We sent the note below out to OSRHINTS as soon as we discovered the issue (and a couple of others).
To join the OSR Hints mailing list, send a blank email to “join dash osrhints at lists.osr.com” (without the quotes, obviously… and note that the subject is ignored) – I can’t put the email address here, because the forum software will obfuscate it. If you’re confused, go to http://www.osr.com and you’ll see the instructions there at the top of the page.
That’s all I’m going to say on this topic – The OSRHINTS list is now two years old, and I think we’ve mentioned it twice on this list in two years.
Peter
OSR
@OSRDrivers
Sent to OSRHINTS 8/2/2016:
Hi!
As you probably know, the new 14393 WDK was released today to accompany Windows Anniversary Update (V1607).
Before you got yourself into a fix, like a whole group of us here at OSR, we wanted to warn you of a few issues we’ve encountered:
a) There appears to be a Code Analysis issue in 14393 that causes POOL_NX_OPTIN to be broken. BEFORE you upgrade, check our blog post on this issue: https:</https:>
b) What’s worse is that attempting to uninstall the 14393 WDK and revert to the previous 10586 WDK doesn’t work, and leaves you with a non-working driver development environment.
c) There’s something in the suggested update for VS 2015 (KB 1365756) that can cause the 10586 WDK to stop working. The symptoms are that the standard driver include files (like WDM.H and NTDDK.H) are no longer found. This is what happens when the SDK isn’t installed, so… we *think* (but don’t know for sure) that it might have something to do with attempting to install the new SDK. In any case, we don’t recommend you install this KB.
d) What’s worse is that attempting to roll-back to the snapshot taken before applying the aforementioned KB renders VS 2015 entirely unusable for anything (ask me how I know).
The combination of the above issues has basically caused work to come to a halt here for several of us. While we’re waiting for VS 2015 with Update 3 to be reinstalled (merely doing the “repair” didn’t work… in fact, it hung), we figured we’d fire-off a “hint” to members of the community warning them about the issues we had.
Be careful of those updates! Check-in with us regularly for the latest updates.
Develop well,
The OSR Engineering team