Are there any limitations to the MetaDefender Core scan engines?

This article applies to all MetaDefender Core V4 and V5 releases deployed on Windows and Linux systems.

Yes.

Certain custom engines have limitations in terms of OS compatibility, maximum file size allowed for scanning, and supported file types.

The latest list of limitations is outlined below.

File Size and OS Limitation

Engine NameFile Size LimitationOS Limitations
Antiy900 MB
Emsisoft4 GB
QuickHeal2 GB
RocketCyber LinuxDoes not function on Redhat and CentOS versions earlier than 8.x.
CylanceDoes not function on Redhat and CentOS versions earlier than 8.x.
Nano AVDoes not function on Amazon Linux 2023
SentinelOne4 GB

Minimum System Resource Requirements

Engine Name

Minimum System Resource Requirements

__

OS
ClamAV2GB + memoryWindows and Linux
IKARUS1GB shared memory in dockerLinux

ClamAV do not work on Redhat 8,9 if FIPS is enabled

For IKARUS, --shm-size=1gb should be added when starting the docker.

If you're using K8s, the section below should be specified in the yaml file

AhnLab’s engine is built several times a day. The main daily build is done at 6 PM Korea Standard Time (KST) the day before its version date. Because of this, the DB update may sometimes show the next day’s date — this is normal and follows the vendor’s process

YAML
Copy

Supported File type for AI engines engines can be founded here

Additional Installed Services

Engine NameInstalled Applications
NETGATESpy Emergency (an icon will display on desktop)
Engine NameScan result
BitdefenderPassword-protected file's result will be returned "Not Scanned" for this engine.

This list is accurate for the latest packages of custom engines.

If you need help navigating MetaDefender scan engine limitations, please follow these instructions on How to Create Support Package With Bundle Tools?, before creating a support case or chatting with our support engineer.

Type to search, ESC to discard
Type to search, ESC to discard
Type to search, ESC to discard