Windows Update on your Lenovo laptop has been ‘working on updates’ for three hours, the progress bar barely moves, and you are starting to wonder if it is stuck or just slow. There is an important difference: a slow update is making progress you can measure, while a stuck update is not. Most ’too long’ updates are genuinely slow — throttled by a mechanical hard drive, a weak connection, or a component that needs attention.

Before you force a shutdown in frustration (do not — interrupting an update mid-install is how machines get broken), work through this speed-up sequence. It is ordered by impact: the fixes that actually move the needle on update time come first, and the diagnostic steps tell you whether your update is slow-but-healthy or genuinely stuck.

An update has three phases — download, staging, and install — and each is slow for different reasons. Downloads are network-bound and easy to measure. Staging, where Windows unpacks and verifies thousands of files, is disk-bound and invisible in the progress bar. The install phase, with its reboots, is both. When owners say updates take too long, they usually mean the staging phase on a mechanical drive, which Task Manager reveals as 100 percent disk with an idle network. Knowing which phase drags tells you whether to fix the network, the disk, or your expectations.

Why this happens

  • A mechanical hard drive bottlenecking the install. Update staging is random-I/O heavy, and HDDs handle it an order of magnitude slower than SSDs.
  • A slow or congested network connection. Large feature updates are gigabytes; weak Wi-Fi stretches the download phase for hours.
  • A nearly full system drive. With little free space, staging and rollback copies fragment and crawl.
  • Antivirus scanning every staged file. Real-time scanning of thousands of update files adds massive overhead.
  • Lenovo utilities competing for disk. Vantage, System Update, or backup tools running concurrently steal I/O from the installer.
  • A partially stuck component slowing the pipeline. One struggling sub-download or verification step holds up everything behind it.
  • Outdated servicing stack. An old stack processes updates less efficiently than the current one.

How to fix it

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

Fix 1: Measure whether it is slow or stuck

Do not treat a healthy-but-slow update like a broken one.

  1. Open Settings > Windows Update and note the exact percentage and phase.
  2. Wait 30 minutes and check again — any movement means progress.
  3. Open Task Manager: sustained disk or network activity means work is happening.
  4. If the percentage has not moved in over an hour with idle disk and network, treat it as stuck: see update stuck downloading .

Fix 2: Switch to wired or faster network

Eliminates the network as the bottleneck in one move.

  1. Plug into Ethernet via USB-C or a dock if possible — it is dramatically faster than weak Wi-Fi.
  2. Move closer to the router if you must use Wi-Fi.
  3. Pause streaming, gaming, and cloud syncs during the update.
  4. In Settings > Windows Update > Advanced options > Delivery Optimization, allow downloads from other PCs on your local network.

Fix 3: Free disk space and quiet competing apps

Gives the installer the room and I/O it needs.

  1. Free at least 20 GB on C: with Disk Cleanup (as admin) and by removing unused apps.
  2. Close browsers, backup tools, and Lenovo Vantage during the install phase.
  3. Temporarily pause OneDrive or Dropbox syncing — they compete for the same disk.
  4. Restart right before starting the update so no stale processes linger.

Fix 4: Temporarily ease antivirus scanning

Real-time scanning is a hidden tax on every update file.

  1. In your antivirus, temporarily disable real-time protection during the install.
  2. Keep Windows Defender’s own scanning at default — the slowdown mostly comes from third-party suites.
  3. Re-enable protection immediately after the update completes.
  4. If updates are consistently faster with scanning eased, add a permanent exclusion for C:\Windows\SoftwareDistribution.

Fix 5: Update the servicing stack and clear the cache

A healthy pipeline processes updates faster than a damaged one.

  1. Install the latest servicing stack update from the Microsoft Update Catalog .
  2. Clear the SoftwareDistribution cache: stop wuauserv and bits, rename the folder, restart the services.
  3. Run the update troubleshooter from Settings > System > Troubleshoot.
  4. Retry the update on the clean, current pipeline and compare timing.

Fix 6: Schedule updates for idle hours

Stop fighting the update for resources — give it the night shift.

  1. Set Active hours to cover your workday so installs happen outside it.
  2. Use Pause updates when you need a guaranteed-fast machine for a deadline.
  3. Leave the laptop plugged in, lid open, overnight once a week for maintenance.
  4. A machine that updates while you sleep never feels slow.

Fix 7: Consider the SSD upgrade for HDD Lenovos

The permanent fix for the slowest update machines.

  1. Check whether your Lenovo has a spinning drive: Task Manager > Performance > Disk shows HDD or SSD.
  2. On HDD models, the same update that takes 3 hours takes 30 minutes on an SSD — no software tweak competes.
  3. Clone or clean-install onto an SSD; Lenovo’s support site lists compatible drives per model.
  4. After upgrading, one full update cycle confirms the new normal. For the 24H2-specific slow case, see update taking too long in 24H2 .

Fix 8: Optimize the drive before major updates

A fragmented or cluttered drive stages updates measurably slower.

  1. Run dfrgui and optimize C: — on HDDs this defragments; on SSDs it issues TRIM.
  2. Empty the Recycle Bin and clear temporary files before Patch Tuesday.
  3. Uninstall applications you have not opened in months; every installed app adds servicing load.
  4. Restart right before the update so the staging phase starts on a clean, quiet system.

Closing

Slow Windows Updates on Lenovo laptops are usually a hardware-speed problem (HDD, weak Wi-Fi) or a pipeline-health problem (cache, servicing stack), not a mystery. Measure first, remove the bottlenecks, keep the pipeline clean, and schedule the work for idle hours. And if your Lenovo still spins a hard drive, the SSD upgrade is the single highest-impact improvement you can make — for updates and everything else.

Frequently asked questions

How long should a Windows update normally take?
A monthly cumulative update typically takes 10 to 30 minutes on an SSD with a decent connection; a feature update takes 30 to 90 minutes. Times beyond that — especially hours with no progress — indicate a bottleneck worth fixing rather than normal behavior.
Why is Windows Update so slow on my Lenovo specifically?
Lenovo laptops with mechanical hard drives are the classic slow-update machines: the update’s disk-heavy staging saturates an HDD. Slow Wi-Fi, a nearly full drive, and Lenovo utilities competing for disk access compound it. Check Task Manager’s Performance tab — if the disk type reads HDD, you have found the primary bottleneck.
Will a faster internet connection fix slow updates?
Only if the internet is the bottleneck. Most slow updates are disk-bound, not network-bound — the download finishes quickly and the install crawls. Check Task Manager: if disk is at 100% while network is idle, bandwidth is not your problem.
Is it safe to use the laptop while it updates?
Light use is fine during the download phase, but heavy disk activity during the install phase slows everything and risks interrupting file operations. For the fastest update, leave the machine idle on AC power. Save your work frequently during updates regardless — a forced rollback from a power loss is the real risk.