TiWorker.exe: CPU usage reaches 50% or 100% in Windows 10| Fix TiWorker issue

What is TiWorker.exe

TiWorker.exe (Windows Modules Installer Worker) is a system component in Microsoft Windows which is responsible for installing new modules and updates. Respectively, the process is able to use your CPU and produce a load on your disk. Usually the CPU usage hovers between 30 and 50% but in some cases TiWorker can load CPU up to 100%. It goes without saying that this will cause bad performance of the system. So let us find out what to do if you encouner high CPU usage by TiWorker.exe process. Here are our tips upon how to fix TiWorker.exe high CPU usage issue in Windows 10.TiWorker.exe high CPU load 50%

How to fix TiWorker high CPU usage issue

If your friend asks “TiWorker.exe is using up to 50% or 100% of the CPU. What can I do?“, let him follow the tips below to envestigate and solve the issue.

Advice 1. Wait!

If you notices the problem for the first time, give TiWorker.exe some time to complete its work. Just close all running apps, leave your PC in idle. Wait for an hour and watch for CPU usage. There is a high probability that the process will complete all its tasks and stop loading the processor.

Advice 2. Reboot

If you have waited for an hour but TiWorker.exe process is still using your CPU, reboot your system. In many cases it calms down after reboot without any extra actions from user.

Advice 3. Search for updates manually

Perform a manual check for updates as we explained here:


If there are any updates available install them and reboot your system. It should be said that this method helps to stop TiWorker.exe using the CPU very often.

Advice 4. Clear Updates Cache

Advice 5. Search for malware and viruses

If the problem persists there is a possibility of the virus infection. Scan your computer using the best utilities and remove all found malware:

Advice 6 (workaround). Turn off updates for Windows 10

If nothing of the above helps to solve the problem and TiWorker.exe is still loading your CPU heavily here is a radical workaround to bring your PC back to working condition. Probably it will be ecpecially useful for old and weak laptops and desktops. All you need to do is stop and disable two services: Windows Modules Installer (TrustedInstaller) and Windows Update (wuauserv):

  • Press Win+R.
  • Type services.msc and hit Enter.
  • Find Windows Modules Installer (TrustedInstaller) and double click it.
  • Select Disabled in Startup type.
  • Click Stop.
  • Click OK.

trustedinstaller disable and stop

Do the same for Windows Update (wuauserv):



  1. The simple and fastest way
    1. open task manager
    2. clik performance tab and then go down left corner
    3. click “open resource Monitor”
    4. find the most paying hi-load application, right click and “SUSPEND”
    5. Only SUSPEND Okey …

    Hi windows …..
    this is one of your failures

    go to MACS, they may have one even better

    1. MacOS doesn’t have this blatant user-experience impacting lazy failure of design. You should try it. This high CPU consumption due to Windows updates has been plaguing Windows since version 7. (I’ve been using Windows since version 3.0)

  2. The real failure here is not tiworker.exe looking to do updates, because that’s a reasonable requirement, but inflexible OS development people who couldn’t build in some user friendly features like delaying the time when the process runs until X minutes after the PC has started (and presumably other startup related processes have finished) and/or lower the CPU priority so that it is not competing against interactive processes. While it is important to keep the OS up to date, it is generally not critical to do it immediately after reboot and even if that were the case, a little intelligence to the tool could flag it, and the user, to alert for a pending critical update.

    1. Exactly! It’s pure laziness and taking the easy way out at the customer’s expenses. That’s why I try to avoid Windows nowadays and that’s from someone who has been using Windows since the 3.0 days.

Leave a Reply

Your email address will not be published.