An issue related to user mapping may cause an unsuccessful migration to Trend Vision One.

Users might not be able to delete selected Data Loss Prevention (DLP) templates successfully.

The system may not properly save and deploy Large Compressed Files and Scheduled Scan policy settings configured in Apex Central to Apex One Security Agents.

An issue related to virus/malware name ID processing may cause the system to display "0" as the detection name for the associated detection logs on the Log Query screen.

An issue related to detection scope enhancement may result in high CPU usage affecting system performance on Security Agent endpoints.

An issue related to data processing on the SQL server may cause Apex One to generate Security Agent unregistered events and Security Agents to apply incorrect security policy settings.

An issue related to the the Program Inspection Engine may prevent the system from running a third-party program ( SS1) on Apex One Security Agent endpoints.

An encryption/decryption mismatch issue in the the Trusted Programs List module may cause the Schoeck Isolink program ("IsolinkP.exe") to stop unexpectedly on Apex One Security Agent endpoints.

Users may not be able to update iProduct services using the Apex One Security Agent installation package (MSI).

The Data Loss Prevention (DLP) service may not function properly in Windows 32-bit web browsers (WoW64) on Security Agent endpoints running 64-bit Windows versions.

Users may not be able to add scan exclusion entries on the Apex One Security Agent console.

When configuring ActiveUpdate settings for connected Apex One from the Service Gateway appliances, Apex One Security Agents may not update the Certified Safe Software Pattern resulting in a pattern compliance issue.

An issue related to user name matching in Apex One Security Agent may cause the Security Agent startup to take an excessive amount of time and the associated system icon to not display.

This Hotfix updates the following product names displayed in the web console:

• "ScanMail for IBM Domino"->"ScanMail for Domino"
• "ScanMail for Lotus Domino"->"ScanMail for Domino"
• "InterScan for IBM Domino"->"InterScan for Domino"
• "InterScan for Lotus Domino"->"InterScan for Domino"
• "SMID"->"SMD"
• "ISID"->"ISD"
• "SMLD"->"SMD"

This Hotfix updates the Spanish Name Dictionary in Data Loss Prevention (DLP) for middle name detection in names.

This Hotfix enables Apex One as a Service to support Security Agents installed on endpoints running Windows 11 (ARM64).

This Hotfix enhances Data Loss Prevention notification messages to include attachments in the compressed format.

This Hotfix updates data synchronization mechanism for the Suspicious Object Lists on Apex One Security Agent endpoints.

This Hotfix removes the redundant Trend Micro Endpoint Basecamp service and installer from the Apex One server.

This Hotfix updates the log forwarding function for Virus/Malware, Web Reputation Service (WRS), and Suspicious Files detection logs in Apex One to enhance the performance of detection log collection and processing.

This Hotfix updates the hash calculation function to ensure that Apex One Security Agents can retrieve the correct Suspicious Object lists.

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.