Why doesn't my KMDF 1.7 Driver Install on Windows Vista?
Well, the root to this current problem lies in the story behind my last post. If I had waited a few hours, Windows Update would have deployed a required SP1 prerequisites package, and the driver I had successfully installed would have ceased working. Reinstalling or installing a different driver after the update was deployed won't work, either. No, you can't remove the update.
If your binaries in %windir%\system32\drivers\wdf* have a fairly recent timestamp [on this machine it was 2/22], you can be quite sure this is the case. You can also look at the version info for wdfldr.sys in that directory with Explorer- it'll say 1.5.6000.0 (for 1.7 it should say 1.7.6001.0).
We're working on the problem. I'm supposed to be testing a fix for it as I write this (which is why I'm rushing it). I'm writing it because we're getting a lot of pings (including several through the IM interface at the head of this blog). So please let my colleagues and I do what needs to be done.
We expect to have an updated WDK with a coinstaller that takes care of the problem by 3/15. If you're hitting this article after that date, have downloaded the new WDK and still have trouble, then by all means contact us- we do want to take care of such issues.
But I can't answer all the inquiries and do my job to help get the fix out- this will affect basically anyone at this point.
For a temp workaround, this is the advice slightly tweaked from what Ilias sent to OSR NTDEV:
Also, another workaround that you can do for testing purposes in your test machines is to "disassemble" the coinstaller, as is described at another earlier post of mine, get the KMDF files (wdf0100.sys and wdfldr.sys) and use the technique described at this article on kernel mustard to install them in your Vista RTM test machines.
If I get the chance I may try to shed some light on how it happened (as long as I can keep clear of any secrets, of course).
