Windows Update Stuck at 0%, 33% or 100%? Diagnose by Where It Stops (2026 Updated Guide)

Quick answer

Where Windows Update gets stuck tells you what stage of the update pipeline failed — and the right fix depends on the stage. Stuck at 0% is a download problem. Stuck somewhere in the middle (typically 33%, 66% or 95%) is usually a service or staging problem. Stuck at 100% with “Please don’t turn off your PC” for hours is a post-install problem you should not interrupt for at least four hours. Most articles online give one generic list of fixes regardless of where you’re stuck. That’s why those fixes don’t work.

Before you start

The single most important rule: if Windows says “Please don’t turn off your PC”, don’t turn off your PC for at least four hours. Cumulative updates legitimately stall for long periods at 100% on slow disks. Forced shutdowns at this stage cause the bulk of “my PC won’t boot after a Windows Update” cases.
You will need administrator rights for most of the fixes below.
Don’t run a third-party “Windows update fixer” tool. Everything required is built into Windows.
Work or school device? See If you are on a work or school device before doing anything.

What “stuck” actually means

Windows Update is not a single operation. It’s a multi-stage pipeline:

Check (0% in some interfaces, blank/spinning in others) — Windows asks Microsoft what’s available for your machine.
Download (0–100% with bytes/seconds counter) — Windows downloads the update payload.
Stage / Prepare (often shown as 0–33%) — Windows verifies signatures and stages the files.
Install (often shown as 33–66%) — Windows applies the update with the OS still running.
Reboot install (the “Please don’t turn off your PC” screen, sometimes labelled with another percent) — Windows finalizes the update during reboot.
Cleanup (sometimes a brief stall just after login on first boot post-update) — Windows finalizes its component store.

When the progress bar stalls, it’s stalled at one of those stages. The bar doesn’t always tell you which stage cleanly — different parts of the Windows Update interface use different progress conventions — but the percentage gives you a strong signal. The right fix matches the stage.

Where this error appears

You’ll see “stuck” Windows Update behavior in:

Settings → Windows Update, where the progress bar stops moving.
The full-screen “Please don’t turn off your PC” screen that appears during shutdown or reboot for cumulative updates.
Bootup scenarios where the PC reaches the “Working on updates” screen and apparently never moves past it.

Diagnose by stuck-percent

Where it’s stuck	What stage failed	Most likely cause
Stuck at 0% (download phase)	Download	Network problem, BITS service stopped, blocked by antivirus, or Windows Update servers throttled
Stuck at any percent under 33% during preparation	Staging	Disk space, corrupted previous download, or a half-installed previous update
Stuck at 33–66% during install	Installation	Servicing-stack corruption, conflicting drivers, antivirus interference
Stuck at 95–99% before reboot prompt	Late install / verification	Disk slow or near full; component store integrity check
Stuck at “Please don’t turn off your PC” during reboot	Boot-time install	Cumulative size + slow disk = legitimately long stall (NOT a bug)
Stuck after login, brief stall before desktop loads	Cleanup	Component store finalization — usually clears in 5–15 minutes

The key insight: a download stall and an install stall are completely different problems. A network fix won’t help an install stall, and a service reset won’t help a network stall.

Fixes by stage

If it’s stuck at 0% — the download problem

Don’t waste time on DISM, SFC, or component-store repair. The update hasn’t even arrived yet. Focus on the download path.

Check your internet connection. Try loading a few websites. Run a speed test. Confirm the connection is actually working.
Pause Windows Update and resume. Settings → Windows Update → Pause for 1 week, wait two minutes, then click Resume updates. This forces the update orchestrator to re-evaluate.
Restart the BITS service. Press Win+R, type services.msc, press Enter. Find Background Intelligent Transfer Service. Right-click and select Restart (or Start if it’s stopped).
Temporarily disable third-party antivirus. Some antivirus suites quarantine partial download files mid-write. If the download starts moving once antivirus is disabled, the right long-term fix is to add the SoftwareDistribution folder as an exclusion.
Disable any VPN. A meaningful number of VPN configurations break Microsoft Update connectivity in subtle ways. Disconnect and retry.
Manually install the update. Note the KB number from Update History, search for it at the Microsoft Update Catalog, download the matching .msu file, and run it. This bypasses Windows Update’s download orchestrator entirely.

If the download still won’t move, see Windows Update error 0x80070643 for related fixes — many “stuck at 0%” cases are actually 0x80070643 errors that Windows isn’t surfacing prominently.

If it’s stuck mid-install (33–66%)

This is where most cases actually live, and where the standard fixes pay off.

Wait at least 30 minutes. The stall may be real but slow. Cumulative updates routinely take 30–45 minutes through the install phase on slower disks.
Check if the disk is busy. Press Ctrl+Shift+Esc to open Task Manager. Look at the disk activity column. If disk activity is consistently above 30%, the install is making progress — wait longer.
If disk activity is at 0% for more than 15 minutes, the install has actually stalled. Restart the PC. Windows will roll back the failed update on the next boot.
After rollback, run the Windows Update troubleshooter. Settings → System → Troubleshoot → Other troubleshooters → Windows Update → Run. Allow it to apply fixes.
Reset Windows Update components. Walk through How to reset Windows Update components. This clears the staging and re-registers the underlying services and DLLs.
Run DISM and SFC. From an elevated Command Prompt:
```
DISM /Online /Cleanup-Image /RestoreHealth
sfc /scannow
```
Allow up to 45 minutes. Then retry the update.

If it’s stuck at “Please don’t turn off your PC”

Wait. I know that’s frustrating advice. It’s also the right advice.

Cumulative updates on slower disks (especially 5400 RPM hard drives, but also SATA SSDs that have filled up) can spend two to four hours at this screen on a normal install. The screen is not lying — Windows really is doing work, even if you can’t see it.

Things to know:

The hard drive activity light tells you everything. If the light is blinking or solid, work is happening. Don’t interrupt.
Most “stuck at install” emergencies in this phase are not stuck at all. Forced shutdowns during this phase are the leading cause of “Windows won’t boot after update” complaints. The two are connected.
Four hours is the genuine “this is now stuck” threshold. If you’ve been at this screen for four straight hours with no disk activity, then yes, something has actually failed. Force a power off (hold the power button for 10 seconds), and on the next boot Windows will roll back the update automatically.
After rollback, run the Windows Update troubleshooter and try the update again.

If your PC won’t boot at all after a forced shutdown during this phase, see recovery error 0xc0000225 for the boot-recovery procedure.

A brief stall (the desktop background appears but the taskbar takes a while to populate, or the system feels sluggish) for 5–15 minutes after a successful update install is normal. Windows is finalizing its component store and processing the post-install hooks for any installed software.

Don’t reboot. Don’t run optimisation tools. Just wait. Performance returns to normal once finalization completes.

If the stall lasts more than 30 minutes — or recurs every reboot afterwards — there is a real problem, and it’s typically a corrupted servicing stack. Run DISM and SFC once the system is responsive enough.

Advanced fixes (any stage)

These are reversible. Run them when the stage-specific fixes haven’t worked.

Reset Windows Update components

The full procedure is documented at How to reset Windows Update components. For “stuck” symptoms specifically, this is the heaviest reset you should try before considering a repair install.

Run DISM /RestoreHealth then SFC

From an elevated Command Prompt:

DISM /Online /Cleanup-Image /RestoreHealth
sfc /scannow

For deeper guidance and what to do when DISM itself errors out, see How to run DISM and SFC safely.

In-place repair install

If the same update keeps failing across multiple attempts, an in-place repair install replaces the Windows component store while preserving your data and applications. Download the Windows 11 ISO, mount it, run setup.exe from inside Windows, and choose Keep personal files and apps. Block out 90 minutes.

If you are on a work or school device

Don’t reset Windows Update components, don’t run DISM, and don’t force a power-off on a managed device without coordinating with your administrator. Particularly in enterprise environments, an update that appears stuck may be one your admin team is actively investigating, and forcing a recovery can complicate that work.

If you’re the de facto IT person for a small business with no separate IT to escalate to, the equivalent admin-side workflow is in our admin checklist for new M365 sign-in failures.

When to stop

Stop and seek a different approach when:

You’ve waited four hours at the “Please don’t turn off your PC” screen with no disk activity. Force a power-off and let Windows roll back on the next boot.
The same update fails to install across three or more attempts even after a successful Update components reset and DISM/SFC. The update genuinely doesn’t apply to your system in its current state — an in-place repair install is the next step.
The PC has begun showing other instability (random freezes, BSODs, files vanishing, apps crashing). The update issue is a symptom of something deeper — diagnose hardware before continuing.
Forced shutdowns during this work have left the PC unable to boot. Stop trying to fix Windows Update and recover the boot first — see recovery error 0xc0000225.

Windows Update error 0x80070643 — generic install failure, often the root cause of “stuck” symptoms.
Windows Update error 0x80070002 — file-not-found error in the download path.
Windows Update error 0x800f081f — source-files-missing error during install.
How to reset Windows Update components — canonical reset procedure.
How to run DISM and SFC safely — system file repair guide.

Official references

Microsoft Support: Fix Windows Update errors
Microsoft Learn: Windows Update troubleshooting reference
Microsoft Update Catalog: catalog.update.microsoft.com

FAQ

My PC has been at “Please don’t turn off your PC” for two hours. Is that normal? On a slower disk (especially a 5400 RPM HDD), yes — entirely normal. The four-hour rule is the threshold for declaring it actually stuck. Two hours with disk activity is just slow, not broken.

Can I tell if Windows Update is actually doing something or just frozen? Yes. The drive activity light is the most direct indicator. If you have an SSD (no light), open Task Manager (Ctrl+Shift+Esc), open the Performance tab, and watch the disk graph. Activity above ~10% means Windows is making progress.

Why does the same update fail at the same percentage every time? Because the failure point is deterministic. The update hits the same step in the same code path each attempt and fails for the same reason. The fix is to address what’s different about your machine versus a machine where the update succeeds — usually a corrupted servicing stack or a third-party tool blocking a specific operation.

Should I just disable Windows Update permanently? No. Disabling Windows Update means your machine no longer receives security patches. The cure is far worse than the disease. If updates are genuinely a recurring nightmare on a particular machine, the right answer is an in-place repair install, not avoidance.

Is my hard drive failing if Windows Update is this slow? It might be. Old spinning-rust hard drives with bad sectors, or SSDs near the end of their write endurance, can cause exactly this symptom. Run chkdsk C: /scan for a read-only scan, and check SMART data via Task Manager’s Performance tab (recent versions of Windows 11 surface SMART warnings directly). If the disk shows warnings, replace it before doing anything else with Windows Update.

Can I safely cancel a stuck update? Cancel from inside Windows (closing the Settings page, restarting from the Start menu) is always safe. Forcing a power-off during the “Please don’t turn off your PC” screen is the dangerous version, and you should avoid it for at least four hours of confirmed inactivity.

↑ Back to top