Windows is an operating system used by people all over the world for different purposes. In fact, it is the most popular operating system in the world. But it is not the most stable operating system ever. It still faces problems like the blue screen of death error or wifi connected but no internet access. And It can’t still beat the Mac OS in terms of stability and performance. Windows OS has many times many software running in the background utilizing resources of CPU which slows down the performance of the entire computer.
One such problem occurring is Windows Modules Installer Worker or Tiworker.exe (name depending on your windows version) 8utilizing a high amount of CPU and RAM in a Windows PC or Laptop. Some users also heard the loud noise of fans in their CPU. Today, on our blog, we have come up with the solution to this problem and eliminating high amount of CPU usage by Windows Modules Installer worker. You will also get all the information about this problem and its causes.
What is Windows Modules Installer Worker or Tiworker.exe?
Windows Modules installer worker is a tool that checks windows updates automatically for the system. This tool is actually essential if you want the Windows to check for the updates automatically on your PC or laptop as this tool will be automatically running while checking for or installing any updates on windows. But due to some issues with the tool, it can sometimes mess up things and show high CPU usage percentage in the task manager taken by a program called windows module installer worker or Tiworker.exe and you might be facing a slowdown in overall system performance in your computer because of this.
Is Tiworker.exe a virus or malware?
As we explained earlier, it is a part of windows itself and used for updates. So, you don’t need to worry about it being a virus or malware. Still, if you’re worried, you can run a virus scan through windows defender or your preferred antivirus and malware scan through Malwarebytes.
How to Fix Windows Modules Installer Worker using a high amount of CPU resources?
There are some solutions and workarounds to this problem and these are given below.
Solution 1: Disable Automatic Windows updates on your PC
As we explained earlier, this tool is running whenever windows is checking for any updates on your computer. So disabling windows updates automatically can solve this problem. To disable automatic Windows updates, follow the steps below :
- Go to “Run” by pressing windows key + R on your machine.
- Type services.msc in it and click OK.
- Search “Windows module installer“.
- Double click on the “Windows module installer”, and make it manual. It is usually set to Automatic.
- Now find and double-click on Windows update.
- Now a dialogue box will appear, select startup type to disabled or manual whatever option you have.
- Select OK.
- Reboot your PC and everything should be fine.
his method usually works for this problem. If this method does not work, try other solutions below.
Solution 2: Run Windows Update troubleshooter
Running the windows update troubleshooter can solve the problem if tiworker.exe has some issues. To do this :
- Go to Settings > Update & security > Troubleshoot > Windows Update on your PC.
- Click on Run the troubleshooter.
- Fix any problem suggested by windows troubleshooter.
Solution 3: Set your internet as metered connection
Some people would recommend this as this won’t let the machine take much use of the internet by windows module installer worker and hence it might stop using high CPU resources.
- You can do this by going to Start > Settings > Network & Internet > Wi-FI.
- Click Advanced Options.
- Then you can select set metered connection “On”.
If you’re using an ethernet connection, it is better to set updates manually.
We hope you got the solution to the problem of high resource usage by windows module installer worker and your PC or laptop is working fine. If you have any doubts or any other better approach to the problem, please type in the comments below. Share this article on social media and let windows geeks know how to solve this error.