CBProcess Component
Properties Methods Events Config Settings Errors
The CBProcess component enables applications to intercept process manager requests.
Syntax
TcbfCBProcess
Remarks
The CBProcess component gives applications the ability to monitor and (in some cases) control process- and thread-related requests. Because the CBProcess API is far less complex than other components' APIs, it uses simple filter rules; please refer to the File and Registry Filter Rules topic for more information.
To learn more about the component's capabilities, please refer to the product's General Information topics.
Getting Started
- If the component's system driver has not been installed yet, call the Install method to do so. This needs to be done only once.
- In production, the driver can be installed (or updated) ahead of time by the application's installation script using the Installer DLL. Please refer to the Driver Installation topic for more information.
- Call the Initialize method to initialize the CBProcess component. This must be done each time the application starts.
- Add one or more filter rules using methods like AddFilteredProcessById and AddFilteredProcessByName. (Rules also can be added or removed after the filter is started.)
- Call the StartFilter method to start filtering process manager requests.
- When finished, call the StopFilter method to stop filtering process manager requests.
- To uninstall the component's system driver, call the Uninstall method. This should not be done as part of the driver upgrade process.
- In production, the driver can be uninstalled by the application's uninstallation script using the Installer DLL. Please refer to the Driver Installation topic for more information.
Property List
The following is the full list of the properties of the component with short descriptions. Click on the links for further details.
Active | This property notes whether the component is active and processing requests. |
Altitude | This property specifies the altitude that the component's system driver should use. |
RunningProcesses | This property includes a collection of running processes' information. |
SerializeEvents | Whether events should be fired on a single worker thread, or many. |
StrictAltitude | This property specifies how to behave if the specified altitude is already in use. |
Tag | This property stores application-defined data specific to a particular instance of the component. |
TrackCommandLine | This property specifies whether the driver should store information about processes' command-line arguments. |
Method List
The following is the full list of the methods of the component with short descriptions. Click on the links for further details.
AddFilteredProcessById | This method adds a process, by process ID (PID), to the list of filtered processes. |
AddFilteredProcessByName | This method adds a process, by name, to the list of filtered processes. |
AddIgnoredProcessById | This method adds a process, by process ID (PID), to the list of ignored processes. |
AddIgnoredProcessByName | This method adds a process, by name, to the list of ignored processes. |
CloseRunningProcessesSnapshot | This method closes the previously created snapshot of running processes. |
Config | Sets or retrieves a configuration setting. |
CreateRunningProcessesSnapshot | This method creates a snapshot of running processes. |
GetDriverStatus | This method retrieves the status of the component's system driver. |
GetDriverVersion | This method retrieves the version of the component's system driver. |
GetOriginatorToken | This method retrieves the security token associated with the process that initiated the operation. |
GetProcessName | This method retrieves the name of the process associated with the specified process ID (PID). |
Initialize | This method initializes the component. |
Install | This method installs (or upgrades) the component's system driver. |
RemoveFilteredProcessById | This method removes a process, by process ID (PID), from the list of filtered processes. |
RemoveFilteredProcessByName | This method removes a process, by name, from the list of filtered processes. |
RemoveIgnoredProcessById | This method removes a process, by process ID (PID), from the list of ignored processes. |
RemoveIgnoredProcessByName | This method removes a process, by name, from the list of ignored processes. |
ResetTimeout | This method resets the timeout duration for the current event handler. |
ShutdownSystem | Shuts down or reboots the operating system. |
StartFilter | This method starts the filtering process and thread operations. |
StopFilter | This method stops the filtering process and thread operations. |
Uninstall | This method uninstalls the component's system driver. |
Event List
The following is the full list of the events fired by the component with short descriptions. Click on the links for further details.
Error | This event fires if an unhandled error occurs during an event. |
ProcessCreation | This event fires when a process is being created. |
ProcessHandleOperation | This event fires when a process handle is being created or duplicated. |
ProcessTermination | This event fires when a process is being terminated. |
ThreadCreation | This event fires when a thread is being created. |
ThreadHandleOperation | This event fires when a thread handle is being created or duplicated. |
ThreadTermination | This event fires when a thread is being terminated. |
WorkerThreadCreation | Fires just after a new worker thread is created. |
WorkerThreadTermination | Fires just before a worker thread is terminated. |
Config Settings
The following is a list of config settings for the component with short descriptions. Click on the links for further details.
FilterOwnRequests | Whether the component's system driver should filter requests made by the application itself. |
LoggingEnabled | Whether extended logging is enabled. |
MaxWorkerThreadCount | The maximum number of worker threads to use to fire events. |
MinWorkerThreadCount | The minimum number of worker threads to use to fire events. |
WorkerInitialStackSize | The initial stack size to create worker threads with. |
BuildInfo | Information about the product's build. |
LicenseInfo | Information about the current license. |
Active Property (CBProcess Component)
This property notes whether the component is active and processing requests.
Syntax
property Active: Boolean read get_Active;
Default Value
false
Remarks
This property reflects whether the component is active and currently processing requests. It will be True after the filter has been attached successfully via a call to StartFilter.
This property is read-only and not available at design time.
Altitude Property (CBProcess Component)
This property specifies the altitude that the component's system driver should use.
Syntax
property Altitude: String read get_Altitude write set_Altitude;
Default Value
'400055'
Remarks
This property specifies the altitude that the component's system driver should use. A driver's altitude determines its absolute position in the stack of filter drivers; drivers with higher altitudes are attached toward the top of the stack, closer to the user mode, which allows them to process requests earlier.
Microsoft's documentation is unclear about how altitudes should be chosen for process manager filter drivers; please refer to the Driver Altitudes topic for more information. The default value of this property is 400055 (which is not registered with Microsoft), but applications can likely choose any value they desire. If the specified altitude is already in use by another driver, the component's driver will behave in the manner specified by the StrictAltitude property.
RunningProcesses Property (CBProcess Component)
This property includes a collection of running processes' information.
Syntax
property RunningProcesses: TcbfRunningProcessList read get_RunningProcesses;
Remarks
This property holds a collection of RunningProcess objects, each of which represents a running process.
Note: This collection is not populated or updated by default. Applications can call the CreateRunningProcessesSnapshot method to populate this collection; and must call the CloseRunningProcessesSnapshot method when finished working with it to release the associated memory.
This property is read-only and not available at design time.
Please refer to the RunningProcess type for a complete list of fields.SerializeEvents Property (CBProcess Component)
Whether events should be fired on a single worker thread, or many.
Syntax
property SerializeEvents: TcbfTSerializeEvents read get_SerializeEvents write set_SerializeEvents;
TcbfTSerializeEvents = ( seOnMultipleThreads, seOnOneWorkerThread );
Default Value
seOnMultipleThreads
Remarks
This property specifies whether the component should fire all events serially on a single worker thread, or concurrently on multiple worker threads. The possible values are:
0 (seOnMultipleThreads) | The component fires events in the context of multiple worker threads. The MinWorkerThreadCount and MaxWorkerThreadCount configuration settings control how many worker threads are used for this. |
1 (seOnOneWorkerThread) | The component fires events in the context of one background worker thread. |
Please refer to the Threading and Concurrency topic for more information.
Note: This property cannot be changed when Active is True, and it cannot be changed within events.
StrictAltitude Property (CBProcess Component)
This property specifies how to behave if the specified altitude is already in use.
Syntax
property StrictAltitude: Boolean read get_StrictAltitude write set_StrictAltitude;
Default Value
false
Remarks
This property specifies how the component's system driver should behave if the specified Altitude is already in use when the StartFilter method is called.
If this property is enabled, the filter will fail to attach. If this property is disabled (default), the driver will attempt to use an adjacent altitude value to attach the filter.
Tag Property (CBProcess Component)
This property stores application-defined data specific to a particular instance of the component.
Syntax
property Tag: Int64 read get_Tag write set_Tag;
Default Value
0
Remarks
This property can be used to store data specific to a particular instance of the component.
TrackCommandLine Property (CBProcess Component)
This property specifies whether the driver should store information about processes' command-line arguments.
Syntax
property TrackCommandLine: Boolean read get_TrackCommandLine write set_TrackCommandLine;
Default Value
false
Remarks
This property specifies whether the component should store command-line parameters for all processes that are running. Set this property to True if you want to receive command lines for each process during enumeration that is created with CreateRunningProcessesSnapshot.
Note: This property cannot be changed when Active is True, and it cannot be changed within events.
AddFilteredProcessById Method (CBProcess Component)
This method adds a process, by process ID (PID), to the list of filtered processes.
Syntax
procedure AddFilteredProcessById(ProcessId: Integer; IncludeChildren: Boolean);
Remarks
This method adds the process with the specified ProcessId (PID) to the list of processes whose requests should be filtered (i.e., that the component should fire events for).
The ProcessId parameter specifies the PID of the process whose requests should be filtered. The value passed for this parameter must be either the PID of an existing process or -1, which means "all processes".
The IncludeChildren parameter specifies whether requests made by the specified process's children should also be filtered.
Note: This method can be called only when Active is True.
AddFilteredProcessByName Method (CBProcess Component)
This method adds a process, by name, to the list of filtered processes.
Syntax
procedure AddFilteredProcessByName(ProcessName: String; IncludeChildren: Boolean);
Remarks
This method adds the process with the specified ProcessName to the list of processes whose requests should be filtered (i.e., that the component should fire events for).
The ProcessName parameter must be a valid process executable name. It may optionally begin with a path, and both the name and the path (if present) may include wildcards (* and ?). A process with a matching executable name does not actually need to exist when this method is called.
The IncludeChildren parameter specifies whether requests made by the specified process's children should also be filtered.
Note: This method can be called only when Active is True.
AddIgnoredProcessById Method (CBProcess Component)
This method adds a process, by process ID (PID), to the list of ignored processes.
Syntax
procedure AddIgnoredProcessById(ProcessId: Integer; IncludeChildren: Boolean);
Remarks
This method adds the process with the specified ProcessId (PID) to the list of processes whose requests should be ignored (i.e., that the component should not fire events for).
The ProcessId parameter specifies the PID of the process whose requests should be ignored. The value passed for this parameter must be the PID of an existing process.
The IncludeChildren parameter specifies whether requests made by the specified process's children should also be ignored.
Note: The component's system driver ignores all processes' requests by default. Applications should use this method only to explicitly exclude a process that otherwise would be filtered because of a process filtering rule added with AddFilteredProcessById or AddFilteredProcessByName.
Note: This method can be called only when Active is True.
AddIgnoredProcessByName Method (CBProcess Component)
This method adds a process, by name, to the list of ignored processes.
Syntax
procedure AddIgnoredProcessByName(ProcessName: String; IncludeChildren: Boolean);
Remarks
This method adds the process with the specified ProcessName to the list of processes whose requests should be ignored (i.e., that the component should not fire events for).
The ProcessName parameter must be a valid process executable name. It may optionally begin with a path, and both the name and the path (if present) may include wildcards (* and ?). A process with a matching executable name does not actually need to exist when this method is called.
The IncludeChildren parameter specifies whether requests made by the specified process's children should also be ignored.
Note: The component's system driver ignores all processes' requests by default. Applications should use this method only to explicitly exclude a process that otherwise would be filtered because of a process filtering rule added with AddFilteredProcessById or AddFilteredProcessByName.
Note: This method can be called only when Active is True.
CloseRunningProcessesSnapshot Method (CBProcess Component)
This method closes the previously created snapshot of running processes.
Syntax
procedure CloseRunningProcessesSnapshot();
Remarks
This method closes the snapshot previously created by CreateRunningProcessesSnapshot, releasing the memory associated with it. Please refer to that method's documentation for more information.
Note: This method cannot be called within events.
Config Method (CBProcess Component)
Sets or retrieves a configuration setting.
Syntax
function Config(ConfigurationString: String): String;
Remarks
Config is a generic method available in every component. It is used to set and retrieve configuration settings for the component.
These settings are similar in functionality to properties, but they are rarely used. In order to avoid "polluting" the property namespace of the component, access to these internal properties is provided through the Config method.
To set a configuration setting named PROPERTY, you must call Config("PROPERTY=VALUE"), where VALUE is the value of the setting expressed as a string. For boolean values, use the strings "True", "False", "0", "1", "Yes", or "No" (case does not matter).
To read (query) the value of a configuration setting, you must call Config("PROPERTY"). The value will be returned as a string.
CreateRunningProcessesSnapshot Method (CBProcess Component)
This method creates a snapshot of running processes.
Syntax
procedure CreateRunningProcessesSnapshot();
Remarks
This method creates a snapshot of information about processes that are running in the system. This information is then used to populate the RunningProcesses* properties.
When the application is finished working with the default rules snapshot, it must close it by calling the CloseRunningProcessesSnapshot method to release the associated memory. If this method is called again before an existing snapshot is closed, the component will attempt to close it before creating a new one.
Note: This method cannot be called within events.
GetDriverStatus Method (CBProcess Component)
This method retrieves the status of the component's system driver.
Syntax
function GetDriverStatus(ProductGUID: String): Integer;
Remarks
This method retrieves the status of the component's system driver. This status can then be used to verify whether it has been properly installed and is ready for use.
The value returned by the method corresponds to the dwCurrentState field of the SERVICE_STATUS structure from the Windows API. It will be one of the following:
MODULE_STATUS_NOT_PRESENT | 0x00000000 | The specified module is not present on the system.
Note: This functionality is only available in Windows. |
MODULE_STATUS_STOPPED | 0x00000001 | The specified module is in the Stopped state.
Note: This functionality is only available in Windows. |
MODULE_STATUS_RUNNING | 0x00000004 | The specified module is loaded and running.
Note: This functionality is only available in Windows. |
ProductGUID is used to distinguish among driver installations performed by different applications. Such information is necessary to guard against unexpected situations, such as 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:
- Install
- Uninstall
- GetDriverStatus
- GetDriverVersion
- Initialize
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.
Note: This method cannot be called within events.
GetDriverVersion Method (CBProcess Component)
This method retrieves the version of the component's system driver.
Syntax
function GetDriverVersion(ProductGUID: String): Int64;
Remarks
This method retrieves the version of the component's system driver. The value is returned as a 64-bit integer composed of four 16-bit words that each correspond to a piece of the overall module version. For example, a version of 2.32.6.28 would cause the value 0x000200200006001C to be returned.
If the component's system driver is not installed, this method returns 0.
ProductGUID is used to distinguish among driver installations performed by different applications. Such information is necessary to guard against unexpected situations, such as 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:
- Install
- Uninstall
- GetDriverStatus
- GetDriverVersion
- Initialize
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.
Note: This method cannot be called within events.
GetOriginatorToken Method (CBProcess Component)
This method retrieves the security token associated with the process that initiated the operation.
Syntax
function GetOriginatorToken(): Int64;
Remarks
This method can be called within events fired for process and thread operations to retrieve the security token associated with the process that initiated the operation. If the query fails, this method returns INVALID_HANDLE_VALUE.
The security token returned by this method can be passed to the Windows API's GetTokenInformation function to obtain more information about the process.
Note: When applications are finished using the returned security token, they must close it using the Windows API's CloseHandle function.
Note: This method can be called only within events.
GetProcessName Method (CBProcess Component)
This method retrieves the name of the process associated with the specified process ID (PID).
Syntax
function GetProcessName(ProcessId: Integer): String;
Remarks
This method retrieves the name of the process with the specified ProcessId (PID). If such a process currently exists, this method returns the fully qualified name of its executable; otherwise, it returns an empty string.
Note: The System process does not technically have a name; passing its PID to this method will cause empty string to be returned.
Initialize Method (CBProcess Component)
This method initializes the component.
Syntax
procedure Initialize(ProductGUID: String);
Remarks
This method initializes the component and must be called each time the application starts before attempting to call any of the component's other methods with the exception of installation-related methods.
ProductGUID is used to distinguish among driver installations performed by different applications. Such information is necessary to guard against unexpected situations, such as 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:
If the required driver was not installed using the Install method with the same value of ProductGUID, Initialize will return a ERROR_FILE_NOT_FOUND error (Win32 error code 2).
If the loaded kernel-mode driver is older than the user-mode API, Initialize will return a ERROR_INVALID_KERNEL_INFO_VERSION error (Win32 error code 340). In this situation, an update of the driver using the Install method is required before the component can be used.
Install Method (CBProcess Component)
This method installs (or upgrades) the component's system driver.
Syntax
function Install(CabFileName: String; ProductGUID: String; PathToInstall: String; Flags: Integer; AllowedControllers: String): Boolean;
Remarks
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, use only the Install method. Previously installed versions of the driver should not be uninstalled first. Calling the Install method will upgrade the previously installed version.
Please refer to the Driver Installation topic for more information.
CabFileName must be the path of the .cab file containing the component's system driver.
Note: This .cab file must remain on the target system (or be available in some other way) after installation, because it is required to uninstall the driver from the system.
ProductGUID is used to distinguish among driver installations performed by different applications. Such information is necessary to guard against unexpected situations, such as 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 the driver to the appropriate Windows system directory.
Flags specifies various installation options and should contain zero or more of the following flags, ORed 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) set it previously. |
INSTALL_OVERWRITE_SAME_VERSION | 0x00000004 | Install the driver file when its version and build number is the same as the version of the already installed driver. |
INSTALL_REQUESTS_VIA_DRIVER_STACK | 0x00001000 | Whether internal requests to the filesystem are sent directly to the filesystem driver or through the stack of filesystem filter drivers.
This flag is applicable only for CBFilter and CBMonitor. 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.
This flag is applicable only for CBFilter and CBMonitor. 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. Note: These preparations will slow down all file open operations; do not enable this feature unless it is 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.
This flag is not applicable for CBProcess. 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). Note: 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.
This flag is not applicable for CBProcess. If this flag is set, the driver will check the security permissions of the controller process anytime a file is opened to verify that the process 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. Note: 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. |
AllowedControllers is the optional parameter that makes it possible to limit communication with the driver to just the predefined set of processes. When the caller specifies one or more names of the executable files, filtering can be started with the specified ProductGUID only when filtering is initiated by the process created from one of the listed executable files. If the name of the caller process does not match any of the allowed names, the call to StartFilter will fail with an error.
The parameter may be either empty or contain one or more EXE file names with complete paths. Separate names/paths should be separated by the LF character (numeric code 10).
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.
RemoveFilteredProcessById Method (CBProcess Component)
This method removes a process, by process ID (PID), from the list of filtered processes.
Syntax
procedure RemoveFilteredProcessById(ProcessId: Integer);
Remarks
This method removes the process with the specified ProcessId (PID) from the list of processes whose requests should be filtered.
The value passed for ProcessId must be one that was previously used to call AddFilteredProcessById; please refer to its documentation for more information.
Note: This method can be called only when Active is True.
RemoveFilteredProcessByName Method (CBProcess Component)
This method removes a process, by name, from the list of filtered processes.
Syntax
procedure RemoveFilteredProcessByName(ProcessName: String);
Remarks
This method removes the process with the specified ProcessName from the list of processes whose requests should be filtered.
The value passed for ProcessName must be one that was previously used to call AddFilteredProcessByName; please refer to its documentation for more information.
Note: This method can be called only when Active is True.
RemoveIgnoredProcessById Method (CBProcess Component)
This method removes a process, by process ID (PID), from the list of ignored processes.
Syntax
procedure RemoveIgnoredProcessById(ProcessId: Integer);
Remarks
This method removes the process with the specified ProcessId (PID) from the list of processes whose requests should be ignored.
The value passed for ProcessId must be one that was previously used to call AddIgnoredProcessById; please refer to its documentation for more information.
Note: This method can be called only when Active is True.
RemoveIgnoredProcessByName Method (CBProcess Component)
This method removes a process, by name, from the list of ignored processes.
Syntax
procedure RemoveIgnoredProcessByName(ProcessName: String);
Remarks
This method removes the process with the specified ProcessName from the list of processes whose requests should be ignored.
The value passed for ProcessName must be one that was previously used to call AddIgnoredProcessByName; please refer to its documentation for more information.
Note: This method can be called only when Active is True.
ResetTimeout Method (CBProcess Component)
This method resets the timeout duration for the current event handler.
Syntax
function ResetTimeout(Timeout: Integer): Boolean;
Remarks
When event timeouts are being enforced, this method can be called within an event handler to inform the component that request processing is taking longer than expected.
If called successfully, this method returns True, and the current event handler's timeout timer is immediately reset to 0; when it reaches the number of milliseconds specified by Timeout, the driver will either "release" the underlying request and pass it onwards, or cancel it by reporting an error; whichever is most appropriate for the event in question. Please refer to the Timeouts topic for more information.
Passing 0 for Timeout disables the timeout timer for the current event handler, allowing it to take as long as it needs to complete.
Note: This method can be called only within events.
ShutdownSystem Method (CBProcess Component)
Shuts down or reboots the operating system.
Syntax
function ShutdownSystem(ShutdownPrompt: String; Timeout: Integer; ForceCloseApps: Boolean; Reboot: Boolean): Boolean;
Remarks
This method shuts down or (if Reboot is True) reboots the operating system. If the appropriate privileges cannot be obtained, or if the InitiateSystemShutdown system call returns False, then this method will return False; otherwise, it returns True. This method can be used if the installation or uninstallation function requires the system to be rebooted in order to complete.
ShutdownPrompt, if non-empty, specifies a message that the OS should display to the user for Timeout seconds. If empty string is passed for ShutdownPrompt, no message is displayed and the Timeout parameter's value is ignored.
ForceCloseApps specifies whether the OS should forcefully close all applications. Please keep in mind that forceful closing of applications with unsaved data can lead to data loss.
Reboot specifies whether the OS should reboot (True) or just shut down (False).
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.
Note: This method cannot be called within events.
StartFilter Method (CBProcess Component)
This method starts the filtering process and thread operations.
Syntax
procedure StartFilter(Timeout: Integer; EventsToFire: Integer);
Remarks
This method attaches the filter, causing the component's system driver to start the filtering process and thread operations according to the filter rules currently present. Rules can be added and removed both before and after this method is called, so long as the Initialize method is called before doing anything else.
This method can fail for a number of reasons, including (but not limited to) the following:
- If the component's system driver has not been properly installed, or is awaiting a system reboot (as indicated by the return value of Install), this method fails with an ERROR_FILE_NOT_FOUND (2) error code.
- If the Initialize method has not been called yet, this method fails with an ERROR_NOT_READY (21) error code.
- If the filter is already Active, this method fails with an ERROR_CONNECTION_ACTIVE (1230) error code.
- If an invalid value is passed for Timeout, this method fails with an ERROR_IMPLEMENTATION_LIMIT (1292) error code.
Timeout
Timeout specifies how many milliseconds the driver should wait for events to execute before releasing or cancelling the underlying OS requests; please refer to the Timeouts topic for more information. Valid values are 0, which disables event timeouts, and values greater than or equal to 3000. When event timeouts are in effect, event handlers can call ResetTimeout to reset the timer if they require additional time to complete.
EventsToFire
EventsToFire specifies the event types that must be fired by the component. The setting should be set by ORing together zero or more flags. Possible values are as follows:
PROC_EVT_NONE | 0 | Don't fire for any process operations.
Events will not fire for any process operations. |
PROC_EVT_PROCESS_CREATION | 1 | Fire during process creation operations.
The ProcessCreation event will fire anytime the OS attempts to create a process. |
PROC_EVT_PROCESS_TERMINATION | 2 | Fire during process closing/termination.
The ProcessTermination event will fire when a process is being terminated. |
PROC_EVT_PROCESS_HANDLE_OPERATION | 4 | Fire during process handle creation or duplication.
The ProcessHandleOperation event will fire when a process handle is being created or duplicated. |
PROC_EVT_THREAD_CREATION | 8 | Fire during thread creation operations.
The ThreadCreation event will fire when a thread is being created, before it is started. |
PROC_EVT_THREAD_TERMINATION | 0x10 | Fire during thread termination operations.
The ThreadTermination event will fire when a thread is being terminated. |
PROC_EVT_THREAD_HANDLE_OPERATION | 0x20 | Fire during thread handle creation or duplication.
The ThreadHandleOperation event will fire when a thread handle is being created or duplicated. |
PROC_EVT_ALL | -1 | Fire for all process and thread operations.
Events will fire for all thread operations. |
StopFilter Method (CBProcess Component)
This method stops the filtering process and thread operations.
Syntax
procedure StopFilter();
Remarks
This method detaches the filter, causing the component's system driver to stop the filtering process and thread operations. This method will block until all pending requests have been completed and the filter has been detached.
Uninstall Method (CBProcess Component)
This method uninstalls the component's system driver.
Syntax
function Uninstall(CabFileName: String; ProductGUID: String; InstalledPath: String; Flags: Integer): Boolean;
Remarks
This method is used to uninstall the component's system driver. If the system must be rebooted to complete the uninstallation process, this method returns True; otherwise, it returns False.
Important: To upgrade the component's driver, use only the Install method. Previously installed versions of the driver should not be uninstalled first. Calling the Install method will upgrade the previously installed version.
Please refer to the Driver Installation topic for more information.
The same values must be passed for the CabFileName, ProductGUID, and InstalledPath parameters as were passed when Install was called; please refer to its documentation for more information.
Flags specifies which versions of the component's system driver should be uninstalled and which should be set by ORing together one or more of the following values:
UNINSTALL_VERSION_PREVIOUS | 0x00000001 | Uninstall modules from previous product versions.
Note: This functionality is only available in Windows. |
UNINSTALL_VERSION_CURRENT | 0x00000002 | Uninstall modules from the current product version.
Note: This functionality is only available in Windows. |
UNINSTALL_VERSION_ALL | 0x00000003 | Uninstall modules from all product versions.
Note: This functionality is only available in Windows. |
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.
Error Event (CBProcess Component)
This event fires if an unhandled error occurs during an event.
Syntax
type TErrorEvent = procedure ( Sender: TObject; ErrorCode: Integer; const Description: String ) of Object;
property OnError: TErrorEvent read FOnError write FOnError;
Remarks
This event fires if an unhandled error occurs during another event. Developers can use this information to track down unhandled errors in an application's event handlers.
Note: Not everything is possible or allowed in the event handlers. For details, see the Recursive Calls topic.
ProcessCreation Event (CBProcess Component)
This event fires when a process is being created.
Syntax
type TProcessCreationEvent = procedure ( Sender: TObject; ProcessId: Integer; ParentProcessId: Integer; CreatingProcessId: Integer; CreatingThreadId: Integer; const ProcessName: String; const ImageFileName: String; FileOpenNameAvailable: Boolean; const CommandLine: String; var ResultCode: Integer ) of Object;
property OnProcessCreation: TProcessCreationEvent read FOnProcessCreation write FOnProcessCreation;
Remarks
This event fires when a process is being created, after its first thread is created but before it begins running.
Applications may use this event to cancel the process creation by returning an appropriate error code (e.g., ACCESS_DENIED) via ResultCode.
The ProcessId parameter reflects the Id of the process being created.
The ParentProcessId parameter reflects the Id of the new process's parent process, from which it may inherit certain resources (e.g., handles, shared memory).
The CreatingProcessId parameter reflects the Id of the process that created the new process (which is not always the same as its parent process).
The CreatingThreadId parameter reflects the Id of the thread that created the new process.
The ProcessName parameter reflects the name of the new process. This parameter's value is the same one that the GetProcessName method would return for ProcessId.
The ImageFileName parameter reflects the name of the new process's executable file, as either a partial or a fully qualified file path.
The FileOpenNameAvailable parameter indicates whether the ImageFileName parameter's contains a fully qualified file path (True) or a partial one (False).
The CommandLine parameter reflects the command line used to start the new process.
Note: To use the event, enable it via the rcfgEventsToFire; configuration setting. For this event to fire, the creating process must match the rules that were added using AddFilteredProcessById or AddFilteredProcessByName. Additionally, if the creating process is the same process that controls the instance of the component, the FilterOwnRequests configuration setting must be set to True.
The ResultCode parameter will always be 0 when the event is fired. If the event cannot be handled in a "successful" manner for some reason (e.g., a resource is not available or security checks failed), set it to a nonzero value to report an appropriate error. Please see the Error Handling topic for more information.
This event is fired synchronously; please refer to the Event Types topic for more information.
ProcessHandleOperation Event (CBProcess Component)
This event fires when a process handle is being created or duplicated.
Syntax
type TProcessHandleOperationEvent = procedure ( Sender: TObject; Duplication: Boolean; ProcessId: Integer; OriginatorProcessId: Integer; OriginatorThreadId: Integer; SourceProcessId: Integer; TargetProcessId: Integer; OriginalDesiredAccess: Integer; var DesiredAccess: Integer; var ResultCode: Integer ) of Object;
property OnProcessHandleOperation: TProcessHandleOperationEvent read FOnProcessHandleOperation write FOnProcessHandleOperation;
Remarks
This event fires when a process handle is being created or duplicated. The new handle allows operations to be performed on the associated process.
Applications may use this event to restrict the access rights that will be granted to the new process handle. For example, to prevent process termination, the application could remove the PROCESS_TERMINATE flag.
The Duplication parameter indicates whether a new process handle is being create (False) or an existing one is being duplicated (True).
The ProcessId parameter reflects the Id of the process whose handle is being created or duplicated.
The OriginatorProcessId parameter reflects the Id of the process that requested a handle be created or duplicated.
The OriginatorThreadId parameter reflects the Id of the thread that requested a handle be created or duplicated.
The SourceProcessId and TargetProcessId parameters reflect the Id of the process that is the source of the handle, and the Id of the process that receives the duplicated handle, respectively. (These parameters' values are valid only if Duplication is True.)
The OriginalDesiredAccess parameter reflects the access rights originally requested for the new handle.
The DesiredAccess parameter specifies the access rights that should be granted to the new handle; it will match OriginalDesiredAccess initially. Applications can remove access flags from this value, but they cannot add additional flags.
Please refer to Microsoft's OB_PRE_CREATE_HANDLE_INFORMATION structure documentation for more information about possible access flags.
The ResultCode parameter will always be 0 when the event is fired. If the event cannot be handled in a "successful" manner for some reason (e.g., a resource is not available or security checks failed), set it to a nonzero value to report an appropriate error. Please see the Error Handling topic for more information.
Note: To use the event, enable it via the rcfgEventsToFire; configuration setting.
Note: The system APIs offer no way to report errors that occur during the processing of this request. Therefore, exceptional ResultCode values are largely ignored.
This event is fired synchronously; please refer to the Event Types topic for more information.
ProcessTermination Event (CBProcess Component)
This event fires when a process is being terminated.
Syntax
type TProcessTerminationEvent = procedure ( Sender: TObject; ProcessId: Integer; const ProcessName: String; var ResultCode: Integer ) of Object;
property OnProcessTermination: TProcessTerminationEvent read FOnProcessTermination write FOnProcessTermination;
Remarks
This event fires when a process is being terminated, just before its last thread is destroyed.
Applications cannot prevent a process from being terminated using this event; use the ProcessHandleOperation event instead.
The ProcessId parameter reflects the Id of the terminating process.
The ProcessName parameter reflects the name of the terminating process. This parameter's value is the same one that the GetProcessName method would return for ProcessId.
Note: To use the event, enable it via the rcfgEventsToFire; configuration setting.
The ResultCode parameter will always be 0 when the event is fired. If the event cannot be handled in a "successful" manner for some reason (e.g., a resource is not available or security checks failed), set it to a nonzero value to report an appropriate error. Please see the Error Handling topic for more information.
Note: The system APIs offer no way to report errors that occur during the processing of this request. Therefore, exceptional ResultCode values are largely ignored.
This event is fired synchronously; please refer to the Event Types topic for more information.
ThreadCreation Event (CBProcess Component)
This event fires when a thread is being created.
Syntax
type TThreadCreationEvent = procedure ( Sender: TObject; ProcessId: Integer; ThreadId: Integer; CreatingProcessId: Integer; CreatingThreadId: Integer; var ResultCode: Integer ) of Object;
property OnThreadCreation: TThreadCreationEvent read FOnThreadCreation write FOnThreadCreation;
Remarks
This event fires when a thread is being created, before it is started.
Applications cannot cancel thread creation; any errors returned during this event are ignored.
The ProcessId parameter reflects the Id of the process to which the new thread belongs.
The ThreadId parameter reflects the Id of the new thread.
The CreatingProcessId parameter reflects the Id of the process that created the new thread.
The CreatingThreadId parameter reflects the Id of the thread that created the new thread.
Note: To use the event, enable it via the rcfgEventsToFire; configuration setting.
The ResultCode parameter will always be 0 when the event is fired. If the event cannot be handled in a "successful" manner for some reason (e.g., a resource is not available or security checks failed), set it to a nonzero value to report an appropriate error. Please see the Error Handling topic for more information.
Note: The system APIs offer no way to report errors that occur during the processing of this request. Therefore, exceptional ResultCode values are largely ignored.
This event is fired synchronously; please refer to the Event Types topic for more information.
ThreadHandleOperation Event (CBProcess Component)
This event fires when a thread handle is being created or duplicated.
Syntax
type TThreadHandleOperationEvent = procedure ( Sender: TObject; Duplication: Boolean; ProcessId: Integer; ThreadId: Integer; OriginatorProcessId: Integer; OriginatorThreadId: Integer; SourceProcessId: Integer; TargetProcessId: Integer; OriginalDesiredAccess: Integer; var DesiredAccess: Integer; var ResultCode: Integer ) of Object;
property OnThreadHandleOperation: TThreadHandleOperationEvent read FOnThreadHandleOperation write FOnThreadHandleOperation;
Remarks
This event fires when a thread handle is being created or duplicated. The new handle allows operations to be performed on the associated thread.
Applications may use this event to restrict the access rights that will be granted to the new thread handle. For example, to prevent thread termination, the application could remove the THREAD_TERMINATE flag.
The Duplication parameter indicates whether a new thread handle is being created (False), or an existing one is being duplicated (True).
The ProcessId parameter reflects the Id of the process whose thread's handle is being created or duplicated.
The ThreadId parameter reflects the Id of the thread whose handle is being created or duplicated.
Note: To use the event, enable it via the rcfgEventsToFire; configuration setting.
The OriginatorProcessId parameter reflects the Id of the process that requested a handle be created or duplicated.
The OriginatorThreadId parameter reflects the Id of the thread that requested a handle be created or duplicated.
The SourceProcessId and TargetProcessId parameters reflect the Id of the process that is the source of the handle, and the Id of the process that receives the duplicated handle, respectively. (These parameters' values are valid only if Duplication is True.)
The OriginalDesiredAccess parameter reflects the access rights originally requested for the new handle.
The DesiredAccess parameter specifies the access rights that should be granted to the new handle; it will match OriginalDesiredAccess initially. Applications can remove access flags from this value, but they cannot add additional flags.
Please refer to Microsoft's OB_PRE_CREATE_HANDLE_INFORMATION structure documentation for more information about possible access flags.
The ResultCode parameter will always be 0 when the event is fired. If the event cannot be handled in a "successful" manner for some reason (e.g., a resource is not available or security checks failed), set it to a nonzero value to report an appropriate error. Please see the Error Handling topic for more information.
Note: The system APIs offer no way to report errors that occur during the processing of this request. Therefore, exceptional ResultCode values are largely ignored.
This event is fired synchronously; please refer to the Event Types topic for more information.
ThreadTermination Event (CBProcess Component)
This event fires when a thread is being terminated.
Syntax
type TThreadTerminationEvent = procedure ( Sender: TObject; ProcessId: Integer; ThreadId: Integer; var ResultCode: Integer ) of Object;
property OnThreadTermination: TThreadTerminationEvent read FOnThreadTermination write FOnThreadTermination;
Remarks
This event fires when a thread is being terminated.
Applications cannot prevent a thread from being terminated using this event; use the ThreadHandleOperation event instead.
The ProcessId parameter reflects the Id of process whose thread is being terminated.
The ThreadId parameter reflects the Id of the terminating thread.
Note: To use the event, enable it via the rcfgEventsToFire; configuration setting.
The ResultCode parameter will always be 0 when the event is fired. If the event cannot be handled in a "successful" manner for some reason (e.g., a resource is not available or security checks failed), set it to a nonzero value to report an appropriate error. Please see the Error Handling topic for more information.
Note: The system APIs offer no way to report errors that occur during the processing of this request. Therefore, exceptional ResultCode values are largely ignored.
This event is fired synchronously; please refer to the Event Types topic for more information.
WorkerThreadCreation Event (CBProcess Component)
Fires just after a new worker thread is created.
Syntax
type TWorkerThreadCreationEvent = procedure ( Sender: TObject; var ResultCode: Integer ) of Object;
property OnWorkerThreadCreation: TWorkerThreadCreationEvent read FOnWorkerThreadCreation write FOnWorkerThreadCreation;
Remarks
This event fires just after a worker thread is created, in the context of that worker thread.
This event is optional; it is provided to give applications a chance to perform additional processing when a new worker thread is created, such as allocating per-thread objects.
The component maintains a pool of worker threads and uses them to fire events; please refer to the Threading and Concurrency topic for more information.
The ResultCode parameter will always be 0 when the event is fired. If the event cannot be handled in a "successful" manner for some reason (e.g., a resource is not available or security checks failed), set it to a nonzero value to report an appropriate error. Please see the Error Handling topic for more information.
This event is fired synchronously; please refer to the Event Types topic for more information.
WorkerThreadTermination Event (CBProcess Component)
Fires just before a worker thread is terminated.
Syntax
type TWorkerThreadTerminationEvent = procedure ( Sender: TObject ) of Object;
property OnWorkerThreadTermination: TWorkerThreadTerminationEvent read FOnWorkerThreadTermination write FOnWorkerThreadTermination;
Remarks
This event fires just before a worker thread is terminated, in the context of that worker thread.
This event is optional; it is provided to give applications a chance to perform additional processing before a worker thread is terminated, such as deallocating per-thread objects.
The component maintains a pool of worker threads and uses them to fire events; please refer to the Threading and Concurrency topic for more information.
Any errors that occur during this event are ignored.
This event is fired synchronously; please refer to the Event Types topic for more information.
RunningProcess Type
The type represents a running process.
Remarks
This type represents a process that is running in the system. The process list is taken from the running CBProcess driver.
Fields
CommandLine
String (read-only)
Default Value: ""
This property reflects the command-line arguments of the process.
This property reflects the command-line arguments, with which the process has been started.
By default, the driver does not store command-line arguments and this property is empty. To enable collection and retrieval of the command-line arguments, set the TrackCommandLine property to True.
ProcessId
Integer (read-only)
Default Value: 0
This property reflects the process Id (PID).
This property reflects the Id of the running process (i.e., the PID).
ProcessName
String (read-only)
Default Value: ""
This property reflects the name of the process.
This property reflects the name of the running process.
Config Settings (CBProcess Component)
The component accepts one or more of the following configuration settings. Configuration settings are similar in functionality to properties, but they are rarely used. In order to avoid "polluting" the property namespace of the component, access to these internal properties is provided through the Config method.CBProcess Config Settings
Normally, this setting should remain disabled (especially in production) to reduce the possibility of system deadlocks occurring. Certain situations, however, do require it to be enabled, such as for testing purposes (so that event handlers can be tested with single-process tests).
This setting's value is stored in the registry and is persistent; it requires administrative rights to be changed.
By default, this setting is set to 0, and the driver automatically chooses an optimal number of threads using this equation: 4 * number_of_processors.
By default, this setting is set to 0, and the driver automatically chooses an optimal number of threads using this equation: max(number_of_processors, 4). If this setting's value exceeds the MaxWorkerThreadCount value, the latter is used instead.
By default, this setting is set to 0, and the driver uses a default stack size (currently, 1 MB).
Note: This setting cannot be changed when Active is True, and it cannot be changed within events.
Base Config Settings
- Product: The product the license is for.
- Product Key: The key the license was generated from.
- License Source: Where the license was found (e.g., RuntimeLicense, License File).
- License Type: The type of license installed (e.g., Royalty Free, Single Server).
Trappable Errors (CBProcess Component)
The component uses Windows error codes during operation as necessary. Please refer to the Error Handling topic for more information.Special Use Errors
21 | ERROR_NOT_READY: Reported by the methods of the component if Initialize has not been called or did not succeed. |
191 | ERROR_INVALID_EXE_SIGNATURE: Reported by the Install method when the CAB file signature cannot be validated. |
575 | ERROR_APP_INIT_FAILURE: Reported by the methods of the component if Initialize has not been called or did not succeed. Differs from ERROR_NOT_READY (21) in that it indicates a specific situation in the internal code. |
588 | ERROR_FS_DRIVER_REQUIRED: Reported if the required system module was not correctly installed for the given ProductGUID. |
614 | ERROR_NO_CALLBACK_ACTIVE: Reported by any method that can only be called within event handlers if it is called outside an event handler. |
1292 | ERROR_IMPLEMENTATION_LIMIT: Reported when the timeout value provided is less than 3 seconds. |
1314 | ERROR_PRIVILEGE_NOT_HELD: Reported by any method that requires elevated permissions if it is called without such permissions. |