Fix Windows Modules Installer Worker High CPU Usage Issue

Windows Modules Installer Worker is a background process that runs in the background of your Windows 7, Windows 8, Windows 8.1, Windows 10 or any other Windows machine. It has several functionalities which make it consume a high amount of resources at times. The problem arises when this process runs even when it is not in a running state.

What is Windows Modules Installer Worker?

It is a powerful tool of the Windows operating system. It uses TiWorker.exe executable file for running. The only problem with it is that it consumes a high amount of CPU. Be it Windows 7, Windows 8, Windows 10, or any other Windows platform, you will find this tool in your system. You must not disable this tool as it has great features that help your Windows run without any bugs and errors.

You might have wondered that what is this “Windows Modules Installer Worker” running in your PC when you open the task manager. If not then check right now by pressing Ctrl + Shift + Esc on your windows machine. You will find that this consumes a high amount of CPU at some time and slows down all your running processes. If you are not finding Windows Modules Installer Worker then it goes by the other name of “TiWorker.exe”, so try looking for that. In Windows 10 you will find it by TiWorker.exe.


Why Windows Modules Installer Worker process is running in the background?

Since Windows is a user-friendly operating system. That is why it provides you with facilities such as automatic updates and bug fixing. Now, the process responsible for this is Windows Modules Installer Worker. So whenever you are using Windows and it is running smoothly, then say thanks to Windows Modules Installer Worker that has made your PC bug free without any help from the user end.

If you feel your PC fan running up or are facing any overheating issues, then go to the task manager, you might find it consuming a lot of CPU and other resources. A lot of updates we download manually by going in Settings and under “Update and Recovery”, going for “Check for Updates”. But Windows comes with a lot of updates and most of these updates run in the background, and Windows Modules Installer Worker is responsible for it.

Why does it consume so much of CPU resources?

This takes up a lot of CPU at certain times but once it has finished installing updates then it will leave its CPU control as well. But till the time it has control over CPU, it will slow down your computer. It may be frustrating at times but there is nothing we can do about it, we can just wait for it to finish installing updates.

Why is it always running?

The problem arises when the system is messed up and Windows Modules Installer Worker is running most of the time and causing the PC to slow down. Actually, Windows Modules Installer Worker takes up few resources while it is doing the updating or recovery task, and as soon as the updates finish installing it frees up space. But sometimes due to some uncleared reasons these resources are not released by Windows Modules Installer Worker and hence these resources keep on using a high amount of CPU even after the updates are finished installing. Now, if you are trying to disable Windows Modules Installer Worker then you must not. If you disable it, then your Windows will stop updating and as a result, you will end up working on old and buggy tools which will also slow down your PC.

How to Fix High CPU Usage Issue

If you are finding that Windows Modules Installer Worker is running unnecessarily on your computer, then you must first let Windows find the possible problem with Windows Update Troubleshooter. For Windows Update Troubleshooter. Search for “Troubleshooting” in the start menu.

Click on “Troubleshooting” and a list of Troubleshooting options will appear. Under “System & Security”, click on “Fix problems with Windows Update”.

Press “Next” and let the Windows find the possible problems.

If you are using Windows 10, then you can go to Start, and then find Settings, in Settings find Update & Security on the left side. After clicking on Update & Security, click on Troubleshoot and then click on “Windows Update” troubleshooter.

Sometimes the disk drive errors can cause a high amount of CPU usage. Press Windows + R and then type in “cmd” or “command” and press “OK”. In command prompt window type CHKDSK and press Enter. It will do the disk checking and find if there are any disk errors.

If it still does not find any problems for you then don’t worry we still have other solutions for you to try.

Another possible solution is that you can disable Automatic Windows Update on your system. To do that press Windows + R to open Run Command, and then type “services.msc” and click on the OK button.

You will get a list of services, scroll down and find “Windows Modules Installer” and under its startup type make the selection as “manual”, if it is set to automatic.

Also, find the “Windows Update” on the same list and set that to manual as well. Click on OK to apply the changes and then Restart the PC.

If you have done this and still the problem persists, then we can set the internet connection as a metered connection as it will stop Windows Modules Installer Worker for unnecessarily using internet resources to download and install non-mandatory updates. To do it go to Settings, under Settings go to “Network”. Now select the Network on which you are working.

Now, turn the “Set as metered connection” On to set the current network as the metered connection.

Final Take

This will most probably cease your problems. No matter how many pages suggest that you disable Windows Modules Installer Worker don’t do it. It will worsen the situation. If you are facing any issues that can’t be solved using the tips above then it may be possible that the issues you are facing are not because of Windows Modules Installer Worker. The real problem might be something else. Firstly, diagnose the actual issue you are facing and then try to work your PC out of that problem. I hope you have found this article helpful for any problems you faced regarding this problem.

Leave a Reply