The system generates a Windows event log when the TICAgentForMDR.exe service becomes unresponsive.

Users with read-only accounts can still import device list files on the Device Control Allowed Devices screen.

An issue related to file name display prevents users from downloading Data Loss Prevention (DLP) forensic files.

Clicking Update Now may not start a Manual Update because the required authentication credential information for the proxy server is not applied properly.

Virus/Malware detection logs may contain incomplete threat names.

On the Security Agent console, the Console Flyover menu may not display some Apex One feature names properly.

When Data Protection is enabled, Security Agents may incorrectly block USB storage devices that are specified in the Approved Devices list.

An issue related to the Location Awareness feature may cause the File Reputation Service (FRS) to appear as "Unavailable" on the Apex One Security Agent console.

An issue related to the proxy settings may prevent the Web Reputation Service (WRS) from detecting and blocking access to potentially malicious website.

Users may not be able to export the status information of Security Agent endpoints on the Agent Management screen.

When you set a Security Agent not to perform an upgrade, the Security Agent still upgrades to the latest version automatically.

This Hotfix enhances the Apex Central service to prevent an unsuccessful service startup due to a large debug log size.

This Hotfix updates the file aucfg.ini to retain customized settings and improve the agent patch update process.

This Hotfix updates the system to automatically delete phantom endpoints that the system no longer manages on the Users/Endpoints screen.

This Hotfix adds a random time period when performing a database re-index process in Apex Central as a Service.

This Hotfix enhances the syslog to include the email subject information for security event logs.

This Hotfix enables Apex One to use the "Microsoft Public RSA Time Stamping Authority" digital signature as a time stamp for code signing.

This Hotfix updates the Apex One server program to enhance the access security of the Apex One web console.

This Hotfix enables Apex One to regenerate all Apex One Firewall profiles regularly and send the updated profile settings to Security Agents.

This Hotfix enhances the forensic data download process for Data Loss Prevention (DLP).

This Hotfix removes the "Scan network drive" option for Real-time Scan. For more information, see "https://success.trendmicro.com/solution/000290827".

This Hotfix updates the OpenSSL library in Apex One to version 1.1.1o and the cURL binary to version 7.83.1 to enhance product security.

This Hotfix updates the Apex One Security Agent program to process proxy server authentication credentials for Predictive Machine Learning.

This Hotfix updates the Data Protection module to version 6.2.5138.

This Hotfix updates the Apex One (Mac) web console to display the agent GUID information on the Agent Management screen.

This Hotfix enables the Apex One (Mac) Server to send the "Last Connected" information to Apex One Central.

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.