NetCfgClassSetup::Install consistently fails on Windows 10

NTDEV
1

Hi,

We have an existing NDIS MUX intermediate driver that works well on Windows 7 and 8.1. The driver consists of an NDIS intermediate driver with protocol lower edge and virtual miniport upper edge, and uses a notify object (DLL) which is registered with the protocol driver. From the notify object’s ApplyProperties() method we call NetCfgClassSetup::Install() to create the virtual miniport instance. On Windows 10 this call consistently fails with 0x80070057 (E_INVALIDARG).

setupapi.app.log indicates that installation was started. It shows several steps including DIF_REGISTERDEVICE, DIF_ALLOW_INSTALL, DIF_INSTALLDEVICEFILES, DIF_REGISTER_COINSTALLERS, DIF_INSTALLINTERFACES. But DIF_INSTALLINTERFACES is followed by DIF_REMOVE although the log does not indicate any errors. Any ideas why this happens?

From this thread https://www.osronline.com/showthread.cfm?link=265884 I understand that network driver installation has changed in W10. However, our implementation is still compliant with the available documentation. Is there any documentation available on what has been changed specifically?

Another interesting observation is that the NDIS MUX driver sample from the WDK shows the same issue.

Any comments are welcome.

Thanks.
Udo

2

Our NDIS MUX Intermediate driver also does not install on Win10. We have opened a problem report thru Sysdev with Microsoft. It seems that the network stack has changed and does not allow this type of NDIS driver to be loaded. MS has been working on this for several months and we hope for a resolution soon.

I suggest you open a problem report also.

Larry C

3

Thanks for the feedback. I will open an issue.

Udo

4

the problem is that NICs looks like they don’t allow bindings to intermediate Drivers, personally think that is a bug. we posted that problem to MSDN forums and also had contact to miscrosoft with no help.

5

>looks like they don’t allow bindings to intermediate
Drivers,

You are correct that the new Network Install Engine has a problem with IM drivers and MS knows this. I am in contact with MS people pretty much daily working this with our IM MUX driver. MS is definitely not ignoring this problem.

Larry C