Sign In with your
Trend Micro Account
Need Help?
Need More Help?

Create a technical support case if you need further support.

Enabling or disabling User-Mode Hooking (UMH) in Worry-Free Business Security Services (WFBS-SVC)

    • Updated:
    • 4 Mar 2018
    • Product/Version:
    • Worry-Free Business Security Services 6.1
    • Worry-Free Business Security Services 6.2
    • Worry-Free Business Security Services 6.3
    • Platform:
    • Windows 10 32-bit
    • Windows 10 64-bit
    • Windows 2008 Server R2
    • Windows 2008 Small Business Server
    • Windows 2008 Standard
    • Windows 2011 Small Business Server Standard
    • Windows 7 32-Bit
Summary

This article serves as an introduction to UMH in WFBS-SVC and provides steps on how to enable or disable User-Mode Hooking.

Details
Public

UMH is an engine in WFBS-SVC that supports the enhanced ransomware solution. It is installed in the Common Client Solution Framework (CCSF) service as a module. It also provides API events for other modules such as Behavior Monitoring, Predictive Machine Learning and others. These modules will make decisions according to the provided API events from the UMH.

The UMH has been added in WFBS-SVC since version 6.1 with the installation directory:

..\Trend Micro\Client Server Security Agent\CCSF\MODULE\20019\

To enable UMH:

  1. Navigate to Devices.
  2. Select a desktop or server group.
  3. Click Configure Policy.
  4. Go to the Windows tab then click Behavior Monitoring.

    Go to Behavior Monitoring tab

  5. On the Settings section, under Ransomware Protection, expand Enable all ransomware protection features.

    Expand Enable all ransomware protection features

  6. Tick Enable program inspection to detect and block compromised executable files.

    Enable program inspection to detect and block compromised executable files

  7. Deploy the setting by clicking the Save button.

To verify the status of UMH in the WFBS-SVC Agent:

  1. Check the following in the WFBS-SVC Agent’s registry:

    • x86 platform:

      [HKEY_LOCAL_MACHINE\SOFTWARE\TrendMicro\PC-cillinNTCorp\CurrentVersion\AEGIS]
      "EnableUMH"=dword:00000001

    • x64 platform:

      [HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\TrendMicro\PC-cillinNTCorp\CurrentVersion\AEGIS]

      "EnableUMH"=dword:00000001

  2. Check the UMH driver status in the command line:

    > sc query tmumh

    UMH should be running.

     
    Run Update Now on the WFBS-SVC Agent to force the UMH status update.

To disable UMH, disable the features that are directly dependent to UMH:

  1. Navigate to Devices.
  2. Select a desktop or server group.
  3. Click Configure Policy.
  4. Go to the Windows tab then click Behavior Monitoring.

    Behavior Monitoring tab

  5. On the Settings section, under Ransomware Protection, expand Enable all ransomware protection features.

    Enable all ransomware protection features

  6. Uncheck Enable program inspection to detect and block compromised executable files.

    Uncheck Enable program inspection to detect and block compromised executable files

  7. Deploy the setting by clicking the Save button.
  8. Go to Administration > Global Settings.
  9. Disable HTTPS Web Threat Protection.

    Disable HTTPS Web Threat Protection

  10. Deploy the setting by clicking the Save button.
 
HTTPS Web Threat Protection is a global setting. Unchecking this option disables the feature on all Windows devices.

To verify the status of UMH in the WFBS-SVC Agent:

  1. Check the following in the OfficeScan agent’s registry:

    • x86 Platform:

      [HKEY_LOCAL_MACHINE\SOFTWARE\TrendMicro\PC-cillinNTCorp\CurrentVersion\AEGIS]
      "EnableUMH"=dword:00000000

    • x64 Platform:

      [HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\TrendMicro\PC-cillinNTCorp\CurrentVersion\AEGIS]
      "EnableUMH"=dword:00000000

  2. Check the UMH driver in command line:

    > sc query tmumh

    UMH should be running before you reboot the computer.

     
    Before rebooting the computer, the UMH driver will still keep running because of some processes already injected. To avoid any risk, keep tmumh running before the system reboot. The new process created will not be hooked by UMH anymore.

    After you reboot the system, the driver will be stopped.

Premium
Internal
Rating:
Category:
Configure; Troubleshoot
Solution Id:
1119452
Feedback
Did this article help you?

Thank you for your feedback!

To help us improve the quality of this article, please leave your email here so we can clarify further your feedback, if neccessary:
We will not send you spam or share your email address.

*This form is automated system. General questions, technical, sales, and product-related issues submitted through this form will not be answered.

If you need additional help, you may try to contact the support team. Contact Support

To help us improve the quality of this article, please leave your email here so we can clarify further your feedback, if neccessary:
We will not send you spam or share your email address.

*This form is automated system. General questions, technical, sales, and product-related issues submitted through this form will not be answered.