Dear ilozen2,
Thank you for reaching out to the Microsoft Community!
I understand how frustrating it can be when Windows Modules Installer Worker (TiWorker.exe) consumes excessive CPU resources, especially when it occurs during working hours, and when no updates are expected. I’d be happy to guide you through several troubleshooting steps that can help resolve this issue.
Please follow the steps below to diagnose and potentially fix the issue:
- Perform a Clean Boot
A clean boot can help you determine whether background services or startup programs are causing the problem. By disabling unnecessary startup items, you can isolate the issue and ensure no conflicting programs are interfering with Windows Update.
Press Windows + R, type msconfig, and press Enter.
Under the General tab, select Selective startup.
Uncheck Load startup items and check Load system services.
Now, go to the Services tab, check the box labeled Hide all Microsoft services, and then click Disable all.
Click OK and restart your computer.
After performing a clean boot, check if Windows Modules Installer Worker still uses excessive CPU. If the issue is resolved, you can re-enable services one at a time to identify which one is causing the problem.
Disclaimer: These steps of "clean boot" might look complicated at first glance. However, to avoid any trouble for you, please follow them in order and step-by step so that it will help you get back on track.
- Run Memory Diagnostics
Issues with system memory can lead to high CPU usage. Running the built-in Memory Diagnostics tool can help identify if there’s an underlying memory problem.
Press Windows + R, type mdsched.exe, and press Enter.
You’ll be asked whether you want to restart your computer now or check for problems the next time you start it. Choose Restart now and check for problems.
Your system will restart, and Windows will run a memory test. If any issues are found, they’ll be displayed upon the next login.
- Set Windows Modules Installer Worker to Manual
Windows Modules Installer Worker is part of the Windows Update process, but you can change its startup type to manual so that it only runs when needed, potentially reducing CPU usage.
Press Windows + R, type services.msc, and press Enter.
Scroll down to find Windows Modules Installer.
Right-click on it and select Properties.
In the Startup type dropdown, change it to Manual.
Click OK and restart your system.
By setting it to manual, Windows Modules Installer Worker will only run when necessary and should prevent it from using CPU during off-hours.
- Reset Windows Update Components
Corrupt or stalled Windows Update components can lead to high CPU usage by Windows Modules Installer Worker. Resetting the Windows Update components may resolve this issue.
Open Command Prompt as an administrator (right-click the Start button and select Command Prompt (Admin)).
Run the following commands one by one:
net stop wuauserv
net stop cryptSvc
net stop bits
net stop msiserver
ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
ren C:\Windows\System32\catroot2 Catroot2.old
net start wuauserv
net start cryptSvc
net start bits
net start msiserver
Once the commands are executed, restart your computer and check if the issue persists.
- Perform an In-Place Upgrade
An in-place upgrade allows you to reinstall Windows without losing your personal files. This process can help fix corrupted system files that may be causing the issue.
Disclaimer: I always recommend that if you have important data, you should back it up before making large system changes.
- Visit the Windows 10 Download page.
- Under Create Windows 10 installation media, select Download the tool now.
- Launch the Media Creation Tool and choose Create installation media for another PC.
- Select the ISO file and save it locally.
- Once downloaded, right-click on the ISO file and select Mount.
- Run the setup.exe on the mounted drive.
- During setup, choose the option to Keep personal files and apps.
- Follow the on-screen prompts to complete the recovery installation.
If the problem persists after completing these steps, please feel free to reach out again, and I’d be happy to assist further!
Best Regards,
Martin | Microsoft Community Support Specialist
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
