The "Spyware Pattern V6" field in Detailed Summary Reports displays inaccurate information.

An irregular Active Directory (AD) synchronization schedule may corrupt existing AD information.

Event notification settings are unexpectedly disabled.

Scheduled download tasks might result in redundant files that occupy disk space.

When using the Apex One Domain policy filter to select a range of targets, the system only selects a subset of the targets in the specified range.

The status logs might occupy too much disk space.

Users are unable to search for AD user accounts on the Device Control Rule screen.

The Data Protection feature for Device Control blocks devices that are in the approved list.

When the Agent Language Configuration setting is changed to "Apex One server language", the language setting is set to English for non-English Apex One versions.

Some files on the Apex One as a Service server may prevent users from upgrading Trend Micro OfficeScan(TM) XG or XG Service Pack 1 Security Agents.

After restarting the Apex One Security Agent endpoint, the Security Agent does not apply the proxy settings until the user logs on to the Security Agent endpoint again.

After restarting the Apex One Security Agent endpoint, the status of the File Reputation Services (FRS) feature remains "Unavailable" on the "Agent Management" screen of the Apex One web console until the user logs on to the Security Agent endpoint again.

After performing an advanced search on the "Agent Management" screen of the Apex One web console, users are not able to sort the "Restart Required" column.

When configuring Device Control policy settings in the Apex Central web console, users may not be able to add new or search for specific Active Directory user groups for user accounts even when the Active Directory connection is still active.

Users might not be able to download the Data Loss Prevention(TM) (DLP) forensic data and encounters the "Unable to download. The file has been removed by the managed product." message instead.

The "DLPForensicDataDelayUploadTracker.db" file is generated in the "C:\" drive of Security Agent computers.

Sometimes, Security Agents with DLP enabled may send duplicate DLP violation logs to the Apex One server.

Sometimes, Security Agents with DLP enabled may send incorrect incident details in DLP violation logs to the Apex One server.

This hotfix enables the Apex Central web console to support special characters in the Application Control criteria of certificates.

This Hotfix updates the Virus Scan Engine (VSAPI) to version 21.570.1004 and enhances the Self-Protection module to remove a detected vulnerability.

This Hotfix improves the command authorization feature of the Apex One server program.

This Hotfix fixes an Arbitrary File Creation by Privilege Escalation security issue in Apex One.

This Hotfix fixes a Stack-based Buffer Overflow Privilege Escalation security issue in Apex One.

This Hotfix enhances security by improving the permission assignment feature of Apex One.

This Hotfix updates the permission assignment process on the Apex One server and Apex One Apex Central Agent to enhance security.

This Hotfix fixes a Null Pointer security issue in the Apex One program.

This Hotfix enables the Apex One (Mac) Security Agent installer program to support the Apple(R) M1 chip.

This Hotfix adds several popup pages for different abnormal scenarios in the Apex One (Mac) Security Agent console.

This Hotfix enhances the Apex One (Mac) Security Agent installer program to prevent the "This package will run a program to determine if the software can be installed" popup to display twice.

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.