0

we are using a open source NDIS IM driver(5.1) which is working fine in windows 7 machine but when we tried in Windows 10 machine its not loading.

Driver : ipfw+dummynet

Ipfw web site : http://info.iet.unipi.it/~luigi/dummynet/ Source Code : https://github.com/luigirizzo/dummynet

Looks like NDIS 5.1 code to be migrated to NDIS 6.X or LWF to work on Windows 10.

Please suggest a solution or a workaround so that we can use this driver in Windows 10 machine,Your help greatly appreciated.

Srikanth Kumar
  • 11
  • 2

1 Answers1

0

Sounds like you have the same issue I talked about here and opened a Microsoft support case about.

In Windows 10, a new network class Installer called NetSetup was added with a shim for the old NetCfg calls. There's a bug in the shim that causes drivers like ours to install but not bind to any adapters. If that's the behavior you're seeing, unfortunately the result of my support case was that MS decided not to fix the problem because it affects so few people. You could open your own case, on the theory that the more reports they get the more likely they are to fix it, but you probably will have to rewrite the driver.

Community
  • 1
  • 1
jeffm
  • 3,120
  • 1
  • 34
  • 57
  • I think not just binding,visually also we are unable to see the driver in the network properties when we are trying to install in windows 10 machine.so the loading the driver itself failing. – Srikanth Kumar Jan 06 '17 at 06:33
  • OK, probably not the same problem then. But it seems that even though there is supposed to be backward compatibility for NDIS 5.x drivers in Windows 10, Microsoft is not committed to maintaining it. So you may want to rewrite the driver anyway. – jeffm Jan 06 '17 at 14:00
  • Thanks Jeffm. I am able to find a solution. – Srikanth Kumar Nov 13 '20 at 09:56