DTM failed "Verify WDF Coinstaller Version for KMDF"
in [Device Drivers]
|
Prev: Syntax error with WinDBG command line -c ".cls;g"
Next: hal!KfLowerIrql change data in system memory for SCSI miniport
From: David Voeller on 7 Sep 2010 17:27 I have an unclassified USB device driver built in XP driver environment. The driver package uses the WDF coinstaller C:\WinDDK\7600.16385.1\redist\wdf\x86\WdfCoInstaller01009.dll. The DTM (DTM version 1.5.7565.000, WTT version 2.2.2098.0) fails the KMDF coinstaller version verification test for the XP, Vista 32/64 and W7 32/64 clients. I've checked the date/timestamp/size of C:\Winodws\System32\WdfCoInstaller01009.dll on each client against that of the driver package and they are the same. Does anyone have any tips on how I can track this failure down?
From: David Voeller on 7 Sep 2010 17:31 I the properties of the WdfCoInstaller01009.dll the certificate is only valid to 4/26/2010. I can't imagine that this is the problem or everyone would be having the same failure. "David Voeller" wrote: > I have an unclassified USB device driver built in XP driver environment. The > driver package uses the WDF coinstaller > C:\WinDDK\7600.16385.1\redist\wdf\x86\WdfCoInstaller01009.dll. > > The DTM (DTM version 1.5.7565.000, WTT version 2.2.2098.0) fails the KMDF > coinstaller version verification test for the XP, Vista 32/64 and W7 32/64 > clients. I've checked the date/timestamp/size of > C:\Winodws\System32\WdfCoInstaller01009.dll on each client against that of > the driver package and they are the same. Does anyone have any tips on how I > can track this failure down?
From: Satya on 7 Sep 2010 20:02 Check for DTM filters from microsoft site. Filters essentially ignore errors and you will eventually pass the test if your error is one of those known failures. Satya http://www.winprogger.com "David Voeller" wrote: > I the properties of the WdfCoInstaller01009.dll the certificate is only valid > to 4/26/2010. I can't imagine that this is the problem or everyone would be > having the same failure. > > > "David Voeller" wrote: > > > I have an unclassified USB device driver built in XP driver environment. The > > driver package uses the WDF coinstaller > > C:\WinDDK\7600.16385.1\redist\wdf\x86\WdfCoInstaller01009.dll. > > > > The DTM (DTM version 1.5.7565.000, WTT version 2.2.2098.0) fails the KMDF > > coinstaller version verification test for the XP, Vista 32/64 and W7 32/64 > > clients. I've checked the date/timestamp/size of > > C:\Winodws\System32\WdfCoInstaller01009.dll on each client against that of > > the driver package and they are the same. Does anyone have any tips on how I > > can track this failure down?
From: David Voeller on 8 Sep 2010 09:08
I have the latest updatefilters.cab file installed on the DTM version 1.5. We might have found a solution to the problem by installing the expired certificate that goes with the version 1.9 coinstaller. I'll know today. "Satya" wrote: > Check for DTM filters from microsoft site. Filters essentially ignore errors > and you will eventually pass the test if your error is one of those known > failures. > > Satya > http://www.winprogger.com > > "David Voeller" wrote: > > > I the properties of the WdfCoInstaller01009.dll the certificate is only valid > > to 4/26/2010. I can't imagine that this is the problem or everyone would be > > having the same failure. > > > > > > "David Voeller" wrote: > > > > > I have an unclassified USB device driver built in XP driver environment. The > > > driver package uses the WDF coinstaller > > > C:\WinDDK\7600.16385.1\redist\wdf\x86\WdfCoInstaller01009.dll. > > > > > > The DTM (DTM version 1.5.7565.000, WTT version 2.2.2098.0) fails the KMDF > > > coinstaller version verification test for the XP, Vista 32/64 and W7 32/64 > > > clients. I've checked the date/timestamp/size of > > > C:\Winodws\System32\WdfCoInstaller01009.dll on each client against that of > > > the driver package and they are the same. Does anyone have any tips on how I > > > can track this failure down? |