Trend Micro Apex One™ Readme (2023)

Solution

This Hotfix updates the DLP module to resolve this issue.

Solution

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

Solution

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

Solution

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

Solution

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

Solution

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

Solution

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

Solution

This Hotfix updates the DLP module to resolve this issue.

Solution

This Hotfix updates the DLP module to resolve this issue.

Solution

This Hotfix updates the DLP module to resolve this issue.

Solution

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

Solution

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

Solution

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

Solution

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

Solution

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

Solution

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

Solution

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

Solution

This Hotfix updates the related module to resolve this issue.

Solution

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

Solution

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

Solution

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

Solution

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

Solution

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

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.

Solution

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

Solution

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

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

4. Save the changes and close the file.
5. Open the Apex One web console and go to the"Agents > Global Agent Settings" screen.
6. 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

7. Restart the agent computer.

Solution

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

Solution

This Patch updates the Agent Packager to resolve this issue.

Solution

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

Solution

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

Solution

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

Solution

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

Solution

This Patch updates the DLP module to resolve this issue.

Solution

This Patch updates the DLP module to resolve this issue.

Solution

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

Solution

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

Solution

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

Solution

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

Solution

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

Solution

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

Solution

This Patch resolves this issue.

Solution

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

Solution

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

Solution

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

Solution

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

Solution

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

Solution

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

Solution

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

Solution

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

Solution

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

Solution

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

Solution

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

Solution

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

Solution

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

Solution

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

Solution

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

Solution

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

Solution

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

Solution

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

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

4. Save the changes and close the file.
5. Open the Apex One web console and go to the "Agents > Global Agent Settings" screen.
6. 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

Solution

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

Solution

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

Solution

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

Solution

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

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.

Solution

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

Solution

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

Solution

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

Solution

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

Solution

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

Solution

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

Solution

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

Solution

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

Solution

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

Solution

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

Solution

This Critical Patch resolves this issue.

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.

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.

Solution

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

Solution

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

Solution

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

Solution

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

Solution

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

Solution

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

Solution

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

Solution

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

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.

Solution

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

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.

Solution

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

Solution

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

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

4. Save the changes and close the file.
5. Open the Apex One web console and go to the "Agents > Global Agent Settings" screen.
6. 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

Solution

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

Solution

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

Solution

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

Solution

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

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)

4. Save the changes and close the file.
5. Restart the Apex One Master Service.

Solution

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

Solution

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

Solution

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

Solution

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

Solution

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

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

4. Save the changes and close the file.
5. Open the Apex One web console and go to the "Agents > Global Agent Settings" screen.
6. 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

Solution

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

Solution

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

Solution

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

Solution

This Patch updates the BM module to fix the issue.

Solution

This Patch updates the DLP module to resolve this issue.

Solution

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

Solution

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

Solution

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

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

4. Save the changes and close the file.
5. Open the Apex One web console and go to the "Agents > Global Agent Settings" screen.
6. 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

Solution

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

Solution

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

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

5. Reload the Apex One Security agent.

Solution

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

Solution

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

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.

Solution

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

Solution

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

Solution

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

Solution

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

Solution

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

Solution

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

Solution

This Patch updates the DLP templates to resolve this issue.

Solution

This Patch corrects the NFC server FQDN.

Solution

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

Solution

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

Solution

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

Solution

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

Solution

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

Solution

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

Solution

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

Solution

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

Solution

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

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 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.

Solution

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

Solution

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

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

4. Save the changes and close the file.
5. Open the Apex One web console and go to the "Agents > Global Agent Settings" screen.
6. 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

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

4. Save the changes and close the file.
5. Open the Apex One web console and go to the "Agents > Global Agent Settings" screen.
6. 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

Solution

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

Solution

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

Solution

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

Solution

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

Solution

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

Solution

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

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

4. 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

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

4. Save the changes and close the file.
5. Open the Apex One web console and go to the "Agents > Global Agent Settings" screen.
6. 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

Solution

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

Solution

This Critical Patch fixes the synchronization issue of the virus detection logs.

Solution

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

Solution

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

Solution

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

Solution

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

Solution

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

Solution

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

Solution

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

Solution

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

Solution

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

Solution

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

Solution

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

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.

Solution

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

Solution

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

Solution

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

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.

Solution

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

Solution

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

Solution

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

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.

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.

Solution

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

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.

Solution

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

Solution

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

Solution

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

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

4. Save the changes and close the file.
5. Open the Apex One web console and go to the "Agents > Global Agent Settings" screen.
6. 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

7. Restart the Apex One security agent.

Solution

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

Solution

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

Solution

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

Solution

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

Procedure

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"

4. Save the changes and close the file.

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.

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.

Solution

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

Solution

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

Solution

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

Solution

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

Solution

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

Solution

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

Solution

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

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

5. Open the Apex One web console and go to the "Agents > Global Agent Settings" screen.
6. 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

Solution

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

Solution

This Critical Patch resolves this issue.

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

4. Save the changes and close the file.
5. Open the Apex One web console and go to the "Agents > Global Agent Settings" screen.
6. 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)

7. Restart the Apex One Security Agent.

Solution

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

Solution

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

Solution

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

Solution

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

Solution

This Critical Patch resolves the issue to remove the vulnerability.

Solution

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

Solution

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

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

4. Save the changes and close the file.
5. Open the Apex One web console and go to the "Agents > Global Agent Settings" screen.
6. 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

Solution

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

Solution

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

Solution

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

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

4. Save the changes and close the file.
5. Open the Apex One web console and go to the "Agents > Global Agent Settings" screen.
6. 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

Solution

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

Solution

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

Solution

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

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

4. Save the changes and close the file.

Solution

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

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.

Solution

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

Solution

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

Solution

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

Solution

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

Solution

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

Solution

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

Solution

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

Solution

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

Solution

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

Solution

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

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

4. Save the changes and close the file.
5. Restart the Apex One Master Service.
6. Perform a restart on the affected Apex One security agents.

Solution

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

Solution

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

Solution

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

Solution

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

Solution

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

Solution

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

Solution

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

Solution

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

Solution

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

Solution

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

Solution

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

Solution

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

Solution

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

Solution

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

Solution

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

Solution

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

Solution

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

Solution

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

Solution

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

Solution

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

Solution

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

Solution

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

Solution

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

Solution

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

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

4. Save the changes and close the file.
5. Open the Apex One web console and go to the "Agents > Global Agent Settings" screen.
6. 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

7. Restart the Apex One security agent.

Solution

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

Solution

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

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.

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

Solution

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

Solution

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

Solution

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

Solution

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

Solution

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

Solution

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

Solution

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

Solution

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

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.

Solution

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

Solution

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

Solution

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

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.

Solution

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

Solution

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

Solution

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

Solution

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

Solution

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

Solution

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

Solution

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

Solution

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.

Solution

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

Solution

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

Solution

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

Solution

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

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

4. Save the changes and close the file.
5. Open the Apex One web console and go to the "Agents > Agent Management > Select domains or agents > Settings > DLP settings" screen.
6. 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

7. Restart the Apex One agent machines.

Solution

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

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

4. Save the changes and close the file.
5. Open the Apex One web console and go to the "Agents > Global Agent Settings" screen.
6. 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_

7. Open the Apex One web console and go to the "Agents > Agent Management > Manage Agent Tree > Add Domain" page.
8. 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.

9. 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 |
10. 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.

11. 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

Solution

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

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

4. Save the changes and close the file.
5. Open the Apex One web console and click "Agents > Agent Management > Select domains or agents > Settings > DLP settings".
6. Click "Save" to deploy the settings to agents.
7. The Apex One server deploys the settings to Apex One agents.

Solution

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

Solution

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

Solution

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

Solution

This patch resolves the Application Control issue.

Solution

This patch fixes the vulnerability.

Solution

This patch fixes the vulnerability.

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.

Solution

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

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

Solution

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

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.

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.

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

4. Save the changes and close the file.
5. Open the Apex One web console and go to the "Agents > Global Agent Settings" screen.
6. 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

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

4. Save the changes and close the file.
5. Restart the Apex One Master Service

Solution

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

Solution

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

Solution

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

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."

Solution

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

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.

Solution

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

Solution

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

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

4. Save the changes and close the file.
5. Open the Apex One web console and go to the "Agents > Global Agent Settings" screen.
6. 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

Solution

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

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.

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

4. 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.

Solution

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

Solution

This hotfix resolves the buffer overrun issue.

Solution

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

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.

Solution

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

Solution

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

Solution

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

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".

4. Save the changes and close the file.
5. Open the Apex One web console and go to the "Agents > Global Agent Settings" screen.
6. 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

7. Restart the Apex One security agent computers.

Solution

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

Solution

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

Solution

This hotfix updates the rule to minimize alerts.

Solution

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

Solution

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

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.

Solution

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

Solution

This hotfix updates the DLP module to resolve this issue.

Solution

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

Solution

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

Solution

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

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".

4. Save the changes and close the file.
5. Open the Apex One web console and go to the "Agents > Global Agent Settings" screen.
6. 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

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.

Solution

This patch updates the DLP module to resolve this issue.

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

4. Save the changes and close the file.

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

Solution

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

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

4. Save the changes and close the file.
5. Open the Apex One web console and go to the "Agents > Global Agent Settings" screen.
6. 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

Solution

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

Solution

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

Solution

This hotfix updates the DLP module to resolve this issue.

Solution

This hotfix updates the DLP module to resolve this issue.

Solution

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

Solution

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

Solution

This hotfix updates the Apex One agent program to prevent this issue from occurring.

Solution

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

Solution

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

Solution

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

Solution

This critical patch updates the Trend Micro EagleEye Driver to resolve this issue.

Solution

This critical patch updates the Attack Discovery pattern to help prevent the high CPU usage issue on the Apex One server computer.

Solution

This critical patch ensures that the PowerShell command line does not automatically convert uppercase characters to lowercase.

Solution

This critical patch updates the Apex One server program to remove this vulnerability.

Solution

This critical patch updates the Apex One server program to remove this vulnerability.

Solution

This critical patch updates the Apex One server program to remove this vulnerability.

Solution

This critical patch updates the Apex One server files to resolve this issue.

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)

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.

Solution

This hotfix resolves this issue so that the system can install the Application Control server successfully.

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

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

4. Save the changes and close the file.
5. Open the Apex One web console and go to the "Agents > Global Agent Settings" screen.
6. 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)

7. Restart the Apex One agent machines.

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

4. Save the changes and close the file.
5. Open the Apex One web console and go to the "Agents > Global Agent Settings" screen.
6. 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!"

7. Restart the Apex One security agent.

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".

3. 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.

4. 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 "/>

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.

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.

Solution

This hotfix resolves the error so the Advanced Threat Assessment Service can be installed successfully.

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.

Solution

This patch updates the database column name in the Apex One Vulnerability Protection server to "SystemVersionID" to resolve this issue.

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

4. Save the changes and close the file.
5. Open the Apex One web console and go to the "Agents > Global Agent Settings" screen.
6. 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

7. Restart the security agent

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.

Solution

This hotfix updates the user mode event related module to version 8.5.2065 to solve the issue.

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

4. Save the changes and close the file.
5. Open the Apex One web console and go to the "Agents > Global Agent Settings" screen.
6. 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"

Solution

This hotfix updates TMVS to resolve this issue.

Solution

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

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.

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.

Solution

The Apex One Endpoint Sensor changes the event source from User mode to kernel mode to resolve this issue.

Solution

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

Solution

This hotfix updates the Apex One server 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 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

4. Save the changes and close the file.
5. Open the Apex One Web console and go to the "Agents > Global Agent Settings" screen.
6. 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

Solution

This critical patch updates the Apex One server program to remove the vulnerability.

Solution

This critical patch updates the Apex One server program to remove the vulnerability.

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)

4. Restart the Apex One security agent.

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

4. Save the changes and close the file.
5. Open the Apex One web console and go to the "Agents > Global Agent Settings" screen.
6. 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

7. Restart the security agent

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.

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.

Solution

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

Solution

This hotfix resolves the issue so the Application Control can be installed successfully on affected endpoints.

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.

Solution

This hotfix resolves the issue.

Solution

This hotfix resolves the issue.

Solution

This hotfix resolves this issue by adding hooking points for event correlation to detect the suspicious attack behavior.

Solution

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

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.

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.

Solution

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

Solution

This hotfix updates the DLP module to resolve this issue.

Solution

This hotfix updates the Apex One server program to resolve the problem.

Solution

This hotfix updates the DAC policies to prevent the false alarms.

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.

Solution

This hotfix updates the policy deployment mechanism to solve the policy conflict issue.

Solution

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

Solution

This hotfix improves the Apex One server's key deployment mechanism to solve this issue.

Solution

This hotfix purges old policy records from the policy tracking table to fix this issue.

Solution

This hotfix updates the Endpoint Sensor hash calculation mechanism to resolve this issue.

Solution

This critical patch updates Apex One agent program to resolve the issue.

Solution

This critical patch updates the Behavior Monitoring Module to prevent the error.

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

4. Save the changes and close the file.
5. Unregister from the Apex Central server.
6. Register the Apex Central again.

Solution

This critical patch updates Apex One server tools to resolve this issue.

Solution

This critical patch updates the Apex One server program to ensure that the last Spyware Scan (Manual) time is updated accurately.

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.

Solution

This critical patch updates the DLP module to update the digital signatures.

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

4. Save the changes and close the file.
5. Open the Apex One web console and click "Agents > Agent Management > Select domains or agents > Settings > DLP settings".
6. 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

Solution

This critical patch updates the Apex One server files to resolve this issue.

Solution

This critical patch updates the Apex One server programs to resolve this issue.

Solution

This critical patch ensures that the criteria information can be removed normally from Apex One Security Agents.

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.

Solution

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

Solution

This critical patch resolves the error so ATAS can start normally.

Solution

This critical patch prevents the Apex One Endpoint Sensor Advanced Threat Assessment Service compatibility issue with the Microsoft Monitoring Agent.

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.

Solution

This critical patch updates the Apex One Vulnerability Protection server to prevent the certificate processing error.

Solution

This hotfix resolves the issue by updating the Apex One agent program to ensure that it can retrieve the correct proxy configuration.

Solution

This hotfix updates the Apex One agent program to wait for few seconds before retrying.

Solution

This hotfix adds support for the DLP AC key type to solve this issue.

Solution

This hotfix resolves the error so ATAS can start normally.

Solution

This hotfix resolves the issue by ensuring that CDT works normally when both VSAPI and Endpoint Sensor are enabled.

Solution

This hotfix updates the Apex One server files to correct the error.

Solution

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

Solution

This hotfix updates the program inspection feature to resolve this issue.

Solution

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

Solution

This hotfix ensures that the ES service will receive the AC key's new expiration date.

Solution

This hotfix resolves the issue.

Solution

This hotfix prevents this issue.

Solution

This hotfix prevents the Apex One Endpoint Sensor Advanced Threat Assessment Service compatibility issue with the Microsoft Monitoring Agent.

Solution

This hotfix updates the Apex One security agent program to remove the vulnerability.

Solution

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

Solution

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

Solution

This hotfix updates the DLP template to resolve this issue.

Solution

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

Solution

This hotfix updates the Security Agent program to remove the WMI service dependency.

Solution

This hotfix updates the Apex One server program to ensure that it can handle an empty public/private key.

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.

Solution

This hotfix updates the Apex Central files to resolve this issue.

Solution

This hotfix updates a parameter in "wofielauncher.exe" to resolve the issue.

Solution

This hotfix updates the Vulnerability Protection server to prevent the TLS version issue.

Solution

This hotfix modifies the Vulnerability Protection service to prevent unusual CPU usage.

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.

Solution

This critical patch enables the Apex One security agent installation to abort the MSI installation process if it encounters an unexpected command.

Solution

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

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.

Solution

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

Solution

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

Solution

This hotfix updates the impersonate method to solve this issue.

Solution

This hotfix resolves the issue by enabling the installer to prioritize the x64 version of the sqlpackage during installation.

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.

Solution

This hotfix ensures that the feature works normally.

Solution

This critical patch updates the Apex One server program to remove the vulnerability.