An issue prevents Apex Central from receiving Personal Firewall logs.

An issue prevents users from successfully editing the Intrusion Prevention Rules (IPS) mode on the IPS page.

Some attributes display as "N/A" in User Access logs when the user account type is "AD Account".

In certain environments, the Application Control policy cannot be deployed through a network proxy successfully.

When an Apex Central deploys policies to multiple Apex One servers and one or more Apex One Servers are unavailable, the Application Control policy will not be deployed to the other normal Apex One servers.

It takes a long time to generate Static Reports.

An issue prevents Apex Central from syncing the Suspicious Object (SO) list.

A watermark overflow issue prevents Apex Central from syncing the SO list.

The "dntdom" CEF key displays incorrect values in Device Access Control syslogs.

A Hub Apex Central does not apply the correct Scan Action specified in the Scan Action Settings on incoming Virtual Analyzer Suspicious Objects.

Duplicate Virtual Analyzer Suspicious Object (VASO) entries trigger errors when users attempt to view the Custom Intelligence and Virtual Analyzer Suspicious Objects lists.

The SSO URL displays IP address instead of FQDN.

DLP Template and DLP Data Identifiers page loading very slow

Threats detailed logs do not display after users Single Sign-On (SSO) to Trend Micro Apex One(TM) from Apex Central.

Log Query results do not display when generated by specifying a specific group within a product.

The Application Control feature can apply specific Application Control criteria for different Active Directory (AD) users or groups, however, the Application Control agent may not be able to perform the correct action if the endpoint login user belongs to different trusted domain.

After a protected computer restarts and the Apex One agent reloads, the Application Control feature may not be able to perform the correct action because the Active Directory (AD) was not initialized on time.

A buffer overrun issue may cause the Apex One NT RealTime Scan ("Ntrtscan.exe") service to stop unexpectedly.

An issue related to the Apex One Security Agent purge function may cause a large number of VS* files to accumulate under the "temp" folder on the Security Agent.

The Update Agent Analytical Report of Apex One as a Service may not provide accurate data results for users.

The Microsoft(TM) System Center Operations Manager (SCOM) agent may not work on Apex One Security Agent computers.

A system error prevents users from deploying a Vulnerability Protection Policy from Trend Micro Apex Central(TM) to Apex One agents.

Security Agents may not properly detect and block uploads to Web Mail when Data Loss Prevention(TM) (DLP) is enabled.

When the "EnableRP=0" hidden key is added and deployed to all Apex One Security Agent computers, the "SupportConnector" folder and related programs may still run after the Security Agent computers restart.

The help is updated.

This Hotfix updates the Behavior Monitoring Detection Pattern (32-bit) and Behavior Monitoring Detection Pattern (64-bit) components to enhance security.

This Hotfix adds a temporary files purging function in the "\PCCSRV\Temp" folder of the Apex One server installation directory to prevent disk space shortage on the Apex One as a Service server. This function can also help improve system reliability.

This Hotfix enables the Apex One Security Agent program to support Microsoft Windows(TM) 11 and Windows Server 2022.

This Hotfix adds a count-dependent log purge function to enhance the retention mechanism for Central Quarantine Restore Logs of Apex One Security Agents and System Event Logs of Apex One.

This Hotfix resolves a Link Following Privilege Escalation security issue.

This Hotfix resolves a Link Following Denial-of-Service security issue.

This Hotfix replaces old 3P documents with the latest 3P documents.

This Hotfix ensures that French (FR) and German (DE) character strings display normally in the Apex One (Mac) Security Agent restart pop-up page.

This Hotfix updates the pattern file in the Apex One (Mac) agent installer to reduce download traffic.

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.