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

Create a technical support case if you need further support.

Collecting logs for the User-Mode Hooking (UMH) module for an application crash issue

    • Updated:
    • 28 Dec 2016
    • Product/Version:
    • OfficeScan 11.0
    • Platform:
    • Windows 10
    • Windows 2008 32-Bit
    • Windows 2008 64-Bit
    • Windows 2012
    • Windows 7 32-Bit
    • Windows 7 64-Bit
    • Windows 8 32-Bit
    • Windows 8 64-Bit
    • Windows 8.1 32-Bit
    • Windows 8.1 64-Bit
Summary

This article introduces how to collect the UMH logs for a application crash issue caused by the UMH module.

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

Below is the installation path for UMH in OSCE:

<OfficeScan Agent Installation Path>\CCSF\MODULE\20019\

UMH has been involved since OfficeScan 11.0 Service Pack 1 Critical Patch 6054 (Ransomware CP) and OfficeScan XG.

Details
Public

To collect the UMH logs:

 
Always back up the whole registry before making any modifications. Incorrect changes to the registry can cause serious system problems.
  1. Set the registry key. Create a reg file and copy following content into it:

    Windows Registry Editor Version 5.00

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Windows Error Reporting\LocalDumps]
    "DumpFolder"=hex(2):43,00,3a,00,5c,00,6c,00,6f,00,63,00,61,00,6c,00,64,00,75,\
    00,6d,00,70,00,73,00,00,00
    "DumpType"=dword:00000002

  2. Import the reg file. Windows will collect the dump in the C:\localdumps folder automatically.
  3. Trigger the problem.
  4. Collect the dump file from the C:\localdumps folder.
  5. Get the UMH-related binary files:
    • <OSCE installation path>\CCSF\module\20019
    • %windir%\system32\tmumh
    • %windir%\syswow64\tmumh
    • %windir%\system32\drivers\tmumh.sys
  6. Get the UMH-related registry keys:
    • HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\tmumh
    • HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\GlobalFlag
    • HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Image File Execution Options
    • HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Windows
  7. Remove the imported registry keys after the logs are collected.
Premium
Internal
Rating:
Category:
Troubleshoot
Solution Id:
1115436
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.