Installation

The driver must have a unique name to avoid the conflicts with the other software.

- Rename nfsrvfilter.sys to <unique_driver_name>.sys and save it to windows\system32\drivers folder. The given name is used as a substring in driver internal devices to avoid the conflicts with the other driver instances and third-party drivers. The name must be unique for each project, because the driver doesn't allow multiple attached processes.

- Register and start the driver with a call nfsrvregdrv.exe <unique_driver_name> under administrative account or call the API function nf_srv_registerDriver. Any application that uses driver API tries to register the driver automatically during a call to nf_srv_init, if it is not yet registered. The administrative rights are required to perform this operation. The driver starts immediately after registration, and reboot is not required. The driver will be loaded automatically on each system start. When the driver is registered and started, a client process doesn't require administrative rights for using it via API.

- To unregister the driver call nfsrvregdrv.exe -u <unique_driver_name> or use the API function nf_srv_unRegisterDriver. Then delete windows\system32\drivers\<unique_driver_name>.sys and reboot. Administrative rights are required in both cases.

Use 64-bit version of the driver (amd64 configuration) for 64-bit OSes. 32-bit API works properly with both 32-bit and 64-bit versions of the driver. It is possible to use 32-bit or 64-bit API on x64 platform, according to your project needs.

Elevated administrative rights must be activated for registering the driver (run the executable using "Run as administrator" context menu item in Windows Explorer).

For Windows 8 x64 and later versions of the Windows family of operating systems, kernel-mode software must have a digital signature to load on x64-based computer systems. The included x64 version of the driver is not signed. For testing enable the administration menu during system boot and choose Disable Driver Signature Enforcement option. For the end-user software you have to obtain the Code Signing certificate and sign the driver.

Supported platforms:
Windows 8/10/2012/2016 x86/x64