Can local AVs interrupt ongoing scans?

Yes, local AV’s may interrupt ongoing scans.

Since MetaDefender Core does not include a real-time AV protection engine, many users may opt to run one or more additional real-time AV agents alongside MetaDefender Core.

Often, these anti-malware agents may already be installed on the system before the MetaDefender Core is deployed.

To implement your exception rule, you must exclude the following from the relevant anti-malware product’s real-time protection:

• Exclude full installation path of MetaDefender Core.
• Exclude the temporary upload path used by MetaDefender Core.
• Exclude specific processes:
  • On Windows: “engineprocess.exe”, “engineprocess32.exe”, “ometascan.exe”, “postgres.exe” and “nginx.exe” processes.
  • On Linux: “engineprocess”, “ometascan”, “postgres” and “nginx” processes.

If you do not add this exception or if you do not disable real-time protection, MetaDefender Core files may be blocked, results returned by MetaDefender Core scanning will not be consistent, and the return value of the scans would be one of the following:

• Clean: If your existing anti-malware product was able to clean the threat
• Failed (or other errors): If your existing anti-malware product removed the file before MetaDefender Core could scan it.