What can I do if MetaDefender shows a high number of files that failed to scan?

Under normal circumstances, all active engines scan every file.

However, there are some situations in which scanning might be impacted and a “failed to scan” result is observed. In such situations, the behavior may be caused by a number of factors:

• Some engines failed to scan, and exceeded the scan failure threshold settings in place on the Core side.
• Core itself has a fatal problem e.g. Core service crashed.
• Due to configurations:
  • Failed the scan when sanitization timeout or failed.
  • Failed the scan when archive extraction failed.

Metadefender Core V5 Releases

To disable this option on V5, follow these steps:

1. In your web browser, navigate to the MetaDefender Core Management Console at http://localhost:8008/ (you may need to log in under admin privilege)
2. On the left menu, navigate to Workflow Management → Workflow to list all available rules
3. Click on a workflow you are using for the current scan to modify the setting
4. Click on the Metascan tab

Uncheck the option Scan Failure Threshold shown below.