Adding file SHA-256 suspicious objects in Trend Vision One may prevent Trend Micro Apex One as a Service from upgrading to Standard Endpoint Protection.

The system may not send notification email for policy owner update to the policy owner in Standard Endpoint Protection.

The system may not display the updated Trend Micro Apex One group name in the Apex Central Product Status view.

An issue may prevent Trend Micro Apex Central from deploying components to integrated Trend Micro products.

An issue related to Application Control criteria processing may result in high CPU usage affecting system performance on Security Agent endpoints.

Data Loss Prevention (DLP) may not function properly for 7-Zip compressed files.

After updating the Trend Micro Apex One Security Agent program, the system may display the Security Agent console unexpectedly on endpoints.

When updating the Suspicious Object (SO) lists in the Trend Micro Apex One Security Agent, the Apex One NT Listener service ("TmListen.exe") may consume high CPU resource affecting system performance on Security Agent endpoints.

An issue related to virus/malware file path processing may cause the system to display spaces in detection file path as ASCII codes for the associated detection logs on the Log Query screen.

An issue related to the Trend Micro Apex One web console may prevent users from viewing the predefined port lists in Firewall Policy Rules.

A blue screen of death (BSOD) error may occur on Trend Micro Apex One Security Agent endpoints when the Trend Micro Unauthorized Change Prevention Service is enabled and users attempt to save Microsoft Office files through network drives.

This Hotfix updates the feature description on the Endpoint Sensor policy settings screen to enhance user experience.

This Hotfix adds application version information in Application Control detection logs for methods matched in the Application Reputation List.

This Hotfix enhances the self-protection capability for the Security Agent program folder to improve product security.

This Hotfix enhances the Predictive Machine Learning module for suspicious Anti-malware Scan Interface (AMSI) event detections.

This Hotfix updates the Apex One Security Agent program to enhance the blue screen of death (BSOD) Loop Prevention monitoring mechanism.

This Hotfix updates the Behavior Monitoring Core Service module to version 2.98.2101 and Behavior Monitoring Core Drive module to version 2.98.2100 to enhance the Security Agent self-protection capabilities.

This Hotfix enhances the Security Agent program update process in Trend Micro Apex One to prevent excessive network bandwidth usage.

This Hotfix enables Trend Micro Apex One (Mac) to send real-time scan status to Trend Micro Apex Central.

This Hotfix updates the iCore module in Trend Micro Apex One (Mac) Security Agent to support the millisecond format in detection logs.

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.