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 Name | File Size Limitation | OS Limitations |
|---|---|---|
| Antiy | 900 MB | |
| Emsisoft | 4 GB | |
| QuickHeal | 2 GB | |
| RocketCyber Linux | Does not function on Redhat and CentOS versions earlier than 8.x. | |
| Cylance | Does not function on Redhat and CentOS versions earlier than 8.x. |
Minimum System Resource Requirements
| Engine Name | Minimum System Resource Requirements __ | OS |
|---|---|---|
| ClamAV | 2GB + memory | Windows and Linux |
| IKARUS | 1GB shared memory in docker | Linux |
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
spec volumesnamedshm emptyDir mediumMemory containersvolumeMountsmountPath/dev/shm namedshmSupported File type for AI engines engines can be founded here
Additional Installed Services
| Engine Name | Installed Applications |
|---|---|
| NETGATE | Spy Emergency (an icon will display on desktop) |
| Engine Name | Scan result |
|---|---|
| Bitdefender | Password-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 a Support Package, before creating a support case or chatting with our support engineer.