Trend Micro Apex One™ Readme (2022)

Prior Hotfixes

Only this Critical Patch was tested for this release. Prior hotfixes were tested at the time of their release.

Data Loss Prevention (DLP) may block file transfers to a CompactFlash card unexpectedly even if users already added the external memory card reader to the USB exception list.

Solution

This Hotfix updates the DLP module to resolve this issue.

The Apex One agent program may allocate additional virtual memory space without releasing previous memory allocations.

Solution

This Hotfix update Apex One agent program to resolve this issue.

An issue occurs wherein the installation of the Apex One Agent VCRuntime component aborts when integrity checking fails on the "CCSF_PTN.zip" file.

Solution

This Hotfix updates the Apex One agent program to resolve this issue.

An issue occurs wherein the virus log of the Virtual Desktop Infrastructure (VDI) agent maps to an incorrect agent.

Solution

This Hotfix updates the Apex One agent program to resolve this issue.

The Apex One web console may display inaccurate agent count information on the Endpoint Status widget (Managed Agents) and the Update Summary screen (Total number of agents).

Solution

This Hotfix updates the Apex One server program to resolve the issue.

A defect exists wherein the "Update Now" function of the Apex One agents does not complete the update and eventually times out.

Solution

This Hotfix updates the Apex One agent program to resolve the issue.

The Apex Central console may display this predefined DLP data identifier as a false positive: Serbia: JMBG - Јединствени матични број грађана (Unique Master Citizen Number).

Solution

This Hotfix updates the Apex Central program to resolve this issue.

DLP may cause false positive alerts when browsing some websites.

Solution

This Hotfix updates the DLP module to resolve this issue.

DLP may not detect Taiwan addresses if there is a space in between the characters.

Solution

This Hotfix updates the DLP module to resolve this issue.

DLP may unexpectedly block file transfers to a USB device even if users already added the USB device to the exception list.

Solution

This Hotfix updates the DLP module to resolve this issue.

The Apexone agent console displays a "Protection Enabled" message even though the agent computer requires a restart.

Solution

This Hotfix updates the Apex One agent program to resolve this issue.

Users cannot adjust the settings when an "HTTP 502.2 – Bad Gateway" error appears if the ESMTP user name contains a percentage sign (%).

Solution

This Hotfix updates the Apex One server program to resolve this issue.

The Apex One management console does not display the firewall pattern and driver version information.

Solution

This Hotfix updates the Apex One agent program to resolve this issue.

The system does not delete database files during the Apex One server uninstallation process.

Solution

This Hotfix updates the Apex One server program to resolve this issue.

The Apex One does not send out email notifications if the NT LAN Manager (NTLM) ESMTP setting is turned on.

Solution

This Hotfix updates the Apex One server program to resolve this issue.

An issue related to the Behavior Monitoring feature causes protected computer systems to stop responding. This problem occurs because the system did not release the allocated memory properly.

Solution

This Hotfix updates the Behavior Monitoring module to resolve this issue.

An issue related to Behavior Monitoring may cause the operating system to stop responding.

Solution

This Hotfix updates the Behavior Monitoring module to resolve this issue.

The Real-time Scan service may stop unexpectedly after starting.

Solution

This Hotfix updates the related module to resolve this issue.

This Hotfix prevents users from applying the release if its version is older than the version they currently use.

When an agent is moved to another server and then moved to another server again without restarting, the corresponding balloon notification may not display after the second move.

Solution

This Critical Patch updates the Apex One agent program to resolve this issue.

An issue may cause the operating systems of agent computers to stop unexpectedly.

Solution

This Critical Patch updates the Apex One agent program to resolve this issue.

Apex One agent processes may fill up the RAM/Swap memory of FTP Servers.

Solution

This Critical Patch updates the Apex One agent program to resolve this issue.

The Apex One NT RealTime Scan service may stop responding because an agent update does not complete properly.

Solution

This Critical Patch updates the Apex One server and agent programs to resolve this issue.

The Server Migration Tool (ServerMigrationTool.exe) may import unknown URLs into the Web Reputation Service (WRS) approved/blocked list of new Apex One servers.

Solution

This Critical Patch updates the Apex One server program to resolve this issue.

An internal Apex One agent may recognize itself as an external agent when the agent endpoint is using Team Network Adapter.

Solution

This Critical Patch updates the Apex One agent program to resolve this issue.

This Critical Patch enables Apex One to display the firewall policy name in Firewall Violation logs on the Apex Central console.

NOTE: This feature requires the installation of a corresponding Apex Central hotfix to enable Apex Central to support this feature.

This Critical Patch resolves a CVE-2018-1285 Apache™ Log4net XXE vulnerability by updating log4net from version 1.2.15.0 to the latest version, 2.0.13.0.

This Critical Patch updates the module related to the Smart Protection Server to resolve an Out-Of-Bounds Read security issue.

This Critical Patch enhances the security check mechanism of Apex One agent services.

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

This Critical Patch 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.

The Application Control agent sends inaccurate managed server name information for detection logs which prevents users from identifying which server is being referred to.

Solution

This Patch updates the Application Control agent files to resolve this issue.

When "EnableCentralWhitelist=0" and Apex One detects a compressed file, the corresponding detection log will not be recorded in the virus log.

Solution

This Patch updates the Apex One agent program to resolve this issue.

During a Manual Scan, system area scans take a long time to complete.

Solution

This Patch updates the Apex One agent program to resolve this issue.

Procedure

To disable shortcut scanner:

  1. Install this Patch (see "Installation").
  2. Open the "ofcscan.ini" file in the "\PCCSRV\"folder of the Apex One server installationdirectory using a text editor.
  3. Under the "Global Setting" section, manuallyadd the following key and set its value to "1".

[Global Setting]DisableShortcutScannerInMS=1

  1. Save the changes and close the file.
  2. Open the Apex One web console and go to the"Agents > Global Agent Settings" screen.
  3. Click "Save" to deploy the setting to agents.The Apex One server deploys the command to security agents and adds the following registry entry on all security agent endpoints:

Path:32bit: HKEY_LOCAL_MACHINE\SOFTWARE\TrendMicro\PC-cillinNTCorp\CurrentVersion\Misc.64bit: \HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\TrendMicro\PC-cillinNTCorp\CurrentVersion\Misc.Key: DisableShortcutScannerInMSType: DWORDValue: 1

  1. Restart the agent computer.

An issue prevents the server migration tool from handling the Unload/Uninstall password settings.

Solution

This Patch updates the server migration tool program to resolve this issue.

When users install the Security Agent using an installation package created by running the clnpack command with the "/ua" variable, the new Security Agent does not act as an update agent.

Solution

This Patch updates the Agent Packager to resolve this issue.

The Apex One Common Client Solution Framework may stop unexpectedly.

Solution

This Patch updates Trend Micro Feedback Engine (TMFBE) to resolve this issue.

Inaccurate Data Loss Prevention™ (DLP) log size information display on the Apex Central console when the actual DLP log is larger than 2 GB.

Solution

This Patch updates the Apex One server program to resolve this issue.

An issue prevents the Apex One Personal Firewall from working normally on endpoints where Checkpoint Endpoint Security VPN is also installed.

Solution

This Patch updates the Apex One agent program to resolve this issue.

The Apex One NT WSC service persists after users uninstall Trend Micro Apex One Security Agent through the control panel of an agent computer.

Solution

This Patch updates the Apex One agent program to resolve this issue.

The DLP module may block USB storage devices that are already in the exception list.

Solution

This Patch updates the DLP module to resolve this issue.

An issue prevents the DLP module from blocking 7-zip files with the "Encrypt file name" function enabled.

Solution

This Patch updates the DLP module to resolve this issue.

The On-Premise self-protection feature is enabled by default since Patch 5. Some users may not be aware that this feature affects certain settings.

Solution

This Patch updates the self-protection feature information on the Apex One server console.

After Apex One Critical Patch 9233 is applied, newly-installed security agents may unload and reload repeatedly before restarting agent computers.

Solution

This Patch updates the Apex One agent program to resolve this issue.

The Apex One Apex Central Agent service may stop unexpectedly.

Solution

This Patch updates the Apex One Server program to resolve this issue.

The self-protection feature triggers Apex One agents to delete temp files for the Advance Threat Scan Engine (ATSE) which generates alerts in Windows Event Logs.

Solution

This Patch updates Apex One agent components to ensure that agents do not delete temp files for ATSE.

When multiple agents use the same IP to report to the Apex One server, multiple certificate mismatch alerts appear in the system event logs.

Solution

This Patch updates the Apex One Server program to resolve this issue.

When the Apex One Server application pool is configured to use the Application Pool Identity Model, users encounter "ACCESS DENIED failure accessing the pipes" and "503 HTTP error code" warnings.

Solution

This Patch updates the Apex One server program to resolve this issue.

OfficeScan XG Service Pack 1 agents that are managed by an Apex One server may update the Behavior Monitoring module repeatedly.

Solution

This Patch resolves this issue.

When users change the action of the Device Control rule for USB storage drives from "Block" to any other action, the Device Control feature of the Data Protection service may still incorrectly block allowed USB storage devices.

Solution

This Patch updates the Data Protection module to resolve this issue.

An issue related to process termination may prevent users from upgrading Security Agents from Trend Micro OfficeScan™ XG or XG Service Pack 1 to Apex One.

Solution

This Patch updates the Apex One Security Agent program to resolve this issue.

Blue screen of death (BSOD) may occur on Apex One Security Agent computers when the Apex One Firewall Service is enabled.

Solution

This Patch updates the Apex One Firewall components to resolve this issue.

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

Solution

This Patch updates the Application Control server files to resolve this issue.

The Update Agent downloads same components repeatedly which adds to and slows down network traffic.

Solution

This Patch updates the Apex One server program to resolve this issue.

Some registry keys and driver files remain on an agent computer after Application Control has been uninstalled.

Solution

This Patch updates the Application Control agent files to resolve this issue.

This Patch enables the Apex One Security Agent program to support Microsoft Windows™ 10 (version 21H2) November 2021 Update, Windows 11, and Windows Server 2022.

This Patch resolves an Authentication Privilege Escalation security issue.

This Patch updates the Apex One Agent program to enhance security against resource exhaustion attacks.

This Patch enables a newly-created domain to inherit the firewall profile of its parent domain by selecting the parent domain in the "Domain" attribute of the firewall profile settings.

This Patch updates the server program to enable it to support wildcard characters in the first part of URLs on the web reputation approved/blocked list, for example "http*://". This allows the server to specify HTTP and HTTPS URLs in a single entry.

This Patch updates the privilege escalation feature of the Apex One agent program to enhance security.

This Patch updates the Trend Micro Control Manager™ MCP AgentSDK to prevent a potential vulnerability issue.

Apex One security agent computers may restart unexpectedly or experience blue screen of death (BSOD).

Solution

This Critical Patch updates the Apex One agent program to resolve this issue.

The Application Control feature can apply specific Application Control criteria for different Active Directory (AD) users or groups, however, the Application Control agent may not be able to perform the correct action if the endpoint login user belongs to different trusted domain.

Solution

This Critical Patch updates the Application Control agent files to resolve this issue.

After a protected computer restarts and the Apex One agent reloads, the Application Control feature may not be able to perform the correct action because the Active Directory (AD) was not initialized on time.

Solution

This Critical Patch updates the Application Control agent files to resolve this issue.

When configuring firewall policies exclusions, a warning message incorrectly warns users that they can specify up to 32 ports when the actual limit is 16 ports only.

Solution

This Critical Patch updates the Apex One server program to resolve this issue.

When users configure a new user account, the options selected in the "Edit user role" screen are not applied.

Solution

This Critical Patch updates the Apex One server program to resolve this issue.

In Spyware/Grayware logs, the Security Threat URL is invalid and redirects to the wrong web page.

Solution

This Critical Patch updates the Apex One server program to resolve this issue.

When users remove the "SupportConnector" folder and program, both are recreated after agent services restart.

Solution

This Critical Patch updates the Apex One agent program to resolve this issue.

The ADOException error from the Apex One Database Server may appear in the Windows event log.

Solution

This Critical Patch updates the Apex One server program to resolve this issue.

The Microsoft™ System Center Operations Manager (SCOM) agent may not work on Apex One security agent computers after Apex One Critical Patch 9601 is applied.

Solution

This Critical Patch updates the related module to resolve this issue.

The Data Loss Prevention™ (DLP) module may trigger duplicate violation notification windows when the User Justification feature is enabled in the policy.

Solution

This Critical Patch updates the DLP module to resolve this issue.

The Apex One server does not purge logs of unregistered Apex One agents from the Apex One SQL database.

Solution

This Critical Patch updates the Apex One server program to ensure that it promptly removes logs of unregistered agents from the SQL database.

When enabled, DLP may block users from saving information onto a mounted network drive unexpectedly.

Solution

This Critical Patch updates the DLP module to resolve this issue.

An issue related to the Unauthorized Change Prevention Service causes a slow system response while users save a file to network drive.

Solution

This Critical Patch updates the Apex One Security Server program and enables users to configure Apex One to skip certain events to help prevent the issue.

Procedure

To apply and deploy the solution globally:

  1. Install this Critical Patch (see "Installation").
  2. Open the "ofcscan.ini" file in the "\PCCSRV\" folder of the Apex One server installation directory using a text editor.
  3. Under the "Global Setting" section, manually add the following key and set its value to "1".
  • [Global Setting]
  • AegisSkipCreateUNCFile=1
  1. Save the changes and close the file.
  2. Open the Apex One web console and go to the "Agents > Global Agent Settings" screen.
  3. Click "Save" to deploy the setting to agents. The Apex One server deploys the command to security agents and adds the following registry entry on all security agent endpoints:
  • Path: HKEY_LOCAL_MACHINE\SOFTWARE\TrendMicro\AEGIS
  • Key: SkipCreateUNCFile
  • Type: DWORD
  • Value: 1

After applying Apex One Critical Patch 9645 on the Apex One server with an Apex One security agent installed, the "Uninstalling..." button may appear on the "Plug-ins" page of web console.

Solution

This Critical Patch updates the Apex One server program to resolve this issue.

The Apex One Agent display name in the "Programs and Features" page remains as "OfficeScan XG" if it does not restart after upgrading from OfficeScan XG.

Solution

This Critical Patch ensures that the display name is updated promptly after the update without requiring a restart.

An issue related to the Apex One Security Agent purge function may cause a large number of VS* files to accumulate under the "temp" folder on the Security Agent.

Solution

This Critical Patch updates the Apex One Security Agent program to resolve this issue.

Security Agents may not properly detect and block uploads to Web Mail when Data Loss Prevention™ (DLP) is enabled.

Solution

This Critical Patch updates the Data Protection module to resolve this issue.

This Critical Patch resolves a Link Following Denial-of-Service security issue.

This Critical Patch resolves a Link Following Privilege Escalation security issue.

This Critical Patch updates the security of the Apex One server program.

This Critical Patch updates the permission control mechanism of the Apex One server program to enhance security.

This Critical Patch improves the permission control mechanism of the Apex One Server Service for enhanced security.

Both the Gray Detection Pattern and Threat Tracing Pattern may appear in the "Component Versions" page of the agent console.

Solution

This Critical Patch updates the Apex One agent program to ensure that the Gray Detection Pattern and Threat Tracing Pattern does not appear on the "Component Versions" page of the agent console.

The Application Control feature can apply specific Application Control criteria for different Active Directory (AD) users or groups, however, the Application Control agent may not be able to perform the correct action if the endpoint login user belongs to different trusted domain.

Solution

This Critical Patch updates the Application Control agent files to resolve this issue.

An issue prevents the Security Agent from uploading quarantined files with filenames encoded in UTF-8.

Solution

This Critical Patch updates the Apex One Server program to resolve this issue.

An issue prevents Data Loss Prevention™ (DLP) from detecting the transfer of information in Microsoft™ Outlook™ Web Access.

Solution

This Critical Patch updates the DLP module to resolve this issue.

DLP may trigger false alarms when data is transferred through certain websites.

Solution

This Critical Patch updates the DLP module to resolve this issue.

When enabled, Device Control may block users from saving information onto certain SD cards unexpectedly.

Solution

This Critical Patch updates the DLP module to resolve this issue.

Clicking on the "Restart Required" column on the agent tree does not sort the agents accordingly.

Solution

This Critical Patch updates the Apex One server program to ensure that the "Restart Required" filter works on Advance Search results.

A large number of firewall logs causes performance issues.

Solution

This Critical Patch updates the Apex One agent program to resolve this issue.

The "Agent Packaging Tool" option appears on the Apex One server's User Role permission settings.

Solution

This Critical Patch updates the Apex One Server program to remove this option from the User Role permission settings.

Administrators may not be able to enable XDR on the Apex One Server.

Solution

This Critical Patch resolves the issue by updating the Apex One Server Programs.

When an agent is upgraded to Apex One without connecting to the Apex One Server, the agent display name is not updated.

Solution

This Critical Patch ensures that the agent display name is updated under the scenario described above.

The "ofcservice.exe" process may stop responding under certain conditions.

Solution

This Critical Patch resolves this issue.

Users might not be able to download the Data Loss Prevention forensic data from the Apex Central console after applying Apex One Critical Patch 9629. The "Unable to download. The file has been removed by the managed product" message appears.

Solution

This Critical Patch updates Apex One server program to ensure users can download the Data Loss Prevention forensic data from the Apex Central console.

A system error prevents users from deploying a Vulnerability Protection Policy from Trend Micro Apex Central™ to Apex One agents.

Solution

This Critical Patch updates the Apex One Vulnerability Protection component to resolve this issue.

This Critical Patch enables users to export the Security Agent's component version to a file by running the following command:

Pccntmon.exe -v > C:\outputfile.txt

Where "outputfile.txt" is a user-specified file name of the output file.

This Critical Patch fixes a Null Pointer security issue in the Apex One program.

This Critical Patch fixes an Arbitrary File Creation by Privilege Escalation security issue in Apex One.

This Critical Patch fixes a Stack-based Buffer Overflow Privilege Escalation security issue in Apex One.

This Critical Patch improves the command authorization feature of the Apex One Server Program.

This Critical Patch enhances security by improving the permission assignment feature of Apex One.

When Behavior Monitoring detects ransomware in a file on a shared folder, the file may not be quarantined.

Solution

This Critical Patch updates the Apex One agent program to resolve this issue.

Multiple endpoints may use the same Data Loss Prevention™ (DLP) violation ID in violation logs.

Solution

This Critical Patch updates the DLP module to resolve this issue.

The DLP module may falsely detect invalid Indian Aadhaar numbers.

Solution

This Critical Patch updates the DLP module to resolve this issue.

An issue related to the DLP module may cause Apex One to block certain USB network adaptors unexpectedly.

Solution

This Critical Patch updates the DLP module to resolve this issue.

An issue prevents users from configuring the value of the "BypassTrustProgramListVerification" key normally on an agent computer.

Solution

This Critical Patch updates the Apex One Security agent program to fix the issue.

The Apex One Master Service may unexpectedly consume a high amount of CPU resources causing the web console to not load properly.

Solution

This Critical Patch updates the Apex One server program to fix the issue.

The Application Control Server may not be able to handle criteria that has been exported and imported again.

Solution

This Critical Patch updates the Application Control Server files to resolve this issue.

The Application Control agent may not be able to start successfully if there is an incomplete agent registry key.

Solution

This Critical Patch updates the Application Control agent files to resolve this issue.

After a Trend Micro OfficeScan™ XG Service Pack 1 server which uses conventional scan as scan method is migrated to an Apex One GM build server and Apex One Patch Build 8378 or any higher build is applied, an HTTP 404 error occurs when users download the Security Agent MSI installation package from the web console.

Solution

This Critical Patch updates the Apex One server program so users can download the Security Agent MSI installation package from the web console under the scenario described above.

An issue may prevent Apex One security agents from detecting an lsass credential dump through the Task Manager. This issue has been resolved in Patch 9565 but reappears after users apply Critical Patch 9601.

Solution

This Critical Patch updates the Behavior Monitoring module to fix this issue.

The "DLPForensicDataDelayUploadTracker.db" file is generated in the "C:\" drive of agent computers.

Solution

This Critical Patch updates the Apex One Security agent program to ensure that the "DLPForensicDataDelayUploadTracker.db" file is generated in the Apex One security agent installation folder.

Sometimes, the "User Name" field in Data Loss Prevention™ (DLP) violation logs is empty.

Solution

This Critical Patch updates the Data Protection module to resolve this issue.

This Critical Patch updates the permission assignment process of the Apex One Server program to enhance security.

This Critical Patch updates the permission control feature of the Apex One agent program to enhance security.

This Critical Patch updates the command authentication mechanism of the Apex One Server to enhance security.

This Critical Patch updates the command authentication mechanism of the Apex One agent to enhance security.

This Critical Patch updates the agent program to improve agent security.

This Critical Patch updates the Damage Cleanup Engine to resolve a Local Privilege Escalation security issue.

This Critical Patch updates the module related to the Smart Protection Server to resolve a Local Privilege Escalation security issue.

(Video) Apex One / OfficeScan Remote Install

Policies on Apex Central may not be deployed successfully during automatic deployment.

Solution

This Critical Patch updates the Apex One Server program to resolve this issue.

When the "Hide these specified drives in My Computer" policy is enabled with the "Restrict all drives" option, local drives may not display preventing users from running system scans.

Solution

This Critical Patch updates the Apex One agent program to resolve this issue.

Procedure

To disable hidden drive in manual scan:

  1. Install this Critical Patch (see "Installation").
  2. Open the "Ofcscan.ini" file in the "\PCCSRV\" folder of the Apex One server installation directory using a text editor.
  3. Under the "Global Setting" section, manually add the "DisableHiddenDriveInMS" key and set its value to "1".
  • [Global Setting]
  • DisableHiddenDriveInMS = 1
  1. Save the changes and close the file.
  2. Open the Apex One web console and go to the "Agents > Global Agent Settings" screen.
  3. Click "Save" to deploy the setting to agents. The Apex One server deploys the command to Apex One agents and adds the following registry entry on all Apex One agent endpoints:
  • Path:HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\TrendMicro\PC-cillinNTCorp\CurrentVersion\Misc.
  • Key: DisableHiddenDriveInMS
  • Type: REG_DWORD
  • Value: 1

3rd-party application installation does not complete when Advanced Protection Service is enabled.

Solution

This Critical Patch updates the user mode hook event module to resolve this issue.

An issue related to the Data Loss Prevention™ (DLP) feature may prevent Apex One from blocking File Transfers during a Zoom Meeting.

Solution

This Critical Patch updates the DLP module to resolve this issue.

An issue related to the DLP Device Control can prevent Apex One from blocking USB network adapters.

Solution

This Critical Patch updates the DLP module to support Thinkpad USB 3.0 Ethernet Adapter.

An error message displays while a 3rd-party application is running on a protected computer.

Solution

This Critical Patch updates the Behavior Monitoring module to fix this issue.

Apex One does not send email notifications to administrators after detecting a security risk. Restarting the Apex One Master Service may solve the issue for a short period of time after which the issue recurs.

Solution

This Critical Patch helps prevent this issue by enabling users to configure the memory usage limit.

Procedure

To set the memory usage limit:

  1. Install this Critical Patch (see "Installation").
  2. Open the "ofcserver.ini" file in the "\PCCSRV\Private" folder of the Apex One server installation directory using a text editor.
  3. Under the "INI_LOG_MEMORY" section, manually add the following key and set its value to the memory usage limit.
  • [INI_LOG_MEMORY]
  • LogQueueMemoryLimit=2147483648(default is 2GB)
  1. Save the changes and close the file.
  2. Restart the Apex One Master Service.

The metadata storage value of the Endpoint Sensor rolls back to default when the Trend Micro Smart Feedback is enabled.

Solution

This Critical Patch ensures that the metadata storage value of Endpoint Sensor does not change when the Trend Micro Smart Feedback is enabled.

The Apex One NT WSC Service may not be deleted when the Apex One Agent program is uninstalled.

Solution

This Critical Patch updates the Apex One agent program to resolve this issue.

An issue on the Apex One web console may prevent users from configuring the Apex One server external proxy.

Solution

This Critical Patch updates the server program to resolve the issue.

An issue prevents the Apex One Master Service from starting after a manual roll back from Patch 5 to the previous build.

Solution

This Critical Patch resolves the issue to ensure that the manual rollback proceeds normally.

Apex One servers that use a Microsoft™ SQL Server database may receive an installation error preventing them from installing the Patch 5 upgrade.

Solution

This Critical Patch updates the upgrade process to resolve this issue.

Blue Screen of Death (BSOD) may occur when users delete files from connected USB storage devices.

Solution

This Critical Patch updates the Behavior Monitoring module and enables users to configure Apex One to skip certain events to help prevent the issue.

Procedure

To apply and deploy the solution globally:

  1. Install this Critical Patch (see "Installation").
  2. Open the "ofcscan.ini" file in the "\PCCSRV\" folder of the Apex One server installation directory using a text editor.
  3. Under the "Global Setting" section, manually add the following key and set its value to "1".
  • [Global Setting]
  • AegisSkipExplorerDeleteFileOnPortableDevice=1
  1. Save the changes and close the file.
  2. Open the Apex One web console and go to the "Agents > Global Agent Settings" screen.
  3. Click "Save" to deploy the setting to agents. The Apex One server deploys the command to security agents and adds the following registry entry on all security agent endpoints:
  • Path: HKEY_LOCAL_MACHINE\SOFTWARE\TrendMicro\AEGIS
  • Key: SkipExplorerDeleteFileOnPortableDevice
  • Type: DWORD
  • Value: 1

The Web Reputation Violation blocking page does not display when "AsyncServerLookup" is set to "0" on the agent computer.

Solution

This Critical Patch resolves this issue by updating the module related to the Web Reputation function.

An issue prevents Apex One from concurrently deploying multiple Vulnerability Protection (VP) policies successfully.

Solution

This Critical Patch updates the Apex One VP server program to resolve this issue.

The size of the Data Loss Prevention™ (DLP) log always appears as 2147483647 on the Apex One server web console when the triggering file on the endpoint is larger than 2GB.

Solution

This Critical Patch updates the Apex One server and agent programs to resolve this issue.

This Critical Patch resolves an Authentication Bypass security issue.

This Critical Patch enables the DLP module to support the identifier for Taiwan Business Administration Numbers.

This Critical Patch enhances the security of the agent process during start up.

This Critical Patch updates the Data Loss Prevention™ (DLP) module to extend the upload file size limit in "File Attributes" of Data Identifiers to 1024 GB.

An issue related to the Behavior Monitoring (BM) feature prevents users from creating a shared folder.

Solution

This Patch updates the BM module to fix the issue.

The Data Loss Prevention™ (DLP) device control feature blocks devices that are in the approved list.

Solution

This Patch updates the DLP module to resolve this issue.

An issue prevents the Apex One Security agent from scanning a newly-connected USB storage device.

Solution

This Patch updates the Apex One Security agent program to fix the issue.

The Apex One installation path cannot be obtained from the registry.

Solution

This Patch updates the Apex One server program to resolve this issue.

An issue related to the Behavior Monitoring feature may prevent Apex One from detecting an lsaas credential dump through the Task Manager.

Solution

This Patch updates the Behavior Monitoring module to fix this issue.

An issue related to the Behavior Monitoring (BM) feature causes agent computers to freeze.

Solution

This Patch updates the BM module and Apex One Security agent program to prevent this performance issue.

Procedure

To enable the new settings:

  1. Install this Patch (see "Installation").
  2. Open the "Ofcscan.ini" file in the "\PCCSRV\" folder of the Apex One server installation directory using a text editor.
  3. Under the "Global Setting" section, manually add the "AegisReputationAsync" key and set its value to "1".
  • [Global Setting]
  • AegisReputationAsync=1
  1. Save the changes and close the file.
  2. Open the Apex One web console and go to the "Agents > Global Agent Settings" screen.
  3. Click "Save" to deploy the setting to agents. The Apex One server deploys the command to Apex One agents and adds the following registry entry on all Apex One agent endpoints:
  • Path:
  • HKEY_LOCAL_MACHINE\SOFTWARE\TrendMicro\AEGIS
  • Key: ReputationAsync
  • Type: REG_DWORD
  • Value: 1

An issue prevents the Apex One server from deploying the iProduct policy from Trend Micro Apex Central™ successfully.

Solution

This Patch updates the Apex One server program to resolve this issue.

When users click the Security Threat link in Virus/Malware logs, they are redirected to an invalid page instead of to the Trend Micro Threat Encyclopedia.

Solution

This Patch updates the Apex One program to ensure that the Security Threat link redirects to the Trend Micro Threat Encyclopedia website.

An interoperability issue occurs between "LogServer.exe" and a third-party application on Apex One Security agents.

Solution

This Patch resolves this issue by adding a hidden key in the Apex One Security agent program.

Procedure

To enable the solution on Apex One Security agents:

  1. Install this Patch (see "Installation").
  2. Unload the Apex One Security agent.
  3. Launch the Command prompt.
  4. According to the Security agent platform version, manually add the "SEG_KeepLocalDebugFlags" registry key under the following registry entry.
  • X64 Path:
  • HKLM\SOFTWARE\WOW6432Node\TrendMicro\PC-cillinNTCorpCurrentVersion\Debug Log Setting
  • X86 Path:
  • HKLM\SOFTWARE\TrendMicro\PC-cillinNTCorp\CurrentVersion\Debug Log Setting
  • Key: SEG_KeepLocalDebugFlags
  • Type: REG_DWORD
  • Value: 1
  1. Reload the Apex One Security agent.

Clicking on the "Restart Required" column on the agent tree does not sort the agents according to which needs to restart or not.

Solution

This Patch updates the Apex One server program to resolve this issue.

An issue related to the DLP device control feature causes blue screen of death (BSoD) on agents running on Microsoft™ Windows™ 10 after a Windows update.

Solution

This Patch updates the DLP module program to resolve this issue.

When a scan engine is rolled back on the Apex One server, the scan engine is not automatically rolled back on Apex One security agents.

Solution

This Patch updates the Apex One server program to ensure that the scan engine is automatically rolled back on Apex One Security agent once it is rolled back on the server.

When the Apex One server is installed on Windows 2012 or 2012 R2, the TLS handshake fails and a Schannel error is generated in the Windows event log.

Solution

This Patch updates the Apex One server program to resolve this issue.

A signature verification issue may prevent the Apex One server from properly accepting an Apex One Security Agent heartbeat notification.

Solution

This Patch updates the Apex One Security Agent program to resolve this issue.

The iES License deactivates unexpectedly on the Apex Central console.

Solution

This Patch updates the Apex One server program to resolve this issue.

A "Warning" message appears in the Windows Application Event Log when there are wildcard characters in the Scan Exclusion list.

Solution

This Patch updates the Apex One agent program to ensure that wildcard characters in the Scan Exclusion list does not trigger the warning.

When the Apex One agent is configured to use the Smart Protection Server Relay to query predictive machine learning, it uses the default port instead of the configured FRS port.

Solution

This Patch ensures that the Apex One agent uses the FRS port for machine learning SPS relay queries.

Domains and agents do not appear on the "Agent Management" page when users log on to the web console using an account under a sub-Active Directory (AD) user group that also belongs to the main AD group.

Solution

This Patch updates the Apex One server program to resolve this issue.

An issue prevents users from sending an email message with a particular file attachment.

Solution

This Patch updates the DLP templates to resolve this issue.

Under certain scenarios, the wrong NFC server fully-qualified domain name (FQDN) may be saved in the Japanese version of Apex One.

Solution

This Patch corrects the NFC server FQDN.

The Device Control feature reads different Device IDs for USB Storage Devices on different Security Agent computers.

Solution

This Patch updates the Data Protection module to resolve this issue.

The 3rd-party Eclipse program cannot be launched on when the Apex One Security Agent has Predictive Machine Learning enabled for process detections.

Solution

This Patch updates the Contextual Intelligence Engine to resolve the issue.

Security Agents that enabled the Apex One Predictive Machine Learning (for Process detections) feature may experience high CPU usage issues on the Trend Micro Unauthorized Change Prevention Service.

Solution

This Patch updates the Contextual Intelligence Engine to resolve the issue.

An issue prevents the Security Agent installation package (MSI) from being upgraded agents from OfficeScan XG / XG SP1.

Solution

This Patch updates the Apex One server program to resolve this issue.

Apex One Security Agents may appear "Offline" after the security agent is connected to the network through VPN.

Solution

This Patch updates the Apex One Security Agent program to resolve this issue.

A signature checking issue related to the Trusted Programs List may cause the Apex One NT RealTime Scan ("Ntrtscan.exe") service to stop unexpectedly.

Solution

This Patch updates the Apex One Security Agent program to resolve this issue.

An issue related to the Data Loss Prevention™ (DLP) exclusion settings may cause the Apex One NT RealTime Scan ("Ntrtscan.exe") service to stop unexpectedly.

Solution

This Patch updates the Data Protection module to resolve this issue.

A buffer overrun issue may cause the Apex One NT Listener service ("TmListen.exe") to stop unexpectedly. When this happens, the Apex One Security Agent is not able to update pattern files successfully.

Solution

This Patch updates the Apex One Security Agent program to resolve this issue.

A Digital Signature checking issue related to the Data Protection module may prevent Apex One Security Agents from updating the Apex One Security Agent program properly.

Solution

This Patch updates the Data Protection module to resolve this issue.

This Patch updates the Apex One Security Agent program to prevent a potential security issue.

This Patch updates the Apex One server program to prevent a potential security issue.

This Patch updates the permission control feature of Apex One agents to improve security.

This Patch updates the Apex One program to prevent a potential security issue.

This Patch enables the Apex One Security Agent program to support Microsoft Windows™ 10 (version 21H1) May 2021 Update.

This Patch enables the Apex One Vulnerability Protection module to support user-defined mode changes for each Intrusion Prevention rule.

NOTE: This feature requires the installation of Apex Central hotfix 5708 or above.

Procedure

To configure the user-defined mode:

  1. Install this Patch (see "Installation").
  2. Open the Apex Central web console and go to the "Policies > Policy Resources > Intrusion Prevention Rules" screen.
  3. Click on the "Mode" of the target rule.
  4. Select the preferred mode option and click "Save" to save the changes.
  5. Go to the "Policies > Policy Management" screen and deploy the policy to agents.

This Patch removes a potential DLL Side-Loading Vulnerability in Apex One.

This Patch enables the Apex One server to use NTLM authentication for ESMTP.

This Patch changes the delimiter in C&C callback logs to prevent the conflict issues that may happen while processing the path.

NOTE: This enhancement requires you to update both the server and agent programs to ensure all functions work normally.

"Trend Micro Apex One Security Services Support Connector" can be removed from the task schedule by setting and deploying "EnableRP=0" in the server settings.

After Critical Patch 9204 is applied, Apex One may not be able to import the Web Reputation Settings (WRS) Approved/Blocked URL List.

Solution

This Critical Patch updates the Apex One Server program to ensure that the WRS Approved/Blocked URL list can be imported normally.

After upgrading from Trend Micro OfficeScan™ XG to Apex One, the agent program becomes corrupted because of incomplete file decompression during the upgrade process.

Solution

This Critical Patch updates the Apex One agent program to resolve this issue.

An issue related to the Behavior Monitoring (BM) feature causes the Horizon VMWARE CDR and RDSH applications to stop responding.

Solution

This Critical Patch updates the BM module program to ensure that both applications work normally on protected computers.

Procedure

To enable the new settings:

  1. Install this Critical Patch (see "Installation").
  2. Open the "Ofcscan.ini" file in the "\PCCSRV\" folder of the Apex One server installation directory using a text editor.
  3. Under the "Global Setting" section, manually add the "tmevtmgr_SkipRdpDr" key and set its value to "1".
  • [Global Setting]
  • tmevtmgr_SkipRdpDr=1
  1. Save the changes and close the file.
  2. Open the Apex One web console and go to the "Agents > Global Agent Settings" screen.
  3. Click "Save" to deploy the setting to agents. The Apex One server deploys the command to Apex One agents and adds the following registry entry on all Apex One agent endpoints:
  • Path:
  • HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\tmevtmgr\Parameters
  • Key: SkipRdpDr
  • Type: REG_DWORD
  • Value: 1

An issue related to the Unauthorized Change Prevention Service causes a slow system response while users browse the Internet.

Solution

This Critical Patch updates the Apex One Security Agent program to resolve this issue.

Procedure

To enable the new settings:

  1. Install this Critical Patch (see "Installation").
  2. Open the "Ofcscan.ini" file in the "\PCCSRV\" folder of the Apex One server installation directory using a text editor.
  3. Under the "Global Setting" section, manually add the "AegisUseQueriedCensusResult" key and set its value to "1".
  • [Global Setting]
  • AegisUseQueriedCensusResult=1
  1. Save the changes and close the file.
  2. Open the Apex One web console and go to the "Agents > Global Agent Settings" screen.
  3. Click "Save" to deploy the setting to agents. The Apex One server deploys the command to Apex One agents and adds the following registry entry on all Apex One agent endpoints:
  • Path:
  • HKEY_LOCAL_MACHINE\SOFTWARE\TrendMicro\AEGIS
  • Key: UseQueriedCensusResult
  • Type: REG_DWORD
  • Value: 1

Inaccurate information appear in the "Spyware\Grayware Restore" page of the Apex One web console.

Solution

This Critical Patch updates the Apex One server program to ensure that the page displays complete and accurate information.

Users encounter an error while editing the firewall exception template on the Apex One web console.

Solution

This Critical Patch updates the Apex One server program to resolve this issue.

The Apex One Administrator Notification email messages do not contain Scan type information because the related function cannot retrieve the information.

Solution

This Critical Patch updates the Apex One server program to resolve this issue.

An issue related to the Apex One BM module causes the Vembu BDR Virtual Drive application to stop responding.

Solution

This Critical Patch updates the Apex One BM module to resolve this issue.

The Apex One server stops unexpectedly when it encounters an empty tmp file while serializing deployment contents.

Solution

This Critical Patch updates the Apex One Server program to resolve this issue.

The Apex One agent Realtime Scan service cannot start after the login user name is replaced with a customized user account.

Solution

This Critical Patch enables the Apex One agent program to always replace the name with "Localsystem".

A large number of "root" log-in logs are generated in the Apex One system event log because Apex Central periodically sends policies and commands to Apex One.

Solution

This Critical Patch provides a way to minimize the number of "root" log-in logs in the system event log.

Procedure

To reduce the number of "root" login logs in the System Event log:

  1. Install this Critical Patch (see "Installation").
  2. Open the "ofcserver.ini" file in the "\PCCSRV\Private" folder in the Apex One server installation directory.
  3. Under the "INI_SERVER_SECTION" section, manually add the "EnableSSOPolicyLoginAuditing" and AddIPtoLoginAccount and set both to "0".
  • [INI_SERVER_SECTION]
  • EnableSSOPolicyLoginAuditing=0
  • AddIPtoLoginAccount=0
  1. Save the changes and close the file.
  • EnableSSOPolicyLoginAuditing
  • Values:0: (Default) reduces the number of "root" log-in logs1: Keep large number of "root" log-in logs
  • AddIPtoLoginAccount
  • Values:0: (Default) show the log-in account information without the IP address1: show the log-in account with the IP address

An issue prevents the Apex One Security Agent program from resolving the server DNS name while processing census queries. As a result, ransomware sample detection fails.

Solution

This Critical Patch updates the Apex One Security Agent program to resolve this issue.

To avoid this problem:

  1. install this hotfix (see "Installation").
  2. Open the "Ofcscan.ini" file in the "\PCCSRV\" folder on the Apex One server installation directory.
  3. Under the "Global Setting" section, manually add the following keys and values.
  • [Global Settings]
  • WRTmufeResolverFlag=0
  1. Save the changes and close the file.
  2. Open the Apex One web console and go to the "Agents > Global Agent Settings" screen.
  3. Click "Save" to deploy the setting to clients. The Apex One server deploys the command to Security Agent and adds the following registry entry on all Security Agent computers:
  • Path: HKEY_LOCAL_MACHINE\SOFTWARE\TrendMicro \PC-cillinNTCorp\CurrentVersion\URL Filtering
  • Key: WRTmufeResolverFlag
  • Type: DWORD
  • Value: 0

The "Duplicate Active Directory structure into the agent tree" Apex One server setting is disabled unexpectedly.

Solution

This Critical Patch updates the Apex One server program to resolve this issue.

A log synchronization issue between Apex One and Apex Central sometimes causes the virus log data that appears as "Access Denied" on Apex One console to display as "File Passed" on the Apex Central console.

When the Edge Relay Server registers to or unregisters from Apex One, the register/unregister task times out which can cause performance issues on the Edge Relay Server.

Solution

This Critical Patch extends the timeout setting of the register/unregister task to prevent the timeout issue.

An issue prevents users from enabling or disabling the Firewall through the global settings.

Solution

This Critical Patch resolves the issue so users with the correct privileges can enable or disable the Firewall through the global settings.

A Svrsvcsetup.exe exception occurs when users on Windows accounts attempt to connect to the SQL express database for Apex One.

Solution

This Critical Patch updates the Apex One server program to resolve this issue.

An issue prevents off premise agents from sending back detection logs through the Edge Relay Server.

Solution

This Critical Patch updates the Apex One server program to resolve this issue.

The Application Control criteria behaves abnormally after a switch in user accounts on a protected computer.

Solution

This Hotfix updates the Application Control Agent files to resolve this issue.

The Application Control agent cannot correctly allow or block applications launched by the operating system.

Solution

This Hotfix updates the Application Control Agent files to resolve this issue.

This Critical Patch updates permissions in the Apex One Agent program to enhance security.

This Critical Patch enhances the restoration of quarantined Spyware/Grayware files.

This Critical Patch updates the Apex One agent program to restrict the switch to MSI repair mode only to users with administrator privileges.

This Critical Patch updates the Data Loss Prevention™ (DLP) module to enhance security.

Remote Desktop Services may not be able to start on endpoints where Behavior Monitoring is enabled.

Solution

This Hotfix updates the Behavior Monitoring module to resolve this issue.

An issue related to the Spyware/Grayware Scan Engine causes the system performance to slow down.

Solution

This Hotfix updates the Spyware/Grayware Scan Engine to resolve this issue.

Users cannot add a RAM disk to the approved device lists because Data Loss Prevention™ (DLP) does not support this device.

Solution

This Hotfix updates the Data Protection module and Device List Tool (listDeviceInfo.exe) to resolve this issue.

After OfficeScan XG agents are migrated from an OfficeScan XG server to an Apex One server, the Network Adapter is automatically enabled on agents where DLP is enabled.

Solution

This Hotfix updates the Data Protection module to resolve this issue.

An ADO Recordset error causes some agents to disappear after users click the "Domain Hierarchy" button to sort agents in agent tree view.

Solution

This Hotfix updates the Apex One server program to resolve the error.

A delimiter issue in the target server IP address list prevents the Apex Central Automation API from moving Apex One Agents.

Solution

This Hotfix enables the Apex One server to recognize the comma "," as a valid delimiter for target server IP addresses. This helps ensure that the Apex Central Automation API can move Apex One Agents normally.

The Apex One Firewall may be unable to correctly identify the internal or external network status of an endpoint and therefore applies incorrect profile settings. This may prevent the endpoint from correctly accessing intranet locations.

Solution

This Hotfix updates the Apex One agent program to resolve this issue.

If users attempt to log on to the Apex One console using an Active Directory user account that contains a space character, the log on is unsuccessful.

Solution

This Hotfix updates the Apex One server program to resolve this issue.

The Device Control feature disables USB storage devices even when the security agent has been unloaded.

Solution

This Hotfix updates the Data Protection module to resolve this issue.

The USB device exception list in the DLP module supports serial IDs up to 32 digits only.

Solution

This Hotfix updates the Data Protection module and Apex One Server program to enable the USB device exception list to support longer serial IDs.

An Apex One Security Agent encounters a high CPU usage issue while installing updates.

Solution

This Hotfix updates the Active Update Module to resolve the issue.

A Microsoft™ Windows™ 10 upgrade fails during VBScript execution on protected computers.

Solution

This Hotfix updates the Apex One agent program to resolve this issue.

The Application Control agent cannot correctly allow or block applications launched by the operating system.

Solution

This Hotfix updates the Application Control Agent files to resolve this issue.

This Hotfix enables the Apex One Vulnerability Protection module to support the approved IP list.
NOTE: This feature requires the installation of Apex Central hotfix 5639 or above.

Procedure

To configure the approved IP list:

  1. Install this Hotfix (see "Installation").
  2. Open the Apex Central web console and go to the "Policies > Policy Resources > Intrusion Prevention Rules" screen.
  3. Click "Configure Exceptions" to add approved IP(s).
  4. Click "Save" to save the changes.
  5. Go to the "Policies > Policy Management" screen and deploy the policy to agents.

An issue prevents the Device List Tool (listDeviceInfo.exe) from retrieving certain SCSI disk device information.

Solution

This Critical Patch updates the Device List Tool (listDeviceInfo.exe) to resolve this issue.

Users encounter the following Microsoft™ Windows™ 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."

Solution

This Critical Patch updates the Apex One Security Agent program to resolve this issue.

The Data Loss Prevention™ (DLP) feature cannot block Adobe™ Acrobat™ Reader DC from saving files into a connected USB storage device.

Solution

This Critical Patch updates the Data Protection module to resolve this issue.

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.

Solution

This Critical Patch updates the Data Protection module to ensure that users will only be able to charge an iOS phone and not access it under the scenario described above.

An issue related to the DLP module causes certain developer tools to start slowly.

Solution

This Critical Patch updates the Data Protection module to resolve this issue.

An issue related to the DLP module causes a third-party application (Teleopti WFM) to stop responding unexpectedly.

Solution

This Critical Patch updates the Data Protection module to resolve this issue.

Certain Huawei webcam devices are recognized as "Modems".

Solution

This Critical Patch updates the Data Protection module to ensure such devices are correctly recognized as "Imaging Devices".

The Apex One Firewall also blocks network packets based on the connection status, as a result, some network packets may appear to be both blocked and accepted by the same rule in the corresponding Apex One Firewall logs.

Solution

This Critical Patch resolves this issue by updating the Apex One Security Agent program to allow users to disable the Firewall log for certain events.

Procedure

To configure Apex One to disable the Firewall logs certain events to help prevent the issue and deploy the solution globally:

  1. Install this Critical Patch (see "Installation").
  2. Open the "ofcscan.ini" file in the "\PCCSRV\" folder in the Apex One server installation directory.
  3. Under the "Global Setting" section, manually add the "PfwFeatureForResult" key and set it to "0".
  • [Global Setting]
  • PfwFeatureForResult=0
  1. Save the changes and close the file.
  2. Open the Apex One web console and go to the "Agents > Global Agent Settings" screen.
  3. Click "Save" to deploy the setting to agents. The Apex One server deploys the command to Apex One security agents and adds the following registry entries on all Apex One agent computers:
  • Path: HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\TrendMicro\PC-cillinNTCorp\CurrentVersion\Misc.
  • Key: PfwFeatureForResult
  • Type: DWORD
  • Value: 0
  1. Restart the Apex One security agent.

The Apex One SQL program returns a data error after users upgrade to Build 9120.

Solution

This Critical Patch updates the Apex One SQL program to resolve this issue.

An issue triggers the Apex One Behavior Monitoring feature to close the Microsoft Office application unexpectedly.

Solution

This Critical Patch updates the Apex One Security Agent program to resolve this issue.

An issue causes the "Spyware/Grayware Outbreaks Alert" widget to return query results from the wrong time range.

Solution

This Critical Patch updates the Apex One server program to ensure that the widget returns logs generated within the specified time range.

The Active Directory (AD) displays abnormally after AD synchronization when the Organizational Unit (OU) name contains a "TAB" character.

Solution

This Critical Patch enables users to configure Apex One to handle OU names that contain a "TAB" character.

Procedure

(Video) Apex One Installation Process

To configure Apex One to handle OU names that contain a "TAB" character:

  1. Install this Critical Patch (see "Installation").
  2. Open the "ofcserver.ini" file in the "\PCCSRV\Private\" folder in the Apex One server installation directory.
  3. Under the "[INI_AD_INTEGRATION_SECTION]" section, manually add "AdScopeSyncUpBatchSeparatorType=1"
  • [INI_AD_INTEGRATION_SECTION]
  • AdScopeSyncUpBatchSeparatorType=1

NOTE:
0: If the OU name does not contain a "TAB" (default) 1: If the OU name contains a "TAB"

  1. Save the changes and close the file.

An "osp_cb_dbGetClientsByCompName" stored procedure leakage issue prevents the "EnableCheckClientComputerName" hidden key from working normally. When this happens, duplicate hostnames are not purged automatically even when the key is enabled.

Solution

This Critical Patch resolves the memory leak issue to ensure that the "EnableCheckClientComputerName" hidden key works normally.

The following message displays on the "Result" field of Virus/Malware logs on the web console when the filename of an infected file contains certain special characters.

"Quarantine is successful at agent, but unable to send the quarantined file to the designated quarantine folder. Refer to the online help for solutions."

Solution

This Critical Patch updates the Apex One Security Agent program to resolve this issue.

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

Solution

This Critical Patch updates the Apex One Security Agent program to resolve this issue and ensure that WRS can correctly detect HTTPS URLs on the Edge web browser.

After applying Apex One Critical Patch 9167, when users generate a setup package while "ForceRefresh=1" in "ofcscan.ini" and use it to install an agent, the Apex One NT Listener service may remain busy and the newly-installed agent cannot be moved to another server using the IpXfer tool.

Solution

This Critical Patch updates the Apex One Security Agent program to resolve this issue.

The "Current Version" information for the Common Firewall Driver on the Agent Updates widget is not accurate.

Solution

This Critical Patch ensures that the correct "Current Version" information displays for the Common Firewall Driver on the Agent Updates widget.

The Real-time Scan feature may use up too much memory which can cause an Apex One agent computer to stop responding.

Solution

This Critical Patch updates the Apex One agent program to resolve the issue.

This Critical Patch updates the file privileges for the database log file in the server installation folder for enhanced security.

This Critical Patch helps prevent false Trend Micro process alerts during Yara investigations.

This Critical Patch fixes the Improper Access Control Privilege Escalation security issue.

This Critical Patch ensures that when an administrator grants users privileges to configure Manual Scan settings, Real-time Scan settings, Scheduled Scan settings and Mail Scan through the Security Agent console, these settings will not be overwritten by changes made through the Apex One console or Apex Central console.

After configuring Data Protection keys that monitor file uploads to websites, Security Agents may still randomly block file uploads to approved sites.

Solution

This Hotfix updates the Data Protection module to resolve this issue.

When users run a third-party inventory scanning software on a security agent computer, the Apex One Security Agent does not report the correct product version properly.

Solution

This Hotfix updates the Apex One Security Agent program to resolve this issue.

The Microsoft Windows login screen may stop unexpectedly after migrating an OfficeScan XG Security Agent to Trend Micro Apex One.

Solution

This Hotfix updates the Apex One Security Agent program to resolve this issue.

An Update Agent running on a 64-bit operating system and which updates agent programs from itself may not be able to upgrade from OfficeScan XG Service Pack 1 to Trend Micro Apex One successfully.

Solution

This Hotfix updates the Security Agent program to resolve this issue.

This Hotfix resolves a payload execution security issue.

This Hotfix helps ensure that Apex One Security agents do not send duplicate virus logs to the server.

An issue causes Apex One Security Agents to appear offline after an agent upgrade.

Solution

This Critical Patch updates the Apex One Security Agent program to resolve this issue.

Procedure

To apply the solution:

  1. Install this Critical Patch (see "Installation").
  2. Open the "ofcscan.ini" file in the "\PCCSRV\" folder on the Apex One server installation directory.
  3. Under the "Global Setting" section, manually add the following keys and values.
  4. Save the changes and close the file.
  • [Global Setting]
  • DelayedAutostartListen=1
  1. Open the Apex One web console and go to the "Agents > Global Agent Settings" screen.
  2. Click "Save" to deploy the setting to clients. The Apex One server deploys the command to Security Agent and adds the following registry entry on all Security Agent computers:
  • Path: HKEY_LOCAL_MACHINE\SOFTWARE\TrendMicro \PC-cillinNTCorp\CurrentVersion\Misc.
  • Key: DelayedAutostartListen
  • Type: DWORD
  • Value: 1

An issue prevents Apex One Security Agents from applying hotfixes successfully from the Apex One server.

Solution

This Critical Patch updates the Firewall module in Security Agents to resolve this issue.

Microsoft™ Word stops unexpectedly on Apex One Security Agent computers.

Solution

This Critical Patch resolves this issue.

Pop-up windows from internal websites do not display when Web Reputation is enabled on Security Agents.

Solution

This Critical Patch updates the Apex One Security Agent program and allows users to configure Apex One to skip certain events that cause the issue.

Procedure

To configure Apex One to skip certain events that cause pop-up windows to be blocked, deploy the following solution globally:

  1. Install this Critical Patch (see "Installation").
  2. Open the "ofcscan.ini" file in the "\PCCSRV\" folder in the Apex One server installation directory.
  3. Under the "Global Setting" section, manually add the "OspreyAsyncServerLookup" key and "UmPassThruFlags" key and set the following values:
  • [Global Setting]
  • OspreyAsyncServerLookup=0
  • UmPassThruFlags=256
  1. Save the changes and close the file.
  2. Open the Apex One web console and go to the "Agents > Global Agent Settings" screen.
  3. Click "Save" to deploy the setting to agents. The Apex One server deploys the command to Apex One security agents and adds the following registry entries on all Apex One agent computers:
  • Path: HKEY_LOCAL_MACHINE\SOFTWARE\TrendMicro\Osprey\Scan\Common\HttpManager\config
  • Key: AsyncServerLookup
  • Type: DWORD
  • Value: 0
  • Path: HKEY_LOCAL_MACHINE\SOFTWARE\TrendMicro\AEGIS
  • Key: UmPassThruFlags
  • Type: DWORD
  • Value: 0x100 (256)
  1. Restart the Apex One Security Agent.

An issue related to the "cgiChkMasterPwd.exe" process may cause the Apex One server to stop unexpectedly.

Solution

This Critical Patch updates the Apex One server program to resolve the issue.

"Svrsvcsetup.exe" may stop unexpectedly during installation of Apex One Patch 3 and any later build.

Solution

This Critical Patch updates the Apex One server program to resolve the issue.

An Apex One server with Security Agent installed uses the agent proxy settings automatically which prevents Apex One from subscribing to the Suspicious Object lists on the registered Apex Central server.

Solution

This Critical Patch updates the Apex One program to resolve the issue.

When connecting to the census server, Security Agents do not bypass the proxy server even when configured to do so through the proxy auto-configuration (PAC) script file.

Solution

This Critical Patch updates the Apex One Security Agent program to resolve this issue.

An issue related to the VSAPI decompress function may cause a vulnerability in the Apex One program.

Solution

This Critical Patch resolves the issue to remove the vulnerability.

The Apex One server uses SSL port "4343" for server-agent communication, but the "TmCCSF.exe" agent process connects to the Apex One server port "443" in certain scenarios.

Solution

This Critical Patch updates the Apex One Security Agent program to resolve this issue.

The spyware scan feature of Manual Scan in Apex One Security Agents is affected by an Improper Access Control Privilege Escalation vulnerability.

Solution

This Critical Patch updates the Apex One Security Agent program to remove the vulnerability.

This Critical Patch enables Apex One to support the application filter hash matching feature for the Firewall Policy Exception so that users are able to specify applications to use the file hash value on.

Procedure

To enable the new settings:

  1. Install this Critical Patch (see "Installation").
  2. Open the "Ofcscan.ini" file in the "\PCCSRV\" folder of the Apex One server installation directory using a text editor.
  3. Under the "Global Setting" section, manually add the "EnableHashMatch" key and set its value to "1".
  • [Global Setting]
  • EnableHashMatch=1
  1. Save the changes and close the file.
  2. Open the Apex One web console and go to the "Agents > Global Agent Settings" screen.
  3. Click "Save" to deploy the setting to agents. The Apex One server deploys the command to Apex One security agents and adds the following registry entry on all Apex One security agent computers:
  • Path:
  • For x64 platforms: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\TrendMicro\PC-cillinNTCorp\CurrentVersion\PFW\
  • For x86 platforms: HKEY_LOCAL_MACHINE\SOFTWARE\TrendMicro\PC-cillinNTCorp\CurrentVersion\PFW\
  • Key: EnableHashMatch
  • Type: REG_DWORD
  • Value: 1

This Critical Patch resolves an Out-Of-Bounds Write security issue in Apex One.

This Critical Patch resolves a Server-Side Request Forgery Information Disclosure security issue in Apex One.

This Critical Patch fixes the exposure of sensitive information to an unauthorized actor security issue.

This Critical Patch resolves an Out-Of-Bounds Read security issue in Apex One.

The Active Directory (AD) structure cannot be synchronized successfully with the Apex One server when the AD forest is large.

Solution

This Hotfix updates the Apex One server program to resolve this issue.

Apex One Off-premise Security Agents may still appear "Offline" on the Apex One web console even when these agents are already connected to the Edge Relay Server and are able to successfully receive the enhanced security policies across the network.

Solution

This Hotfix updates the Apex One SQL package to resolve the issue.

The domain users and groups used in User-Defined Rules for Application Control criteria can't take correct action based on criteria settings.

Solution

This Hotfix updates the Application Control files to resolve this issue.

Certain applications may take a long time to launch while the Device Control feature is enabled on a protected computer.

Solution

This Hotfix updates the Behavior Monitoring module to resolve this issue.

Procedure

To apply and deploy the solution globally:

  1. Install this Hotfix (see "Installation").
  2. Open the "ofcscan.ini" file in the "\PCCSRV\" folder of the Apex One server installation directory using a text editor.
  3. Under the "Global Setting" section, manually add the following key and set its value to "1".
  • [Global Setting]
  • AegisSkipExplorerCreateMutant=1
  1. Save the changes and close the file.
  2. Open the Apex One web console and go to the "Agents > Global Agent Settings" screen.
  3. Click "Save" to deploy the setting to agents. The Apex One server deploys the command to security agents and adds the following registry entry on all security agent endpoints:
  • Path: HKEY_LOCAL_MACHINE\SOFTWARE\TrendMicro\AEGIS
  • Key: SkipExplorerCreateMutant
  • Type: DWORD
  • Value: 1

The "Summary/Dashboard" screen of the Apex One web console displays as a blank page. This happens because the specified Microsoft™ Windows™ account does not have sufficient web service framework access permissions.

Solution

This Hotfix updates the Apex One server program to resolve the issue.

After applying Trend Micro Apex One Patch 3, the Security Agent status may not display accurately on the Apex One web console. This occurs if the existing Apex One SQL database was not migrated correctly which may corrupt the database.

Solution

This Hotfix updates the Apex One server program to resolve this issue.

Users cannot install the Security Agent remotely from the Apex One Web Console and get the "An error occurred. Make sure your network connection is active and that the Apex One service is running. If you encounter this error again, contact your support provider for troubleshooting assistance." message appearance.

Solution

This Hotfix updates the Apex One server program to resolve this issue.

This Hotfix enables users to configure the Apex One console to only display the Summary/Dashboard screen to users who log on using the "root" account. Enabling this feature will prevent all other accounts from viewing any dashboard widgets/data after logging on to the Apex One console.

Procedure

To configure Apex One to restrict access to the Dashboard to "root" account users:

  1. Install this Hotfix (see "Installation").
  2. Open the "ofcserver.ini" file in the "\PCCSRV\Private" folder on the Apex One server installation directory.
  3. Under the "INI_SERVER_SECTION" section, manually add the "HideDashboardForNonRoot" key and set its value to "1".
  • [INI_SERVER_SECTION]
  • HideDashboardForNonRoot=1
  1. Save the changes and close the file.

Users may not be able to view Predictive Machine Learning Log Details on the Apex One web console when the file name or the file path contains Japanese characters.

Solution

This Patch updates the Apex One server program and SQL package to resolve the issue.

Users will not be able to uninstall a security agent using the "PccNTMon.exe -m <uninstallation password>" command if the agent uninstallation password contains "-c".

Solution

This Patch updates the Apex One Security Agent program to resolve this issue.

The following error occurs when users run the "autopcc.exe -f -u" command onan agent computer.

"Unable to upgrade/update the Apex One Security Agent. At least one file cannot be replaced. Unload the Apex One Security Agent and try again."

Solution

This Patch updates the Apex One server program to resolve this issue.

When an incorrectly formatted Device Control settings file is loaded, Apex One Real-time Scan does not start as expected.

Solution

This Patch updates the Apex One Security Agent program to resolve this issue.

Apex One cannot retrieve the correct domain information for agents that are in the Read-Only Domain Controller (RODC).

Solution

This Patch updates the Apex One agent program to resolve this issue.

The Apex One Master Service stops responding repeatedly after Apex One Patch 3 Build 8378 is applied.

Solution

This Patch updates the Apex One server program to resolve this issue.

Sometimes, an issue related to the "tmescore.sys" and "tmesutil.sys" drivers of the Apex One Endpoint sensor may trigger blue screen of death (BSOD) on Dell laptops.

Solution

This Patch updates the Apex One security agent program to resolve this issue.

The Apex One server may not display Security Agent logs on the web console.

Solution

This Patch updates the Apex One server program to prevent this issue.

The Apex One Common Client Solution Framework service may stop unexpectedly and create multiple dump files due to a threading issue.

Solution

This Patch updates the Apex One Security Agent program to resolve the issue.

The Apex One Common Client Solution Framework may stop unexpectedly on the Security Agents.

Solution

This Patch updates the Apex One Security Agent program to resolve this issue.

Apex One uses a version of PHP that may cause vulnerabilities.

Solution

This Patch upgrades PHP to version 7.4.9 to prevent these vulnerabilities.

Policy deployment failure issue when upgrade from Apex One B2xxx or earlier build.

Solution

This Patch updates the Apex One server program to resolve this issue.

An issue prevents External Agents from querying the Global Web Rating server using HTTPS.

Solution

This Patch resolves the issue so External Agents can query the Global Web Rating server using HTTPS normally.

When Apex One Security Agents are installed in Virtual Desktop Infrastructure (VDI) environment, virtual desktops are created and abandoned quickly which leaves a large number of duplicate machine name entries on the Apex One server web console. The entries will not have the same IP Address and MAC Address. This makes the total security agent count inaccurate. This Patch enables Apex One to delete duplicate machine name entries.

Procedure

To configure Apex One to delete the duplicate machine name entries:

  1. Install this Patch (see "Installation").
  2. Open the "ofcserver.ini" file in the "\PCCSRV\Private" folder on the Apex One server installation directory.
  3. Under the "INI_SERVER_SECTION" section, manually add the "EnableCheckClientComputerName" key and set its value to "1".
  • [INI_SERVER_SECTION]
  • EnableCheckClientComputerName=1
  1. Save the changes and close the file.
  2. Restart the Apex One Master Service.
  3. Perform a restart on the affected Apex One security agents.

This Patch updates the Server Migration tool program to prevent binary version mismatch issues.

Security Agent installation support for the Windows 10 October 2020 Update (20H2).

Installing Trend Micro Apex One Patch 3 also installs the Support Connector tool by default. This tool creates a scheduled task "Trend Micro Apex One Security Services Support Connector" and runs an hourly poll on the backend. This Patch allows users to disable the polling behavior. Refer to "https://success.trendmicro.com/solution/000232603" for details.

This Patch adds the SQL Transfer Tool to provide support to move the Endpoint Sensor database (if installed on the same SQL Server as the Apex One database).

This Patch improves the Data Loss Prevention forensic data upload to increase the maximum uploaded file size to 100MB. To better facilitate the import of larger files, the queue mechanism has been enhanced to minimize the risk of upload timeouts. In order to enable the larger file size upload, some manual configuration steps are required on the Apex One and Apex Central servers. For the detailed steps, see https://success.trendmicro.com/solution/000282727.

This Patch updates the Apex One information in the server and changes the default installation folder name to "Security Agent" for freshly installed agents.

This Patch adds Enhanced Support Services for Apex One server. This is part of a future update channel that will be used for rapid deployment of solution patches. Refer to the following website for more details.https://success.trendmicro.com/solution/000283789

An issue prevents the Trend Micro Apex One Data Protection Service from starting after Apex One Critical Patch 8417 is applied on a computer running on the Microsoft™ Windows™ 7 platform.

Solution

This Critical Patch updates the Data Protection module to resolve this issue.

When the Apex One Data Protection Service is enabled on the Apex One Security Agent, sharing files over a network may be delayed or blocked.

Solution

This Critical Patch updates the Data Protection module to resolve this issue.

DLP Violation Detection alerts may be generated through the HTTP/HTTPS channels when users drag files onto web browsers and the action is not for file upload.

Solution

This Critical Patch updates the Data Protection module to resolve this issue.

An issue related to the Apex One Data Protection Service can disable the Wireless NIC interface unexpectedly when users start the Mozilla(R) Firefox(R) web browser on protected computers.

Solution

This Critical Patch updates the Data Protection module to resolve this issue.

It may take a long time to share files between protected computers over a network when the Apex One Data Protection Service is enabled on the Apex One security agent.

Solution

This Critical Patch updates the Data Protection module to resolve this issue.

Sometimes, the Dashboard page of the Apex One web console appears as a blank page.

Solution

This Critical Patch updates the Apex One server program to resolve this issue.

After applying Apex One Patch 3, users may not receive email notifications for security risk detections.

Solution

This Critical Patch updates the TMNotify module to resolve this issue.

An ADOexception error on the Apex One Database Service may cause inaccurate agent count information to display on the "Managed Agents" group of the Endpoint Status Widget and on the "Total number of agents" field on the "Update Summary" page of the Apex One web console.

Solution

This Critical Patch updates the Apex One server program to resolve this issue.

Garbled characters may appear under the "Infected File/Object" column in Virus/Malware Logs on the Apex One web console.

Solution

This Critical Patch updates the Apex One Security Agent program to resolve this issue.

"Google Drive" displays in the "Channel" field in Trend Micro Data Loss Prevention™ (DLP) logs when it should be "OneDrive".

Solution

This Critical Patch updates the Data Protection module to resolve this issue.

On the "Agents > Agent Management > Status" page of the Apex One web console, the platform information of agents installed on the Microsoft™ Windows™ Server 2019 platform appear as Windows Server 2016.

Solution

This Critical Patch updates the Apex One server program to resolve this issue.

After applying Apex One Critical Patch 8400, users cannot save changes to the Web Reputation Settings on the web console.

Solution

This Critical Patch updates the Apex One server program to resolve this issue.

After applying Apex One Critical Patch 8400, the confirmation message does not display after users click "Save" on the "Spyware/Grayware Approved List" page.

Solution

This Critical Patch updates the Apex One server program to resolve this issue.

After applying Apex One Patch 3, the "Logs > System Events" page of the Apex One web console displays a blank page.

Solution

This Critical Patch updates the Apex One server program to resolve this issue.

Sometimes, an issue related to the Apex One Data Protection feature prevents users from opening an encrypted file through a third-party software.

Solution

This Critical Patch updates the Data Protection module to resolve the issue.

The Trend Micro Data Loss Prevention™ (DLP) module cannot block webmail in "Outlook.com" on any web browser.

Solution

This Critical Patch updates the DLP module to resolve this issue.

After an Apex One agent switches scan methods from smart scan to conventional scan, it becomes a conventional scan agent but its information still appear in the update logs of the Smart Scan Agent Pattern.

Solution

This Critical Patch resolves this issue by enabling Apex One to check the scan method of agents before writing agent component update logs.

After applying Apex One Patch 2, you may not be able to save new custom Security Agent domain names or group names on the "Add IP Address Grouping" screen if the name contains certain characters. Existing domains containing the characters may also appear garbled on the "Add IP Address Grouping" screen.

Solution

This Critical Patch updates the Apex One server program to prevent this issue.

The Apex One Behavior Monitoring feature may cause high CPU usage issues in protected computers.

Solution

This Critical Patch updates the Behavior Monitoring module to resolve the issue.

An issue prevents the Server Migration tool from importing the Trend Micro OfficeScan™ 11.0 Service Pack 1 server settings to Apex One.

Solution

This Critical Patch updates the Server Migration tool program to resolve this issue.

An issue prevents users from relocating Apex One agents to another server or another directory on the same server using the Apex Central Automation API.

Solution

This Critical Patch updates the Apex One server program to resolve this issue.

After applying Apex One Patch 3, users cannot move Security Agents to another server using the EnableMoveNATClient feature. This happens due to an enhanced security check mechanism for moving Security Agents in Patch 3.

Solution

This Critical Patch updates the security check mechanism to ensure that you can move Security Agents using the EnableMoveNATClient feature.

Users may receive false positive C&C callback alerts on Apex One security agents. This happens because the Network Content Inspection Engine (NCIE) reloads every few seconds.

Solution

This Critical Patch resolves the issue by updating the Apex One agent program.

The memory usage of the Apex One Security Agent console process "PccNt.exe" increases unexpectedly when it runs for a long time.

Solution

This Critical Patch updates the Apex One Security Agent program to resolve this issue.

The Trend Micro Unauthorized Change Prevention Service may slow down the performance of Microsoft™ Word applications when the officeatwork Add-In is enabled.

Solution

This Critical Patch updates the Behavior Monitoring module and enables users to configure Apex One to skip certain events to help prevent the issue.

Procedure

To configure Apex One to skip certain events to help prevent the issue and deploy the solution globally:

  1. Install this Critical Patch (see "Installation").
  2. Open the "ofcscan.ini" file in the "\PCCSRV\" folder in the Apex One server installation directory.
  3. Under the "Global Setting" section, manually add the "DisableLoadImageNotify" key and "AegisDisablePostCloseSync" key and set both to "1".
  • [Global Setting]
  • DisableLoadImageNotify=1
  • AegisDisablePostCloseSync=1
  1. Save the changes and close the file.
  2. Open the Apex One web console and go to the "Agents > Global Agent Settings" screen.
  3. Click "Save" to deploy the setting to agents. The Apex One server deploys the command to Apex One security agents and adds the following registry entries on all Apex One agent computers:
  • Path: HKEY_LOCAL_MACHINE\SOFTWARE\TrendMicro\AEGIS
  • Key: DisablePostCloseSync
  • Key: DisableLoadImageNotify
  • Type: DWORD
  • Value: 1
  1. Restart the Apex One security agent.

Users may not be able to send enhanced security policies to Security Agents across the network successfully when managing the Apex One server from the Apex Central web console. This happens because the specified Microsoft Windows account that manages the existing Apex One SQL database does not have sufficient web service framework access permissions when writing the related debug logs.

Solution

This Critical Patch updates the Apex One server program to prevent this issue from occurring.

Sometimes, users may not be able to run a security assessment on Security Compliance for Unmanaged Endpoints successfully.

Solution

This Critical Patch updates the Apex One server program to resolve this issue.

Certain third-party web applications may not work properly on endpoints with the Apex One Firewall enabled.

Solution

This Critical Patch resolves the issue by updating the Apex One Security Agent program and adjusting the service flow of the Trend Micro NDIS 6.0 Filter Driver (TmLWF.sys) in the Apex One Firewall.

There is a typographical error in the "Initiate Unloading" button on the "Agent Uninstallation" page of the Apex One French web console.

Solution

This Critical Patch updates the Apex One server files to correct the error.

NOTE: Please refer to the following link for the steps to show how an Administrator can unload single or multiple Apex One agents simultaneously from the Apex One web console if customer need: https://success.trendmicro.com/intkb/solution/1117401

On the Windows 10 platform, the SYSTEM process reports a commit size while the DLP service is running on agent computers.

Solution

This Critical Patch updates the DLP module to resolve this issue.

The DLP feature may block the USB Scanner application unexpectedly.

Solution

This Critical Patch updates the DLP module to resolve this issue.

An issue prevents users from enabling the DLP addin for Microsoft Outlook.

Solution

This Critical Patch updates the DLP module to resolve this issue.

A security agent's status may remain "Offline" and its location indicated as "external" even when it is already connected to the Apex One server.

Solution

This Critical Patch updates the Apex One server program to resolve this issue.

Sometimes, Apex One security agents cannot download pattern files from the Apex One server normally because the Apex One Real-time Scan ("Ntrtscan.exe") service runs into a deadlock situation.

Solution

This Critical Patch updates the Apex One security agent program to resolve the issue.

Users that do not have the required permissions may be able to access the Apex One (Mac) plugin console.

Solution

This Critical Patch updates the permission checkpoint logic to resolve the issue.

The Apex One Security Agent cannot retrieve the latest Application Control criteria because the Application Control policy content is incomplete.

Solution

This Critical Patch updates the Application Control policy files to resolve this issue.

An issue prevents users from selecting or deselecting applications in the Application Reputation List of the Application Control Criteria.

Solution

This Critical Patch updates the Application Control files to resolve this issue.

The Application Control certificate criteria does not work normally when matching by certificate types.

Solution

This Critical Patch updates the Application Control files to resolve this issue.

Users cannot move agents to a specific domain on the target server using the EnableMoveNATClient feature in the following command format:

  • #moveto_<target Server IP or hostname>:HTTP port|HTTPS port\targetdomain

This happens because the backslash "\" prevents the feature from retrieving the full domain name from the SQL database.

Solution

This Critical Patch updates the Apex One agent program to resolve this issue.

After applying Apex One Patch 3, the major version of the Virus Scan Engine should be "12", but appears as "10" on the "Update Summary" page.

Solution

This Critical Patch ensures that the correct major version information for the Virus Scan Engine appears on the "Update Summary" page.

After a Security Agent unsuccessfully attempts an upgrade, the error log incorrectly displays the Apex One server hostname, not the endpoint hostname.

Solution

This Critical Patch updates the Apex One Security Agent to properly record the endpoint hostname in the error logs.

Customized DLP templates disappear after applying Apex One Patch 3, because Patch 3 does not migrate these templates.

Solution

This Critical Patch adds the DLP templates migration process to prevent this issue.

On the Apex One web console, firewall logs do not display any process name information for incoming traffic detected.

Solution

This Critical Patch updates the Apex One server program to prevent this issue.

Procedure

To configure Apex One to skip certain events to help prevent the issue and deploy the solution globally:

  1. Install this Critical Patch (see "Installation").
  2. Open the "ofcserver.ini" file in the "\PCCSRV\Private" folder in the Apex One server installation directory.
  3. Under the "INI_SERVER_SECTION" section, manually add the "CFWShowAllPV" key and set it to "1".[INI_SERVER_SECTION]CFWShowAllPV=1
  4. Save the changes and close the file.
  5. Restart the Master services.

After applying Apex One Patch 3, Apex One agents cannot update the Contextual Intelligence Query Handler component to version 1.100.1073.

Solution

This Critical Patch updates the install process to prevent this issue.

Outdated Apex One agents do not appear on the dashboard after users click the outdated link.

Solution

This Critical Patch updates the Apex One Server program to prevent this issue.

The Apex One scan exclusion setting does not work properly when there are no exclusions at the root level.

Solution

This Critical Patch updates certain SQL stored procedures to solve this issue.

Sample files are not sent to the Trend Micro Deep Discovery Analyzer server because the Apex One Deep Discovery service has stopped unexpectedly.

Solution

This Critical Patch updates the Apex One server program to resolve this issue.

False DLP alerts may be generated when users run "WinScp.exe".

Solution

This Critical Patch updates the DLP module to resolve this issue.

An issue related to the Trend Micro Browser Exploit Prevention module may cause an Out-of-bounds Read vulnerability.

Solution

This Critical Patch updates the Trend Micro Browser Exploit Prevention module to resolve the vulnerability.

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

Solution

This Critical Patch updates the Apex One server program to remove the vulnerability.

The Suspicious Connection Service stops after Apex One Patch 3 is installed on an external agent that does not directly connect to the Apex One server.

Solution

(Video) Install agent Apex One as a service - Trendmicro

This Critical Patch updates the Apex One Security Agent program to resolve the issue.

After applying Apex One Patch 3, Trend Micro Apex One Antivirus appears multiple times in the query results when users check for antivirus software on a system using the following command:

wmic /namespace:\\root\securitycenter2 path antivirusProduct get /format:list

Solution

This Critical Patch updates the Apex One agent program to resolve this issue.

Third-party FTP applications may experience slow file transfer when the Apex One Data Protection Service is enabled on the Security Agent.

Solution

This Critical Patch updates the Data Protection module to resolve this issue.

After configuring the Data Protection keys that monitor file uploads to websites, Data Protection appears to randomly block uploads to any website.

Solution

This Critical Patch updates the Data Protection module to resolve this issue.

The Apex One Master Service stops unexpectedly after users upgrade an OfficeScan XG server to Apex One Patch 3.

Solution

This Critical Patch updates the Apex One server program to resolve this issue.

An issue prevents users from migrating an Apex One SQL server using SQL 2008 R2.

Solution

This Critical Patch updates the Apex One SQL program to prevent this issue.

Users may still be able to access USB storage devices even after setting the Device Control permissions for USB Storage Devices to "Block".

Solution

This Critical Patch updates DLP Endpoint SDK 6.2 to add a switch that responds when a device status changes to help prevent the issue from occurring.

Procedure

To enable the switch to respond when the device status changes:

  1. Install this Critical Patch (see "Installation").
  2. Open the "dlp.ini" file in the "\PCCSRV\Private\" folder of the Apex One server installation directory using a text editor.
  3. Under the "Configure" section, manually add the "DEVICE_CHANGE_QUICK_RESP" key and set its value to "true".
  • [Configure]
  • DEVICE_CHANGE_QUICK_RESP=true
  1. Save the changes and close the file.
  2. Open the Apex One web console and go to the "Agents > Agent Management > Select domains or agents > Settings > DLP settings" screen.
  3. Click "Save" to deploy the setting to agents". The Apex One server deploys the setting to Apex One agents and adds the following key in the "dsa.pro" file in the "\Windows\System32\dgagent\" folder:
  • DEVICE_CHANGE_QUICK_RESP=true
  1. Restart the Apex One agent machines.

Security Agent computers running on Microsoft™ Windows™ 10 May 2020 Update (20H1) may experience blue screen of death (BSOD) after waking up from sleep mode.

Solution

This Critical Patch updates the Behavior Monitoring module to resolve the issue.

This Critical Patch allows administrators to move agents to a specific domain on the target server using the EnableMoveNATClient feature by creating domain hierarchy under the "#moveto_<target Server IP or hostname>:HTTP port|HTTPS port" domain on the source server.

Procedure

To move agents to a specific domain on the target server using the EnableMoveNATClient feature:

  1. Install this Critical Patch (see "Installation").
  2. Open the "ofcscan.ini" file in the "\PCCSRV\" folder on the Apex One server installation directory.
  3. Add the following keys under the "Global Setting" section and set the following values:
  • [Global Setting]
  • EnableMoveNATClient=1, enables administrators to move unreachable clients between servers
  • MoveNATClientDomainPrefix=#moveto_, (default) domain prefix for moving unreachable clients
  1. Save the changes and close the file.
  2. Open the Apex One web console and go to the "Agents > Global Agent Settings" screen.
  3. Click "Save" to deploy the setting to agents. The Apex One server deploys the command to security agents and adds the following registry entries on all security agent computers:
  • Path: HKLM\SOFTWARE\TrendMicro\PC-cillinNTCorp\CurrentVersion\Misc.\
  • Key: EnableMoveNATClient
  • Value: 1
  • Path: HKLM\SOFTWARE\TrendMicro\PC-cillinNTCorp\CurrentVersion\Misc.\
  • Key: MoveNATClientDomainPrefix
  • Value: #moveto_
  1. Open the Apex One web console and go to the "Agents > Agent Management > Manage Agent Tree > Add Domain" page.
  2. Specify the domain name "#moveto_<target Server IP or hostname>:HTTP port|HTTPS port".For example, "#moveto_10.1.1.1:80|443" or "#moveto_serverB:8080|4343".
  • NOTES:
  • Use the target Server IP if Apex One agents identify the server by IP while installing the target server.
  • Use the target Server hostname if Apex One agents identify the server by hostname while installing the target server.
  1. Create the domain hierarchy under "#moveto_<target Server IP or hostname>:HTTP port|HTTPS port" domain or drop existing domain to "#moveto_<target Server IP or hostname>:HTTP port|HTTPS port" domain.For example,
    • Apex One Server
    • ----- #moveto_serverB:8080|4343
    • ---------- | subdomain1 |
    • --------------- | subdomain2 |
  2. Move the agent to the specific domain in the domain hierarchy created in step 9.For example, put agent in subdomain2 domain
    • Apex One Server
    • ----- #moveto_serverB:8080|4343
    • ---------- | subdomain1 |
    • --------------- | subdomain2 | agent
  • NOTES: You may skip this step if you drop existing domain in step 9 and the agent has existed in the domain.
  1. The agent will be moved to the specific domain on the target server.For example,
    • Apex One Server
    • ----- | subdomain1 |
    • ---------- | subdomain2 | agent

This Critical Patch enables the Behavior Monitoring feature to handle "svchost.exe" events and adds the following registry entry on all Security Agent computers.

  • Path: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\tmactmon\Parameters
  • Key: SendCreateProcessFromInspectionProcess
  • Type: DWORD
  • Value: 1

The Apex One Web Reputation feature cannot block websites in the Microsoft™ Edge™ Chromium web browser.

Solution

This Patch resolves the issue by enabling Apex One to support the Edge Chromium web browser.

The Trend Micro Data Loss Prevention™ (DLP) module generates two violation logs for a single Webmail action.

Solution

This Patch updates the DLP module to resolve this issue.

Procedure

To configure the Sync mode cache (for blocking action) setting:

  1. Install this hotfix (see "Installation")
  2. Open the "dlp.ini" file in the "\PCCSRV\Private\" folder on the Apex One server.
  3. Under the "Configure" section, manually add the following setting.
  • [Configure]
  • SYNC_MODE_FILE_CACHE=true
  1. Save the changes and close the file.
  2. Open the Apex One web console and click "Agents > Agent Management > Select domains or agents > Settings > DLP settings".
  3. Click "Save" to deploy the settings to agents.
  4. The Apex One server deploys the settings to Apex One agents.

The Apex One firewall service may block the connection to version 2.4.8 of OpenVPN.

Solution

This Patch updates the Apex One Security Agent program to resolve this issue.

Installation of Trend Micro Apex One Patch 3 may be unsuccessful due to required files being locked by unknown processes.

Solution

This patch resolves the issue by ensuring that the necessary files can be released and updated.

After installing Trend Micro Apex One Patch 3, Apex One (Mac) users were unable to log on to the console if the latest version of Apex One (Mac) was not installed.

Solution

This patch resolves the issue and ensures users can continue to access the Apex One (Mac) console.

During installation of Trend Micro Apex One Patch 3, an error may occur that prevented the necessary upgrade of Application Control files.

Solution

This patch resolves the Application Control issue.

A possible vulnerability existed that could allow an attacker to inject arbitrary files into an update file path if the Apex One server updated from a local directory.

Solution

This patch fixes the vulnerability.

Trend Micro Apex One was found to have the Improper Access Control Privilege Escalation Vulnerability.

Solution

This patch fixes the vulnerability.

vcruntime140.dll missing error when upgrading agents from OfficeScan XG / XG SP1

Solution

This patch resolves the agent upgrade issue.

If the following two keys have been added to an agent, the "PccNTMon.exe -n <password>" command will not work to unload the agent.

  • Path: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\tmactmon\Parameters
  • Keys: SkipVirtualHarddisk
  • Type: DWORD
  • Value: 1 or 0
  • Path: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\tmevtmgr\Parameters
  • Keys: SkipDeviceVolume
  • Type: DWORD
  • Value: 1 or 0

Solution

This Patch updates the Behavior Monitoring Module to resolve this issue.

In non-English Apex One versions, garbled characters appear in the exported CSV file of certain logs.

Solution

This Patch updates the Apex One server program to resolve this issue.

Security Agents can prevent ransomware attacks that leverage a vulnerability in the Encrypting File System (EFS) for Windows.

This Patch removes the "Exclude the Apex One server database folder from Real-time Scan" option from the "Security Settings" tab on the "Global Agent Settings" page of the Apex One web console since Apex One no longer uses Codebase database.

Apex One supports Security Agent installation on the Windows 10 May 2020 Update (20H1).

The Apex One server and Security Agents collect Windows event logs related to critical system events (move Security Agent, uninstall Security Agent, reset password) and sends the logs to Apex Central Product Auditing Event logs.

The Unload and Uninstall Security Agent feature includes enhanced password complexity requirements for better security.

Support Connector Tool can assist in deploying a dedicated Support Connector Package for performing further troubleshooting steps upon the customers authorization.

Please refer to https://success.trendmicro.com/solution/000232603

Except for the administrator account created during installation, user account passwords for the web console can be updated even when users have provided the wrong current password.

Solution

This hotfix updates the Apex One server program to remove the vulnerability.

When users set "bypass_itunes_nonstor_usb_dc=true" in the "dlp.ini" file of the Apex One server, they should be able to charge an iPhone on a Microsoft Windows™ 10 computer even when the device is set to "Block" Mobile Devices under the Device Control settings but users should not be able to access the iPhone. However, users can still access the iPhone under this configuration.

Solution

This hotfix updates the Data Protection module to ensure that when "bypass_itunes_nonstor_usb_dc=true", users may be able to charge an iPhone but not access it.

When the DLP service is enabled on Apex One security agent computers, Google Chrome 80 and higher versions may stop unexpectedly while users upload file attachments in Webmail.

Solution

This hotfix updates the DLP module to resolve this issue and enable it to block the upload of file attachments in Webmail on Google Chrome.

This hotfix updates the Apex One Security Agent program to allow users to disable the system balloon notification.

Procedure

To disable the system balloon notification:

  1. Install this hotfix (see "Installation").
  2. Open the "Ofcscan.ini" file in the "\PCCSRV\" folder on the Apex One server installation directory.
  3. Under the "Global Setting" section, manually add the following keys and values.
  • [Global Settings]
  • SkipBalloonNum=x, the number of notifications to disable
  • SkipBalloonID0=yyy, balloon ID of the first notification
  • SkipBalloonID1=zzz, balloon ID of the next notification

NOTE: Specify the balloon IDs of each notification to be disabled.

For example, to disable the following three notifications, set:

  • [Global Setting]
  • SkipBalloonNum=3
  • SkipBalloonID0=101
  • SkipBalloonID2=102
  • SkipBalloonID3=103
  1. Save the changes and close the file.
  2. Open the Apex One web console and go to the "Agents > Global Agent Settings" screen.
  3. Click "Save" to deploy the setting to clients. The Apex One server deploys the command to Security Agent and adds the following registry entry on all Security Agent computers:
  • Path: HKEY_LOCAL_MACHINE\SOFTWARE\TrendMicro \PC-cillinNTCorp\CurrentVersion\Misc.
  • Key: SkipBalloonNum
  • Type: DWORD
  • Value: x
  • Path: HKEY_LOCAL_MACHINE\SOFTWARE\TrendMicro \PC-cillinNTCorp\CurrentVersion\Misc.
  • Key: SkipBalloonID0
  • Type: DWORD
  • Value: yyy

This hotfix updates the Apex One Master Service to change the callback address token in C&C callback alert email notifications from "http/https" to "hxxp/hxxps".

Procedure

To apply the solution:

  1. Install this hotfix (see "Installation").
  2. Open the "ofcserver.ini" file in the "\PCCSRV\Private" folder in the Apex One server installation directory.
  3. Under the "CCCA" section, manually add the following key and set it to "1":
  • [CCCA]
  • EnabledReplaceURL=1
  1. Save the changes and close the file.
  2. Restart the Apex One Master Service

This hotfix adds the "UK: RD&E Hospital Number" field to the DLP module rule template.

After upgrading to Apex One Patch 2 Build 2146 and any higher version, users cannot register Apex One successfully to Trend Micro Apex Central™ using certificates.

Solution

After applying the hotfix, users can successfully register Apex One to Apex Central using certificates.

Endpoints with "VMware Airwatch Tunnel" connected may experience a performance issue with web browsers due to a signature issue with the Windows Antimalware Scan Interface (AMSI) integration feature.

Solution

This hotfix updates the signature on the AMSI provider to resolve this issue.

An issue prevents the Security Risk Detections Over Time Widget from working normally.

Solution

This hotfix updates the Upgrade SQL Schema to resolve the issue so the Security Risk Detections Over Time Widget works normally.

A manual update may take an unusually long time to complete when launched by right-clicking the Security Agent icon in the Windows Task Bar and then selecting "Update Now".

Solution

This hotfix updates the Apex One server program to resolve this issue.

The following message appears on the notification panel of the Apex One Dashboard even when the Apex One server has already registered to an Apex Central server.

"Apex Central recommended. Your product license includes additional security features managed directly from the Apex Central console. Integrate with Apex Central to start using Vulnerability Protection and Application Control."

The Apex One Predictive Machine Learning (PML) feature may prevent users from running scripts to write files normally.

Solution

This hotfix resolves the issue by allowing PML to follow the Real-time Scan Exclusion settings to bypass certain file I/O events that are hooked by the Behavior Monitoring module.

Sometimes, enhanced security policies cannot be sent to Security Agents across the network successfully when the Apex One server is managed from the Apex Central web console. This may happen when some settings on the Microsoft Internet Information Service (IIS) Application Server Manager have not been set properly. However, there are no relevant debug logs for tracing this issue.

Solution

This hotfix updates the Apex One server program to enhance debug log visibility for this issue.

If the "Enable CVE exploit scanning for files downloaded through web and email channels" option of the Real-time Scan Settings is enabled, users may experience high CPU usage issues on protected computers when an on-demand Manual Scan, Scan Now, or Scheduled Scan starts.

Solution

This hotfix updates the Apex One security agent program to resolve the issue.

A restart is required to complete updates for certain drivers. This hotfix enables administrators to configure how frequent the "Restart Computer" notification pops up on the agent console.

Procedure

To set the interval and number of times of "Restart Computer" notification which is popped up from agent console.

  1. Install this hotfix (see "Installation").
  2. Open the "ofcscan.ini" file in the "\PCCSRV\" folder of the Apex One server installation directory using a text editor.
  3. Under the "Global Setting" section, manually add the following keys and set a preferred value for each.
  • [Global Setting]
  • EnableUserDefinedPopupNotify=1, to disable the feature, set this key to "0".
  • UserDefinedPopupCount=X, the "Restart Computer" notification will pop up X times before users restart the computer, supports any integer from 1.NOTE: When administrators modify and re-deploy these three keys to the security agent or when the agent is reloaded, the number of times the "Restart Computer" notification pops up will be reset to zero.
  • UserDefinedPopupNotifyIntervalMinute=Y, the "Restart Computer" notification will pop up about every Y minutes before users restart the computer, supports any integer from 1.

For example, to set the "Restart Computer" notification to popup every 30 minutes up to three times when ignored by the user, set:

  • [Global Setting]
  • EnableUserDefinedPopupNotify=1
  • UserDefinedPopupCount=3
  • UserDefinedPopupNotifyIntervalMinute=30
  1. Save the changes and close the file.
  2. Open the Apex One web console and go to the "Agents > Global Agent Settings" screen.
  3. Click "Save" to deploy the setting to agents. The Apex One server deploys the command to security agents and adds the following registry entry on all security agent computers:
  • Path:
    • For x64 platforms: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\TrendMicro\PC-cillinNTCorp\CurrentVersion\Misc.\
    • For x86 platforms: HKEY_LOCAL_MACHINE\SOFTWARE\TrendMicro\PC-cillinNTCorp\CurrentVersion\Misc.\
  • Key: EnableUserDefinedPopupNotify
  • Type: DWORD
  • Value: 1
  • Key: UserDefinedPopupNotifyCount
  • Type: DWORD
  • Value: X
  • Key: UserDefinedPopupNotifyIntervalMinute
  • Type: DWORD
  • Value: Y

Under certain extreme conditions, the CRC full pattern update process goes into an endless loop and causes a high CPU usage issue.

Solution

This hotfix adds a new iCRC engine in Apex One to resolve this issue.

When disabling Windows Defender, the Apex One agent program always checks whether it is still running or has stopped. If it is still running, the Apex One agent calls the API to disable it and displays a "Restart Required" message on the Apex One agent console.

Solution

This hotfix updates the Apex One agent program to remove this checking mechanism so it does not trigger the "Restart Required" message on the Apex One agent console.

This hotfix provides a way to prevent Apex One from applying the settings of a new domain on automatically grouped agents. This means that when a group of agents are transferred to a new domain, the agents will retain the existing policy settings instead of following the settings of the new domain.

Procedure

To prevent Apex One from applying the settings of a new domain on automatically grouped agents:

  1. Install this hotfix (see "Installation").
  2. Open the "ofcscan.ini" file in the "\PCCSRV\" folder on the Apex One server installation directory.
  3. Under the "Global Setting" section, manually add the "SkipApplyNewDomainSettings" key and set its value to "1".
  • [Global Setting]
  • SkipApplyNewDomainSettings=1
  1. Save the changes and close the file.

NOTE: After applying this key, security agents that were automatically moved to new domains will not apply the settings of the new domain and will retain the existing policy settings.

Microsoft™ Windows™ updates take longer to complete and use up more CPU resources on computers where the Apex One on-prem agent program is installed.

Solution

This hotfix updates the Apex One security agent program to resolve this issue.

A buffer overrun issue prevents users from uninstalling the German version of the Apex One Security Agent successfully.

Solution

This hotfix resolves the buffer overrun issue.

When OfficeScan XG agents are migrated from an OfficeScan XG server to an Apex One server, the agent upgrade process may encounter a looping issue which prevents the agent program from upgrading to Apex One.

Solution

This hotfix resolves the issue by ensuring that the Apex One server program handles legacy files properly.

When users upgrade OfficeScan 11 agents to Apex One agents using an upgrade package generated by the Agent Packager tool, some files under the agent installation folder are not updated.

Solution

This hotfix updates the Apex One server program to ensure that the Agent Packager includes all the necessary binaries in the Apex One security agent "Setup" installer package.

The update source for the Integrated Smart Protection Server is automatically set to "Trend Micro Apex Central" in the "Apex Central" settings page.

Solution

This hotfix updates the Apex One server program to resolve this issue.

An exception error triggers the Apex One Master Service to stop unexpectedly while extracting a pattern file from a compressed file.

Solution

This hotfix updates the Apex One server program to enable it to handle the exception.

The Vulnerability Protection (VP) policy cannot be deployed because the Apex One VP agent program does not support customized installation paths (C:).

Solution

This hotfix updates the Apex One VP agent program to support customized installation paths.

It may take a long time to log on to Apex One security agent computers after start up.

Solution

This hotfix allows users to set the following three drivers that are related to the Virus Scan Engine to "on-demand start" on the Apex One security agent:

  • TmFilter.sys
  • TmPreFilter.sys
  • VSApiNt.sys

Procedure

To set the three drivers related to Virus Scan Engine to "on-demand start" on Apex One security agents:

  1. Install this hotfix (see "Installation").
  2. Open the "ofcscan.ini" file in the "\PCCSRV\" folder on the Apex One server installation directory.
  3. Under the "Global Setting" section, manually add the following key and set its value to "1".
  • [Global Setting]
  • VSAPIServiceStartOnDemand=1 NOTE: To disable the setting, set this key to "0". The three drivers will be set to the default action "automatic start".
  1. Save the changes and close the file.
  2. Open the Apex One web console and go to the "Agents > Global Agent Settings" screen.
  3. Click "Save" to deploy the setting to agents. The Apex One server deploys the command to Apex One security agents and changes the following registry values from "2" (default) to "3" on all Apex One security agent computers:
  • Path: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\TmFilter
  • Key: Start
  • Type: DWORD
  • Value: 3
  • Path: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\TmPreFilter
  • Key: Start
  • Type: DWORD
  • Value: 3
  • Path: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\VSApiNt
  • Key: Start
  • Type: DWORD
  • Value: 3
  1. Restart the Apex One security agent computers.

Third-party applications may experience a performance issue when Behavior Monitoring is enabled on the Security Agent.

Solution

This hotfix updates the Behavior Monitoring module to resolve this issue.

After synchronizing Active Directory domains, some selected groups on the "Unmanaged Endpoints > Active Directory / IP Address Scope" screen are no longer selected.

Solution

This hotfix updates the Apex One server program to resolve this issue.

The attack discovery rule for "Winlogon execute sethc" triggers too many alerts.

Solution

This hotfix updates the rule to minimize alerts.

Endpoint Sensor returns an "upload file format incorrect" error if the YARA rule uses the hash module.

Solution

This hotfix updates the YARA library in both the server and agent program to resolve this issue.

Users may encounter a "Windows upgrade failed" error on an Apex One agent computer running on the Microsoft™ Windows™ 10 platform. This happens when the Apex One agent ever acted as an Update Agent (UA) and some existing files match the blocking software range in Microsoft Windows.

Solution

This hotfix updates the Apex One agent program and adds a folder checking mechanism to resolve the issue.

The Behavior Monitoring program inspection feature still blocks certain applications on Apex One security agent computers even after users have added these applications into the Trusted Programs List or the approved list of the Behavior Monitoring Exceptions on security agents.

Solution

This hotfix updates the Apex One security agent program to resolve this issue.

The "The To field must be between 1 to 256 characters." error message displays on the "Administration > Notifications > Administrator > Email" tab when users click on the "Save" button after ticking the following options in the Virus/Malware Detections, Spyware/Grayware Detections, or C&C Callbacks section.

  • Enable notification via email
  • Send notifications to users with agent tree domain permissions

Solution

This hotfix updates the Apex One server program to prevent the error and ensure that users can update and save the notification settings normally.

Apex One may not be able to download the Web Blocking List component from smart protection sources because the Trend Micro Local Web Classification Server service stops unexpectedly.

Solution

This hotfix updates the Apex One server program to resolve this issue.

The Trend Micro Data Loss Prevention™ (DLP) service does not work normally in Google Chrome and Microsoft Internet Explorer™ with HTTPS.

Solution

This hotfix updates the DLP module to resolve this issue.

In the Traditional Chinese version, garbled characters appear in the exported CSV file of DLP logs.

Solution

This hotfix updates the Apex One server program to resolve this issue.

The Apex One Master Service may stop unexpectedly because the allocated memory was not released properly.

Solution

This hotfix updates the Apex One server program to resolve this issue.

After Patch 2146 is applied, users encounter an error while manually deleting logs from the "Log Criteria" on the "Agents > Agent Management > Logs > Delete Logs" and "Logs > Agents > Security Risks > Delete Logs" pages.

Solution

This hotfix updates the Apex One server program to resolve this issue.

This hotfix allows the Apex One agent to bypass the proxy settings when connecting to the Apex One server if it detects a proxy exception. This hotfix also improves the duration of manual updates on Apex One agents.

This hotfix provides a way to configure Apex One to keep track of when USB storage devices are plugged into Apex One security agent computers. The logs can be queried in the Device Control violations on the Apex Central web console. These events are also recorded in the "UsbInsert_yyyymmdd.log" file on the Apex One server "\PCCSRV\Log" folder.

NOTES:

  • The logs in the "UsbInsert_yyyymmdd.log" file will appear in the following format: [Timestamp] [Log Generation Time] [Agent GUID] [Computer Name] [Action] [USB:Vendor:Model:Serial ID]
  • The "UsbInsert_yyyymmdd.log" file will be deleted regularly according to the "Logs to Delete" and "Log Deletion Schedule" settings in the "Log Maintenance" page on the Apex One web console. You need to ensure that the "Enable scheduled deletion of logs" feature is enabled with the "Device Control Logs" log type selected.

Procedure

To configure Apex One to keep track of when USB storage devices are plugged into Apex One security agent computers:

  1. Install this hotfix (see "Installation").
  2. Open the "ofcscan.ini" file in the "\PCCSRV\" folder on the Apex One server installation directory.
  3. Under the "Global Setting" section, manually add the following key and set its value to "1".
  • [Global Setting]
  • EnableUsbLogging=1

NOTE: To disable the setting, set this key to "0".

  1. Save the changes and close the file.
  2. Open the Apex One web console and go to the "Agents > Global Agent Settings" screen.
  3. Click "Save" to deploy the setting to agents. The Apex One server deploys the command to Apex One security agents and adds the following registry entry on all Apex One security agent computers:
  • Path:
    • 32-bit: \HKEY_LOCAL_MACHINE\SOFTWARE\TrendMicro\PC-cillinNTCorp\CurrentVersion\DlpLite
    • 64-bit: \HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\TrendMicro\PC-cillinNTCorp\CurrentVersion\DlpLite
  • Key: EnableUsbLogging
  • Type: DWORD
  • Value: 1

The Apex One Behavior Monitoring feature may use up a huge amount of memory on certain protected computers.

Solution

This patch updates the Behavior Monitoring module to resolve this issue.

The following two issues related to the Apex One Data Protection Service may occur on protected computers:

  • Users may have trouble accessing the https://fast.com website.
  • Agents cannot connect to VPN through the Cisco AnyConnect Secure Mobility Client.

Solution

This patch updates the Data Loss Prevention™ (DLP) module to resolve this issue.

The DLP module cannot properly block users from uploading file attachments on endpoints running Microsoft™ Windows™ 10 Redstone 5 (version 1809).

Solution

This patch updates the DLP module to resolve this issue.

This patch applies updates to improve the security of Apex One server operations.

This patch enables users to configure Apex One to use a customized OfcOSFWebApp certificate.

Procedure

To configure Apex One to use a customized OfcOSFWebApp certificate:

  1. Install this patch (see "Installation").
  2. Open the "ofcscan.ini" file in the "\PCCSRV\" folder on the Apex One server installation directory.
  3. Under the "INI_SERVER_SECTION" section, manually add the "CN_OSFWebApp=" key and specify the customized certificate.
  • [INI_SERVER_SECTION]
  • CN_OSFWebApp=customized CN
  1. Save the changes and close the file.

NOTE: Please contact Trend Micro Support for the procedures to adding a customized OfcOSFWebApp certificate.

An issue prevents the Application Control agent service from initializing the Digital Signature Pattern (tmwlchk.ptn) in lockdown mode. Application Control needs this pattern to determine which applications are from trusted Trend Micro vendors to be able to allow these applications to run from a protected computer.

Solution

This hotfix updates the Application Control files to resolve this issue.

Executable files take a long time to launch on network drives when the Behavior Monitoring service is enabled.

Solution

This hotfix updates the Behavior Monitoring module to resolve this interoperability issue.

Procedure

To apply and deploy the solution globally:

  1. Install this hotfix (see "Installation").
  2. Open the "Ofcscan.ini" file in the "\PCCSRV\" folder of the Apex One server installation directory using a text editor.
  3. Under the "Global Setting" section, manually add the following key and set its value to "1".
  • [Global Setting]
  • AegisSkipNotificationEvent=1
  • AegisSkipCreateProcessWithCmdLineEvent=1
  1. Save the changes and close the file.
  2. Open the Apex One web console and go to the "Agents > Global Agent Settings" screen.
  3. Click "Save" to deploy the setting to agents. The Apex One server deploys the command to security agents and adds the following registry entry on all security agent endpoints:
  • Path: HKEY_LOCAL_MACHINE\SOFTWARE\TrendMicro\AEGIS
  • Key: SkipNotificationEvent
  • Key: SkipCreateProcessWithCmdLineEvent
  • Type: DWORD
  • Value: 1

The Apex One firewall service may block the connection to version 12.1.51.19 of the Citrix Gateway.

Solution

This hotfix updates the Apex One security agent program to ensure that the firewall policy exception list works normally.

The exceed unmanaged agents IP ranges logs cannot be displayed when there are more than 201 sets of IP ranges.

Solution

This hotfix updates the Apex One server program to resolve this issue.

An issue prevents Apex One security agents from updating the Data Loss Prevention™ (DLP) policy successfully.

Solution

This hotfix updates the DLP module to resolve this issue.

The DLP service triggers an alert on a single instance of Movement Reference Number (MRN) when sending as an email.

Solution

This hotfix updates the DLP module to resolve this issue.

The link on the Apex One server dashboard notification redirects to an unavailable website.

Solution

This hotfix updates the Apex One server HTML files to ensure that the link redirects to the correct website.

Security Agents should use the configured Smart Protection Service Proxy settings when querying Smart Protection sources for the Predictive Machine Learning and the Behavior Monitoring features. However, Security Agents still use the proxy settings configured in Microsoft™ Internet Explorer™ to access the network even when the Smart Protection Service Proxy is enabled.

Solution

This hotfix updates the Apex One agent program to resolve this issue.

An Apex One agent installed on Microsoft Windows™ Server 2016 may appear "Offline" on the Apex One web console. This happens because the HTTPS communication port of the agent cannot be successfully initialized for listening while the protected computer starts.

Solution

This hotfix updates the Apex One agent program to prevent this issue from occurring.

An ADOexception error appears in Apex One server's Event Viewer logs when the Apex One Database Service encounters an exception because an invalid GUID was sent to the SQL server.

Solution

This hotfix updates the Apex One server program to resolve this issue.

If OfficeScan 11.0 or OfficeScan XG Agent (before Service Pack 1) is upgraded to Apex One Agent, clients will not be able to establish a connection to the server because the agent now uses HTTP communication but the server incorrectly recognizes it as HTTPS. As a result, the client appears offline on the web console.

Solution

This hotfix updates the Apex One program to resolve this issue.

The ASE setting on the agent side switches to "0" unexpectedly.

Solution

This hotfix updates the Apex One security agent program to prevent this issue.

This hotfix extends the validity of Microsoft certificates for some expired DLP drivers.

Apex One security agents may encounter a blue screen of death (BSOD) when the Osprey kernel file (tmusa.sys) is unloaded unexpectedly.

Solution

This critical patch updates the Trend Micro EagleEye Driver to resolve this issue.

A high CPU usage issue occurs on the Apex One server computer.

Solution

This critical patch updates the Attack Discovery pattern to help prevent the high CPU usage issue on the Apex One server computer.

The PowerShell command line sometimes automatically converts uppercase characters to lowercase.

Solution

This critical patch ensures that the PowerShell command line does not automatically convert uppercase characters to lowercase.

A potential process communication risk in the security agent exists in the Apex One server.

Solution

This critical patch updates the Apex One server program to remove this vulnerability.

A potential file deletion issue with system privileges exists via a Directory Traversal vulnerability in security agents.

Solution

This critical patch updates the Apex One server program to remove this vulnerability.

A potential issue with file uploads exists via a Directory Traversal vulnerability in security agents.

Solution

This critical patch updates the Apex One server program to remove this vulnerability.

The "Plug-ins" page does not display normally when users Single Sign-On (SSO) to the Apex One web console from the Apex Central web console.

Solution

This critical patch updates the Apex One server files to resolve this issue.

This critical patch integrates Windows Antimalware Scan Interface (AMSI) with Apex One to improve protection against malicious scripts.

Procedure

To enable the new settings:

  1. Install this critical patch (see "Installation").
  2. Open the Apex One web console and go to the "Agent > agent management" page.
  3. Right-click to select the specific domain or agents and go to the "Settings > Behavior Monitoring Settings" screen.
  4. Tick the "Enable program inspection to detect and block compromised executable files" and "Terminate programs that exhibit abnormal behavior associated with exploit attacks".
  5. Save the changes.
  6. The Apex One server deploys the following registry entry on the selected security agent computers:
  • Path:
    • For x64 platforms: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\TrendMicro\PC-cillinNTCorp\CurrentVersion\AEGIS\
    • For x86 platforms: HKEY_LOCAL_MACHINE\SOFTWARE\TrendMicro\PC-cillinNTCorp\CurrentVersion\AEGIS\
  • Key: EnableUMH / EnableUMHExploit
  • Type: REG_DWORD
  • Value: 1 (0x00000001)

This critical patch enhances the security of the Server Migration Tool.

This critical patch updates the program update checking logic on Apex One security agents to help ensure that only authentic program updates are applied.

This critical patch adds Endpoint Sensor features by enabling the use of on-premises Apex Central to manage on-premises Apex One servers. This enhancement requires users to upgrade on-premises Apex One servers to Build 2117 and on-premises Apex Central servers to Build 4363 or any higher build.

The Application Control agent service is dependent on some Microsoft™ Windows™ services. If some Windows services are not running, the system does not start the Application Control agent service.

Solution

This hotfix resolves the Application Control agent service dependency issue. After applying this hotfix, the Application Control agent service starts some Windows services automatically as it is starts up.

The system cannot successfully install the Application Control server if the SQL server contains a semi-colon (";") in its password.

Solution

This hotfix resolves this issue so that the system can install the Application Control server successfully.

Data Loss Prevention™ (DLP) feature may slow down the performance of certain web applications on the Apex One Security agent.

Solution

This hotfix updates the DLP module to resolve this issue.

NOTE: Please refer to the following link for the steps to manually set the monitored websites if customer need: https://success.trendmicro.com/intkb/solution/1120248

The 3rd-party ICE WebStart program cannot be launched while the Apex One Firewall service is running.

Solution

This hotfix updates the Trend Micro Apex One Firewall components and provides a way to prevent this issue from occurring.

Procedure

To enable the new settings:

  1. Install this hotfix (see "Installation").
  2. Open the "Ofcscan.ini" file in the "\PCCSRV\" folder of the Apex One server installation directory using a text editor.
  3. Under the "Global Setting" section, manually add the following key and set its value to "256".
  • [Global Setting]
  • PFW_KEventMaxCount=256
  1. Save the changes and close the file.
  2. Open the Apex One web console and go to the "Agents > Global Agent Settings" screen.
  3. Click "Save" to deploy the setting to agents. The Apex One server deploys the command to Apex One agents and adds the following registry entry on all Apex One agent endpoints:
  • Path: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\tmWfp\Parameters
  • Key: KEventMaxCount
  • Type: REG_DWORD
  • Value: 256 (0x100)
  1. Restart the Apex One agent machines.

The Apex One Behavior Monitoring feature may prevent users from opening Microsoft Office applications normally and may cause high CPU usage issues on protected computers.

Solution

This hotfix updates the Apex One agent program to resolve this issue.

Procedure

To apply and deploy the solution globally:

  1. Install this hotfix (see "Installation").
  2. Open the "ofcscan.ini" file in the "\PCCSRV\" folder on the Apex One server installation directory.
  3. Under the "Global Setting" section, manually add the "UnregUMHEventList" key and set its value to "140".
  • [Global Setting]
  • UnregUMHEventList=140
  1. Save the changes and close the file.
  2. Open the Apex One web console and go to the "Agents > Global Agent Settings" screen.
  3. Click "Save" to deploy the setting to agents. The Apex One server deploys the command to security agents and adds the following registry entry on all security agent computers:
  • Path:
  • For x64 platforms: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\TrendMicro\PC-cillinNTCorp\CurrentVersion\AEGIS\
  • For x86 platforms: HKEY_LOCAL_MACHINE\SOFTWARE\TrendMicro\PC-cillinNTCorp\CurrentVersion\AEGIS\
  • Key: UnregUMHEventList
  • Type: String
  • Value: "The encrypted string with the prefix !CRYPTEX!"
  1. Restart the Apex One security agent.

This hotfix enables the Apex One server to download the list of approved mobile devices and USB storage devices from the Device Control settings in the Apex Central server and to deploy the list to Apex One security agents.

Procedure

To configure Apex One server to download and deploy the Device Control approved list of mobile devices and USB storage devices from the Apex Central server to all Apex One security agents:

  1. Run the Device List Tool (listDeviceInfo.exe) to retrieve the device information. The tool provides Vendor, Model, Serial ID, and Device information for each device.
  2. Make a Device Control approved list in CSV file format specifying the Vendor, Model, Serial ID, and Device information of mobile devices and USB storage devices.

    For example:

  • 05AC,12A8,35AD13C948ECD47904B2B7AD4D5E8AFBF4C70C48,Mobile Devices
  • ADATA,DC1A,285252344010000C,USB Storage Devices

    NOTE: The "Device" field is optional, if there is no device type listed in the CSV file, it will be treated as "USB Storage Devices".

  1. Copy the CSV file to the Apex Central server in the "\Trend Micro\Control Manager\WebUI\WebApp\widget\repository\widgetPool\product\OSCE\" folder and rename the CSV file as "dc_dev_exception.csv".

NOTE: Users can import the Device Control approved list from the "Policies > Policy Resources > Device Control Allowed Devices" page of the Apex Central console.

  1. Deploy an Apex One Security Agent policy with Device Control setting to agents from the Apex Central console. All agents will receive the approved list.

    NOTE: On the Apex One server, users can check the "DC_GLOBAL_DEV_EXCEPTION" section in "dlp.ini" file under the "\PCCSRV\Private" folder.

    For example:

  • [DC_GLOBAL_DEV_EXCEPTION]
  • DevExceptionGlobalCount=2
  • DevExceptionGlobal_00000000= VendorName,Model,serialNo,1(USB Storage Devices)
  • DevExceptionGlobal_00000001=VendorName,Model,serialNo,2097152(Mobile Devices)

    On the Apex One security agent, users can check the "dc_in.xml" and "dc_out.xml" file under the "\Security Agent\dlplite" folder.

    For example:

  • <usbException exceptionDeviceType="0x00000001"(USB Storage Devices) serialNo="xxxxxxxx" model=" xxxxxxxx " vendorName="xxxxxxxx "/>
  • <usbException exceptionDeviceType="0x00200000"(Mobile Devices) serialNo=" xxxxxxxx " model=" xxxxxxxx " vendorName="xxxxxxxx "/>

This hotfix removes the "Enable debug log" check box from the "Debug Log Setting" window in the Apex One console.

When administrators set the Internet proxy settings from the browser, the Apex One Security proxy always applies the Internet proxy settings to update components from the Trend Micro Global ActiveUpdate server instead of the Apex One server.

Solution

This hotfix enables the Security Agent console to allow administrators the option to choose and apply "Use Windows Internet Options Settings" when updating components.

By default, the system does not apply and update components from the Apex One server.

On computers with low specifications, the Application Control agent may run into performance issues when several applications installed on the computer match the Application Control criteria.

Solution

This hotfix helps prevent the performance issues by enabling the Application Control agent to store matched applications in the criteria cache after these applications run for the first time.

A "Failed to get server certificate." error appears on the installation log during Advanced Threat Assessment Service installation.

Solution

This hotfix resolves the error so the Advanced Threat Assessment Service can be installed successfully.

The real-time scan exception settings from the Apex One security agent are restored unexpectedly after an Apex One security agent update.

Solution

This hotfix updates the Apex One security agent program to preserve the current real-time scan exception settings after an Apex One security agent update.

The Apex One agent keeps track of un-scanned files but does not send the information to the server, so users do not see the information on the Apex One server.

This hotfix enables Apex One agents to upload un-scanned file logs to the "C:\Program Files (x86)\Trend Micro\Apex One\PCCSRV\Log\UnScanFile" folder on the server.

(Video) Trend Micro Apex One As A Service - Creating Policy

The Apex One Vulnerability Protection service cannot start successfully on the Turkish version of the Microsoft™ Windows™ server platform because it uses the all caps version of the database column name, "SYSTEMVERSIONID".

Solution

This patch updates the database column name in the Apex One Vulnerability Protection server to "SystemVersionID" to resolve this issue.

A program on an endpoint triggers the Behavior Monitoring module.

Solution

This patch adds a command related to the program to the exception list to solve this issue.

Procedure

To apply and deploy the solution globally:

  1. Install this patch (see "Installation").
  2. Open the "ofcscan.ini" file in the "\PCCSRV\" folder on the Apex One server installation directory.
  3. Under the "Global Setting" section, manually add the following keys and values.
  • [Global Setting]
  • AegisSPSetCMDCount=1
  • AegisSPSetCMDSubImagePath0=C:\Windows\System32\cmd.exe
  • AegisSPSetCMDImagePath0=certutil.exe
  • AegisSPSetCMDCmdLine0=-urlcache-splithttpzip*
  • AegisSPSetCMDAct0=0
  1. Save the changes and close the file.
  2. Open the Apex One web console and go to the "Agents > Global Agent Settings" screen.
  3. Click "Save" to deploy the settings to agents. The Apex One server deploys the command to security agents and adds the following registry entries on all security agent computers:
  • Path: HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\TrendMicro\PC-cillinNTCorp\CurrentVersion\AEGIS
  • Key: AegisSPSetCMDCount
  • Type: DWORD
  • Value: 1
  • Path: HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\TrendMicro\PC-cillinNTCorp\CurrentVersion\AEGIS
  • Key: AegisSPSetCMDSubImagePath0
  • Type: REG_SZ
  • Value: C:\Windows\System32\cmd.exe
  • Path: HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\TrendMicro\PC-cillinNTCorp\CurrentVersion\AEGIS
  • Key: AegisSPSetCMDCmdLine0
  • Type: REG_SZ
  • Value: -urlcache-splithttpzip*
  • Path: HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\TrendMicro\PC-cillinNTCorp\CurrentVersion\AEGIS
  • Key: AegisSPSetCMDImagePath0
  • Type: REG_SZ
  • Value: certutil.exe
  • Path: HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\TrendMicro\PC-cillinNTCorp\CurrentVersion\AEGIS
  • Key: AegisSPSetCMDAct0
  • Type: DWORD
  • Value: 0
  1. Restart the security agent

This patch enables the Apex One security agent program to support Microsoft Windows™ 10 (version 1909) November 2019 Update.

This patch adds a mechanism that can help reduce the probability of errors during Apex One server and Apex One security agent updates.

The maximum supported character length of the following registry key on Apex One security agents may be insufficient to save the proxy exceptions list.

  • [HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\TrendMicro\PC-cillinNTCorp\CurrentVersion]
  • WinProxySpecifiedProxyBypass

Solution

This hotfix extends the registry key's maximum supported character length to resolve this issue.

A performance issue occurs on Apex One agent computers because a module generates a large number of logs.

Solution

This hotfix updates the user mode event related module to version 8.5.2065 to solve the issue.

The Apex One Predictive Machine Learning feature may prevent users from running scripts through a third-party application normally.

Solution

This hotfix provides a way for users to make and edit a list of approved programs to run with deferred scanning by Predictive Machine Learning to prevent these issues.

Procedure

To create and edit the list of approved programs to run with deferred scanning by Predictive Machine Learning:

  1. Install this hotfix (see "Installation").
  2. Open the "Ofcscan.ini" file in the "\PCCSRV\" folder on the Apex One server installation directory.
  3. Under the "Global Setting" section, manually add the following keys and specify each approved program separately.
  • [Global Setting]
  • DS_ProcessCount=the number of programs in the approved list, supports any integer from 1 to 1000
  • DS_ProcessName000=process name of the approved program, where "000" notes the first item on the list

    For example:

  • [Global Setting]
  • DS_ProcessCount=2
  • DS_ProcessName000=cscript.exe
  • DS_ProcessName001=wscript.exe
  1. Save the changes and close the file.
  2. Open the Apex One web console and go to the "Agents > Global Agent Settings" screen.
  3. Click "Save" to deploy the setting to agents. The Apex One server deploys the command to security agents and adds the following entries of TXS.ini on all security agent computers:
  • [TrendX_Settings]
  • DS_ProcessCount=2
  • DS_ProcessName000="The encrypted string of the preferred program"
  • DS_ProcessName001="The encrypted string of the preferred program"

The Trend Micro Vulnerability Scanner (TMVS) cannot perform remote installation when the logon account password includes special characters.

Solution

This hotfix updates TMVS to resolve this issue.

On the Apex One web console, users may be able to view the user account that have just been logged out by pressing the back button of the web browser.

Solution

This hotfix updates the Apex One server program to prevent this issue from occurring.

On the Apex One web console, the "PHPSESSID" and "wf_CSRF_token" cookies are the same for every logon session.

Solution

This hotfix ensures that the widget framework generates new "PHPSESSID" and "wf_CSRF_token" cookies for each new logon session.

An issue prevents the Apex One server from deploying the following settings to Apex One security agents properly.

Under the "Privileges and Other Settings > Other Settings".

  • Do not allow users to access the Security Agent console from the system tray or Windows Start menu

Solution

This hotfix updates the Apex One server program to resolve the issue.

The Apex One security agent does not send the "Logon User" information to the Apex One server when the Apex One server restricts the user's access to the security agent console only from the system tray or from the Microsoft™ Windows™ "Start" menu.

Solution

This hotfix updates the Apex One security agent program to ensure that Apex One security agents send the "Logon User" information to the Apex One server under the scenario described above.

The Apex One Endpoint Sensor receives several user mode events that can prevent Microsoft™ RemoteApp from updating the event source.

Solution

The Apex One Endpoint Sensor changes the event source from User mode to kernel mode to resolve this issue.

The Export Info Tool stops unexpectedly when querying virus logs.

Solution

This hotfix updates the Apex One server program to resolve the issue.

Users may not be able to activate managed product licenses (Application Control, Endpoint Sensor, Vulnerability Protection) across the network successfully when managing the Apex One server from the Apex Central web console. This happens because the Apex One server does not handle the license key string properly.

Solution

This hotfix updates the Apex One server program to resolve this issue.

The Apex One NT Listener service (TmListen.exe) may cause a high CPU usage issue on security agents.

Procedure

To apply and deploy the solution globally:

  1. Install this hotfix (see "Installation").
  2. Open the "Ofcscan.ini" file in the "\PCCSRV" folder of the Apex One server installation directory using a text editor.
  3. Under the "Global Setting" section, manually add the following key and set its value to "1".
  • [Global Setting]
  • IgnoreScanIncompleteFlagFromServer=1
  1. Save the changes and close the file.
  2. Open the Apex One Web console and go to the "Agents > Global Agent Settings" screen.
  3. Click "Save" to deploy the setting to agents. The Apex One server deploys the command to Apex One agents and adds the following registry entry on all Apex One agent endpoints:
  • Path: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\TrendMicro\PC-cillinNTCorp\CurrentVersion\URL Filtering
  • Key: IgnoreScanIncompleteFlagFromServer
  • Type: DWORD
  • Value: 1

A directory traversal vulnerability may allow an attacker to log on to the Apex One Management Console as a root user.

Solution

This critical patch updates the Apex One server program to remove the vulnerability.

A command injection vulnerability may allow an attacker to extract files from an arbitrary zip file to the specific folder in Apex One server.

Solution

This critical patch updates the Apex One server program to remove the vulnerability.

This hotfix provides a way to delay Application Control hooking events while an endpoint computer starts up.

Procedure

To apply this solution:

  1. Install this hotfix (see "Installation").
  2. Unload the Apex One security agent.
  3. Open the registry editor, add the following key, and specify the preferred time delay in minutes:
  • Key: HKEY_LOCAL_MACHINE\SOFTWARE\TrendMicro\iACAgent\DelayLoadAC
  • Type: DWORD
  • Valid Range: 0-10 (min)
  1. Restart the Apex One security agent.

In certain environments, the Behavior Monitoring feature may add the "csrss.exe" file to the kernel exception later than expected which can then cause an interoperability issue that can trigger security agent computers to stop unexpectedly.

Solution

This hotfix updates the Behavior Monitoring module and enables users to configure the Behavior Monitoring feature to add "csrss.exe" to the kernel exception earlier to prevent the interoperability issue.

Procedure

To apply and deploy the solution globally:

  1. Install this hotfix (see "Installation").
  2. Open the "ofcscan.ini" file in the "\PCCSRV\" folder on the Apex One server installation directory.
  3. Under the "Global Setting" section, manually add the "AegisAsyncCsrssEvent" key and set its value to "1".
  • [Global Setting]
  • AegisAsyncCsrssEvent=1
  1. Save the changes and close the file.
  2. Open the Apex One web console and go to the "Agents > Global Agent Settings" screen.
  3. Click "Save" to deploy the setting to agents. The Apex One server deploys the command to security agents and adds the following registry entry on all security agent computers:
  • Path: HKEY_LOCAL_MACHINE\SOFTWARE\TrendMicro\AEGIS
  • Key: AsyncCsrssEvent
  • Type: DWORD
  • Value: 1
  1. Restart the security agent

Enhanced security policies may not be sent to Security Agents across the network successfully when users manage the Apex One server from the Apex Central web console. This happens when the Apex One SQL database is installed on a Microsoft™ SQL Server that users a collation method other than the default "SQL_Latin1_General_CP1_CI_AS".

Solution

This hotfix updates the Apex One server program to resolve this issue.

This hotfix enables users to query the OSFWebApp web service status through the "svrsvcsetup.exe" tool using the following command on the Apex One server command prompt.

svrsvcsetup.exe -testosfwebapp

This hotfix enables users to search for multiple agents on the "Agent Management" page by specifying multiple agent names in the "Search for endpoints" text box.

NOTES:

  • Use a blank character " " delimiter to separate each agent name in the "Search for endpoints" text box.
  • The field supports wildcard characters. Use a question mark "?" to represent a single character and an asterisk "*" to represent several characters.
  • The field supports a maximum of 256 characters.

After a built-in Active Directory (AD) user group, for example "Administrators", is added in the "User Accounts" settings, and users login to Apex One using an AD account in this group, the Apex One console will not display any user or domain in "Agent Management" view.

Solution

This hotfix updates Apex One server program to resolve the issue.

This hotfix enables Apex One to support Microsoft Windows 8.0.

NOTE: If the security agent has been installed on Windows 8.0, it will be registered to the Apex One server after it restarts.

This hotfix updates the Trend Micro Data Loss Prevention™ (DLP) module to ensure that it can block drag-and-drop file operations in Google Chrome 76 and 77.

The Apex One Security Agent service stops responding while starting after Apex One Hotfix 1141 is applied.

Solution

This hotfix updates the Apex One security agent program to resolve this issue.

An issue prevents users from successfully installing the Application Control agent on endpoints with Chinese computer names.

Solution

This hotfix resolves the issue so the Application Control can be installed successfully on affected endpoints.

The information in the "action" column on Data Loss Prevention™ (DLP) logs in Apex One server is not consistent with the corresponding information in the DLP logs on Apex Central server.

Solution

This hotfix resolves the issue by modifying the wording in the "action" column in DLP logs on both the Apex One server and agents.

An issue prevents the Trend Micro Advanced Threat Assessment Service from starting successfully.

Solution

This hotfix resolves the issue.

Garbled characters may appear in syslog if the language setting of the operating system contains Big-5 characters.

Solution

This hotfix resolves the issue.

The Apex One Endpoint Sensor cannot detect the dump of lsass.exe (Local Security Authority Process).

Solution

This hotfix resolves this issue by adding hooking points for event correlation to detect the suspicious attack behavior.

Advanced Threat Assessment has a new process that collects additional information.

The device control function does not work if the policy is deployed for a specific user and the username contains Hebrew characters.

Solution

This hotfix updates Apex One security agent program to resolve the issue.

The Smart Scan Service may behave abnormally on Apex One Security Agents when multiple proxy servers have been configured for each protocol (HTTP, Secure, FTP, Socks) in the Microsoft™ Internet Explorer™.

Solution

This hotfix updates the Apex One Security Agent program to ensure that the Smart Scan Service works normally when multiple proxy servers are configured for Internet Explorer.

Users may not be able to activate managed product licenses (Application Control, Endpoint Sensor, Vulnerability Protection) or may not be able to send the enhanced security policies to Security Agents across the network successfully when managing the Apex One server from the Apex Central web console. This happens because the specified Microsoft Windows™ account that manages the existing Apex One SQL database does not have sufficient web service framework access permissions.

Solution

This hotfix resolves the issue by updating the SQL Server Database Configuration Tool to add the Windows account to the IIS_IUSRS group to obtain the correct permissions.

Procedure

To add the Windows account to the IIS_IUSRS group to obtain the correct permissions:

  1. Install this hotfix (see "Installation").
  2. On the Apex One server computer, browse to "<Server installation folder>\PCCSRV\Admin\Utility\SQL".
  3. Double-click "SQLTxfr.exe" to run the tool.
  4. Provide the authentication credentials of the Windows account for the SQL Server database.IMPORTANT: The user account must belong to the local administrator group or Active Directory (AD) built-in administrator.
  5. Click "Start" to apply the configuration changes.

Users may not be able to activate managed product licenses (Application Control, Endpoint Sensor, Vulnerability Protection) or may not be able to send the enhanced security policies to Security Agents across the network successfully when managing the Apex One server from the Apex Central web console. This happens because:

  1. The specified Windows account that manages the existing Apex One SQL database changes the logon credentials used to connect to the existing database.
  2. Users change the Authentication Type of the existing Apex One SQL database from "Windows Account" to "SQL Server Account".

Solution

This hotfix updates the SQL Server Database Configuration Tool to ensure that the Apex One server uses the correct authentication credentials for the SQL Server database.

Procedure

To ensure that the Apex One server uses the correct authentication credentials for the SQL Server database:

  1. Install this hotfix (see "Installation").
  2. On the Apex One server computer, browse to "<Server installation folder>\PCCSRV\Admin\Utility\SQL".
  3. Double-click "SQLTxfr.exe" to run the tool.
  4. Provide the authentication credentials for the SQL Server database.IMPORTANT: The user account must belong to the local administrator group or AD built-in administrator.
  5. Click "Start" to apply the configuration changes.

This hotfix improves the accuracy of the Apex One Application Control version reporting to Apex Central.

The "Active Directory Integration" page may expose the credential key when the page is opened with developer tools on a web browser.

Solution

This hotfix updates the Apex One server program to remove the vulnerability.

When the Trend Micro Data Loss Prevention™ (DLP) service is enabled on Apex One security agent computers, Google Chrome version 75 and higher versions may stop unexpectedly while accessing certain URLs.

Solution

This hotfix updates the DLP module to resolve this issue.

On the web console, "Advanced Search" from "Agents > Agent Management" page yields inaccurate results when the "Restart Required" is enabled and both "Update" and "Cleanup" options are selected.

Solution

This hotfix updates the Apex One server program to resolve the problem.

In Microsoft™ Windows™ 10, the new system process "MemCompression" may incorrectly trigger a false detection for violating the Device Access Control (DAC) policies.

Solution

This hotfix updates the DAC policies to prevent the false alarms.

Users are able to change to a password that contains German Umlaut characters but will not be allowed to log in to the web console after the change. The pop-up error message is not triggered that prevents from saving invalid password.

Solution

This hotfix updates the server program to ensure that the corresponding pop-up error message that prevents users from saving invalid passwords is triggered correctly.

When users deploy an agent policy to enable or disable the Endpoint Sensor feature while registering or unregistering from the TIC at the same time, the policy deployment will fail.

Solution

This hotfix updates the policy deployment mechanism to solve the policy conflict issue.

After a hotfix is applied, the pattern version and last update time of "Certified Safe Software pattern" are reset to "0", and as a result, the wrong pattern information appears on the Apex Central dashboard.

Solution

This hotfix updates the Apex One server files to resolve this issue.

This hotfix integrates an Antimalware Scan Interface (AMSI) for suspicious PowerShell detection to the Endpoint Sensor.

During license key deployment, Endpoint Sensor may not be able to receive the product key and storage key properties.

Solution

This hotfix improves the Apex One server's key deployment mechanism to solve this issue.

Some Security Agents may be unable to retrieve new policy settings from the Apex Central server.

Solution

This hotfix purges old policy records from the policy tracking table to fix this issue.

The Endpoint Sensor on Apex One agents may not be able to calculate the hash value of a specific process which can prevent the terminate process function from terminating the process.

Solution

This hotfix updates the Endpoint Sensor hash calculation mechanism to resolve this issue.

The Endpoint Sensor feature has been enhanced to only monitor and record memory "Read" events for the lsaas.exe process. All other "Read" events are ignored. In addition, a cache has been implemented for processes that open the memory "Write" event to avoid recording duplicated events that may cause a resource issue on the endpoint.

TmListen stops unexpectedly when the Apex One agent queries Suspicious Object (SO) information that contains a null notify setting.

Solution

This critical patch updates Apex One agent program to resolve the issue.

On the 64-bit Microsoft ™ Windows ™ 10 platform, an error occurs while running a 64-bit debug script in Microsoft Visual Studio 2017.

Solution

This critical patch updates the Behavior Monitoring Module to prevent the error.

The Apex One server may not be able to register to the Apex Central server if the TLS 1.2 protocol is enabled on Apex One servers only.

Solution

This critical patch updates the Apex One server program to resolve this issue.

Procedure

To apply the solution:

  1. Install this critical patch (see "Installation").
  2. Open the "Agent.ini" file in the "\PCCSRV\CmAgent\" folder on the Apex One server installation directory using a text editor.
  3. Under the "Network" section, manually modify the value of the following key.
  • [Network]
  • SSL_Cipher_List=ECDHE-RSA-AES256-GCM-SHA384
  1. Save the changes and close the file.
  2. Unregister from the Apex Central server.
  3. Register the Apex Central again.

The Apex One server tool "IpXfer.exe" cannot run properly when the Apex One Security Agent is offline.

Solution

This critical patch updates Apex One server tools to resolve this issue.

The Apex One server updates the timestamp of the Last Spyware Scan (Manual) according to the last connection establishment time.

Solution

This critical patch updates the Apex One server program to ensure that the last Spyware Scan (Manual) time is updated accurately.

When users create a "Setup" installer package for the Apex One security agent using Agent Packager, the Vulnerability Protection and Application Control agent installers are not included by default.

Solution

This critical patch updates the Apex One server program to ensure that the Agent Packager includes both installers in the Apex One security agent "Setup" installer package.

The digital signature of some DLP files are expired.

Solution

This critical patch updates the DLP module to update the digital signatures.

The DLP module does not work on the Microsoft Edge web browser.

Solution

This critical patch updates the DLP module to resolve this issue.

Procedure

To enable Apex One security agents to block sensitive information on the Edge web browser.

  1. Install this critical patch (see "Installation").
  2. Open the "dlp.ini" file in the "\PCCSRV\Private\" folder on the Apex One server.
  3. Under the "Configure" section, manually add the following key and value.
  • [Configure]
  • ENABLE_DYNAMIC_CODE_POLICY=true
  1. Save the changes and close the file.
  2. Open the Apex One web console and click "Agents > Agent Management > Select domains or agents > Settings > DLP settings".
  3. Click "Save" to deploy the settings to agents. The Apex One server deploys the settings to Apex One agents and adds the following key in the "dsa.pro" file in the "\Windows\System32\dgagent\" folder:
  • enable_dynamic_code_policy=true

Users cannot expand the domains or add spyware/greyware detections into the approve list on the Apex One server web console.

Solution

This critical patch updates the Apex One server files to resolve this issue.

Duplicate Apex One agents appear in the Microsoft Windows Startup console.

Solution

This critical patch updates the Apex One server programs to resolve this issue.

When the trust permission of the Application Control Criteria is set to "Inheritable execution rights", the criteria information remains on the Apex One Security Agent database after users remove the criteria from the policy setting.

Solution

This critical patch ensures that the criteria information can be removed normally from Apex One Security Agents.

In rare situations, the Apex One Vulnerability Protection program uses up a huge amount of memory when processing a large number of Intrusion Prevention logs.

Solution

This critical patch prevents the high memory usage issue when the Apex One Vulnerability Protection program processes a large number of Intrusion Prevention logs.

The Apex One server does not send the policy information to Apex Central after deploying a policy.

Solution

This issue updates the Apex One server program to resolve this issue.

An access denied error related to a certain component prevents the Trend Micro Advanced Threat Assessment Service (ATAS) from starting successfully.

Solution

This critical patch resolves the error so ATAS can start normally.

An issue related to the Microsoft™ Monitoring Agent may cause the Apex One Endpoint Sensor Advanced Threat Assessment Service application pool to stop unexpectedly after installing the Apex One server.

Solution

This critical patch prevents the Apex One Endpoint Sensor Advanced Threat Assessment Service compatibility issue with the Microsoft Monitoring Agent.

An "Error ID: 420" occurs while the Apex One Endpoint Sensor policy is deployed and the "Unable to get the registered server list. There are no registered servers." error appears on the Apex Central "Preliminary Investigation" page.

Solution

This critical patch helps prevent the Apex One Endpoint Sensor Advanced Threat Assessment Service from being corrupted when Endpoint Sensor is installed using Trend Micro Apex One Installer Maintenance Mode.

The Trend Micro Vulnerability Protection Service cannot start while processing a specific certificate.

Solution

This critical patch updates the Apex One Vulnerability Protection server to prevent the certificate processing error.

This critical patch updates some Apex One files to detect inconsistent certifications from the Microsoft Management Console certificate store. If it detects an inconsistency, Apex One will automatically recover the authentication file (OfcIPCer.dat) from the Microsoft Management Console certificate store on the Apex One server.

An Apex One agent that runs on Windows 7 and automatically detects proxy settings will not be able to connect to the Apex One server.

Solution

This hotfix resolves the issue by updating the Apex One agent program to ensure that it can retrieve the correct proxy configuration.

When the agents call "cgiOnScan.exe" and fails, the system keeps resending the request without waiting. This issue generates lots of records in the IIS log.

Solution

This hotfix updates the Apex One agent program to wait for few seconds before retrying.

This hotfix enables Apex One to send "Dropped" and "Accepted" action results in firewall violation logs to Apex Central. This ensures that both action results display normally on Apex Central instead of being displayed as "unknown".

An issue prevents the Data Loss Prevention™ (DLP) license from being deployed from Apex Central to Apex One.

Solution

This hotfix adds support for the DLP AC key type to solve this issue.

An access denied error related to a certain component prevents the Trend Micro Advanced Threat Assessment Service (ATAS) from starting successfully.

Solution

This hotfix resolves the error so ATAS can start normally.

The operating system may stop responding when users switch both the Scan Engine (VSAPI) and the Endpoint Sensor to debug mode at the same time using the Case Diagnostic Tool (CDT).

Solution

This hotfix resolves the issue by ensuring that CDT works normally when both VSAPI and Endpoint Sensor are enabled.

There is a typographical error in the "Type the full program path" hint on the "Behavior Monitoring Settings" page of the Apex One web console.

Solution

This hotfix updates the Apex One server files to correct the error.

An issue causes Apex One security agent remote installation to fail.

Solution

This hotfix updates the Apex One server program to resolve this issue.

Security Agents with the Behavior Monitoring program inspection feature enabled may cause Adobe Acrobat/Reader to stop unexpectedly.

Solution

This hotfix updates the program inspection feature to resolve this issue.

When users attempt to configure the Device Control settings on an Apex One Security Agent by deploying a policy from the Apex Central web console, the Device Control settings cannot be applied on the agent if Data Loss Prevention™ (DLP) is not enabled on the agent.

Solution

This hotfix updates the Apex One server program to resolve this issue.

If the activation (AC) key is deployed after its expiration date has been extended, the ES service will still receive the original expiration date.

Solution

This hotfix ensures that the ES service will receive the AC key's new expiration date.

The Endpoint Sensor may purge the Root Cause Analysis results by mistake when Apex Central is managing more than one Apex One server.

Solution

This hotfix resolves the issue.

In rare instances, the Endpoint Sensor may receive the investigation results from an agent at the same time that the same agent is being uninstalled. When this happens, the Endpoint Sensor may not be able to send all the results back to TIC.

Solution

This hotfix prevents this issue.

An issue related to the Microsoft™ Monitoring Agent may cause the Apex One Endpoint Sensor Advanced Threat Assessment Service application pool to stop unexpectedly after installing the Apex One server.

Solution

This hotfix prevents the Apex One Endpoint Sensor Advanced Threat Assessment Service compatibility issue with the Microsoft Monitoring Agent.

An unquoted service path enumeration vulnerability may allow an attacker administrator privileges to the Apex One security agent service.

Solution

This hotfix updates the Apex One security agent program to remove the vulnerability.

Coexisting Apex One security agents cannot set the server information of the Smart Protection Service Proxy correctly. When this happens, the coexisting agents do not send query requests through the Smart Protection Service proxy but directly to the Trend Micro Smart Protection Network instead. This may cause a connection issue if the agents cannot connect to the Internet.

Solution

This hotfix updates the Apex One security agent program to resolve the issue.

The installation status on the "Agent Installation Progress" page of the Apex One web console is inaccurate.

Solution

This hotfix updates the Apex One server program to resolve this issue.

A specific keyword triggers the DLP template that does not have any criteria specified.

Solution

This hotfix updates the DLP template to resolve this issue.

The Connection Status (Online/Offline) of an agent on the web console changes each time a user logs on or off from the client computer.

Solution

This hotfix updates the Apex One agent program to resolve the issue.

Attempting to restart or stop the WMI service (winmgmt) is unsuccessful on endpoints with the Security Agent installed. The tmlisten service of the Security Agent has a dependency with the WMI service.

Solution

This hotfix updates the Security Agent program to remove the WMI service dependency.

When the Apex One server registers to the Apex Central server, the Apex One Master Service may stop unexpectedly because of an empty private key.

Solution

This hotfix updates the Apex One server program to ensure that it can handle an empty public/private key.

An "Error ID: 420" occurs while the Apex One Endpoint Sensor policy is deployed and the "Unable to get the registered server list. There are no registered servers." error appears on the Apex Central "Preliminary Investigation" page.

Solution

This hotfix helps prevent the Apex One Endpoint Sensor Advanced Threat Assessment Service from being corrupted when Endpoint Sensor is installed using Trend Micro Apex One Installer Maintenance Mode.

Users cannot export the Application Control criteria in Microsoft™ Internet Explorer™ or the Edge web browser.

Solution

This hotfix updates the Apex Central files to resolve this issue.

When the "Do not allow users to access the Security Agent console from the system tray or Windows Start menu setting" option is enabled on the Apex One web console, the Apex One Security Agent console cannot be accessed while "PccNT.exe" is running.

Solution

This hotfix updates a parameter in "wofielauncher.exe" to resolve the issue.

The Vulnerability Protection server service start up fails on platforms that disable Transport Layer Security (TLS) 1.0.

Solution

This hotfix updates the Vulnerability Protection server to prevent the TLS version issue.

Vulnerability Protection causes unusual CPU usage on some workstations and servers.

Solution

This hotfix modifies the Vulnerability Protection service to prevent unusual CPU usage.

This hotfix adds a dynamic share key for Apex One security agents in the encryption and decryption algorithm.

This hotfix adds new Regular Expressions to the Trend Micro Data Loss Prevention™ (DLP) Data Identifiers.

This hotfix updates the Apex Central files to display more information about the Application Control violation log entries.

NOTE: This feature requires the installation of Apex Central hotfix 3919 or above.

The Security Agent program may become corrupted when users install it from the MSI installation package (Windows Installer) using the wrong command in the command line.

Solution

This critical patch enables the Apex One security agent installation to abort the MSI installation process if it encounters an unexpected command.

An issue related to the Microsoft™ Excel™ files with macro content cannot be saved to a network shared folder from an endpoint, some Microsoft Excel temp files cannot be deleted after trying to save the files.

Solution

This critical patch updates the Apex One security agent program to resolve this issue.

This critical patch enables the Apex One security agent program to support Microsoft Windows™ 10 (version 1903) May 2019 Update.

Changes in the Google API prevents Data Loss Prevention™ (DLP) from detecting sensitive information sent through Gmail in Google Chrome 73.

Solution

This hotfix resolves the issue by enabling the DLP module to support the "Http/Https" and "Open file dialog" functionality in Google Chrome 73.

The tmlisten service stops unexpectedly when users add an NIC description in the Personal Firewall (PFW) profile and deploy the profile to agents.

Solution

This hotfix updates the Apex One Security Agent program to resolve the issue.

The Smart Scan Pattern of File Reputation Services occupies a large amount of disk space on the Apex One server.

Solution

This hotfix updates the Apex One server program to resolve this issue.

When users install Apex One and use a domain account to connect to the database, the installation will not be able to create a database and iES will not be installed successfully.

Solution

This hotfix updates the impersonate method to solve this issue.

When the Apex One environment runs an sqlpackage older that 2016 or one that contains both x86 and x64 versions of version 2016, iES will not be able to create the database because of an incompatible sqlpackage version.

Solution

This hotfix resolves the issue by enabling the installer to prioritize the x64 version of the sqlpackage during installation.

When a user starts a Security Agent outside the corporate network, the Security Agent does not communicate on Online status to the Edge Relay Server.

Solution

This hotfix updates Security Agent program to send an Online status to the Edge Relay Server as soon as the Security Agent program starts.

The Apex One Application Control lockdown feature does not work after users switch to a different user account.

Solution

This hotfix ensures that the feature works normally.

This hotfix updates the DLP template to reduce the performance impact of Apex One.

A directory traversal vulnerability may allow an attacker to modify arbitrary files on the product's management console.

FAQs

Is Trend Micro Apex One legit? ›

Accurate and perfect Security application Trend Micro Apex One . It provides reliable and secure environment with in the organization which increase organizational growth and enhances customer relationship . it provides security against ransomware which is great features and prevents ransomware .

What is Trend Micro Apex One as a service? ›

Trend Micro Apex One™ Application Control allows you to: Block malicious software from running using customizable lockdown, safelisting, and blocklisting policies. Create dynamic policies by leveraging Trend Micro's application categorization and reputation intelligence to reduce management overhead.

Is Trend Micro Apex One an antivirus? ›

The Trend Micro Endpoint Security platform Apex One (formerly OfficeScan) provides antivirus and malware detection, and endpoint visibility. The product suite can be extended with associated applications that cover mobile endpoint protection, endpoint encryption, as well as network and server vulnerability protection.

How do I know if I have Trend Micro Apex 1? ›

Better understanding of Trend Micro Technical Support since these information will be requested during the initial support contact.
...
Product version or build
  1. Log on to the Apex One web console.
  2. Click Help > About.
  3. On the window that opens, check the product version and build:

What is the latest version of Trend Micro Apex One? ›

Trend Micro has released Apex One Patch 5 (Build 9565) and is now available in the Trend Micro Download Center. This patch contains accumulated fixes, security enhancements, and support for the Microsoft Windows™ 10 (Version 21H1) May 2021 Update. For support assistance, please contact Trend Micro Technical Support.

Is the apex Anti Virus good? ›

It's been stable, reliable, and has provided excellent protection. It doesn't get in the way of users and has minimal impact on system performance. It's also easy to administer, and with the upgrade to Apex One, promises an even easier path to administration for overworked IT units.

What is the latest version of Trend Micro? ›

LAST UPDATED: APR 08, 2022

Know if your Windows 11, Windows 10, or Windows 8.1 laptop or desktop computer is running the latest version of Trend Micro Security. Open Trend Micro. Hover your mouse at the top left corner. It should display Version: 17.7.

Is Trend Micro Apex One EDR? ›

Apex One introduces expanded endpoint detection and response (EDR) capabilities. It also connects to Trend Micro's managed detection and response (MDR) service option that boosts in-house teams with threat hunting and alert monitoring.

How do I install an apex one? ›

  1. Log in to your Apex Central web console.
  2. Go to Administration > Security Agent Download. ...
  3. Select the Operating system.
  4. Select the Installation mode: ...
  5. Select Package type:
Mar 10, 2022

What is Trend Micro used for? ›

About Trend Micro

As a leader in cloud and enterprise cybersecurity, our platform delivers central visibility for better, faster detection and response and a powerful range of advanced threat defense techniques optimized for environments, like AWS, Microsoft, and Google.

How do I cancel Trend Micro? ›

Cancel your Trend Micro Cloud One account
  1. Sign in to your Trend Micro Cloud One account and navigate to the Workload Security console.
  2. Click your account name and select Cancel Account.
  3. Select the I have read and understood the above information check box, and then click Cancel My Account.

How do I update my Trend Micro Apex One? ›

Manually update the components on the Apex One server after installing or upgrading the server and whenever there is an outbreak.
  1. Go to Updates > Server > Manual Update.
  2. Select the components to update.
  3. Click Update. The server downloads the updated components.

Is Trend Micro compatible with Windows 11? ›

YES. Trend Micro customers who have the current Trend Micro Security version installed on their PC are ready and compatible with Windows 11.

How do I know if my Trend Micro is working? ›

Go to Settings > Applications > Manage Applications > All (tab) and check if Mobile Security (with the Trend Micro t-ball logo) is listed. Go to Settings > Applications > Running Service > Running (tab) and check if Mobile Security (with the Trend Micro t-ball logo) is listed.

How do I know if Trend Micro is updated? ›

in the taskbar notification area, then select Check for Program Updates. If you cannot see it, click the Show hidden icons arrow ^ next to the notification area. The About Your Software window will appear and show the program version. It will also check for available updates.

Is Trend Micro compatible with Windows 10? ›

The Windows upgrade error appears because the current version of the Trend Micro Security Agent is not compatible to the newer Windows OS build.

Are Trend Micro Apex One patches cumulative? ›

These cumulative packages fix issues identified in support tickets are ultimately bundled into upgrades (patch, service pack…) and are made available in the Trend Micro Download Center on a regular basis.

Does Apex support Windows 7? ›

Apex One Security Agent Supported Platforms

Support for Windows 7 is being phased out. Refer to this article for more information and end-of-support dates.

What is Apex on PC? ›

Apex Legends is a free-to-play battle royale game that's available on PS4, Xbox One, and PC. Learn the basics of how to play Apex Legends on your PC including where to download, how to play with friends, and everything else that you need to know to become a champion.

How do I disable Trend Micro security agent without password? ›

Go to Administration > Global Settings > Desktop/Server. Under Security Agent Uninstallation Password section, select Allow the client user to uninstall the Security Agent without a password. Click Save.

How do I enable Apex one on my Mac? ›

Apex One (Mac) Security Agent.
...
  1. On the alert notification window, click Enable Extension. ...
  2. Click Open Safari Extensions.
  3. Select the Trend Micro Toolbar for Mac option to enable the extension.

Does Trend Micro scan for malware? ›

What is Trend Micro HouseCall? It is a free scanner that detects and cleans viruses, worms, malware, spyware, and other malicious threats that can harm computers and laptops.

How many devices can I protect with Trend Micro? ›

Maximum Security

Covers up to five (5) devices: Windows or Mac laptops or desktop computers; Android phones or tablets; iPhones or iPads. Number of protected devices may vary per country.

Why is my Trend Micro not updating? ›

Why did this happen? Your computer may have a corrupted Trend Micro update file or a conflicting third-party security software.

What is the difference between AV and EDR? ›

AV provides the ability to detect and respond to malware on an infected computer using a variety of different techniques. EDR incorporates AV and other endpoint security functionality providing more fully-featured protection against a wide range of potential threats.

Is Trend Micro Worry Free an EDR? ›

Trend Micro™ Worry-Free™ Services Endpoint Sensor gives insight to detections by allowing threat investigators to explore detections using EDR investigation functionality.

What is an EDR sensor? ›

Endpoint detection and response (EDR), also known as endpoint threat detection and response (ETDR), is an integrated endpoint security solution that combines real-time continuous monitoring and collection of endpoint data with rules-based automated response and analysis capabilities.

How do I install an apex one agent on Windows 10? ›

Step-by-Step Installation Guide
  1. In the web console, go to Agents > Agent Installation > Remote.
  2. Select the target endpoints. ...
  3. Type the user name and password and then click Log in. ...
  4. Repeat steps 3 and 4 to add more endpoints.
  5. Click Install when you are ready to install the Apex One agent to target endpoints.
Mar 7, 2022

How do I install Trend Micro endpoint protection? ›

Double-click the Endpoint Application Control server program on the Windows Add/Remove Programs screen. b. Click Control Panel > Add or Remove Programs. Locate and double-click Trend Micro Endpoint Application Control.

How do I install Trend Micro on Windows Server? ›

To install the OfficeScan 10.6 server:
  1. Locate and launch the Setup program. You can do choose to: ...
  2. Accept the Software License Agreement. Select I accept the terms of the license agreement and then click Next.
  3. Review the installation requirements and Access Usage Guides. Client Deployment.

Does Trend Micro slow down your computer? ›

Trend Micro Anti-Malware Solutions has started slowing everything down on my computer. Disk usage is 100%.

Is Trend Micro a Russian company? ›

Trend Micro Inc. (トレンドマイクロ株式会社, Torendo Maikuro Kabushiki-Gaisha) is a Japanese multinational cyber security software company with global headquarters in Tokyo, Japan and Irving, Texas, United States, and global R&D headquarters in Taipei, Taiwan.

Is Trend Micro a good VPN? ›

In short: Trend Micro's VPN is much, much less useful than any of the top VPNs on the market. It's not even good when compared to other antivirus-bundled VPNs like those of Norton and McAfee.

How long does Trend Micro last? ›

LAST UPDATED: SEP 06, 2021

The free trial Trend Micro offers is good for 30 days. After it lapses, purchase the full version to make sure your computer stays protected.

How do I stop automatic renewal of data? ›

With a short USSD Code you dial on your smartphone, auto-renewal will be cancelled permanently for all active data bundles on your line. Simply dial *229*0# to deactivate this feature.

How do I stop auto-renewal? ›

Stop Auto Renew on Android phone and tablet
  1. Open the Google Play Store. ...
  2. Tap the profile icon located at the top-right corner.
  3. Tap Payments & Subscription, then select Subscriptions.
  4. Select the subscription that you want to cancel.
  5. Tap Cancel subscription.
  6. Follow the remaining instructions.
Jun 28, 2022

How do I update my apex client? ›

Click the provided link to Single Sign-On to the Apex One server. Go to Updates > Agents > Update Source. Under the Customized Update Source list, click Add. Enter the range of the IP addresses of the clients/agents that will receive the updates from the Update Agent.

How do I update Smart Scan Agent pattern in Trend Micro? ›

Look for the Smart Scan Agent Pattern version and compare it with the current version. If the current version is outdated, go to Updates > Server > Manual Update. Under Components to Update, expand Antivirus and select "Smart Scan Agent Pattern". Click Update.

How do I install Trend Micro on Windows 11? ›

How to install Trend Micro Security 2021 on your PC - YouTube

Does Trend Micro work with Google Chrome? ›

Install Trend Micro extension on Google Chrome or Chromebook

Get the app from the Chrome Web Store. If you purchased Trend Micro through Best Buy, click here instead. Click the Add to Chrome button. Click Add Extension, then wait for it to finish downloading.

Can I uninstall and reinstall Trend Micro? ›

As long as you have a Trend Micro account setup, reinstalling the Trend Micro program should not be a problem. Please go to this link so that you can be redirected to your Trend Micro account page.

How do I download Trend Micro to my computer? ›

How to install Trend Micro for Best Buy on Windows
  1. Click here to download the installer.
  2. Double-click the downloaded file to run the installer. If the User Account Control window appears, click Yes.
  3. Follow the instructions to complete the installation.
  4. Fill out the account information to activate your protection.
Apr 26, 2022

Does Trend Micro update automatically? ›

Trend Micro Internet Security, by default, definitely downloads the updates automatically for you. It constantly checks online for security updates to stop new threats every 3 hours.

How do I update my Trend Micro antivirus in Windows 10? ›

How to update Trend Micro Security on Windows
  1. Right-click the Trend Micro icon. in the taskbar notification area, then select Check for Program Updates. ...
  2. Click Close after seeing Components are up-to-date. Latest Version Update: 17.7.1337.
Apr 14, 2022

What is Trend Micro yearly plan? ›

Detected 100 percent of all Android malware. Antivirus software for iOS, Android, Mac or Windows devices. Prices start at $39.95 a year, with yearly and two-year packages available.

Videos

1. Apex Central Malware Policy Configuration Best Practices
(Trend Micro)
2. Registering Apex One to Apex Central
(Trend Micro)
3. Apex Central Installation Process
(Trend Micro)
4. Trend Micro Vision One Demo and Overview
(Trend Micro)
5. Trend Micro Deep security part 1
(Abhishek Security Vision)
6. Windows Bootable NVMe RAID 0 Tutorial on Gigabyte TRX40 Designare using Sabrent Rocket NVMe 4.0
(BuildOrBuy)

Latest Posts

Article information

Author: Duncan Muller

Last Updated: 08/21/2022

Views: 5583

Rating: 4.9 / 5 (59 voted)

Reviews: 82% of readers found this page helpful

Author information

Name: Duncan Muller

Birthday: 1997-01-13

Address: Apt. 505 914 Phillip Crossroad, O'Konborough, NV 62411

Phone: +8555305800947

Job: Construction Agent

Hobby: Shopping, Table tennis, Snowboarding, Rafting, Motor sports, Homebrewing, Taxidermy

Introduction: My name is Duncan Muller, I am a enchanting, good, gentle, modern, tasty, nice, elegant person who loves writing and wants to share my knowledge and understanding with you.