This Hotfix resolves the following issue(s):
Wrong product name displayed in user-defined suspicious objects page.
Solution
The Hotfix resolves the issue.
This Hotfix resolves the following issue(s):
The notification of firewall policy violation does not behave according to the policy rule settings.
Solution
This Hotfix enhances logging mechanism to resolve the issue.
Apex One agent is unable to start Data Loss Prevention (DLP) service due to version comparison issue.
Solution
This Hotfix enhances version comparison methodology to resolve this issue.
Malicious IP is not being blocked by user defined suspicious object (UDSO).
Solution
This Hotfix updates the NCIE module to version 3.7.1021 to resolve the issue.
Manual scan ends with the displayed message “Stopped by Apex One” without any user interaction.
Solution
This Hotfix enhances manual scan tracking flow to resolve the issue.
There are no issues for this Hotfix release.
There are no enhancements for this Hotfix release.
The following enhancements are included in this Hotfix:
This Hotfix updates the Virus Scan Engine (VSAPI) to version 25.560.1005 to deliver proactive and advance solutions to address challenging real-world threats.
This Hotfix updates the Damage Cleanup Engine (DCE) to version 7.5.1217 to enhance process chain cleanup capability and provides more details for cleanup information.
This Hotfix updates the TmEyes module to version 8.55.1403 and AMSP module 6.6.1216 to enhance ransomware detection capability.
This Hotfix includes a new module Net Filter 1.0.456 to enhance web browser detection capability.
This Hotfix updates the Data Loss Prevention (DLP) to version 6.2.6098 to enhance print check logic and support Windows 11 25H2.
This Hotfix enhances the log upload mechanism to reduce network payload for Data Loss Prevention, Device Access Control, Behavior Monitoring, and Predictive Machine Learning logs.
This Hotfix enhances the quarantined file verification to prevent incorrect operations.
This Hotfix updates the Trend Micro Apex One Security Agent program to protect against a potential resource loading security issue.
The following enhancements are included in this Hotfix:
This Hotfix supports Trend Micro Apex One (Mac) Security Agent installation on endpoints running macOS 26 (Tahoe).
This Hotfix removes support for macOS 11 (Big Sur) for Trend Micro Apex One (Mac) after November 2025.
This Hotfix updates multiple third-party libraries in Trend Micro Apex One (Mac) Security Agent to enhance product security.
Version:
Security Agent version: 14.0.20311
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:
Security Agent Version: 3.5.8082
Security Agent Restart Requirement: Not required
Estimated size of network traffic (in terms of bandwidth) required for deployment:
64-bit Security Agent Hotfix = 275MB
Additional Requirements: Enable web browser extension (https://success.trendmicro.com/solution/000273346)
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.
There are no known issues for this Hotfix release.
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.
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.