AD synchronization cannot work normally.

When the Application Control feature uses the system proxy settings, Apex Central policy deployment to Apex One is unsuccessful.

After patch installation process is complete, some database schema error logs are generated.

The logon screen of the web console may stop responding or time out.

Apex Central is unable to synchronize tree information with Active Directory properly due to special characters (for example, ()+-&#) in object names.

A privilege escalation vulnerability has been found in the policy resource file.

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 other Security Agent endpoints successfully.

After configuring and deploying a weekly Scheduled Scan policy, Security Agents may not display the Scheduled Scan settings accurately.

On the Apex One web console, the Agent Management screen may not display the Data Loss Prevention (DLP) version properly, even for Security Agents with DLP disabled.

A race condition issue related to the Apex One Common Client Solution Framework ("TmCCSF.exe") service may prevent users from accessing websites using a supported web browser unless users click "Update Now" to perform an agent update on Security Agent endpoints.

Security Agents may block programs that are added to the Behavior Monitoring Approved List, even when the related program files are located in the specified UNC paths that bypass Behavior Monitoring scanning.

A code signing order issue in the Trend Micro WFP callout ("TMWFP.sys") driver may prevent the system from activating the Apex One Firewall service properly on Security Agent endpoints running on Microsoft™ Windows™ 7.

A reference counting issue in the Behavior Monitoring module may cause the Trend Micro Unauthorized Change Prevention ("TMBMSRV.exe") service to stop unexpectedly.

This Hotfix improves Apex Central performance in Inventory view.

This Hotfix enhances the syslog to generate logs for all tb_DeploymentPlansTF process operations, allowing administrators to troubleshoot component update deployment issues.

The systemconfiguration.xml file update process is enhanced to improve system stability.

Include Global Agent Settings in Apex One server policy deployment for Apex One Windows Security Agents.

This Hotfix prevents Apex One Security Agents from sending duplicated Data Loss Prevention(TM) (DLP) forensic data to the Apex One server to reduce network bandwidth consumption.

This Hotfix enhances the service recovery capabilities of Apex One Security Agents when related services are disabled.

This Hotfix enhances the Permission Assignment component in the Apex One server program to improve product security.

This Hotfix enhances endpoint protection by preventing unauthorized modification to the anti-malware scanning process running on Security Agent endpoints.

This Hotfix updates the term "anonymous" to "protected" on the Smart Protection Network screen in the web console.

This Hotfix adds ICOREX and Real-time Scan agent count information to the BIF feedback data.

This Hotfix integrates the ATSE engine ( 21.600.1005) in the Apex One (Mac) agent program.

This Hotfix updates the iCore module to enhance the performance of the Apex One (Mac) Security Agent.

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.

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.