Exported images on the User/Endpoint Directory screen in Timeline view contain no data.

For Active Directory user accounts, Apex Central is unable to synchronize the associated email address information from Active Directory.

The web console displays an empty Component List due to a product profile issue.

If multiple Security Agents are associated with the same endpoint, the User Name displayed for the product status is incorrect.

The User/Endpoint Directory screen does not display entries for all Security Agents.

The database connection credential is encrypted but not hashed.

On the Log Query screen, the system always displays the "N/A" status in the "Remote Domain" column for Network Content Inspection logs.

When changing the Device Permissions of Device Control action from "Block" to "Allow" for USB storage drives, the status for USB devices may appear as disabled on Windows Device Manager.

A compatibility issue between the Trend Micro User Mode Hooking (UMH) component in Apex One Security Agent and the Microsoft Windows 11 (KB5014019 and KB5014697) and Windows Server 2022 (KB5013944 and KB5014678) patches (released in May and June 2022 respectively) may cause the Program Inspection feature to stop detecting and blocking compromised executable files.

A compatibility issue between the Data Protection module in Apex One Security Agent and the Microsoft Windows 11 (KB5014019 and KB5014697) and Windows Server 2022 (KB5013944 and KB5014678) patches (released in May and June 2022 respectively) may cause the Data Protection Service to stop working properly.

This Hotfix allows you to set the UTCTimeFormat parameter to 1 to include the local component updated time in the Engine/Pattern Update Status logs. The default value is 0.

This Hotfix enhances the web console to display the correct license status during the grace period on the License Information screen after re-deployment.

This Hotfix enables the Apex One Server NTSG Certificate to support the SHA-256 hash algorithm.

This Hotfix adds the feature control setting in the Trend Micro Unauthorized Change Prevention Service to prevent Citrix from becoming unresponsive.

This Hotfix updates the Apex One Security Agent program to protect against a potential local privilege escalation vulnerability.

This Hotfix enhances the thread termination blocking mechanism for the Behavior Monitoring feature in Apex One Security Agent.

The Hotfix enhances the Apex One Server upgrade process to prevent timeout issues when related services are stopped during the process.

This Hotfix updates the ActiveUpdate (AU) module to version 2.88.1111.

This Hotfix updates the Behavior Monitoring Core Driver and Behavior Monitoring Core Service modules to version 2.98.1808.

This Hotfix enhances the detection capabilities of Apex One to scan for the EMOTET malware.

This Hotfix enhances the service protection capabilities of the Apex One Security Agent on Security Agent endpoints.

This Hotfix updates the Program Inspection Engine to version 2.9.1027.

This Hotfix enhances the user-agent information checking mechanism for Apex One Server components to improve product security.

This Hotfix updates the iCore configuration to enhance the network 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.