Did you notice High CPU usage or 100% Disk or memory usage by Windows Modules Installer Worker (TiWorker.exe)? Windows Became Unresponsive, file, folder or apps won’t open at startup, And on task manager, it’s showing almost 99% system resource usage by Windows Modules Installer Worker or TiWorker.exe? Here every possible solution to fix Windows Modules Installer Worker High CPU Usage in Windows 10. But let’s first Understand What is Windows Modules Installer Worker? Why it’s running on the windows computer.

What is Windows Modules Installer Worker?

The Windows Modules Installer Worker or WMIW or TiWorker.exe is a systems process that checks for new updates from the Windows server. And prepares your computer for the installation and checks frequently for new updates. In other words, when you’re checking for Windows update or install Windows update on your computer, this process will be running automatically. Also, TiWorker.exe completes the various tasks that are needed after an update to Windows.

Generally, this Tiworker.exe windows modules installer worker will terminate all the resource that is necessary for an update once the update is finished. But sometimes due to any technical reasons these resources will keep on running in the background, Which Cause high System Resource usage and your computer gets slow down. Also, Some Times Virus malware infection, Corrupted system files, corrupted windows update components etc cause windows modules installer worker 100% CPU usage or High Disk usage.

Fix TiWorker.exe High CPU Usage problem

Now After understand what is Windows Modules Installer Worker? How TiWorker.exe works on a windows computer and Why Tiworker.exe windows modules installer worker usage High System Resources on windows 10. Let’s apply bellow solutions to fix TiWorker.exe High CPU Usage problem.

Note: Bellow solutions are applicable to fix windows modules installer worker high CPU Usage, 100% Disk usage on Windows 10 / 8.1 and 7 computers.

Install Pending Updates

Mostly Windows Modules Installer Worker High System resource usage problem cause if there any Pending updates stuck / Or app installation stuck in the installation process. So make sure you have installed all apps and updates.

You can check and install updates from settings -> update & security -> windows update -> check for updates.

To check and install Store apps open windows store -> Click on user account picture -> then click on Downloads and updates and install the pending download and updates.

windows store downloads and updates
windows store downloads and updates

After completely Install / Update Restart windows and check there is no more High System Resource usage.

Run Windows Update Troubleshooter

If after check and install pending apps updates still, you notice High CPU usage by Windows Modules Installer Worker, then run the Windows Update troubleshooter which check and fix update related problems and help to fix high System resource usage problem.

Firs download the Windows Update TroubleshooterWindowsUpdateDiagnostric.diagcab and run it. The tool checks the registry keys to fix potentially corrupt files & programs. This will take some time to check and fix update related problems. After That Restart windows and check TiWorker.exe or Windows Modules Installer Worker no longer occupies much of your CPU & Disk usage.

Temporarily Disable Automatic updates

As discussed this Problem is related to windows modules installer worker (TrustedInstaller) and Windows Update (wuauserv) service. May these services not responding, crashes or not function properly, which cause High CPU or 100% Disk usage. Try to Temporarily Disable both Services windows modules installer worker (Trusted Installer) and Windows Update (wuauserv) and check TiWorker.exe High CPU Usage problem fixed.

To Disable These services First open Windows services by press Win + R, Type services.msc and hit the enter key. Here on Services window look for service named windows modules installer worker. Double click on it, Change the Startup Type Disable and click on stop next to service status. Repeat this step for the Windows Update service.

For Windows 7 and 8.1 users: Open the Control Panel and click on Windows Update. On the left side, you can see the option Change Settings. Switch it to “Check for updates but let me choose whether to download and install them”. Reboot your computer to take a fresh Start, This time windows modules installer and Windows update service no longer starts in the background. Check There is no more 100% CPU usage issue by windows modules installer.

Tweak SoftwareDistribution folder

The Windows Update Storage folder (commonly known as “SoftwareDistribution” folder), is the location where Windows stores the downloaded updates. If this folder is corrupted, then you will face problems during Windows Update And may Tiworker.exe windows modules installer worker High CPU usage is one of them. So, delete all downloaded updates and force Windows to re-create a new empty SoftwareDistribution folder. To do that: Navigate to “C:\Windows” folder. Here Delete (or rename e.g. to “SoftwareDistributionOLD”) the SoftwareDistribution folder.

Rename Software Distribution folder
Rename Software Distribution folder

Note: Upon restart, the next time the Windows Update checks for available updates. A new empty SoftwareDistribution folder will be created automatically by Windows to store updates.

Now Restart windows to take a fresh start, Then check and install latest available updates. As Before We Disabled the Windows update and windows modules installer service, First start them from windows services and check for latest updates.

Disable Automatic Maintenance

Open control panel -> system and security -> Security and Maintenance. On the next screen, you will notice few options on the left sidebar, click Change Security and Maintenance settings. Then Deselect Automatic Maintenance and lastly, click OK to disable the service.

Disable Automatic Maintenance
Disable Automatic Maintenance

Run DISM and System File Checker

Again If system files get corrupted, missing (especially after recent windows 10 upgrade ) Then this may cause different startup problems, Include High system resource usage. We recommend to Run the System file checker Utility which scans and restore missing System files from a compressed folder located on %WinDir%\System32\dllcache.

To run system file checker tool open command prompt as administrator and type SFC /scannow and hit the enter key. If sfc results found corrupted files but unable to repair them then run DISM command which repair system image and allow sfc to do its job.

Dism / online / Cleanup-image / restore health 

dism restorehealth with Source options
dism restore health with Source options

Perform a Clean Boot

Also Try to perform clean boot which allows you to start Windows without running non-Microsoft services. In clean boot state, Windows doesn’t load any third-party programs and services during startup. Which may help you troubleshoot and determine what application or program is causing the problem that you have.

To perform Clean boot press Win + R, type msconfig and hit the enter key to open system configuration. Here under ‘General’ tab, click to select the option Selective startup, and then uncheck the Load startup items check box. Also, Make Sure the Load system services and Use original boot configuration is checked.

Go to Services tab, From there, Mark Hide all Microsoft services. You will find it at the bottom of that window Now, click on Disable all. Click Apply then OK And Restart windows. Check There is no more High System resource usage, If yes then any third party application causing the

These are some most applicable solutions to fix tiworker.exe windows modules installer worker High Cpu usage. Windows modules installer worker high System resource usage, tiworker high CPU usage windows 10 problem. I hope Apply these steps resolve High System Resource usage, 100% CPU usage problem. Still have any query, suggestion or face any difficulty while applying above steps feel free to discuss on comments below Fix DNS_PROBE_FINISHED_NXDOMAIN Error on Google Chrome.