Supported Trend Micro Products/Versions
The following section lists all Trend Micro products/versions that are considered current and are fully supported by Trend Micro, along with milestone dates (End-of-Sale and End-of-Life) that have been formally announced.Please refer to Trend Micro’s latest End-of-Life Policy for more information on milestone definitions and standard timelines. You can also view the products/versions that have reached End-of-Life in the past 12 months here.
End-of-Life Trend Micro Products/Versions
The following section lists all Trend Micro products and versions that have reached End-of-Life (EOL) status (formerly End-of-Support or EOS) in the last twelve (12) months and are no longer actively supported by Trend Micro. If the product/version you are looking for is not listed below, it is either still supported or is an older version that has been End-of-Life for more than 12 months.Please refer to Trend Micro’s latest End-of-Life Policy for more information on milestone definitions and standard timelines.
Behavior Monitoring Detection Pattern Shows as 0.000.0 in Trend Micro Apex One™
Trend Micro has received reports of Apex One Security Agents showing Behavior Monitoring Detection Pattern version: 0.000.0 after applying Patch 4.
Trend Micro Apex One™ Service Pack 1 - Patch 4 (Build 13984) is now available
Trend Micro has released Apex One Service Pack 1 - Patch 4 (Build 13984). This patch contains accumulated fixes and enhancements.
2025 Release Schedule for Trend Micro Apex One™ and Trend Micro Apex Central™
This article provides information on Year 2025 release schedule for Trend Micro Apex One and Trend Micro Apex Central On-premise.
Trend Micro Endpoint Compatibility Issues with Microsoft Update KB5052093
Trend Micro has received reports of compatibility issue between Trend Micro Endpoint solutions and Windows 11 Microsoft Update (KB5052093). Affected endpoints would show “Bad image” popup errors: Dism.exe - Bad ImageC:\WINDOWS\system32\tmumh\20019\AddOn\8.55.0.1333\TmUmEvt64.dll is either not designed to run on Windows or it contains an error. Try installing the program again using the original installation media or contact your system administrator or the software vendor for support. Error status 0xc0000428. Dism.exe - Bad ImageC:\WINDOWS\system32\tmumh\20019\TmMon\2.9.0.1205\tmmon64.dll is either not designed to run on Windows or it contains an error. Try installing the program again using the original installation media or contact your system administrator or the software vendor for support. Error status 0xc0000428.
Locating the folder path of the Trend Micro Apex One™ (Mac) agent after deployment
Learn the Apex One (Mac) agent folder path after deployment.
Trend Micro Apex One™ error "Smart Scan is not Available"
Trend Micro has identified a compatibility issue between Apex One Integrated Smart Protection Server and "Microsoft Windows 2025-01 Cumulative Update" for Windows 2016 & Windows 2019 server.Trend Micro Apex One Integrated Smart Scan Server may show “Update unsuccessful” error. Security agents may also report message, “Smart Scan is not Available.”
Deploying policies from Trend Micro Apex Central™ is stuck at "Pending: Waiting for product agent" status because the IIS Server is handling too many requests
When policies are deployed from Apex Central to Apex One, all agents show the "Waiting for product agent" status.Root Cause AnalysisHTTP Error 503 can be seen in the following logs: From Apex One ofcdebug.log located at ...\Trend Micro\Apex One\PCCSRV\Log\: These logs correspond to Apex One Vulnerability Protection issue: 2020 02/27 12:20:14 [0a04 : 21f8] (00) (I) [][ofcservice.exe]BoostHTTPContext::prepareContext - prepare context scheme=[https], host=[DMZTMAO01.interdomain.com], port=[4343], target=[/officescan_ivp/command/osf/OnQuery] - [libosfsvcclienthttpcontext.cpp(228)] 2020 02/27 12:20:14 [0a04 : 21f8] (00) (E) [][ofcservice.exe]BoostHTTPClient::receive - http response code=503 - [libosfsvcclienthttpclient.cpp(101)] These logs correspond to Apex One Application Control issue: 2020 02/27 12:21:14 [0a04 : 22f0] (00) (I) [][ofcservice.exe]BoostHTTPContext::prepareContext - prepare context scheme=[https], host=[192.168.25.113], port=[4343], target=[/officescan_iac/osf/ONQUERY] - [libosfsvcclienthttpcontext.cpp(228)] 2020 02/27 12:21:14 [0a04 : 22f0] (00) (E) [][ofcservice.exe]BoostHTTPClient::receive - http response code=503 - [libosfsvcclienthttpclient.cpp(101)] From diagnostic.log of Apex Central located under ...\Control Manager\WebUI\WebApp\widget\repository\log\Diagnostic.log Apex One Vulnerability Protection error: 2020-02-27 12:21:00,208,DEBUG,null,null,[modOSCE IVPProxy][send_policy]URL = https://dmztmao01.interdomain.com:4343/officescan_ivp/command 2020-02-27 12:21:00,208,DEBUG,null,null,[modOSCE IVPProxy][send_policy] HTTP failed, HTTP status code: [503]. Apex One Application Control error: 2020-02-27 12:21:00,208,DEBUG,null,null,[modOSCE IACProxy][send_policy_to_osce_server]In2020-02-27 12:21:00,208,ERROR,null,null,[modOSCE IACProxy][send_data]HTTP failed, HTTP status code: [503]. The HTTP 503 error may occur if there are too many requests being handled by the IIS server, causing the request limit to be exceeded.
"ActiveUpdate self integrity check fail" error appears due to pattern update failure in Trend Micro Apex One™
On the ..\AU_Data\AU_Log\TmuDump.txt, you see the following error message:"UpdateManager endwith 69 (450000): ActiveUpdate self integrity check fail." The "ActiveUpdate self integrity check fail" error usually appears when necessary certificates are missing. As a result, the updates cannot be validated and will fail.For endpoints that do not have the required certificates in their trusted certificate stores, the following issues may occur: The agents remain in an "Updating" state and do not receive their pattern updates. The server cannot verify the computer's digital signatures during Inter-Process Communication (IPC). The installation of the Data Protection Module may fail
