A potential vulnerability is found in Apex Central.

An internal issue may cause the system to generate and save an excessive amount of duplicate data in the database.

Apex Central may only obtain partial account scope data when synchronizing accounts with Trend Vision One in Standard Endpoint Protection Mode.

After performing a Manual Scan on Security Agent endpoints, the Real-time Scan service ("Ntrtscan.exe") may stop unexpectedly.

A communication issue in the Apex One NT WSC service ("TmWSCSvc.exe") in Trend Micro Apex One Security Agent may prevent the agent program from upgrading successfully.

When accessed through the Agent Management screen in the web console, the system may not display the Scan Operation logs with the "Interrupted by system" status.

Trend Micro Apex One Security Agent may incorrectly block the powershell script that is used for Exchange Online PowerShell connection.

The Trend Micro Apex One Data Protection service ("DSAGENT.exe") may stop operating on Security Agent endpoints running Microsoft™ Windows™ Server 2016.

An issue related to proxy access on Security Agent endpoints may prevent users from updating the Security Agent program successfully from an Update Agent.

A blue screen of death (BSOD) error may occur on Trend Micro Apex One Security Agent endpoints when the Suspicious Connection Service is enabled.

This Hotfix adds a new predefined expression (Taiwan: Uniform ID for Foreign Nations) for Data Loss Prevention.

This Hotfix adds a new auditing log to record changes for the following settings:

• Virus/malware scan (Real-time Scan | Scheduled Scan | Scan Now)
• Spyware/grayware scan (Real-time Scan | Scheduled Scan | Scan Now)
• Malware Behavior Blocking
• Predictive Machine Learning
• Web Reputation(Internal and external agents)
• Vulnerability Protection
• Device Control(Internal and external agents)
• Application Control
• Suspicious file submission to Virtual Analyzer (Sample Submission)

This Hotfix adds an option to validate remote connections.

This Hotfix enables the system to display Apex One (Mac) Security Agents on the Security Posture Dashboard in Trend Vision One to enhance product integration.

This Hotfix enables the Trend Micro Apex One Security Agent program to support endpoints running Microsoft Windows 11 24H2.

This Hotfix enables the Trend Micro Apex One Security Agent endpoint to support policy configuration export through the pccntmon command line.

This Hotfix supports Trend Micro Apex One (Mac) Security Agent installation on endpoints running macOS 15 (Sequoia).

This Hotfix removes support for macOS 10.15 (Catalina) for Trend Micro Apex One (Mac) after November 2024.

This Hotfix enhances the Device Control feature in Trend Micro Apex One (Mac) for USB storage devices with FAT file system.

This Hotfix updates the Trend Micro Apex One (Mac) Security Agent program to enhance system performance.

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.

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.