This is the strict step-by-step edition: seven ordered steps to fix Windows Modules Installer Worker (TiWorker.exe) high disk usage on any Windows laptop. No branching, no optional detours — just a sequence that runs from diagnosis through the most likely repairs to the final hardware check. Follow it top to bottom, verify after each step, and stop the moment disk usage normalizes.

The sequence respects one rule above all: diagnose before repairing. TiWorker at 100 percent disk is often legitimate update work, and “fixing” legitimate work just interrupts it. Step 1 tells you which situation you are in; the remaining steps apply only to the stuck case. Keep the laptop plugged into AC power throughout — servicing throttles on battery, which only prolongs the episode.

You need nothing you do not already have: Task Manager, Settings, an administrator Command Prompt, and Disk Cleanup. Let us begin.

Why this happens

  • Legitimate update installation: the most common cause — TiWorker doing its actual job, loudly.
  • A stuck package looping retries: a failed download the worker cannot finish.
  • Corrupted update cache: bad staged files forcing endless re-verification.
  • Component store damage: WinSxS staging failures retrying in a loop.
  • Post-update cleanup: compressing superseded components after a successful install.
  • Pending reboot: an install waiting on a restart while the worker holds the queue.
  • A failing drive: read errors retried indefinitely as supposed package corruption.

How to fix it

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

Fix 1: Diagnose — is TiWorker working or stuck?

Two minutes here determines whether steps 2 through 7 are even necessary.

  1. Open Task Manager (Ctrl+Shift+Esc), go to Processes, and confirm Windows Modules Installer Worker is the disk hog.
  2. Right-click it, choose Open file location, and verify it resolves under C:\Windows — anything else is malware, not servicing.
  3. Open Settings, then Windows Update: if packages show moving progress, the worker is working — skip to Step 2’s waiting guidance, not the repairs.
  4. Watch the Performance tab’s disk graph for 10 minutes: bursts with idle gaps are healthy; a flat 100 percent with no update progress is stuck.
  5. If a reboot is pending, reboot first — the worker often cannot finish until you do. For related pipeline symptoms, the Windows 11 TiWorker guide goes deeper.

Fix 2: Support a legitimate run — or confirm the stuck case

If Step 1 said “working,” help it finish. If it said “stuck,” confirm once more before repairing.

  1. Plug into AC power and close your applications to stop competing for disk I/O.
  2. Allow up to an hour on SSD (longer on HDD) for the current update cycle to complete.
  3. Install any pending reboot the moment it is offered.
  4. If disk usage settles and the update queue empties, you are done — no further steps needed.
  5. If the disk stays flatlined past these windows with no progress, proceed to Step 3 — the worker is confirmed stuck.

Fix 3: Restart the servicing stack

The gentlest true repair: break the retry loop with a clean service restart.

  1. Open Command Prompt as administrator.
  2. Type net stop wuauserv and press Enter, then net stop bits and press Enter.
  3. In Task Manager, end the TiWorker.exe process — it restarts cleanly with the services.
  4. Back in the prompt, type net start wuauserv and net start bits, pressing Enter after each.
  5. Watch Task Manager for 10 minutes: if disk usage ramps down, the loop is broken — stop here.

Fix 4: Reset the update cache

The highest-yield repair for a stuck worker: discard the corrupt staged files it keeps choking on.

  1. In an elevated Command Prompt, stop all four services: net stop wuauserv, net stop cryptSvc, net stop bits, net stop msiserver.
  2. Type ren C:\Windows\SoftwareDistribution SoftwareDistribution.old and press Enter.
  3. Type ren C:\Windows\System32\catroot2 catroot2.old and press Enter.
  4. Restart the four services with net start and reboot the laptop.
  5. Open Windows Update and let it rebuild the queue on a stable connection — Microsoft documents this reset on its update support pages . Verify the worker settles.

Fix 5: Repair the component store with DISM and SFC

When the store TiWorker stages into is damaged, every operation fails and retries.

  1. In an elevated Command Prompt, type DISM /Online /Cleanup-Image /RestoreHealth and press Enter.
  2. Wait for 100 percent completion — 10 to 30 minutes; do not close the window.
  3. Type sfc /scannow, press Enter, and wait for verification.
  4. Reboot and monitor the worker for 20 minutes.
  5. If the loop persists on a repaired store, the drive is the remaining suspect — continue.

Fix 6: Free space and manage the schedule

Reduce the conditions that make servicing heavy and badly timed.

  1. Run Disk Cleanup as administrator; select Windows Update Cleanup, Temporary files, and Delivery Optimization Files.
  2. Confirm 15 to 20 GB free on C:; enable Storage Sense under Settings, then System, then Storage.
  3. Set active hours in Windows Update so heavy install phases land overnight.
  4. Use Pause updates (up to a week or more) when you need guaranteed quiet — the worker idles safely.
  5. For one stubborn package, install it manually from the Microsoft Update Catalog while plugged in and idle, then verify the worker goes quiet.

Fix 7: Check drive health — the final verdict

A worker that survives every software repair is telling you about hardware.

  1. In an elevated Command Prompt, run wmic diskdrive get status — anything other than OK is a red flag.
  2. Run chkdsk C: /f, reboot, and let the scan complete.
  3. Check detailed SMART data with your drive manufacturer’s utility.
  4. Back up your files immediately if any warning appears — this outranks all further troubleshooting.
  5. Replace a failing drive; on the fresh system, updates — and TiWorker — behave normally. Our Windows 10 TiWorker guide covers the same verdict for older machines.

Closing

Seven steps, one principle: never repair what you have not diagnosed. Most TiWorker episodes end at Step 2 (it was working) or Step 4 (the cache was corrupt). The later steps exist for the stubborn remainder, and the final step reframes persistence itself as evidence — a worker that will not quiet down on a healthy queue is a drive asking for retirement. Work the sequence, trust the verifications, and the 100-percent-disk mystery stops being a mystery.

Frequently asked questions

How long does the full step-by-step TiWorker fix take?
Most cases resolve within the first three steps — about 30 minutes including observation time. The full sequence, including DISM/SFC and drive-health checks, takes roughly 90 minutes on an SSD and longer on a hard drive. Each step has a verification check so you stop as soon as disk usage normalizes; almost nobody needs the final hardware step.
Do I need to download anything for these steps?
No. Every step uses built-in Windows tools: Task Manager, Settings, Command Prompt, and Disk Cleanup. The only external resource mentioned is the Microsoft Update Catalog, and only as an optional manual-install route for a stubborn package. Avoid third-party ‘TiWorker fixer’ utilities — they cannot do anything the built-in steps do not, and some are outright harmful.
Is it ever correct to just disable Windows Update to stop TiWorker?
No. Disabling the update service stops the symptom by breaking security patching — the digital equivalent of removing a smoke detector’s battery. The supported way to buy quiet time is pausing updates in Settings, which is temporary and reversible. Fix the stuck queue with this sequence instead, and the worker goes quiet on its own while updates keep flowing.
What if TiWorker is still at 100% after all seven steps?
Then the evidence points to hardware: a drive whose errors the worker keeps retrying as corruption. Back up your files immediately, confirm with the manufacturer’s SMART diagnostic, and replace the drive. On a healthy drive with a healthy queue, TiWorker simply does not sustain 100 percent disk — the persistence itself is the diagnosis.