This Hotfix resolves the following issue(s):
Users are unable to view Data Discovery logs for custom templates.
Solution
The Hotfix resolves this issue.
Incorrect file paths are displayed in Spyware/Grayware log query results.
Solution
The Hotfix resolves this issue.
User list truncated on Change Policy Owner.
Solution
The Hotfix resolves the issue.
On the Notification Settings screen in the web console, users are unable to specify the SMTP server FQDN with a dash ("-") in the domain name.
Solution
The Hotfix resolves the issue.
If there is an excessive number of user accounts, the system may take some time to display the User Account list in the web console.
Solution
The Hotfix resolves this issue.
There are no issues for this Hotfix release.
There are no issues for this Hotfix release.
The following enhancements are included in this Hotfix:
This Hotfix updates the internal process in Apex Central to enhance data synchronization with Trend Vision One.
The following enhancements are included in this Hotfix:
This Hotfix updates the related modules to prevent compatibility issues between June 2024 Batch 1 build 14.0.13217 and Behavior Monitoring Threat Tracing Pattern x64(144664) / x86(144600).
For more information, see "https://success.trendmicro.com/dcx/s/solution/000298436".
There are no enhancements for this Hotfix release.
Security Agent version: 14.0.13219
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:
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.
There are no known issues for this Hotfix release.