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

Create a technical support case if you need further support.

GenCRCDiff.exe process causes high CPU utilization in Worry-Free Business Security (WFBS)

    • Updated:
    • 1 Apr 2020
    • Product/Version:
    • Worry-Free Business Security Standard/Advanced 7.0
    • Worry-Free Business Security Standard/Advanced 8.0
    • Worry-Free Business Security Standard/Advanced 9.0
    • Worry-Free Business Security Standard/Advanced 9.5
    • Platform:
    • Windows 2000 Professional
    • Windows 2000 Small Business Server
    • Windows 2003 Home Server
    • Windows 2003 Small Business Server
    • Windows 2003 Standard Server Edition
    • Windows 2008 Essential Business Server
    • Windows 2008 Small Business Server
    • Windows 7 32-bit
    • Windows Vista 32-bit
    • Windows XP Professional

Learn how to resolve the issue of the WFBS GenCRCDiff.exe process causing high CPU utilization.


SmartScan's GenCRCDiff process consumes much CPU and disk input/output. This is why the Core 2 Duo processor is recommended for Smart Scan Mode.

The Core 2 Duo processor has a throttling mechanism for CPU usage for GenCRCDiff, but it only works for non-hyper thread low-level machines. The default value is "60", which means that Smart Scan-related processes cannot use CPU over 60%.

Below are some data for your reference:

  • For Core 2 Duo processor high-level machines, it takes 1 to 2 minutes of high CPU to generate diffs (only one core).
  • For P4 2.0G non-hyper thread low-level machine, it takes 11 to 13 minutes of 60% CPU usage to generate diffs.
  • For middle-level machines, the processing time to generate diffs is longer and the CPU usage is in between low-level and high-level processors.

To change the CPU limit of the Smart Scan-related process:

Option I

Adjust the value of the CPU limit.

  1. Open the ..\Program Files\Trend Micro\Security Server\PCCSRV\wss folder\AU.ini file using a text editor like Notepad.
  2. Look for the "CPULimit" parameter, and set the value you prefer.
    It is up to you to decide the amount of CPU limit that you want to allocate to SmartScan. You can set it between 30 to 60, with "60" being the recommended value. You can set it lower, but the trade-off for lower CPU usage is longer GenDiff time, which is launched hourly.
  3. Save the changes.
  4. Restart Trend Micro Security Server Master Service.

Option II

Disable SmartScan to switch all clients to Conventional Scan mode.

Solution Id:
Did this article help you?

Thank you for your feedback!

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