This Hotfix resolves the following issue(s):
If the parameter m_iZipReportAttachment is set to 0 in the file SystemConfiguration.xml, the system is unable to generate scheduled reports.
Solution
This Patch resolves the issue.
The system is unable to send scheduled reports to recipients.
Solution
This Patch resolves the issue.
When the "Static Templates" report content and "Email the Report as an Attachment" options are selected, the system is unable to send scheduled reports properly.
Solution
This Patch resolves the issue.
On the Policy Management screen in the web console, the system may not remove multiple policies selected for deletion.
Solution
This Patch resolves the issue.
This Hotfix resolves the following issue(s):
Restoring quarantined files on the Central Quarantine Restore screen may take an excessive amount of time.
Solution
This Hotfix updates the Apex One server program to resolve this issue.
After uninstalling and resinstalling a USB wireless network adapter on a Security Agent endpoint, the system may not apply the Data Loss Prevention (DLP) policies properly.
Solution
This Hotfix updates the Data Protection module to version 6.2.5247 to resolve this issue.
When the Endpoint Basecamp agent and Service Gateway services are enabled, the Apex One Vulnerability Protection agent service may become unresponsive during policy deployment.
Solution
This Hotfix updates the Trend Micro Vulnerability Protection agent program to resolve this issue.
Security Agents may use an invalid proxy server for network connections and appear as "Offline" on the Apex One web console.
Solution
This Hotfix updates the Apex One Security Agent program to resolve this issue.
The Trend Micro Unauthorized Change Prevention ("TMBMSRV.exe") service may stop unexpectedly.
Solution
This Hotfix updates the Behavior Monitoring Core Service module to version 2.98.1948 to resolve this issue.
There are no issues for this Hotfix release.
The following enhancements are included in this Hotfix:
This Patch updates the Apex One for Mac widget to protect against Cross-Site Scripting (XSS) security issues.
The following enhancements are included in this Hotfix:
This Hotfix updates the third-party product uninstallation process in Apex One to enhance product security.
The following enhancements are included in this Hotfix:
This Hotfix updates the description for the "Update Now" feature in the Apex One (Mac) Security Agent console to enhance user experience.
This Hotfix updates the Apex One (Mac) Security Server widget to protect against the Cross-Site Scripting (XSS) security issues.
This Hotfix updates the Apex One (Mac) server to enhance the integrity check of Apex One (Mac) Security Agents.
Security Agent version: 14.0.12637
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.7106
Security Agent Restart Requirement: Not required
Estimated size of network traffic (in terms of bandwidth) required for deployment:
64-bit Security Agent Hotfix = 229MB
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.
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.