The system displays an incorrect error message in the web console when users attempt to log in with an incorrect password.

The numbers of managed Security Agents on Apex One and Trend Vision One do not match.

After upgrading and migrating accounts to Trend Vision One, the system may display duplicate account entries in the web console.

The system displays an error when users try to start a "Start Scan Now" task on the Product Directory screen in the web console.

An error may occur when the system is unable to perform a component download task due to an excessive number of tasks in the command queue.

In the Apex Central web console, the system does not display all the managed Apex One Security Agents in the agent tree and policies.

When Real-time Scan is enabled, downloading compressed files through a web browser may affect system performance on Security Agent endpoints.

An issue related to the third-party product uninstallation process in Apex One may prevent the system from uninstalling the Apex One Security Agent on endpoints successfully.

An issue related to the threshold checking mechanism in Apex One may prevent Apex One Security Agents from sending firewall detection logs to the Apex One server properly.

The system is unable to remove inactive Apex One (Mac) Security Agents from the Apex One (Mac) server.

The system may display the incorrect MAC address information for Apex One (Mac) Security Agents in the web console.

This Hotfix adds a new channel value "Webmail(Zoho)" for Data Loss Prevention (DLP) logs.

This Hotfix adds the new "ProcessName" field in the tb_LogIntrusionPrevention table in the database.

This Hotfix updates the Data Loss Prevention (DLP) module to prevent false-positive alerts on Malaysia NRIC (National Registration Identity Card Number).

This Hotfix enhances the account management feature to prevent the deletion of a user account that is associated with a policy.

This Hotfix enhances the Product Status View for Apex One to include the policy description information.

This Hotfix updates the Apex One Security Agent program to protect against the Updater Link Following Local Privilege Escalation security issue.

This Hotfix updates the "IPXfer.exe" server tool in Apex One to support certificate integrity checking for Azure Code Signing (ACS).

This Hotfix updates the Inter-process communication (IPC) command authentication mechanism in Apex One Security Agent to enhance product security.

This Hotfix updates the Virus Scan Engine (VSAPI) to version 23.580.1004 and the Advanced Threat Scan Engine (ATSE) to version 23.580.1003 to resolve a potential Link Following Local Privilege Escalation security issue.

This Hotfix updates the Damage Cleanup Engine (DCE) to version 7.5.1188 to resolve a potential Link Following Local Privilege Escalation security issue.

This Hotfix enhances the detection logs from Apex One Security Agents to improve data visibility.

This Hotfix updates the Anti-Spyware Engine (SSAPI) to version 6.2.1.4067 to resolve a potential Link Following Local Privilege Escalation security issue.

This Hotfix updates the Data Protection module to enhance the authentication mechanism for inter-process communication (IPC) commands in Apex One Security Agent.

This Hotfix removes support for macOS 10.14 (Mojave) for Trend Micro Apex One (Mac) after November 2023.

This Hotfix updates the iCore module in Apex One (Mac) Security Agent to enhance product security.

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.