Trend Micro Apex One™ as a Service
English - Windows - 32-bit / 64-bit
Hotfix - Build 202504
1. Hotfix Release Information
Resolved Known Issues
Trend Micro Apex Central™ as a Service
This Hotfix resolves the following issue(s):
Adding file SHA-256 suspicious objects in Trend Vision One may prevent Trend Micro Apex One as a Service from upgrading to Standard Endpoint Protection.
Solution
This Hotfix resolves the issue.
The system may not send notification email for policy owner update to the policy owner in Standard Endpoint Protection.
Solution
This Hotfix resolves the issue.
The system may not display the updated Trend Micro Apex One group name in the Apex Central Product Status view.
Solution
This Hotfix resolves the issue.
An issue may prevent Trend Micro Apex Central from deploying components to integrated Trend Micro products.
Solution
This Hotfix resolves the issue.
Trend Micro Apex One™ as a Service
This Hotfix resolves the following issue(s):
An issue related to Application Control criteria processing may result in high CPU usage affecting system performance on Security Agent endpoints.
Solution
This Hotfix updates the Application Control component to resolve the issue.
Data Loss Prevention (DLP) may not function properly for 7-Zip compressed files.
Solution
This Hotfix updates the Trend Micro Apex One Security Agent program to resolve the issue.
After updating the Trend Micro Apex One Security Agent program, the system may display the Security Agent console unexpectedly on endpoints.
Solution
This Hotfix updates the Trend Micro Apex One Security Agent program to resolve the issue.
When updating the Suspicious Object (SO) lists in the Trend Micro Apex One Security Agent, the Apex One NT Listener service ("TmListen.exe") may consume high CPU resource affecting system performance on Security Agent endpoints.
Solution
This Hotfix updates the Trend Micro Apex One Security Agent program to resolve the issue.
An issue related to virus/malware file path processing may cause the system to display spaces in detection file path as ASCII codes for the associated detection logs on the Log Query screen.
Solution
This Hotfix updates the Trend Micro Apex One Security Agent program to resolve the issue.
An issue related to the Trend Micro Apex One web console may prevent users from viewing the predefined port lists in Firewall Policy Rules.
Solution
This Hotfix updates the Trend Micro Apex One server program to resolve the issue.
Trend Micro Apex One™ (Mac) as a Service
There are no issues for this Hotfix release.
Enhancements
Trend Micro Apex Central™ as a Service
The following enhancements are included in this Hotfix:
This Hotfix updates the feature description on the Endpoint Sensor policy settings screen to enhance user experience.
This Hotfix adds application version information in Application Control detection logs for methods matched in the Application Reputation List.
Trend Micro Apex One™ as a Service
The following enhancements are included in this Hotfix:
This Hotfix enhances the self-protection capability for the Security Agent program folder to improve product security.
This Hotfix enhances the Predictive Machine Learning module for suspicious Anti-malware Scan Interface (AMSI) event detections.
This Hotfix updates the Apex One Security Agent program to enhance the blue screen of death (BSOD) Loop Prevention monitoring mechanism.
This Hotfix updates the Behavior Monitoring Core Service module to version 2.98.2101 and Behavior Monitoring Core Drive module to version 2.98.2100 to enhance the Security Agent self-protection capabilities.
Trend Micro Apex One™ (Mac) as a Service
The following enhancements are included in this Hotfix:
This Hotfix enables Trend Micro Apex One (Mac) to send real-time scan status to Trend Micro Apex Central.
This Hotfix updates the iCore module in Trend Micro Apex One (Mac) Security Agent to support the millisecond format in detection logs.
Additional Information
Trend Micro Apex Central™ as a Service
No additional information available.Trend Micro Apex One™ as a Service
Security Agent version: 14.0.14488
Security Agent restart: Yes
Security Agent OS reboot: Not required for Security Agents are running build versions later than 10000.
Estimated size of network traffic (in terms of bandwidth) required for deployment:
- 32-bit Security Agent Hotfix = 425 MB
- 64-bit Security Agent Hotfix = 510 MB
Trend Micro Apex One™ (Mac) as a Service
Security Agent Version: 3.5.7996
Security Agent Restart Requirement: Not required
Estimated size of network traffic (in terms of bandwidth) required for deployment:
64-bit Security Agent Hotfix = 262MB
Additional Requirements: Enable web browser extension (https://success.trendmicro.com/solution/000273346)
2. Documentation Set
-
The document set includes:
- Trend Micro Apex One™ as a Service documents
- Readme: Contains a list of known issues and may also contain late-breaking product information not found in the Online Help or printed documentation.
- Knowledge Base: An online database of problem-solving and troubleshooting information. It provides the latest information about known product issues. To access the Knowledge Base, go to the following website: http://esupport.trendmicro.com
- Trend Micro Apex Central™ as a Service documents
- Administrator's Guide: A PDF document that provides detailed instructions for how to configure and manage the Trend Micro Apex Central™ as a Service console and features.
- Data Protection Lists (Chapter 1 only): A PDF document that lists predefined data identifiers and templates for Data Loss Prevention.
- Widget and Policy Management Guide: Explains how to configure Dashboard widgets and Policy Management widgets on the Trend Micro Apex Central™ as a Service console.
- Automation Center: Online user guides and references that explain how to use the Apex Central Automation APIs: https://automation.trendmicro.com/apex-central/home
- Online Help: Provides "how to's", usage advice, and field-specific information. The Help is also accessible from the Trend Micro Apex Central™ as a Service console.
- Trend Micro Apex One™ server documents
- Administrator's Guide: A PDF document that discusses getting started information and Trend Micro Apex One™ server administration.
- Online Help: Provides "how to's", usage advice, and field-specific information. The Help is accessible from the Trend Micro Apex One™ server, agent, and Policy Server consoles, and from the OfficeScan Master Setup.
- Trend Micro Apex One™ (Mac) server documents
- Administrator's Guide: A PDF document that discusses getting started information and Trend Micro Apex One™ (Mac) server administration.
- Online Help: Provides "how to's", usage advice, and field-specific information for Trend Micro. The Help is also accessible from the Trend Micro Apex One™ as a Service console.
- Security Agent documents
- Trend Micro Apex One™ Security Agent Online Help: Discusses getting started information, Trend Micro Apex One™ Security Agent installation procedures, and Trend Micro Apex One™ Security Agent management.
- Trend Micro Apex One™ Security Agent Readme: Contains a list of known issues and may also contain late-breaking product information not found in the Online Help or printed documentation.
- Trend Micro Apex One™ (Mac) Security Agent Online Help: Discusses getting started information, Trend Micro Apex One™ (Mac) Security Agent installation procedures, and Trend Micro Apex One™ (Mac) Security Agent management.
Download the latest versions of the PDF documents and readme at our online documentation.
3. Post-installation Configuration
No post-installation steps are required.
NOTE: Trend Micro recommends that you update your scan engine and virus pattern files immediately after installing the product.
4. Known Issues
Trend Micro Apex Central™ as a Service
There are no known issues for this Hotfix release.
Trend Micro Apex One™ as a Service
Known issues in this release:
Security Agent consoles running build 13.95 display an incorrect policy name. To resolve this issue, upgrade the Security Agent to 14.0. After the Security Agent contacts the server, the policy name displays correctly.
Off-premises and Security Agents in Independent mode cannot update the Certified Safe Software Pattern from external update sources.
Coexist mode Security Agents on endpoints with Windows Defender may experience installation issues or be unable to upload data to the Apex One server due to a file locking issue. To resolve this issue, add Endpoint Sensor (ESEServiceShell.exe and ESClient.exe) in the exclusions list of Windows Defender to prevent the locking issue.
After copying a file to a remote server using a relative path as the source, Apex One is unable to translate the relative path into the full system directory.
The quality of RCA analysis chain image files is reduced when viewing the files using Windows 10 Photo Viewer.
When attempting to start a Historical Investigation from the Attack Discovery Detections widget that includes Registry value name or Registry value data criteria, the Historical Investigation displays an error message if the length of the Registry value name exceeds 260 characters or the Registry value data exceeds 64 characters.
After updating the Attack Discovery Pattern file (tmesadp.ptn) on Security Agents, a database schema error may occur that causes the Endpoint Sensor feature to continuously report the same detections to the server during each synchronization. This causes duplicate records to display on the Apex Central server.
Root Cause Analysis email attachment results may also include temporary files created when the user saved the file.
The number of matched endpoints that display on a Root Cause Analysis chain may appear to be greater than the total if the Security Agent on an endpoint was uninstalled or no longer reports to the same managing server.
The Endpoint Sensor service may have high memory usage.
The Endpoint Sensor may have high peak CPU usage occasionally.
Endpoint Sensor has CPU peak during Windows Update phase.
The user or account name in ADE detection may be empty.
The EC module may stop responding while handling NULL data which may cause the ESEService and ADE functionality to behave abnormally.
In rare conditions, ESEService stops responding while unloading.
A time zone issue may cause the system to display different log generation time information in the web console. In the web console, the system displays the log generation time in the time zone of the Apex One server.
- The Apex One server stores the log generation time information in GMT+0.
- The Security Agent sends the log generation time information (GMT+0 or local time) to the Apex One server.
Trend Micro Apex One™ (Mac) as a Service
Known issues in this release:
After enabling the Scan Time Machine option for Manual Scan and Scheduled Scan, Apex One (Mac) cannot perform any actions (clean, quarantine, or delete) on detected malware threats due to a permission limitation in Mac OS. Configured scan actions are displayed as unsuccessful in the product logs.
When performing a historical investigation on Apex One (Mac) endpoints, the system replaces a slash (/) with a colon (:) in file names, preventing users from searching for file names that contain backslashes in investigation results.
To resolve this issue, use a colon (:) to search for the files.
5. Contact Information
Contact Trend Micro via fax, phone, and email, or visit our website to download evaluation copies of Trend Micro products.
https://www.trendmicro.com/en_us/contact.html
NOTE: This information is subject to change without notice.
6. About Trend Micro
As a global leader in IT security, Trend Micro develops innovative security solutions that make the world safe for businesses and consumers to exchange digital information.
Copyright 2025, Trend Micro Incorporated. All rights reserved.
Trend Micro, Trend Micro Apex Central, Trend Micro Apex One, Trend Micro Apex One (Mac) and the t-ball logo are trademarks of Trend Micro Incorporated and are registered in some jurisdictions. All other marks are the trademarks or registered trademarks of their respective companies.
7. License Agreement
Third-party licensing agreements can be viewed:
- By selecting the "About" option in the application user interface
- By referring to the "Legal" page of the Administrator's Guide