Installs (or upgrades) the component's system driver.
function Install(CabFileName: String; ProductGUID: String; PathToInstall: String; FilterMode: Integer; Altitude: Integer; Flags: Integer): Boolean;
This method is used to install or upgrade the component's system driver. If the system must be rebooted to complete the installation process, this method returns True; otherwise, it returns False.
Important: To upgrade the component's driver, just use the Install method, do not uninstall it first!
Please refer to the Driver Installation topic for more information.
CabFileName must be the path of the cbfilter.cab file containing the component's system driver. Important: This .cab file must remain on the target system (or be available in some other way) after installation, as it is required for uninstalling the driver from the system.
ProductGUID is used to distinguish between driver installations performed by different applications. Such information is necessary to guard against unexpected situations such as, e.g., the driver being uninstalled by one application despite other applications still needing it.
Therefore, to ensure proper operation, it is critical that each individual application have its own unique ProductGUID value, and that applications (and their installation scripts) use that value when calling any of the following methods:
PathToInstall controls where the driver is installed. Pass empty string (highly recommended) to automatically install them to the appropriate Windows system directory.
FilterMode specifies whether the driver should operate in legacy mode or minifilter mode. After installation, the filter mode can be changed at any time using the FilterMode property. Possible values for this parameter are:
|FS_FILTER_MODE_LEGACY||0||Use legacy filesystem filter mode.
Note: Legacy mode is obsolete; support for it is deprecated, and will be removed in a future product update. Please refer to the Minifilter and Legacy Modes topic for more information.
|FS_FILTER_MODE_MINIFILTER||1||Use filesystem minifilter mode.|
Altitude specifies the driver altitude to use when operating in minifilter mode. An altitude value must be assigned by Microsoft before deploying a filesystem minifilter in production; please refer to the Driver Altitudes topic for more information. After installation, the altitude can be changed at any time using the Altitude property.
Flags specifies various installation options, and should contain zero or more of the following flags, OR'd together:
|INSTALL_REMOVE_OLD_VERSIONS||0x00000001||Uninstall drivers from previous component versions (e.g., 2017).|
|INSTALL_KEEP_START_TYPE||0x00000002||Keep the driver's current start type setting in the registry.
If this flag is not set (default), the installation logic will reset the driver's start type setting in the Windows registry to the default value. Setting this flag causes the installation logic to preserve the current value, which may be necessary if the user (or the application itself) set it previously.
|INSTALL_REQUESTS_VIA_DRIVER_STACK||0x00000004||Whether internal requests to the filesystem are sent directly to the filesystem driver or through the stack of filesystem filter drivers.
After installation, the effects of this flag can be changed using the SendRequestsViaDriverStack configuration setting.
|INSTALL_ALWAYS_PREPARE_FILES||0x00010000||Whether the driver should keep track of information for files that are already open when (i.e., were opened before) the component is initialized.
If this flag is set, the driver will prepare information about each file as it is opened, regardless of whether a CBFilter/CBMonitor-based application is actually running at the time. This information then allows applications to receive events for any files that are already open when the CBFilter/CBMonitor component is initialized. Please note that these preparations will slow down all file open operations; don't enable this feature unless it's actually necessary.
After installation, the effects of this flag can be changed using the AlwaysPrepareFiles configuration setting.
|INSTALL_FORCE_APP_PERMISSION_CHECK||0x00020000||Whether the driver should require the controller process to have elevated or system privileges.
If this flag is set, the driver will verify that the controller process is a system service (or is executing with elevated privileges) anytime a file is opened. If the controller process does not meet these requirements, the file will be skipped (i.e., not filtered in any way). Please note that this additional verification will slow down all file open operations.
After installation, the effects of this flag can be changed using the ForceAppPermissionCheck configuration setting.
|INSTALL_FORCE_SECURITY_CHECKS||0x00040000||Whether the driver should prevent the controller process from filtering files that it would not normally have access to.
If this flag is set, the driver will check the security permissions of the controller process anytime a file is opened in order to verify that the process itself has access to the file. If the controller process does not have access to the file, the file will be skipped (i.e., not filtered in any way). For example, if this flag is set and the controller process is running with limited privileges, then the driver will not allow it to filter files that require greater privileges to access. Please note that this additional verification will slow down all file open operations.
After installation, the effects of this flag can be changed using the ForceSecurityChecks configuration setting.
This method is available in both the component API and the Installer DLL included with the product; please refer to the Driver Installation topic for more information about the latter.
This method requires administrative rights to execute successfully. If the user account of the process that calls this method doesn't have such rights, the call will fail with an ERROR_PRIVILEGE_NOT_HELD ($0522) error.
Note: This method cannot be called within events.