Behavior Monitoring and Predictive Machine Learning log queries return blank results.

Users cannot Single Sign-on (SSO) to the Apex One server using an account name that is longer than 36 characters.

An issue prevents the Apex Central web console from exporting policies.

The MDR service cannot resume after being suspended.

Scheduled Update settings change unexpectedly after an Apex One Hotfix is applied.

An issue prevents the Dashboard from displaying widgets properly.

The Activation Code cannot be deployed to the product server due to an improper Product Profile merge.

Adding new entries using the User-Defined Suspicious Object (UDSO) API returns an error when multiple requests are sent within a short time period.

An issue causes the MsgReceiver.exe application to stop responding.

The display format and symbol for the file path are incorrect.

It takes a long time to query email recipients which causes delays in sending out email notifications.

An issue prevents users from deploying pattern/engine updates to endpoints through Scheduled Update or Manual Update.

The system configuration file becomes corrupted because the configuration was saved without any content integrity check.

Email notifications are not triggered because the process cannot retrieve the correct configuration.

Component updates do not work normally because of an issue that prevents the process from retrieving the correct configuration.

An issue prevents the Application Control server from reporting the correct policy status to Trend Micro Apex Central(TM) when the policy contains a large number of Application Control rules.

An issue related to Data Protection module installation may prevent Security Agents where the Apex One Data Protection Service is enabled from properly detecting sensitive information and restricting device access on endpoints.

Security Agents running on endpoints always appear under the "Outdated Agents" group of the Apex One Firewall component in the Endpoint Status Widget on the Apex One web console.

The following message displays when the "Initiate Scan Now" task is triggered on selected Security Agents from the Agent Management Screen of the Apex One web console.

"Security Agents will receive the scan command during the next scheduled or manual agent update."

An issue related to garbled logon user information may cause Security Agent computers to disappear from the Agent Management Tree on the Apex One web console.

False Data Loss Protection alerts may be generated when Security Agents with Data Loss Prevention(TM) (DLP) are configured to monitor sensitive data in Web Mail.

In Japanese versions of Apex One as a Service, the Security Agent may update components from the ActiveUpdate Server at "https://osce12-p.activeupdate.trendmicro.co.jp" which is for Trend Micro OfficeScan(TM) XG or XG Service Pack 1 only.

The following message displays on the Agent Selection Screen of the Apex One web console when users search for "Outdated Agents" from the Endpoint Status Widget of the Apex One web console.

"The Apex One server notifies agents installed on the selected endpoints to update components. To proceed, click Initiate Update."

This message is redundant for Apex One as a Service.

Blue screen of death (BSOD) may occur on Apex One Security Agent computers when the Behavior Monitoring module encounters an invalid NULL pointer handling issue.

This Hotfix helps mitigate SQL exceptions during updates to Apex Central.

This Hotfix extends the capacity of the database column that stores the department name from the Active Directory (AD) from 64 to 256 characters.

This Hotfix adds the requested support identifiers for the following:

• Social Security Number for Hungary
• Tax Identification Number for Hungary

This Hotfix enables LogForwarder to forward mapping string labels instead of numbers when forwarding the contents of the Action, Policy, Event_Type, Operation, and Risk_Level columns in Behavior Monitoring logs.

For better synergy with Security Information and Event Management (SIEM) servers, this Hotfix adds a %processname% variable as the process name that accesses the URL in the web access policy violation event notifications found in the Microsoft Windows(TM) event logs.

This Hotfix updates the Virus Scan Engine (VSAPI) to version 21.600.1006.

This Hotfix retires the Intrusion Detection System (IDS) feature of the Apex One Firewall service. Refer to "https://success.trendmicro.com/solution/000289884" for details.

This Hotfix enables the Apex One Security Agent program to finish installing an update of Trend Micro AMSI Provider Module without restarting the Security Agent computer.

This Hotfix improves the message integrity checking process of the Apex One server program to enhance security.

This Hotfix updates the Apex One OpenSSL to version 1.1.11 and the cURL binary to version 7.78.0 to prevent a potential vulnerability issue.

This Hotfix resolves a Link Following Privilege Escalation security issue in the Apex One Security Agent program.

This Hotfix enables Trend Micro Apex One (Mac) to officially drop support for macOS 10.11 (El Capitan) and macOS 10.12 (Sierra) on January 2022.

This Hotfix updates the Trend Micro Apex One (Mac) system requirements in the Online Help Center.

This Hotfix ensures character strings display normally in the Apex One (Mac) Security Agent Device Control pop-up page.

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.