Windows Modules Installer Worker High CPU Usage [4 Fixes]

Windows Update service is responsible for this issue

Reading time icon 3 min. read

Readers help support Windows Report. We may get a commission if you buy through our links. Tooltip Icon

Read our disclosure page to find out how can you help Windows Report sustain the editorial team Read more

Windows Modules Installer Worker high cpu

Windows Modules Installer Worker high CPU usage can cause various problems, and it can negatively impact your performance.

However, this problem can be resolved, and in today’s guide, we’re going to show you the best ways to do that.

Why is Windows Module Installer using 100% CPU?

Issues with Windows Update or corrupted system files are the most common culprits for this issue.

How do I fix Windows Modules Installer Worker with high CPU usage?

It’s possible that high CPU usage is caused by an update install in the background, so waiting is the best option. If the problem persists after an hour or so, try using one of the following solutions.

1. Delete the SoftwareDistribution folder

1.1 Stop Windows Update service

1. Press Windows key + R to open Run. Type services.msc and hit Enter.

services windows modules installer worker high cpu

2. In the Service window, look for Windows Update service.

3. Right-click on Windows Update service and select Stop.

stop windows modules installer worker high cpu

1.2 Delete the SoftwareDistribution folder

  1. Open File Explorer and navigate to the following directory: Local Disk (C:) > Windows
  2. Look for the SoftwareDistribution folder. Right-click on it, and select Delete.
    software distribution
  3. Reboot your PC.
  4. Press Windows + I and click on Update & security.
    update and windows modules installer worker high cpu
  5. Finally, click the Check for updates button.
    check for

2. Stop this process from running

  1. Press Ctrl + Shift + Esc to open Task Manager.
  2. Navigate to the Details tab.
  3. Locate TiWorker, right-click it, and choose End Task.

3. Prevent automatic Windows updates

  1. Press the Windows key + R, type services.msc, and click OK.
  2. Right-click the Windows Modules Installer option to open its properties.
  3. Now, set its Startup type to Manual and click Apply, followed by OK.
    manual option
  4. Go back to the Services window and double-click the Windows Update service.
    update windows modules installer worker high cpu
  5. Set its Startup type to Manual and click the Apply button, followed by OK.
    manual update windows modules installer worker high cpu
  6. Now, close the Services window.

4. Run Windows troubleshooter

  1. Press the Windows key + I and select the Update & Security option.
    update and windows modules installer worker high cpu
  2. Click Troubleshoot in the left pane and select Additional troubleshooters.
  3. Now, select Windows Update and click Run the troubleshooter.
    run the windows modules installer worker high cpu
  4. Finally, follow any recommendations to fix the issue with the Windows update.

Is Windows Modules Installer Worker safe?

Yes, Windows Modules Installer Worker is a Microsoft’s built-in system service, and it’s perfectly safe, even it causes high CPU usage.

Is Windows Modules Installer necessary?

This service is used for downloading and installing Windows updates, so it’s necessary if keep your system up to date.

We have a great guide on how to disable Windows Modules Installer, if you don’t want to use this service, so don’t miss it.

Why is Windows Module Installer Worker always running?

This service is closely related to Windows Update service, and if Windows Update service is running, the Module Installer Worker will run as well.

And with this, we can conclude this guide on how to solve this high CPU usage issue. We believe you have everything to fix the issue for good and get your PC working again.

If you are facing a similar issue in TiWorker.exe high CPU usage, check our detailed guide to fix it. We also have a guide on other Windows Modules Installer Service issues, so check it out for more solutions.

Feel free to let us know the solution that helped you fix this issue in the comments below.

More about the topics: High CPU usage