Why Are Windows Updates So Slow? (And How to Speed Them Up)

AvatarByEric Dawson Computers & Software

Windows updates feel slow because most of the real work happens after the download finishes. Downloading is usually the quick part. The slow stretch belongs to the Windows Module Installer, TiWorker.exe, which unpacks components, swaps system files, and then spends hours cleaning up the versions it just replaced. Microsoft’s own guidance says a machine needs at least two continuous connected hours, and up to six total connected hours, to reliably finish quality and feature updates, although most finish in under an hour. Older drives, 8GB of memory, and a crowded startup list push that further out.

What Actually Happens During a Windows Update

Every update runs as three separate jobs stacked together, and only the first shows a progress number that moves at a sensible pace. Working out which stage has stalled tells you whether to blame the connection, the hardware, or a damaged component store. Task Manager, opened with Ctrl+Shift+Esc, is the fastest way to see which process is actually busy.

The Download Phase

Packages run from roughly 500MB for a routine rollup to 3GB for a full feature update, according to Ask Leo’s breakdown of update sizes. Most broadband connections chew through that in minutes. Trouble starts when the route to Microsoft’s delivery servers is congested, and a responder on Microsoft’s support answers forum, working through a slow-update case, put the worst outcome plainly: a poor connection to the update server can drag the process past 10 hours. Their wider point was that this stage tracks your network and Microsoft’s servers far more closely than it tracks your PC.

The Installation Phase

Once the files are on disk, Windows unpacks them and moves components into place. Resource use during this stage looks odd if you watch it. That same support forum case showed the processor sitting near 17 percent and memory under 60 percent while the installer inched forward, which rules out a plain shortage of horsepower. The explanation offered there was that the installer grinds through thousands of small files, and Windows caps how hard it pushes so the machine stays usable while it works.

The Cleanup Phase After the Restart

TiWorker.exe, the Windows Module Installer worker, takes over once you are back at the desktop. Its job list covers deleting superseded update files, reorganizing system components, refreshing internal databases, and optimizing the files that just changed. XDA Developers and Ask Leo both describe this stage running for several hours on slower machines, which is why a PC can feel sluggish long after the update reports success.

Windows Search piles on more load. After an update it rebuilds its database of file locations, and that rebuild is most obvious on mechanical hard drives, low-power processors, and machines with 8GB of memory or less. Feature updates add another layer by resetting configuration: background processes, visual effects, and preinstalled apps you had switched off can come back on, each one taking a slice of the same processor the installer wants. XDA Developers lists that reset as one of the main reasons a freshly updated PC feels worse than it did the day before.

How Long a Windows Update Should Take

Monthly quality updates are the common case, and after the restart they usually need only a few minutes to apply. Feature updates are the ones that eat an evening. Microsoft’s guidance, reported by Computerworld and Tom’s Guide and checked again in September 2026, sets a floor rather than an average: a device needs a minimum of two continuous connected hours and six total connected hours online to reliably install quality and feature updates. David Guyer, the Microsoft program manager behind that research, has said the majority of updates finish start to finish in less than an hour.

Update Type Hardware Typical Time Reported By
Monthly cumulative update, apply phase after restart Any A few minutes DTPTips
Feature update such as 24H2 or 25H2 Modern system An hour or more Windows OS Hub
Download plus install, whole process Solid state drive About 15 minutes Ask Leo readers
Download plus install, whole process Older PC with a hard disk drive 45 minutes or more Ask Leo readers
Quality and feature updates, full completion Mixed fleet Up to six hours, most under one hour Tom’s Guide, Computerworld
Reliability minimum for one device Any Two continuous connected hours, six total Microsoft

Figures like these describe different things, which is why the advice online seems to contradict itself. Ask Leo argues there is really no way to know how long a given update will take, because the variables stack: connection quality, package size, disk speed, and whatever else is running. Microsoft’s numbers do not disprove that. They are a planning minimum aimed at IT departments, describing how much connected time a fleet of machines needs, not how long your particular restart will sit at 34 percent.

My rule would be to judge the update by its type before judging the PC. A monthly update that is still applying after a restart for several hours deserves more suspicion than a feature update that takes the same time. For a feature update, I would leave the machine connected and give it the full six-hour window, because the work includes installation, cleanup, and later optimization rather than one simple download. I would only start treating the delay as a problem after that window has passed without clear progress.

What Makes One PC Update Slower

Two machines on the same network, given the same update, can differ by a factor of three. Storage is usually the largest single reason, with memory, background load, and the state of the system files filling in the rest.

Storage: SSD vs HDD

Update installation is a write-heavy, small-file workload, close to the worst case for a mechanical drive. Readers reporting their own timings to Ask Leo describe roughly 15 minutes on a solid state drive against 45 minutes or more on older hardware with a spinning disk. Fragmentation and a nearly full drive make it worse, because Windows needs room to download, unpack, stage the new files, and keep enough of the old ones to roll back if the install fails.

Memory, Processor and Background Load

Machines with 8GB of memory or less, or a low-power mobile processor, spend real time on the decompression and optimization steps a faster system absorbs quietly. Background software competes for exactly those resources. One specific culprit is the Settings app: leaving the Windows Update page open keeps the MoUSO Core Worker Process busy reporting status, so closing Settings once the download has started removes a small but genuine drag, as XDA Developers points out.

Malware, Full Drives and Damaged System Files

An infected system slows updates the same way it slows everything else, by stealing processor cycles and disk throughput. Corrupted system files are the subtler problem. When a component the installer needs is damaged, the update either grinds for hours or fails and rolls back, and waiting longer will not fix it. Running the System File Checker before you retry is the standard first move, and Ask Leo lists malware and a near-full disk alongside it as routine causes of an update that never seems to end.

The Network and Microsoft’s Servers

Patch Tuesday concentrates millions of downloads into a few hours, and Ask Leo points to those peaks as a real source of server-side slowdown. Households create the same squeeze locally, since a video call and two streaming sessions leave little bandwidth for a 3GB package. Neither factor touches the installation phase, though. A fast download followed by a very long restart points at hardware and the component store, not at your internet service.

Why Windows 10 Updates Take Longer

Windows 10 machines receive substantially larger update packages than Windows 11 machines do, and the gap is by design. Compression work built into Windows 11 cut update size by around 40 percent, which trims both the download and the amount of data the installer has to unpack and write. Computerworld cited that reduction as one of the practical arguments for moving off Windows 10. For anyone still running it and wondering why a newer laptop in the same house finishes first, package size is a large part of the answer.

How to Make Windows Updates Install Faster

Nothing below makes Microsoft’s servers quicker or changes how TiWorker.exe behaves. These steps remove competition for disk and processor time, and clear the conditions that turn a slow update into a failed one. DTPTips, which walks through much the same checklist, is honest about the payoff: results depend on what is running, how powerful the hardware is, and how old the Windows installation is, so some machines improve noticeably and others barely move.

Before You Start the Update

  1. Free up disk space. Aim for 10GB to 20GB free on the system drive. Windows needs working room to unpack and stage files, and a nearly full drive is one of the most common causes of a stalled install.
  2. Trim what starts with Windows. Open Task Manager with Ctrl+Shift+Esc, switch to the Startup apps tab, and disable anything you do not need at boot. System Configuration, which you reach by typing msconfig into the Start menu and pressing Enter, covers background services the same way.
  3. Repair the system files first. Right-click the Start button, choose Terminal (Admin) or Command Prompt (Admin), and run sfc /scannow. If it reports files it could not repair, follow with DISM /Online /Cleanup-Image /RestoreHealth and then run the checker again.
  4. Clear the network. Updating while three other people in the house are streaming turns a 10 minute download into an hour. Wired Ethernet beats Wi-Fi for a large feature update where the connection has to stay stable.
  5. Pick the window deliberately. Microsoft’s two continuous connected hours is the figure to plan around, so start a feature update when the machine can stay on, awake, and online rather than at the end of the working day.

While the Update Is Running

  • Close the Settings app. Watching the percentage costs you processor time through the MoUSO Core Worker Process, and the update continues perfectly well with the window shut.
  • Leave heavy software alone. Games, video exports, and full antivirus scans fight the installer for the same disk.
  • Keep it plugged in and awake. A laptop that sleeps partway through loses the continuous connected time Microsoft says the process needs.

Expect modest gains from all of this on a modern machine, because it was never the bottleneck. On an older laptop with a mechanical drive and 8GB of memory, clearing disk space and killing startup clutter can be the difference between an update that finishes over lunch and one that is still going at bedtime.

How to Cancel a Windows 11 Update Pending Restart

The fastest fix is opening Settings, going to Windows Update, and selecting Pause updates, which stops the restart prompt for up to a week without deleting anything. Stronger options exist for a pending install that will not go away, running from clearing the update cache to registry surgery, so work down the list and stop at the first one that solves the problem. EASEUS, which documents the stronger methods, recommends backing up the machine before you touch the registry or Group Policy, since a wrong edit there can leave the system unbootable.

Pause Updates for Seven Days

Open Settings, go to Windows Update, and select Pause updates. The default pause is one week, and the dropdown lets you extend the date further. Nothing is deleted, so this is the right choice when you simply want the restart prompt to stop until the weekend.

Clear the SoftwareDistribution Folder

Downloaded but uninstalled update files sit in a staging folder, and emptying it cancels the pending install and forces Windows to fetch fresh copies later. The same trick fixes downloads that have corrupted halfway.

  1. Stop the services. Open Command Prompt as administrator, then run net stop wuauserv followed by net stop bits.
  2. Empty the folder. Browse to C:\Windows\SoftwareDistribution and delete the contents, particularly everything inside the Download subfolder. Leave the folder itself in place.
  3. Start the services again. Run net start wuauserv and net start bits, or simply restart the PC.

If the Folder Will Not Clear

Files that refuse to delete usually mean a service is still holding them. Check that both commands in step one actually returned a success message, then try again from Safe Mode. Windows OS Hub describes the offline version of this repair, carried out from the Windows Recovery Environment, where you delete C:\Windows\WinSxS\pending.xml, C:\Windows\WinSxS\cleanup.xml, and the contents of C:\Windows\SoftwareDistribution\Download to break a restart loop on a machine that will not boot normally.

Uninstall an Update That Has Already Installed

Go to Settings, Windows Update, View update history. Under Feature Updates or the related updates list, choose Uninstall updates, find the entry you want gone, and select Uninstall. Windows will ask to restart, and the rollback itself can take as long as the original install did, so do not start this five minutes before you need the machine.

Revert Pending Actions with DISM

When a pending update has wedged the machine into a restart loop, booting into the Windows Recovery Environment and undoing the staged work is the cleanest fix. From the recovery Command Prompt, Windows OS Hub gives the command as DISM /image:C:\ /ScratchDir:C: /cleanup-image /RevertPendingActions. Adjust the drive letter if recovery has mounted your Windows partition somewhere other than C.

One more registry step belongs with this. On an offline image, open Registry Editor, load the system hive, navigate to HKLM\SYSTEM\CurrentControlSet\Control\Session Manager, and delete the PendingFileRenameOperations value, which tells Windows to stop trying to finish file swaps that never completed.

Lock the Feature Update Version in the Registry

Blocking a specific feature update, rather than a monthly patch, is a different job. EASEUS describes adding two values under HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate: a DWORD called TargetReleaseVersion set to 1, and a string called TargetReleaseVersionInfo holding the version you want to stay on, such as 21H2 in their walkthrough. Group Policy achieves the same result on Pro and Enterprise editions through the Windows Update settings, where you can also enable the policy that turns off automatic restarts during active hours. Home edition does not include the Group Policy Editor, which is why the registry route exists.

If the Update Still Will Not Finish

The point to stop waiting and start intervening is zero disk activity for over an hour on a restart screen that never changes, since a genuinely stuck update and a very slow one look identical up to then. From there, the fix is interrupting the update and repairing the component store, not more patience.

Tell a Stuck Update from a Slow One

Watch the drive activity light, or the disk column in Task Manager if you can still reach the desktop. Steady activity means work is happening even when the percentage has not moved for 20 minutes. Zero disk activity for over an hour, on a restart screen that never changes, is the point where Microsoft’s six hour window stops being a reason to keep waiting. Note the exact percentage before you act, because a stall at the same number after a forced restart tells you the problem is repeatable rather than a one-off.

Repair the Component Store and Retry

After you cancel or interrupt an update, check the system before letting Windows try again. Run DISM /Online /Cleanup-Image /RestoreHealth from an administrator Command Prompt, then sfc /scannow, and let each finish. Windows OS Hub recommends exactly this pair after reverting pending actions, on the reasoning that an interrupted install can leave component files in a half-swapped state that the next attempt will trip over. Should the same update fail twice with the same error, downloading it by name from the Microsoft Update Catalog and installing it manually skips whatever part of the automatic pipeline is broken.

Frequently Asked Questions

Does an SSD Really Make Updates Faster?

Yes, and it is the single biggest hardware difference. Readers reporting timings to Ask Leo describe around 15 minutes for a full update cycle on a solid state drive, against 45 minutes or more on older machines with a mechanical hard drive. Installation is a small-file, write-heavy job, which is the workload where mechanical drives fall furthest behind.

Why Is My PC Still Slow After the Update?

Two background jobs are usually to blame: TiWorker.exe finishing its cleanup, and Windows Search rebuilding its file index. Both can run for hours on modest hardware. Feature updates also re-enable visual effects, startup apps, and background services you had previously turned off, so check the Startup apps tab in Task Manager once the dust settles.

Is Six Hours Normal for One Update?

Six hours is the outer edge of Microsoft’s own guidance, not a typical result. The company’s figures describe how much connected time a device needs to complete quality and feature updates reliably, and its program manager has said most updates finish in under an hour. A monthly patch that takes six hours points to a mechanical drive, a very poor connection, or a fault worth investigating.

Will Pausing Updates Stop the Restart Prompt for Good?

No. Pausing buys seven days by default, extendable through the dropdown in Windows Update, after which Windows resumes and the prompt returns. Blocking a specific feature update long term needs the TargetReleaseVersion registry values or the equivalent Group Policy setting, and neither should be used to skip security patches indefinitely.

What Does TiWorker.exe Do in Task Manager?

TiWorker.exe is the Windows Module Installer worker, the process that applies updates and then tidies up after them. Heavy processor use from it in the hours after an update is normal behavior, not a sign of infection. Should it still be pinning the processor days later, run sfc /scannow and DISM /Online /Cleanup-Image /RestoreHealth to check for damaged component files.

Practical version: give a monthly patch a few minutes after the restart and a feature update a couple of free hours, clear 10GB to 20GB of disk space and close Settings before you start, and reserve the SoftwareDistribution and DISM repairs for the times an update genuinely refuses to move. Most slow updates are working exactly as designed, just on hardware that makes the design obvious.

What This Page Does Not Publish

  • I do not prescribe a room temperature or cooling setup for updates.
  • I do not explain every internal design choice behind Windows installer resource limits.
  • I do not offer a separate timing formula for security patches and feature updates.

References

Author Profile

Eric Dawson
Eric Dawson
I'm Eric Dawson, the writer behind The Money Watch. I live in the Columbus, Ohio area and I write about the ordinary questions that turn out to be complicated: computers, shopping, food, travel, parking, small businesses, fees, rules and products. Every article starts with the official page, the maker or the agency, then the sources that check it, and I say plainly where they disagree and what I would do. More about how I work is on the About page.