Installation

Windows Packet Filter provides production-ready installation packages for Windows systems, featuring official Microsoft driver signatures across x64, ARM64, and x86 processor architectures.

Standard Setup Packages

For end-user systems and development environments, select the MSI installer for the system’s architecture (x64, ARM64, or x86) from the Downloads page. The MSI installs and registers the NDIS Lightweight Filter (LWF) driver. SDK libraries, headers, and examples are obtained separately.

Redistribution & Silent Installation

Commercial licensees redistributing Windows Packet Filter with their applications can use Windows Installer’s silent-installation options. Run these commands from an elevated command prompt, substituting the appropriate MSI filename:

REM Install the x64 driver silently
msiexec /i "Windows.Packet.Filter.3.6.2.1.x64.msi" /qn /norestart

REM Uninstall using the same MSI package
msiexec /x "Windows.Packet.Filter.3.6.2.1.x64.msi" /qn /norestart

Driver Verification

After installation, applications can verify driver availability using the IsDriverLoaded API function.

Installation and Runtime Privileges

Administrator privileges are required to install or uninstall the driver. Once installed, the standard ndisrd driver build allows a standard-user application to open the driver and capture packets without administrator elevation. Runtime access is governed by the driver device object’s access-control list (ACL); a custom build or a deployment with restricted permissions may require an explicitly authorized account or an elevated process. Applications can also impose their own privilege requirements.

Production Access Restrictions

For production deployments, restrict access to the driver device object to the intended service account or other trusted users. This is a recommended deployment security policy, not a requirement for packet capture with the standard build. Validate the application’s runtime account against the device ACL; Windows service-management permissions and driver device access are separate controls.