Windows System Software -- Consulting, Training, Development -- Unique Expertise, Guaranteed Results

Home NTDEV

Before Posting...

Please check out the Community Guidelines in the Announcements and Administration Category.

More Info on Driver Writing and Debugging


The free OSR Learning Library has more than 50 articles on a wide variety of topics about writing and debugging device drivers and Minifilters. From introductory level to advanced. All the articles have been recently reviewed and updated, and are written using the clear and definitive style you've come to expect from OSR over the years.


Check out The OSR Learning Library at: https://www.osr.com/osr-learning-library/


Using netcfg to remove an ndis LWF doesn't remove it from the driver store?

Michael_VincentMichael_Vincent Member Posts: 5

Hi,

When we try to remove our NDIS LWF using netcfg -u, i notice that it doesn't remove it from the driver store (can be seen with pnputil /enum-drivers).

This is causing problem because on some Windows 10 machines, if we uninstall the previous version of our NDIS LWF and install the new one, for some unknown reason the old inf is still used to install it! And i assume its because the inf still has the same componentID? We are updating the INF file in order to attach to some virtual adapters that we previously couldn't attach.

So my questions are:

  1. Why is Windows still using the previous INF from driver store when we try to install the new updated driver that has a different INF?

  2. What is the proper way to fully remove the previous NDIS LWF, including from driver store? If we need to use pnputil to fully remove it from driver store, then what is the proper way of finding the OEM number, considering that pnputil -drequires an OEM number?

Comments

  • Peter_Viscarola_(OSR)Peter_Viscarola_(OSR) Administrator Posts: 8,986

    Why is Windows still using the previous INF from driver store when we try to install the new updated driver

    The most common reason for this is that you haven't (correctly) changed the DriverVer directive in the INF. If the DriverVer isn't updated to indicate that the new INF is "newer" then Windows uses the old INF.

    Peter

    Peter Viscarola
    OSR
    @OSRDrivers

  • Michael_VincentMichael_Vincent Member Posts: 5

    @Peter_Viscarola_(OSR) said:

    Why is Windows still using the previous INF from driver store when we try to install the new updated driver

    The most common reason for this is that you haven't (correctly) changed the DriverVer directive in the INF. If the DriverVer isn't updated to indicate that the new INF is "newer" then Windows uses the old INF.

    Peter

    Thank you, indeed the problem was that we used the same driver version and forgot to update it.

  • Peter_Viscarola_(OSR)Peter_Viscarola_(OSR) Administrator Posts: 8,986

    Glad to help.

    I've seen that error no less than sixty two zillion times in our driver seminars over the years. So, you're not the only one to miss this.

    Peter

    Peter Viscarola
    OSR
    @OSRDrivers

Sign In or Register to comment.

Howdy, Stranger!

It looks like you're new here. Sign in or register to get started.

Upcoming OSR Seminars
OSR has suspended in-person seminars due to the Covid-19 outbreak. But, don't miss your training! Attend via the internet instead!
Writing WDF Drivers 12 September 2022 Live, Online
Internals & Software Drivers 23 October 2022 Live, Online
Kernel Debugging 14 November 2022 Live, Online
Developing Minifilters 5 December 2022 Live, Online