In DDI 3.2, you were able to import the sandbox image in vmdk format because DDI 3.2 supports sandbox image in vmdk format but when you upgraded DDI 3.2 to DDI 3.5, the usandbox module update failed because DDI 3.5 does not support sandbox image in vmdk format.
In this scenario, because you have disabled the sandbox feature, you did not notice that the upgrade has failed in the DDI 3.2 to DDI 3.5 upgrade. Disabling the sandbox feature hides the result of the upgrade.
After upgrading DDI 3.5 to DDI 3.6, DDI verifies the Virus Scan API (VSAPI) patterns using usandbox commands. This capability is a new feature in DDI 3.6. Since your usandbox module was not successfully updated after upgrading from DDI 3.2 to DDI 3.5, DDI cannot verify and update the VSAPI patterns.
To resolve this issue, choose one of the following scenarios:
- If you have a backup of the original DDI 3.2 installation before the upgrade:
- Restore the backup of the original DDI 3.2 installation.
- Create and customize the sandbox image using Virtualbox and then import the image.
- Upgrade to DDI 3.5 and then to DDI 3.6.
- If you don't have a backup, you need to do a fresh installation of DDI 3.6 and then import the configuration from the old one but the old logs will be lost.
- If you don't want to do a fresh installation, contact Trend Micro Technical Support.