This filter is used to decide which files to extract from the scan file for processing and/or displaying by the recognition engine.

This filter determines which of the files that are passed through the load filter are also sent to the recognition engine for processing. Sending too many files will make it slightly slower, however, passing less files through the recognition engine will possibly result in inferior recognition.

This filter is different to the load filter in that a load filter might load .exe, .com and .dll files, but a recognition filter might be limited to .exe and .com. This means that .dlls are loaded but not recognized. This can be useful (depending on the Scanner configuration) since the .dll files will still give version information without being recognized.

This filter is based on the recognition status. Recognition status can be:

Main

Main files identify the application. An application can have multiple main files, but normally there is only one. If a Main file is found, the application is considered present.

Associated

Associated files are part of an application but not the main file.

3rd party

Files such as some DLL files that are technically used by the application, but are also distributed freely and can be used by other applications.

CheckVer file

CheckVer files are files that are found in the Recognition library, but do not match any of the known versions of an application. This usually indicates that it is a newer version. If this is the case, it might be a good idea to obtain an updated Recognition Library from .

Unidentified file

These files cannot be identified.

Unprocessed file

These files have not been processed by the recognition engine. For example, they are passed to the load filter, but not to the recognition filter.

Junk files

These files have been identified as junk files as set up in the Recognition tab page Advanced options.

Auto-identified file

These files are known to be a device driver file and were not recognized by the application library. Files used as Device Drivers represent a large portion of the files that are not identified by the Application Library. Being able to identify these automatically can significantly reduce the effort required to achieve good recognition rates.

When performing analysis or recognition, it can be beneficial to allow everything to pass through the display filter (apart from files you have designated as junk). This effectively causes the Analysis Workbench to store and display information about all files, irrespective of their recognition status. In this state, the file data that is needed to teach more applications is available.