Third-party antivirus software (e.g., McAfee, Symantec) or Trend Micro OfficeScan/Apex One installed on the same machine prevents DSA's Anti-Malware driver from being installed.
Reinstall the latest verified version of the DSA and activate it. Phase 3: Resolving the Issue on Linux Environments
A simple reboot resolves a significant percentage of driver offline issues, especially after an agent upgrade. Open the Windows Registry Editor ( regedit ).
If you have exhausted all steps, gather the following items and contact Trend Micro Technical Support for further assistance:
Network drops or unexpected system halts during installation corrupted the agent's internal configuration state. Third-party antivirus software (e
The ds_agent is the main engine, while Amsp represents the Trend Micro Anti-Malware Solution Platform. Both must report a RUNNING status. sudo systemctl status ds_agent Use code with caution. Step 2: Query the Specific Anti-Malware Kernel Drivers
or temporarily disable Secure Boot to confirm it is the cause of the offline status. www.trendmicro.com 3. Clean Reinstallation
If on a test machine, reboot and press → Disable Driver Signature Enforcement . If the driver loads, you need to sign it properly or update Deep Security Agent.
Remove the package using your distribution's package manager: : rpm -e ds_agent DEB-based : dpkg -r ds_agent Verify that the agent directories are cleared: rm -rf /opt/ds_agent/ rm -rf /var/opt/ds_agent/ Open the Windows Registry Editor ( regedit )
& "C:\Program Files\Trend Micro\Deep Security Agent\dsa_control" -m Linux: /opt/ds_agent/dsa_control -m
Install the package and run the activation script provided by your DSM console. Long-Term Prevention Strategies
Look for "Required key not available" or "Signature successfully verified" errors.
Before pushing major agent upgrades to production, test them on a staging environment to ensure driver compatibility. Conclusion Both must report a RUNNING status
If Secure Boot is enabled, the Linux kernel may reject the Trend Micro driver modules because they are not signed by the hardware vendor's trusted keys.
/opt/ds_agent/dsa_control -r followed by /opt/ds_agent/dsa_control -a dsm://[DSM_IP_or_Hostname]:4118/ Send Policy from DSM Log into your Deep Security Manager console. Go to Computers and locate the affected machine.
If Secure Boot is required by policy but blocking the driver, you must either disable it in the BIOS or sign the kernel module (advanced procedure). For most environments, disabling Secure Boot in the system BIOS is the standard fix for "Not Installed" driver issues on fresh deployments.
Reboot the machine to flush cached kernel drivers completely.