“Taking too long” is the vaguest Windows Update complaint and the most common — the update is not erroring, not crashing, just consuming hours while you wait to use your laptop. The frustration is compounded by uncertainty: is it stuck? Should you intervene? Will restarting break everything? This guide removes the guesswork with a step-by-step method: first determine which phase is slow (download, install, or restart), then whether it is slow or stuck, then apply the targeted fixes for that phase. Different slowness has different causes, and the step-by-step approach finds yours.

The underlying truth is that update speed is a resource equation — disk throughput, CPU availability, free space, network speed, and system health all contribute. Most “too long” cases trace to one dominant bottleneck, and the steps below identify it before you waste effort on the wrong fix. Work them in order; each step builds on the last.

Why this happens

  • Mechanical hard drive. Spinning disks are dramatically slower at the random I/O updates require.
  • Corrupted cache causing retry loops. Damaged downloads retrying endlessly instead of progressing.
  • Low disk space. Staging operations crawling on a nearly full drive.
  • Background contention. Antivirus scans, cloud sync, and apps competing for disk and CPU.
  • Slow or metered network. The download phase stretching over hours.
  • Update backlog. Months of skipped updates compounding into one marathon session.
  • Battery throttling. Power-saving limits slowing update operations on battery.

How to fix it

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

Fix 1: Identify which phase is slow

Download slowness, install slowness, and restart slowness have different fixes. Pin down the phase.

  1. Download phase (percentage in Settings > Windows Update, “Downloading”): network or Delivery Optimization issue.
  2. Install phase (“Installing” or “Pending install”): disk, CPU, or system-health issue.
  3. Restart phase (“Working on updates” during reboot): disk speed or component-store issue.
  4. Note your phase and the elapsed time. A download stuck at a percentage for hours differs completely from an install crawling at 30% — the steps below target each.

Fix 2: Rule out “stuck” before optimizing “slow”

Do not optimize a stuck update — fix the stall first.

  1. Record the percentage and wait 30 minutes without touching the machine.
  2. Check for life: drive light, fan changes, percentage movement, Task Manager showing installer activity.
  3. If there is any activity, it is slow, not stuck — continue with the speed-ups below.
  4. If zero activity for 2+ hours, treat it as stuck: see our stuck downloading guide for the stall repairs, then return here for speed.

Fix 3: Free resources for the download phase

If downloads crawl, clear the path.

  1. Pause OneDrive/cloud sync and close bandwidth-heavy apps during the download.
  2. Prefer wired Ethernet over Wi-Fi for multi-gigabyte feature updates.
  3. In Settings > Windows Update > Advanced options > Delivery Optimization, check the settings — try toggling local-network sharing based on whether it helps or hurts your setup.
  4. If a specific update’s download loops, reset the cache: stop wuauserv/bits/cryptsvc, rename SoftwareDistribution and catroot2, restart services, and retry — a clean download beats a corrupted resume.

Fix 4: Free disk space and reduce contention for the install phase

Install-phase slowness is almost always disk-bound. Give the installer room and uncontested access.

  1. Free at least 20 GB on C: via Storage Sense and Disk Cleanup (system files).
  2. Close all applications; pause antivirus real-time scanning temporarily during the install window.
  3. Plug in the AC adapter — battery power throttles the CPU and disk operations updates need.
  4. Disable unnecessary startup apps in Task Manager so the post-restart finalization is not fighting your autostart load.

Fix 5: Reset the cache to kill retry loops

Corruption does not always fail loudly — sometimes it just makes everything retry slowly.

  1. Open Command Prompt as administrator.
  2. Stop the services: net stop wuauserv, net stop bits, net stop cryptsvc.
  3. Rename: ren C:\Windows\SoftwareDistribution SoftwareDistribution.old and ren C:\Windows\System32\catroot2 catroot2.old.
  4. Restart the services and check for updates. This converts many “3-hour updates” into 30-minute ones by replacing grind-through-retries with a clean single pass.

Fix 6: Repair system health for chronic slowness

If every update is slow, the system itself needs maintenance.

  1. Run DISM /Online /Cleanup-Image /RestoreHealth in an elevated prompt (15–30 minutes).
  2. Follow with sfc /scannow to full completion.
  3. Update storage/chipset drivers from your laptop manufacturer’s support site — old drivers throttle the disk throughput updates depend on.
  4. Establish the monthly habit: install cumulative updates each Patch Tuesday instead of letting them backlog. For the full maintenance picture, Microsoft’s Windows support hub documents healthy update behavior.

Fix 7: Address the hardware bottleneck

When software fixes plateau, the bottleneck is physical — and fixable.

  1. Check your drive type: Task Manager > Performance > Disk — HDD vs SSD.
  2. If HDD, plan an SSD upgrade: it is the single biggest update-speed improvement available, typically halving install times while transforming general responsiveness.
  3. Check RAM pressure during updates in Task Manager — if memory is maxed, close apps or consider a RAM upgrade where the laptop allows it.
  4. After any hardware change, run one full update cycle to confirm the improvement, then enjoy updates as the background event they were meant to be. For HP-specific slowness factors, our HP slow update guide covers vendor bloatware contention.

Closing

Slow updates are a bottleneck problem, and the step-by-step method finds your bottleneck: identify the phase, rule out stuck, clear the download path, free disk resources, reset the cache, repair system health, and address hardware last. Most cases resolve at the cache reset or resource-freeing steps — the update was never truly slow, it was fighting corruption or contention. Remove the fight and the speed follows.

Frequently asked questions

How do I know if my update is stuck or just slow?
Watch for signs of life over 30 to 60 minutes: drive activity light flickering, fan speed changes, or the percentage creeping upward. A responsive Ctrl + Alt + Delete screen means Windows is working underneath. Only zero progress plus zero drive activity for over two hours indicates a genuinely stuck update — everything else is slowness with a fixable cause.
Why do updates take longer on older laptops?
Three compounding factors: mechanical hard drives handle update file operations far slower than SSDs, older CPUs take longer on the cryptographic verification and compression steps, and years of accumulated system cruft slow every operation. The fixes in this guide address the software side; an SSD upgrade addresses the hardware side permanently.
Does internet speed affect the install phase or just downloads?
Only the download phase. Once the packages are downloaded, install speed depends on disk speed, CPU, available RAM, and system health — not bandwidth. If your update downloads quickly but installs slowly, the bottleneck is local hardware or system corruption, and the fixes target those instead.
Can I speed up updates by installing them more often?
Yes, counterintuitively. Monthly cumulative updates are incremental — installing each month means each session is small. Skipping months lets the backlog compound into a giant session that takes far longer than the sum of the monthly ones would have. Regular small updates are faster than rare big ones.