General and Known Issues - Metadefender Core

Metadefender Core 1, 4, and 8 come with a trial license good for 15 days after fresh installation (reinstalling does not reset trial). Metadefender Core 12, 16, and 20 do not come with a trial license. To obtain a trial license, please contact OPSWAT sales (sales@opswat.com).

  • Metadefender Core 1, 4, and 8 come with a trial license good for 15 days after fresh installation (reinstalling does not reset trial).

  • Metadefender Core 12, 16, and 20 do not come with a trial license. To obtain a trial license, please contact OPSWAT sales (sales@opswat.com).

  • Metadefender Core should be restarted whenever a new license has been applied.

  • Metadefender Core was previously called Metascan.

  • Metadefender Core categorizes files as 'blocked' or 'allowed' based on the process results. Please refer to Callback for Processing a File (COM) for details.

  • Metadefender Core embedded engines should not be installed on a system which has an alternate product provided by the same vendor, for example, installation of the Norman Scan Engine with Norman Security Suite. This configuration is not supported by Metadefender Core.

  • Metadefender Core license allows up to 10 Remote Desktop (RDP) sessions to a server running Metadefender Core . Please contact OPSWAT support if you need more than ten connections via RDP.

  • Scanning boot sector is only supported by the Total Defense/Quick Heal scan engine. Other engines will fail to scan for boot sector scan request.

  • REST Web Service installation may fail to install if UAC (User Access Control) is enabled. Turn off UAC and run the installation with Administrator privileges.

  • If logging all scan history is enabled, the Metadefender Core Management console dashboard may cause high load on mongoDB.

  • ICAP server does not block traffic if server is overloaded by default.

  • Metadefender Core does not support installation to directory paths that include non-ASCII characters.

  • Metadefender Core must have archive handling enabled in order to correctly scan GZIP content through the ICAP interface.

  • When Metadefender Core is configured to use a local instance of MongoDB (the default configuration) the HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\OPSWAT\Metascan\db_instance (or HKEY_LOCAL_MACHINE\SOFTWARE\OPSWAT\Metascan\db_instance for 32 bit systems) key must be set to 'localhost' or '127.0.0.1'. The local system cannot be referred to by IP address.

  • Metadefender Core does not support installation on systems where the TEMP environment variable contains more than one path.

  • In Metadefender Core 20 packages, the Sophos engine must have its definitions updated before scans can successfully complete.

  • Archives scanned through the COM interface do not have their scan results logged.

  • The setting "Maximum File Size for files scanned through the web interface" found on the Configuration->Scan Configuration page in the Metadefender Core Management Console cannot currently be imported or exported through the Backup/Restore feature.

  • Disabling the 'support_custom_engine' property will disable all engines in Metadefender Core.

  • Threats found within archives will not be removed even if Metadefender Core is configured to delete or quarantine files that contain threats.

  • Stopping the Metadefender Core service may not stop all engine handlers (omsAMEHandler.exe and omsCEHandler.exe processes) if there are engine updates in progress. Engine handlers will terminate after the update has completed or they can be terminated manually.

  • The retention policy does not clean up quarantined files when the REST server is configured to use HTTPs.

The following are applicable only if the Metadefender Mail functionality is being used:

  • Metadefender Email agent will be installed as part of Metadefender Core. Before installing Metadefender Core, please uninstall mail agent before installing Metadefender Core.

  • A separate SMTP server is required for notification.

  • Exchange (malware agent configuration) may block release from quarantine.

  • Email sanitization to HTML may be blocked and attachment may be replaced with text "This attachment was removed because it contains data that could pose a security risk."

  • An attachment that has been sanitized may be larger than the original attachment. As a result, it may be necessary to increase the maximum attachment size setting on your mail server

ncG1vNJzZmirY2Ourq3ZqKWar6NjsLC5jqabZq2jmr9us9Sim55npmh8dICWcGxqZpipuq0%3D

 Share!