How Long Does a Windows Update Take?

Windows updates have a reputation for arriving at the worst possible moment — and then dragging on longer than expected. Understanding what's actually happening during an update, and why timing varies so dramatically from one machine to the next, takes a lot of the frustration out of the process.

What Actually Happens During a Windows Update

A Windows update isn't a single action — it's a sequence of stages, each taking its own slice of time:

1. Downloading — Windows pulls update files from Microsoft's servers (or a local network cache in business environments).
2. Preparing/Staging — Files are verified, unpacked, and staged in the background, sometimes while you're still using the PC.
3. Installing — Changes are applied to system files, drivers, and registry entries.
4. Restarting and configuring — The system reboots, applies remaining changes, and finalizes the new state.

The progress bar you see during restart covers that last phase — which is why a machine can sit at "30% complete" for several minutes and then jump to 80% almost immediately.

Typical Time Ranges — A General Benchmark ⏱️

There's no single honest answer to "how long," but general patterns hold across most setups:

These are general benchmarks, not guarantees. Real-world times stretch significantly based on the variables below.

The Factors That Determine How Long Your Update Takes

Hardware Age and Specs

This is the biggest variable. Older machines with mechanical hard drives (HDDs) are dramatically slower during updates than systems running solid-state drives (SSDs). The installation and configuration phases involve thousands of small file reads and writes — exactly the kind of work where SSDs outperform HDDs by a wide margin.

CPU speed and RAM also matter. A slower processor takes longer to decompress files and apply system changes. Low RAM (4GB or less) can cause Windows to lean heavily on the page file during updates, which compounds slowness.

Internet Connection Speed

Download speed affects the first phase only. A fast connection (100 Mbps or more) will pull most updates in seconds to minutes. A slow or congested connection — common on older DSL lines or heavily shared Wi-Fi — can turn the download phase alone into a 20–30 minute wait.

Once files are downloaded, internet speed no longer matters. The remaining slowness is entirely local.

The Size of the Update

Cumulative updates released on Microsoft's monthly Patch Tuesday cycle typically range from a few hundred megabytes to over 1GB. Feature updates — the larger annual upgrades that shift Windows to a new version — involve several gigabytes of data and far more system-level changes, which is why they take significantly longer.

Whether the Update Is Being Applied Fresh or Incrementally

If a system has been regularly updated, each new patch is relatively small. A machine that hasn't been updated in months may need to chain together multiple updates — effectively downloading and installing several rounds in sequence — before it reaches current.

Background Processes and System Load

Windows tries to download and stage updates in the background while the PC is in use, but a heavily loaded machine running resource-intensive software during this phase will slow things down. This is less visible but real.

Why the "Installing Updates" Screen Takes So Long on Some Machines 🖥️

The restart phase — where the screen shows a percentage while Windows configures updates — is the one most people watch impatiently. On an HDD-equipped machine, this phase can take 20–45 minutes by itself for a mid-sized cumulative update. On a modern SSD, the same phase often completes in under 10 minutes.

This is also the phase most sensitive to being interrupted. Powering off a machine mid-update (not just restarting, but hard-shutting-down) can corrupt system files. Windows is designed to recover from incomplete updates, but recovery itself takes time and doesn't always work cleanly.

Windows 11 vs. Windows 10 Update Times

Microsoft has invested in making Windows 11 updates faster and less disruptive than older Windows 10 cycles. Smaller update packages and more background staging mean the visible "installing" time has generally decreased on supported hardware. However, unsupported hardware running Windows 11 through workarounds may see longer or less reliable update behavior.

What Can Slow Updates Beyond the Norm

• Antivirus scanning update files in real time (most reputable security software is designed to minimize this, but budget or misconfigured tools can interfere)
• Disk nearly full — Windows needs free space to stage and apply updates; less than 10–15GB free can cause failures or extreme slowness
• Corrupted update cache — sometimes the Windows Update component store develops errors that require manual repair via tools like DISM or sfc /scannow
• Enterprise-managed devices — IT policy controls, compliance checks, and network routing through a WSUS server add steps that consumer machines don't have

The Spectrum: Fast vs. Slow Update Experiences

A modern laptop with an NVMe SSD, 16GB RAM, a reliable broadband connection, and a clean, regularly updated Windows install will often complete a standard Patch Tuesday update — including restart — in under 15 minutes.

The opposite end of that spectrum: an older desktop with a spinning hard drive, 4GB RAM, a slow internet connection, and several months of missed updates can spend two or more hours working through a backlog, with long pauses during each restart phase.

Same operating system. Wildly different experiences. ⚙️

Why Your Experience May Not Match General Estimates

The ranges above describe patterns across many machines and configurations, but your specific outcome depends on where your hardware, software state, and network conditions sit within those variables. A machine that updates quickly today might slow down as its drive fills or its hardware ages. A recently refreshed install on older hardware might surprise you with its speed.

The gap between general timelines and your actual experience is always your own setup — and sometimes the only way to know is to let an update run and observe what phase is taking the longest.