Why Does Adaptive Sandbox Return “No Specific Configuration”?
This article applies to all MetaDefender Core releases deployed on Windows and Linux systems.
The message “No specific configuration” appears when none of the configured workflow conditions match the scan result of the file being analyzed. As a result, the sandbox does not execute.
To ensure Adaptive Sandbox operates as intended, all relevant scan result types must be explicitly selected in the workflow settings.
How to Resolve
Follow these steps to review and update the workflow configuration:
Navigate to Workflow Management → Workflows → Adaptive Sandbox.
Locate the section Engine result(s) filtering.
Under Enable for AV scan result(s), verify that all necessary scan result types are selected.
- For example, if Metascan returns "No threat found" during file analysis, make sure "No threat found" is selected. If it is not, the sandbox will not be triggered for clean files, and the “No specific configuration” message will appear.
- Save the configuration after making the necessary selections.
If Further Assistance is required, please proceed to log a support case or chatting with our support engineer.