Windows 10 - NDIS LWF compatibility

NTDEV
1

Hi All,

We are installing NDIS 6.30 driver on Windows 10 build(10056). On installation we collected following observations:

  1. State of installed driver is stopped state.
  2. Network is not accessible.
  3. After installation if we reboot the system, everything is working(driver in running state, network accessible).
  4. Found net component entry in NetCfg database. [netcfg -s n]

Also we used the NDIS LWF sample filter driver on Windows 10. We found same above observations.

Have anyone come across such scenario?

Thanks,
Rajendra.

2

Does the problem go away if you run “net start ”?

We made some big changes to how network drivers are installed in Windows 10, and there’s some OS bugs we’re working through. Chances are good that this is not a bug in your driver, but a bug in the OS.

3

Thanks for your reply…!

Yes, with the command, its state changes to running and everything works fine. We also used StartService() API to start driver. And it’s working fine.
What we think is DriverEntry() is not called when we install NDIS lwf.

Thanks,
Rajendra.

4

This will be fixed in a future preview build of Windows 10. The issue is that NetCfg isn’t honoring CoServices from the INF.

5

Thanks…!
We will verify it in upcoming preview build of Windiws 10.

Thanks,
Rajendra.

6

Hi,

During uninstallation of NDIS LWF, sometimes net component is not removed/uninstalled.
Error: INetCfgClassSetup::DeInstall() failed with error HRESULT:0x80071A90.

Thanks,
Rajendra.

7

Yup, we know about that one too. That’s caused because we switched to using KTM to install drivers. This gives us additional reliability in case the system crashes or shuts down in the middle of some operation. However, KTM brings with it a whole new source of errors that must be handled carefully.

I can’t promise the fix for this one will be in the next public preview release.

8

Thanks for reply…!

How one should install/uninstall NDIS LWF on Windows 10?

Some more observations:
On un-installation of NDIS LWF, most of the times net component is not uninstalled and in such case after reboot network is not accessible. This might be because of LWF service entry is removed from SCM database(also .sys file is deleted) but the net component entry present in NetCfg database.

Thanks,
Rajendra.

9

Hi Jeffrey,

On un-installation of NDIS LWF, most of the times net component is not
uninstalled and in such case after reboot network is not accessible.

We think this is serious issue/bug. Else one have to shift to WFP driver.

Waiting for your reply.

Thanks,
Rajendra.

10

Our NDIS 6.3 filter doesn’t start on recent windows 10 builds as well (at
least since 10054). We use netcfg for installation, and after a reboot the
driver starts properly.

Latest build we tried was 10108. This affects our installation flow, it
would help to know whether it’s the same issue and possibly a heads up when
a new build fixes this.

On Tue, Apr 28, 2015 at 9:13 AM, wrote:

> Hi Jeffrey,
>
> On un-installation of NDIS LWF, most of the times net component is not
> uninstalled and in such case after reboot network is not accessible.
>
> We think this is serious issue/bug. Else one have to shift to WFP driver.
>
> Waiting for your reply.
>
> Thanks,
> Rajendra.
>
>
> —
> NTDEV is sponsored by OSR
>
> Visit the list at: http://www.osronline.com/showlists.cfm?list=ntdev
>
> OSR is HIRING!! See http://www.osr.com/careers
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>