When using the Security Agent Download page on Apex Central with on-premises Apex One Service Pack 1 Patch 5, the server dropdown may not display any available servers when Windows ARM64 (AArch64) is selected as the operating system.

When registering Apex One servers running the Korean, Italian, Spanish, Polish, or Russian language editions to Apex Central, the affected servers may not appear as available targets when deploying an OS License in the License Management console.

The Log Deletion Schedule setting may be incorrectly changed from a weekly schedule to a daily schedule.

An issue may cause policy deployment processes to remain in the memory queue indefinitely if the TrendAI Apex One Master Service restarts during policy deployment.

After accessing the Agent Status screen in the TrendAI Apex One web console, an issue may cause the system to generate an Application Event (ID 900) in the Windows Event Log.

Exporting and then re-importing root domain settings may cause Web Reputation, Predictive Machine Learning, and Behavior Monitoring settings to be disabled.

An issue related to data parsing may cause the system to include incorrect data in exported CSV files using the "Export Scan Exclusions" function in the TrendAI Apex One web console or the ExportInfo tool.

An issue related to disk space thresholds in Data Loss Prevention (DLP) may prevent forensic file uploads in the TrendAI Apex One Server when disk space is low.

An issue may cause an "Error converting data type nvarchar(max) to uniqueidentifier" exception when viewing Web Reputation Service (WRS) logs in the web console.

When the TrendAI Apex One Server and Security Agent are installed on the same machine, the system may not create registry backup files correctly, preventing the Security Agent console from displaying.

TrendAI Apex One Security Agents may report inconsistent Scheduled Scan settings in the management console after a policy is deployed using the "Apply to All" option.

An issue in the URL filtering engine may cause the Common Client Solution Framework (CCSF) to become unresponsive, affecting system performance and preventing successful policy deployments.

The system may incorrectly display "(32-bit)" in the Windows Task Manager for TrendAI Apex One Security Agent binaries on 64-bit or ARM64 platforms.

When adding entries to the Behavior Monitoring exclusion list in the TrendAI Apex One Security Agent console, an issue related to Double-byte character set (DBCS) processing may prevent the system from applying the exclusions properly.

High CPU usage and performance degradation may occur on endpoints with TrendAI Apex One Security Agent and Microsoft Purview Data Loss Prevention (DLP).

The TrendAI Apex One Security Agent may detect potential threats on external USB drives even when the Device Control policy is configured to block access.

After moving TrendAI Apex One Security Agents configured as an Update Agent to a new server using the IpXfer tool, an issue related to root certificate mismatch may prevent successful pattern updates on TrendAI Apex One Security Agents.

An issue may cause File Reputation and Web Reputation services to appear as unavailable due to incorrect registry value processing and validation.

An issue may prevent the system from installing TrendAI Apex One Security Agent on endpoints that require non-Azure Code Signing (ACS) support.

A potential heap buffer overflow vulnerability (CVE-2026-48095) is found in the 7-Zip library used in TrendAI Apex One Security Agent.

The TrendAI Apex One Security Agent tray icon may be missing on multi-session Citrix or Virtual Desktop Infrastructure (VDI) hosts.

This Hotfix updates the 7-zip component to 26.02.

This Hotfix updates the PHP library to 8.2.32.

This Hotfix updates the Virus Scan Engine and Advanced Threat Scan Engine to version 26.550-1003.

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

This Hotfix updates the Network Filtering Driver to version 1.0.0.548 to hide URLs in default logs.

This Hotfix updates the TrendAI Apex One Security Agent program to improve the traceability of the DLL monitoring state by ensuring related events are logged regardless of the configured debug level.

This Hotfix updates the Apex One (Mac) Security Agent program to enhance the performance of the TmLoginMgr process.

This Hotfix updates the iCore module in Apex One (Mac) Security Agent to enhance product security.

This Hotfix updates multiple third-party libraries in Apex One (Mac) Security Server to enhance product security.

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.

A time zone issue may cause the system to display different log generation time information in the web console. In the web console, the system displays the log generation time in the time zone of the Apex One server.

• The Apex One server stores the log generation time information in GMT+0.
• The Security Agent sends the log generation time information (GMT+0 or local time) to the Apex One server.

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.