After updating to Standard Endpoint Protection in Trend Vision One, the system does not display the policy status for Apex One servers.

An issue related to the account deletion function may cause account synchronization with Trend Vision One to fail.

After updating to Standard Endpoint Protection in Trend Vision One, the Clear Data button is disabled on the Active Directory and Compliance Settings screen.

An issue related to the time format may prevent Apex Central from synchronizing suspicious object lists successfully.

It may take an excessive amount of time for the system to display the query results for spyware/grayware detection logs on the Apex Central web console.

The system is unable to display "non-Latin" characters for policy filter rules on the Policies screen.

When assessment mode is enabled, the system may still display Application Control violation pop-up notifications on Security Agent endpoints.

An issue related to the Apex One Master Service ("ofcservice") may prevent Apex Central from deploying security policies to Security Agents through Apex One based on the server polling interval.

For new Apex One Security Agent installations using the MSI installation package, an issue related to the agent move function in Apex One may prevent the system from installing the Trend Micro Endpoint Basecamp service.

An issue related to the proxy settings on Security Agents acting as Update Agents may prevent users from updating or upgrading the Security Agent program on Security Agent endpoints.

When Device Control is enabled, the system does not display a pop-up notification when a external device is connected to a protected Security Agent endpoint.

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

Apex One Security Agent may not send all Device Control detection logs to the Apex One server.

The Trend Micro Unauthorized Change Prevention service ("TMBMSRV.exe") may stop unexpectedly.

When Data Loss Prevention (DLP) is enabled, it may take an excessive amount of time to load files through SFTP on Security Agent endpoints.

A system issue may prevent users from importing or exporting the Device Control exceptions list in CSV format.

When the configuration key "bypass_itunes_nonstor_usb_dc" is set to "true" for Device Control, users are unable to charge iOS devices connected to protected Security Agent endpoints.

This hotfix allows Apex Central to process risk level and FilterCRC data to enhance suspicious object synchronization from Trend Vision One and improve product integration.

This Hotfix adds support for the new Trend Vision One user account type "SamlGroupSeamless".

This Hotfix updates the template for Japanese surnames to enhance Data Loss Prevention (DLP) detections.

Apex One no longer supports Security Agent installation and updates on endpoints running Windows operating systems that have reached the end of service. This Hotfix adds environment pre-checking in the Apex One server and Security Agent installation packages (MSI). For more information on supported Windows operating systems, see "https://success.trendmicro.com/dcx/s/solution/000283031".

This Hotfix updates the log forwarding function in Apex One to enhance the performance of Security Agent detection log collection and processing.

This Hotfix updates the Apex One Security Agent program to protect against the Time-Of-Check Time-Of-Use Local Privilege Escalation security issue.

This Hotfix updates the encryption algorithm in the Apex One Security Agent program to enhance product security.

This Hotfix enhances data synchronization between Apex One Security Agent and Endpoint Basecamp to improve product integration.

This Hotfix enables Apex One (Mac) Security Agent to perform a malware scan that is initiated from Trend Vision One.

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

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.