NDIS Filter Driver Installation
This section provides information about installing NDIS filter drivers. Lightweight Filter drivers are different from filter intermediate drivers. The configuration manager supplies NDIS with a list of filter modules for each miniport adapter. There's no virtual device (or virtual miniport) that is associated with a filter driver as there is with an NDIS filter intermediate driver.
To install a filter driver, you must provide a single INF file. The configuration manager reads configuration information about the filter driver from the INF file and copies it to the registry.
The filter driver INF file defines a network service. Filter drivers don't have a miniport INF file. For an example filter driver INF file, see the ndislwf sample driver.
Once you have provided your filter driver INF file, to install or uninstall your filter driver you must use the INetCfg family of Network Configuration Interfaces. For example, to install or remove network components, call into the INetCfgClassSetup interface. You can either call into these interfaces programmatically or you can indirectly call them with netcfg.exe, which calls INetCfg for you. You can't install a driver package through the INetCfg and use the Driver Store feature on older Windows versions. To successfully install the driver package in this scenario, you need to have a minimum OS build number of 25319. You can't use SetupAPI to install or uninstall an NDIS filter driver.
For an example of calling into INetCfg through code, see the Bindview Network Configuration Utility sample.
This section includes:
Specifying Filter Driver Binding Relationships
Feedback
Coming soon: Throughout 2024 we will be phasing out GitHub Issues as the feedback mechanism for content and replacing it with a new feedback system. For more information see: https://aka.ms/ContentUserFeedback.
Submit and view feedback for