This Hotfix resolves the following issue(s):
A potential vulnerability is found in the Dashboard module.
Solution
This Hotfix resolves the issue.
On the Product Components Status Widget in the web console, the tooltip contains the incorrect Trend Vision One navigation path.
Solution
This Hotfix resolves the issue.
A issue may prevent the system from displaying the Standard Endpoint Protection screen in Trend Vision One.
Solution
This Hotfix resolves the issue.
This Hotfix resolves the following issue(s):
When the Web Reputation security level is set to "High" and the "Block pages that have not been tested by Trend Micro" option is not enabled in a policy, the system may incorrectly block untested domains.
Solution
This Hotfix updates the Trend Micro Apex One Security Agent program to resolve the issue.
The system may encounter issues related to DLL corruption (TmUmEvt64.dll) on Security Agent endpoints.
Solution
This Hotfix updates the Trend Micro Apex One Security Agent program to resolve the issue.
The system may display garbled content for Web Browser Extension on Security Agent endpoints running on supported but non-English version operating systems.
Solution
This Hotfix updates the Trend Micro Apex One Security Agent program to resolve the issue.
Trend Micro Apex One Security Agent may block URLs or websites that are not under monitoring.
Solution
This Hotfix updates the Data Loss Prevention (DLP) component to version 6.2.6099 to resolve the issue.
Sometimes the TCacheGen_x64.exe tool might not stop PccNTMon.exe properly.
Solution
This Critical Patch updates the Trend Micro Apex One server to resolve the issue.
There are no issues for this Hotfix release.
The following enhancements are included in this Hotfix:
This Hotfix enables Trend Micro Apex Central to synchronize the suspicious object lists for Trend Micro Apex One as a Service with Trend Vision One.
The following enhancements are included in this Hotfix:
This Hotfix updates the Virus Scan Engine (VSAPI) and Advanced Threat Scan Engine (ATSE) to version 25.580.1003 to enhance memory and file scans.
The Hotfix updates the Network Content Inspection Engine (NCIE) to version 3.7.1028 to enhance secure driver loading.
This Hotfix updates the Trend Micro Apex One server program to protect against a potential path traversal security issue.
This Hotfix updates the Curl module to version 8.16.0 and OpenSSL to 3.6.0 to enhance product security.
This Hotfix updates the TmEyes module to version 8.55.1409 to enable Windows 11 25H2 support.
This Hotfix updates the Behavior Monitoring Core Service module to version 2.98.2141 and Behavior Monitoring Core Drive module to version 2.98.2131 to enhance system performance.
The following enhancements are included in this Hotfix:
This Hotfix removes support for macOS 11 (Big Sur) for Trend Micro Apex One (Mac) after November 2025.
This Hotfix updates the Trend Micro Apex One (Mac) Security Agent program to enhance integration with Trend Vision One.
Version: 7160
Security Agent version: 14.0.20372
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.8103
Security Agent Restart Requirement: Not required
Estimated size of network traffic (in terms of bandwidth) required for deployment:
64-bit Security Agent Hotfix = 274MB
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.