none
HLK 10.1.0.10586 NDISTest 6.0 cannot find ndprot660.sys RRS feed

  • Question

  • With a fresh installed Server 2012R2, freshly installed HLK 10.1.0.10586, the NDIS 6.0 tests (all of them) fail for Windows 10 (10586) with an error during

    "Client - Copy NDISTest 6.0 Binaries"

    with error

    "Cause : Failed to Copy File : "\\<CONTROLLER>\tests\x86\nethlk\ndistest\bin\ntndis660\ndprot660.sys" ..."

    The path in the error does not exist on the controller, where are these binaries?, and why have they not installed with the hlk setup?

    Thursday, March 17, 2016 3:05 PM

All replies

  • Hi there.

    Have you found what is the problem? We have exact same setup and exact same problem...

    Friday, April 22, 2016 4:15 AM
  • Hi,

    We have the same problem as well. 

    We copied the missing binaries for the ndistest.net directoy and some of the tests are now passing. However, I still think there is some problem with the version - other tests seem to fail to to incorrect protocol driver version.


    Tuesday, May 3, 2016 8:24 AM
  • Just got work from MS support:

    .....failures in any of these tests are allowed because of this error. NDISTest 6.0 - [1 Machine] - 1c_64BitOIDs NDISTest 6.0 - [1 Machine] - 1c_FaultHandling NDISTest 6.0 - [1 Machine] - 1c_IOCTLCoverage NDISTest 6.0 - [1 Machine] - 1c_KernelCalls NDISTest 6.0 - [1 Machine] - 1c_Mini6PerfSend NDISTest 6.0 - [1 Machine] - 1c_Mini6Send NDISTest 6.0 - [1 Machine] - 1c_NdisRequestCov NDISTest 6.0 - [1 Machine] - 1c_OidsDeviceIoControl NDISTest 6.0 - [1 Machine] - 1c_OidsWMI NDISTest 6.0 - [1 Machine] - 1c_Registry NDISTest 6.0 - [1 Machine] - 1c_WMICoverage NDISTest 6.0 - [2 Machine] - 2c_Mini6CheckConnections NDISTest 6.0 - [2 Machine] - 2c_Mini6Performance NDISTest 6.0 - [2 Machine] - 2c_Mini6SendRecv NDISTest 6.0 - [2 Machine] - 2c_Mini6SendRecvReply NDISTest 6.0 - [2 Machine] - 2c_Mini6Stress NDISTest 6.0 - [2 Machine] - 2c_OidsNdisRequest NDISTest 6.0 - [2 Machine] - 2c_Priority

    If this is the case, please use mention that these errors are covered by Manual Erratum ID 5864 in the readme file when submitting your driver package for certification to Sysdev.


    Wednesday, May 4, 2016 5:30 AM