This Hotfix resolves the following issue(s):
When accessing web console through Standard Endpoint Protection in Trend Vision One and the web console times out, the system displays the incorrect logon screen.
Solution
This Hotfix resolves the issue.
An issue related to suspicious object synchronization from Trend Vision One may affect system performance.
Solution
This Hotfix resolves the issue.
An issue related to character processing may prevent Trend Micro Apex Central from sending test email notifications.
Solution
This Hotfix resolves the issue.
After registering both Trend Micro Apex One On-premises and Trend Micro Apex One SaaS to Trend Micro Apex Central, the system may not perform license deployment properly to the correct target due to an issue related to merging product profiles.
Solution
This Hotfix resolves the issue.
Potential vulnerabilities are found in the PHP component used in Trend Micro Apex Central.
Solution
This Hotfix updates the PHP component to resolve the issue.
Potential vulnerabilities are found in the Curl module used in Trend Micro Apex Central.
Solution
This Hotfix updates the Curl module to resolve the issue.
Potential vulnerabilities are found in the JsonWebToken module used in Trend Micro Apex Central.
Solution
This Hotfix updates the JsonWebToken module to resolve the issue.
Potential vulnerabilities are found in the Zip module used in Trend Micro Apex Central.
Solution
This Hotfix updates the Zip module to resolve the issue.
A potential vulnerability is found in a Javascript library.
Solution
This Hotfix updates the related library to resolve the issue.
This Hotfix resolves the following issue(s):
When Behavior Monitoring is enabled, an issue may cause excessive memory usage in the system.
Solution
This Hotfix updates the Behavior Monitoring Core Service module to version 2.98.2121 to resolve the issue.
When configuring scan exceptions, the system may create duplicate entries.
Solution
This Hotfix resolves the issue.
An issue related to the agent update process may prevent Security Agents from performing updates.
Solution
This Hotfix updates the related modules to resolve the issue.
Sometimes the system tray icon may not display.
Solution
This Hotfix updates the related components to resolve the issue.
When the Ntrtscan.exe process becomes unresponsive, the Security Agent console may display the "Protection at Risk" status.
Solution
This Hotfix updates the related components to resolve the issue.
Sometimes the agent driver (tmnciesc.sys) may become unresponsive.
Solution
This Hotfix updates the Trend Micro Apex One Security Agent program to resolve the issue.
An issue related to Data Loss Prevention (DLP) may prevent the system from applying the approved list for the SMB channel.
Solution
This Hotfix updates the DLP module to version 6.2.6095 to resolve the issue.
An issue related to Data Loss Prevention (DLP) may prevent the system from checking attachments in email messages.
Solution
This Hotfix updates the DLP module to version 6.2.6087 to resolve the issue.
There are no issues for this Hotfix release.
There are no enhancements for this Hotfix release.
The following enhancements are included in this Hotfix:
This Hotfix removes the Diagnostic Tool UI from the web console to enhance user experience.
This Hotfix updates the Windows SDK to version 10.0.19041.
This Hotfix enhances the protection capabilities of Behavior Monitoring to detect and block malicious behaviors originating from a valid driver.
This Hotfix updates the ofcntcer.dat file.
This Hotfix enables the system to remove specific outdated components from the agent folder.
This Hotfix updates the debug log to enhance agent processes on x86 platforms.
This Hotfix updates the Virus Scan Engine (VSAPI) to version 25.560.1004 and the Advanced Threat Scan Engine (ATSE) to version 25.560.1004 to enhance memory and file scans.
The following enhancements are included in this Hotfix:
This Hotfix updates the Trend Micro Apex One (Mac) Security Agent program to enhance integration with Trend Vision One.
Version: 7101
Security Agent version: 14.0.20168
Security Agent restart: Yes
Security Agent OS reboot: Not required for Security Agents are running build versions later than 10000.
Estimated size of network traffic (in terms of bandwidth) required for deployment:
Security Agent Version: 3.5.8060
Security Agent Restart Requirement: Not required
Estimated size of network traffic (in terms of bandwidth) required for deployment:
64-bit Security Agent Hotfix = 264MB
Additional Requirements: Enable web browser extension (https://success.trendmicro.com/solution/000273346)
No post-installation steps are required.
NOTE: Trend Micro recommends that you update your scan engine and virus pattern files immediately after installing the product.
There are no known issues for this Hotfix release.
Known issues in this release:
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.
Known issues in this release:
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.