sodcalculator

10 Tech How-To

How to Fix TiWorker.exe High Disk Usage on Windows 10

Guide 10-43663 · Updated · Step by step

If your Windows 10 PC is running slowly and the disk usage is stuck at 100%, TiWorker.exe (Windows Modules Installer Worker) is often the culprit. This guide walks you through proven fixes to reduce or eliminate the high disk usage caused by TiWorker.exe, from simple restarts to deeper system repairs.

What You’ll Need

  • Administrator access to your Windows 10 PC
  • A stable internet connection (for some fixes)
  • Patience – some steps may take a few minutes to complete

Step-by-Step

  1. Restart your computer. A simple reboot often clears temporary glitches that cause TiWorker.exe to run excessively. Save your work and restart, then check if disk usage drops.
  2. Run Windows Update manually. TiWorker.exe is part of the Windows Update process. Sometimes it gets stuck. Go to Settings > Update & Security > Windows Update and click “Check for updates.” Let it finish, then restart again.
  3. Run the Windows Update Troubleshooter. In the same Settings page, click “Troubleshoot” (or “Additional troubleshooters”), select “Windows Update,” and run it. This tool automatically finds and fixes common update problems.
  4. Clear the SoftwareDistribution folder. This folder stores temporary update files. Corrupted files here can cause TiWorker.exe to loop.
    1. Open Command Prompt as Administrator (right-click Start > Command Prompt (Admin)).
    2. Type net stop wuauserv and press Enter.
    3. Type net stop bits and press Enter.
    4. Open File Explorer and navigate to C:\Windows\SoftwareDistribution. Delete everything inside the folder (you may need to skip files in use).
    5. Go back to Command Prompt and type net start wuauserv then net start bits.
    6. Restart and check if disk usage improves.
  5. Run System File Checker (SFC). Corrupted system files can trigger TiWorker.exe. Open Command Prompt as Administrator and type sfc /scannow. Let it finish (may take 15-20 minutes). If it finds errors, restart and run it again.
  6. Run DISM (Deployment Imaging Service and Management Tool). If SFC doesn’t fix it, run DISM to repair the system image. In Command Prompt (Admin), type: DISM /Online /Cleanup-Image /RestoreHealth. This can take up to 30 minutes, so be patient.
  7. Disable Windows Update temporarily (last resort). If nothing else works, you can stop the Windows Update service to see if TiWorker.exe stops. Open Services (type services.msc in Run), find “Windows Update,” right-click and select “Stop.” Set its startup type to “Disabled.” Remember to re-enable it after a few days to get security updates. This is not recommended long-term.

Common Mistakes

  • Deleting TiWorker.exe itself. This is a core system file; deleting it can break Windows Update permanently. Never do this.
  • Skipping the restart. Many fixes require a reboot to take effect. Don’t skip it.
  • Running SFC and DISM at the same time. They can interfere with each other. Run SFC first, then DISM if needed.
  • Disabling Windows Update permanently. This leaves your PC vulnerable to security threats. Use it only as a temporary test.

Tips

  • Perform these fixes during a time when you don’t need your PC, as some steps (SFC, DISM) are resource-intensive.
  • Keep your Windows 10 up to date. Microsoft regularly patches TiWorker.exe issues in cumulative updates.
  • Check your disk health. A failing hard drive can cause TiWorker.exe to run slowly and appear stuck. Use tools like CrystalDiskInfo (free) to check SMART status.
  • If you have an SSD, ensure TRIM is enabled. Open Command Prompt (Admin) and type fsutil behavior query DisableDeleteNotify. If it returns 1, enable it with fsutil behavior set DisableDeleteNotify 0.

Troubleshooting

If the steps above don’t resolve the issue:

  • Check for pending updates. Sometimes TiWorker.exe is actually doing its job – installing updates. Wait a few hours and see if disk usage drops.
  • Boot into Safe Mode. If TiWorker.exe still runs at 100% in Safe Mode, the problem is likely a corrupted system component. Try a system restore to a point before the issue started.
  • Use Performance Monitor. Press Win + R, type perfmon, and go to “Performance Monitor.” Add a counter for “Process > % Disk Time” and select TiWorker.exe. This shows if it’s actually writing data or just stuck.
  • Check for malware. Malware can disguise itself as TiWorker.exe. Run a full Windows Defender scan or a third-party antivirus.
  • Reset Windows Update components manually. If the troubleshooter fails, download the “Windows Update Reset” script from Microsoft’s official site (search for “Windows Update Reset tool”). Run it as Administrator.

Frequently Asked Questions

What is TiWorker.exe?

TiWorker.exe (Windows Modules Installer Worker) is a legitimate Windows system process that installs, modifies, and removes Windows updates. It runs in the background and is essential for system maintenance.

Is TiWorker.exe a virus?

Not usually. It’s a genuine Microsoft file located in C:\Windows\WinSxS. However, malware can disguise itself with the same name. Check its location – if it’s not in the WinSxS folder, scan your system.

Why does TiWorker.exe use so much disk?

It usually happens during or after a Windows Update. The process is decompressing and installing update files, which is disk-intensive. If it gets stuck, it can loop and cause 100% disk usage.

Can I disable TiWorker.exe?

You can temporarily stop the Windows Update service, but you should not disable TiWorker.exe permanently. It’s needed for security updates and system stability.

How long does TiWorker.exe run?

Normally, it runs for a few minutes after an update. If it runs for hours or days, something is wrong. The fixes above should resolve it.

Will these fixes work on Windows 11?

Most steps are similar, but some menu names differ slightly. The core fixes (SFC, DISM, clearing SoftwareDistribution) work on Windows 11 as well.

Related

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.

More in this bed

The whole Tech How-To bed →