Disk at 100%, everything frozen, and Task Manager points at Windows Modules Installer Worker — the TiWorker.exe process doing Windows Update’s heavy file work. On laptops with mechanical hard drives this can make the machine nearly unusable: every click queues behind the worker’s relentless reading and writing. The good news is that this is one of the most fixable performance problems in Windows, because the causes are few and well understood.

The key question, as always, is whether the worker is doing legitimate work or stuck. Legitimate work — the hour after a cumulative update on an HDD — needs patience. A stuck worker — 100% disk for hours with no update activity, or the same pattern every single day — needs the intervention sequence below. This guide is the fix path: confirm, unstick, repair, verify.

Before diving in, open Settings > Windows Update > Update history and check for recent activity — that single glance tells you which branch you are on. If CPU rather than disk is the saturated resource, our TiWorker high-CPU guide for Windows 11 is the matching resource.

Why this happens

  • Post-update component work on an HDD — Mechanical drives saturate at 100% under the worker’s file operations; the same workload barely registers on an SSD.

  • Corrupted update cache — Damaged files force endless retry loops, each retry re-reading and re-writing at full disk speed.

  • Stuck update services — Wedged wuauserv/BITS states leave the worker grinding on operations that cannot complete.

  • Component store corruption — CBS damage triggers repeated failed staging attempts, all disk-intensive.

  • Huge update backlog — Months of deferred updates compress into one giant disk-thrashing session.

  • Antivirus scanning the worker’s files — Real-time scanning of every file the worker touches doubles the disk I/O.

  • Failing drive amplifying everything — A struggling disk turns normal file operations into retry storms at 100% utilization.

How to fix it

Work through these in order — diagnose first, then act.

Fix 1: Confirm the pattern: legitimate work vs. stuck worker

Two minutes of diagnosis prevents hours of wrong fixes. Check the update context first. Resource Monitor’s Disk tab (via Task Manager’s Performance tab) shows exactly which files the worker is reading and writing — if it hammers the same SoftwareDistribution paths repeatedly, that is a retry loop, not legitimate work.

  1. Open Task Manager (Ctrl + Shift + Esc), sort by Disk, and confirm Windows Modules Installer Worker tops the list.
  2. Open Settings > Windows Update > Update history — recent updates mean legitimate work: wait up to 2 hours on HDD.
  3. If no recent updates and high disk persists for hours or daily, it is stuck — continue below.
  4. Note whether the disk is HDD or SSD (Task Manager > Performance) — it changes expectations dramatically.

Fix 2: Pause updates for immediate relief

If the machine is unusable right now, buy yourself breathing room the safe way — a temporary pause, not a disabled service. Pausing is fully reversible and disables no protection; it simply tells Windows Update to stop scheduling work while you repair.

  1. Open Settings > Windows Update.
  2. Click Pause updates and choose 1 week.
  3. Restart the laptop — the worker should go quiet.
  4. Use the relief window to work through the repairs below, then unpause.

Fix 3: Restart the Windows Update services

Clear the wedged service state that keeps the worker grinding.

  1. Open an elevated Command Prompt.
  2. Run net stop wuauserv, net stop bits, net stop cryptsvc.
  3. Wait 30 seconds, then restart each with net start.
  4. Unpause updates and monitor disk for 15 minutes.

Fix 4: Clear the corrupted update cache

Remove the damaged files driving the retry loop.

  1. Open an elevated Command Prompt.
  2. Run net stop wuauserv and net stop bits.
  3. Delete the contents of C:\Windows\SoftwareDistribution\Download and DataStore.
  4. Run net start wuauserv and net start bits. For machines where downloads also stall, our stuck-downloading guide pairs well with this step.

Fix 5: Run the Windows Update troubleshooter

Let the built-in tool detect the stuck states you might have missed.

  1. Go to Settings > System > Troubleshoot > Other troubleshooters.
  2. Run the Windows Update troubleshooter and apply its fixes.
  3. Restart the laptop.
  4. If the troubleshooter reports fixing ‘service registration’ or database corruption, restart before judging the result — those fixes only take effect on reboot.
  5. Check Task Manager disk usage after 15 minutes of idle time.

Fix 6: Repair the component store

For worker loops rooted in servicing corruption, fix the store. If DISM reports it cannot find source files, mount a Windows ISO and rerun it with the /Source flag pointing at the mounted install.wim.

  1. Open an elevated Command Prompt.
  2. Run DISM /Online /Cleanup-Image /RestoreHealth.
  3. Follow with sfc /scannow, then restart.
  4. Details on both utilities are in the Windows support hub .

Fix 7: Verify drive health — and consider an SSD

On HDDs, chronic 100% disk from the worker is often the drive telling you it is done. Check, then upgrade.

  1. Run chkdsk C: /f from an elevated prompt and reboot to scan.
  2. Check drive health in Settings > System > Storage > Disks & volumes > Properties.
  3. If the HDD is healthy but slow, an SSD upgrade eliminates this entire problem class — the worker’s heaviest sessions become background noise.
  4. If failing, back up immediately and replace.

Fix 8: Rule out third-party interference with a clean boot

Antivirus suites and system utilities can fight the worker over the same files, doubling disk I/O and causing the retry storms that look like a stuck worker. A clean boot isolates this variable definitively: if the worker behaves with third-party software disabled, you have found your amplifier.

  1. Press Win + R, type msconfig, and on the Services tab check Hide all Microsoft services, then Disable all.
  2. Open Task Manager’s Startup tab and disable every startup item.
  3. Restart, unpause updates, and watch the worker’s disk usage for 20 minutes.
  4. If it is calm now, re-enable services in halves to identify the culprit — then update, reconfigure, or remove that program.

Closing

Windows Modules Installer Worker at 100% disk is either legitimate post-update work — wait it out — or a stuck loop you can break: pause for relief, restart the services, clear the cache, repair the store. And on a mechanical drive, an SSD is the permanent cure.

Frequently asked questions

What is Windows Modules Installer Worker?
Windows Modules Installer Worker (TiWorker.exe) is the system process that installs, modifies, and removes Windows updates and optional Windows components. It is a core part of Windows servicing, digitally signed by Microsoft and located in C:\Windows\WinSxS. When it uses high disk, it is reading and writing large numbers of system files as part of update work — legitimate activity that becomes a problem only when it never finishes.
Is 100% disk usage from Windows Modules Installer Worker normal?
Temporarily, yes — during and shortly after updates, sustained high disk from this process is expected, especially on mechanical hard drives. It becomes abnormal when it persists for hours, happens daily with no updates occurring, or makes the system unusable for extended periods. The fixes below target the stuck cases, not the normal post-update activity that resolves on its own.
How is this different from TiWorker.exe high CPU?
It is the same process viewed through a different bottleneck. On systems with fast CPUs but slow disks (especially HDDs), the worker’s file operations saturate the disk before the CPU; on fast SSDs with slower CPUs, the same work shows as CPU usage. The underlying causes — stuck updates, corrupted cache, damaged store — are identical, which is why the fix sequences overlap heavily.
Will disabling Windows Update stop the high disk usage?
It would stop the worker, but at the cost of leaving your system unpatched and vulnerable — a terrible trade. The correct fix is to let the worker finish legitimate work or repair whatever has it stuck, as this guide covers. If you need temporary relief, pausing updates for a week (Settings > Windows Update > Pause updates) is the safe, reversible alternative to disabling anything.