Other antivirus products (e.g., OfficeScan, Apex One, or third-party AVs) can conflict with the Deep Security driver installation. Kernel Incompatibility (Linux):
: Ensure the server has the latest Microsoft root certificate updates. In some cases, conflicting third-party certificates (like Comodo) must be cleared and reinstalled to allow the Trend Micro drivers to initialize properly. 3. Secure Boot and Kernel Compatibility (Linux)
Open an elevated Command Prompt and check if the Trend Micro filter drivers are actively attached to your storage volumes: fltmc filters Use code with caution.
: The operating system kernel was updated to a version that the current Deep Security Agent version does not yet support. Other antivirus products (e
sc query AMSP sc query tmcomm sc query tmactmon sc query tmevtmgr Use code with caution. Services should report STATE: 4 RUNNING .
Even offline, the agent must be paired with DSM (using IP/hostname on same LAN) to activate the anti-malware feature. The DSM can push the final driver registration if the agent has the binaries.
Understanding why this error happens helps narrow down the correct troubleshooting path. The most common causes include: sc query AMSP sc query tmcomm sc query
Delete any leftover directories in C:\Program Files\Trend Micro\Deep Security Agent\ .
This public link is valid for 7 days and shares a thread, including any personal information you added. This link or copies made by others cannot be deleted. If you share with third parties, their policies apply. Can’t copy the link right now. Try again later. Prevent Ransomware using Trend Micro products and solutions
Trend Micro builds drivers for specific Linux kernel versions. If the Linux security team patched the kernel recently, the existing Deep Security driver may fail to load. Check your current kernel: uname -r Use code with caution. Go to Anti-Malware > General .
Common root causes observed
Verify whether the driver successfully loaded into the kernel stack: lsmod | grep tbk Use code with caution.
The Windows OS lacks the CA certificates required to verify the Anti-malware driver's digital signature. Third-Party Conflicts:
If Secure Boot is enabled, you must enroll the Trend Micro Public Key into your system’s Machine Owner Key (MOK) facility: mokutil --import /opt/ds_agent/mok.pub Use code with caution.
Navigate to and double-click the affected machine. Go to Anti-Malware > General .