An unexpected "Database Busy" warning message displays in the "User/Endpoint Directory" page when users attempt to update the Apex Central web console.

Duplicate email addresses appear in customized reports generated by Apex Central.

Inaccurate information displays when users drill down the "Agent Connection Status" widget.

An issue prevents Apex Central from sending logs to the syslog server.

Users cannot specify a time range while creating a new custom template.

Inaccurate information displays when users drill down the "Product Component Status" widget.

A memory leak issue causes high CPU usage on protected computers.

An issue prevents users from accessing the application control console and deploying the log maintenance module.

Report contents do not display properly because of an improper template setting.

Users can modify Apex One settings after accessing the Apex One console through Single Sign-On (SSO) using an account with "Read-Only" privileges.

Duplicate organizational unit (OU) entries cause the Active Directory (AD) sync to fail.

Inaccurate Product Status information appear in Log Query results.

"Suspicious object detections by channel/infection layer" reports cannot be generated successfully because the number of detection logs exceeds the limit.

A policy cannot be deployed when a large number of AD OUs are selected as filter criteria.

Users can select the "SSO_User" role when creating accounts.

The SMTP server settings do not accept Fully Qualified Domain Names (FQDN) with last domain names longer than three characters.

"CasProcessor.exe" stops unexpectedly.

The Data Loss Prevention(TM) (DLP) module does not support CJK Compatibility Ideographs.

An issue false to remove schedule task which prevents Apex Central to pull logs from Product.

OU names that contain diacritics cause AD sync to fail.

An issue prevents users from retrieving the "Last Manual Scan" time information from the log query after running a manual scan on an agent computer.

Users are redirected to a different web page after clicking the "Learn More" link under "Ransomware Prevention" on the dashboard.

The customized email notification templates for Attack Discovery detections revert to the default setting after upgrading.

The number of logs in the "Endpoint Spyware/Grayware" custom reports does not match the information in "Detailed Spyware/Grayware Information" custom reports.

The Application Control criteria in the Apex One Security Agent policy disappears from the Apex Central policy.

Sometimes, an issue prevents the Application Control agent from handling a rule correctly which can trigger it to impose the rule unexpectedly.

The Trend Micro Firewall components always appear as "outdated" on the Apex Central dashboard.

Apex One is affected by an arbitrary file write vulnerability related to its file restoration process.

Apex One is affected by an Improper Access Control Information Disclosure vulnerability.

Apex One Security Agents still use the proxy server in proxy auto-configuration (PAC) after the network location has been changed to a non-PAC environment. When this happens, Security Agents appear "Offline" on the Apex One web console.

Apex One Security Agent Service may be unable to start properly or become blocked by third-party security software. This may occur because the Apex One Security Agent leverages a PowerShell script to update its antivirus software status. Some third-party security software prevents the execution of the Powershell script.

When "bypass_itunes_nonstor_usb_dc=true", users can access an iOS phone from a protected computer even when the Device Control feature is configured to "Block" mobile devices.

Users encounter the following Microsoft(TM) Windows(TM) system event error message after disabling the "Global Agent Settings > Enable Early Launch Anti-Malware protection" feature on an endpoint.

"The Apex One NT WSC service failed to start due to the following error:

Windows cannot verify the digital signature for this file. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source."

An issue prevents the Web Reputation Service (WRS) from blocking access to HTTPS URLs on Microsoft(TM) Edge (Chromium) even when configured to block these websites.

The Web Reputation blocking page copyright year is still 2020.

Migration of the Endpoint Detection and Response (EDR) features to Trend Micro Vision One related apps continues, providing a better user experience.

EDR customers can single sign-on to the appropriate Trend Micro Vision One app for EDR features in the following menu paths.

• Response > Historical Investigation
• Dashboard > Threat Investigation > Quick Investigation widget
• Dashboard > Threat Investigation > Attack Discovery Detections widget

Analyze Impact has been removed from the following pages.

• Directories > Users/Endpoints (click detection name under Threats column) > Analyze Impact
• Threat Intel > Virtual Analyzer Suspicious Objects > Analyze Impact
• Threat Intel > Custom Intelligence > User-Defined Suspicious Objects > Analyze Impact
• Threat Intel > Custom Intelligence > OpenIOC > Analyze Impact

For more details of EDR migration scope and FAQ, please visit the Trend Micro Knowledge Base.

NOTE: Only the Customer Licensing Portal (CLP) account can do a single sign-on to Vision One console but not native Apex One SaaS local accounts. Refer to the Trend Micro Knowledge Base for the details if you need to use a local account to log in to the Vision One console.

This Hotfix ensures that users can configure email messages using the "mail" or "proxyAddresses" attribute of Active Directory (AD) users.

This Hotfix improves the Isolate, Restore, Relocate, or Uninstall Security Agent API by adding the "host_name_filter" to the following blur search criteria for the "host_name" variable.

• Start with
• End with
• Contains
• Not start with
• Not end with
• Not contains

For more information, refer to "https://automation.trendmicro.com/apex-central/home".

This Hotfix enables the Security Posture Widget to display Mac Agents under managed endpoints.

This Hotfix updates the Application Control files to extend the maximum number of Application Control Criteria to 350 in the Apex Central console.

This Hotfix adds the "Assessment" option in the Application Control rule assignment page.

This Hotfix improves the stability of deploying Active Keys from Apex Central.

This Hotfix enables the Apex One Vulnerability Protection module to support the approved IP list.

This Hotfix updates the file privileges for the "SqlMigration.log" file in the server installation folder for enhanced security.

This Hotfix fixes the Improper Access Control Privilege Escalation security issue.

This Hotfix adds a data collection function for the Apex One Web Reputation Service feature. Refer to the following website for more details.

https://success.trendmicro.com/solution/1120644

This Hotfix enables Apex One (Mac) to handle Web Reputation logs that contain URLs with Russian characters.

This Hotfix enables the Apex One (Mac) agent to collect and send its process performance counter information to Trend Micro.

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.