DTM of vista/win7 driver on Windows7 client-fails

NTDEV
1

Hello,

I have USB drivers for vista 32 bit and windows7 32 bit OS.
Vista driver is built on 6001.18001 DDK and windows7 driver built on 7100.0.0(Win7)DDK.
With out doing test signing of driver, i have done the DTM.

The test Device Install Check for other Device Stability has failed and the log shows the error,
Context Index: 2977204774
Current: Unexpected Error
Parent: Device Install Check for Other Device Stability
Start Test 6/23/2009 3:06:10.450 PM Unexpected Error
Message 6/23/2009 3:06:10.450 PM Could not load file or assembly ‘WDTF.Interop, Version=6.1.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35’ or one of its dependencies. Strong name validation failed. (Exception from HRESULT: 0x8013141A)
End Test 6/23/2009 3:06:10.450 PM Unexpected Error
Result: Fail

i would like to know , why it is failing and what is strong name verification? To avoid the error do we need to do something at the stage of driver build or test sign before DTM?

2

This is a known issue and has a 2 solutions:

  1. Download and install WLK 1_4 QFE002 from
    https://connect.microsoft.com/Downloads/DownloadDetails.aspx?SiteID=668&
    DownloadID=20345 - See NOTE before installing

Or

  1. On the system you are testing on:

  1. Open cmd line with elevated permission

  2. Run ‘reg add
    “HKLM\SOFTWARE\Microsoft\StrongName\Verification*,31bf3856ad364e35”’

  3. Run the test as usual

  4. Once finished running the test, run ‘reg delete
    “HKLM\SOFTWARE\Microsoft\StrongName” /f’

Or see
https://connect.microsoft.com/site/sitehome.aspx?SiteID=668 (at the
bottom)

Daryl

3

Thanks for the information.

In the solution you have given 2 options.

Is the first solution , a patch for this issue?

And the second solution, what exactly it does in the client machine, by adding the registry key?

Hope your reply…

Nisheedh

4

Hello,

I have done the second solution that you have mentioned. I am able to override the strongname verification error.

But after DTM, am getting one failure in Device Install Check for other Device Stability.
Failed test, ?Device Install Check for other Device Stability?, has 4 tasks namely Device scan, Reinstall with I/O, Device scan, Setup Appverif. In this, ?Device scan? test after ?Reinstall with I/O? has failed.
The Device scan test has 150 sub tasks, of which, 1 subtask fails.
The failed subtask has the context,
Context
Context Index: 680584470
Current: Verify Device Attributes for Device ID:SW{EEAB7790-C514-11D1-B42B-00805FC1270E}\ASYNCMAC
Parent: Device Install Check for Other Device Stability
Start Test 6/26/2009 2:31:32.452 PM Verify Device Attributes for Device ID:SW{EEAB7790-C514-11D1-B42B-00805FC1270E}\ASYNCMAC
Message 6/26/2009 2:31:32.452 PM Microsoft System Management BIOS Driver added newly
Message 6/26/2009 2:31:32.452 PM Device Attribute Status DeviceName RAS Async Adapter Description RAS Async Adapter ProblemCode 0 Driver {4d36e972-e325-11ce-bfc1-08002be10318} DriverName AsyncMac IsDisabled False IsFailedStart False IsFailedInstall False IsReinstallNeeded False IsStarted True
End Test 6/26/2009 2:31:32.452 PM Verify Device Attributes for Device ID:SW{EEAB7790-C514-11D1-B42B-00805FC1270E}\ASYNCMAC
Result: Fail

i would like to know what is this error? Why the Microsoft serial network driver asyncmac.sys has started on DTM of our USB driver?
Is it a known issue?
can you help me in resolving the issue, so that our customer can sign the driver at microsoft?

Hope your reply
thanks in advance
Nisheedh