Windows Update Hanging for Hours? When to Wait vs Act

If Windows Update is frozen at the same percentage for hours in Windows 11 or Windows 10, the fix is almost always the same: confirm the disk activity light has actually gone idle first, then either give it more time or clear the update cache — you rarely need anything more drastic than that. Here's the part almost nobody tells you: Microsoft itself has publicly admitted, more than once, that its own update process can hang at a random number like 32% or 61% for reasons that have nothing to do with your PC being broken. This isn't a new mystery we've solved for the first time today — we watched this exact bug play out in public back in 2019, and the honest fix hasn't changed much since.

Jake found this out the expensive way. A customer dropped off an older laptop at his phone shop on a Tuesday morning, asking for a quick Windows 10-to-11 upgrade before a job interview the next day. Jake started the update, went to lunch, came back, and it was still sitting at 32%. He waited another hour. Still 32%. By the time he gave up and force-restarted it that evening, the customer's interview prep time was gone, and Jake refunded half the service fee out of his own pocket rather than lose the customer entirely.

"I genuinely thought I'd bricked it," Jake told Ethan afterward. Ethan's response was blunt: "You didn't do anything wrong by waiting — you did something wrong by not knowing when to stop waiting. Those are two different skills, and most guides only teach one of them." That's the gap this post is built to close: not just what to click, but how to tell, in the moment, which kind of "stuck" you're actually looking at.

Which One Is Actually Happening to You?

"Windows Update is stuck" covers at least four different situations, and they don't all get the same fix. Before you touch anything, work out which one you're in.

1. The percentage hasn't moved, but the PC is still working

Open Task Manager (Ctrl + Shift + Esc) and look at the Disk column, or watch the little activity light on a laptop's edge if it has one. If disk usage is still bouncing around, the update is doing real work behind a number that just isn't reporting it well. This is the single most common case, and it's the one where doing nothing is the correct move.

2. The percentage hasn't moved and neither has anything else

Disk usage sits at 0%, the fan has spun down, and nothing has changed in 20+ minutes. This is a genuine hang, not a slow update. It still doesn't mean you should restart immediately — some hangs resolve themselves in the first hour — but it does mean the clock on "how long is reasonable" starts now.

3. It restarts, gets to "Working on updates 100%," and restarts again

This loop, sometimes running through two or three restarts, is normal for larger cumulative updates and feature updates. Each restart applies a different phase of the update. It only becomes a problem if the same restart happens more than three or four times in a row with no progress between them.

4. It rolled back on its own, with a message about undoing changes

This isn't actually "stuck" — it's Windows Update failing safely and reverting rather than leaving your PC half-updated. It's frustrating, but it's the system doing exactly what it's designed to do when something goes wrong partway through. The fix here is different from the other three, and we'll cover it in the failure-modes section below.

Fixing a Stuck Update in Windows 11

Most Windows 11 PCs today are on version 25H2, the current mainstream release, with the most recent monthly update being build 26200.8875 (KB5101650) and the newest preview build at 26200.8973 (KB5101684). None of that changes the basic troubleshooting order below, but it's worth knowing so you're not chasing a build-specific rumor that doesn't apply to your machine.

Step 1: Confirm it's actually frozen (don't skip this)

Go back to the diagnostic section above if you haven't already. This single step is the difference between fixing a working update and breaking one that was fine.

Step 2: Run the built-in Windows Update troubleshooter

Open the Run box — Win + R, a small text box that lets you launch a program or system tool by typing its name instead of hunting for it in a menu — and go to Settings > System > Troubleshoot > Other troubleshooters, then run Windows Update. It won't unfreeze a currently-hung install, but it clears out several common causes of the same hang happening again next month.

Step 3: Force a restart the right way

Hold the power button for 10 seconds. On a laptop with a removable battery, that's rarely an option anymore, so the power button is genuinely your only tool here. Ethan's take on this is blunt: "Force-restarting isn't the reckless move people think it is — the reckless move is doing it at the five-minute mark instead of the six-hour mark." Once you've confirmed real inactivity for an extended stretch, holding the button is the correct next step, not a last resort.

Step 4: Clear the update components

This is the same core fix Microsoft was already pointing people toward years ago, and it still works because the underlying update pipeline hasn't fundamentally changed: stop the update-related background services, rename the folder where partially downloaded updates are staged, then restart those services so Windows rebuilds it fresh.

1. Open the Run box (Win + R) and type services.msc — the ".msc" tells Windows to open this as a Microsoft Management Console tool, which is how most background-service and system-administration screens in Windows are built.
2. Find "Windows Update" and "Background Intelligent Transfer Service" in the list, right-click each, and choose Stop.
3. Open File Explorer, go to C:\Windows\SoftwareDistribution, and rename the folder to something like SoftwareDistribution.old rather than deleting it outright — that way you have a fallback if something in the folder turns out to matter.
4. Go back to services.msc, right-click the same two services, and choose Start.
5. Try Windows Update again from Settings.

This doesn't touch your files, your apps, or your settings. It only clears out the update engine's temporary download cache, which Windows rebuilds automatically the next time it checks for updates.

Fixing a Stuck Update in Windows 10

These steps are the same on both — the Task Manager check, the forced restart, and the SoftwareDistribution reset above all work identically on Windows 10. What's different is the context you're troubleshooting in, since Windows 10 reached the end of its support lifecycle on October 14, 2025.

The honest state of Windows 10 updates right now

Windows 10 22H2 no longer receives free security updates. It still boots, still activates, and Microsoft Edge and Defender definitions still update normally — but new feature updates for unenrolled devices have stopped. If your update is stuck and you're not enrolled in Extended Security Updates (ESU), you may be troubleshooting a genuinely smaller, less frequent kind of update than you were a year ago, which is worth knowing before you assume something is broken.

If you're stuck during ESU enrollment itself

Consumer ESU enrollment happens through Settings > Windows Update > "Enroll now," and it needs a Microsoft account signed in — a local account won't show the option at all. If the enrollment step itself hangs rather than a regular update, sign out and back into the Microsoft account first, then retry, before assuming it's the same freeze covered above. Coverage under this program was extended in June 2026 and now runs through October 2027 for devices that enroll, and enrollment is still open as of this writing, so there's no rush that should push you into force-restarting too early.

One honest note on Windows 10 going forward

If you're fighting update problems on a PC that's now out of mainstream support, it's worth asking whether you're spending more time maintaining an aging install than a Windows 11 upgrade — or, if the hardware genuinely can't run Windows 11, a newer machine — would cost you. That's not a sales pitch so much as a real trade-off: ESU buys time, it doesn't buy back the years the hardware doesn't have left in it.

What It Looks Like When None of That Works

Most stuck updates resolve with the steps above. Some don't, and it helps to know what the next failure actually means rather than guessing.

"Undoing changes made to your computer"

This message means Windows Update tried, failed partway through, and rolled itself back rather than leaving the system in a broken half-updated state. Annoying, but it's the safety net working. After it finishes rolling back, run the SoftwareDistribution reset above before trying again — retrying immediately with the same corrupted cache tends to fail the same way twice.

A boot loop into Automatic Repair

If the PC restarts into a blue "Automatic Repair" screen repeatedly instead of finishing Windows normally, that's a step beyond a stuck update — it's a sign the update was interrupted at a point that left system files in an inconsistent state. From the Automatic Repair screen, choose Advanced Options > Troubleshoot > Advanced Options > Startup Repair before anything else. If that doesn't resolve it, this has moved past "stuck update" territory into "needs a repair install," which is a different guide entirely — and if there's data on that drive you can't afford to lose, that's the point to stop and back it up from a recovery environment before trying anything more aggressive.

The same error code every time you retry

A repeating numeric error code (rather than a silent freeze) means Windows Update is actually failing, not hanging — those are different problems with different fixes, and no amount of waiting resolves a genuine failure code. Note the exact code before you do anything else; it's the single most useful piece of information for narrowing down what's actually wrong.

Why Preview Builds Hang More Than Stable Releases

If you're running an Insider Preview build rather than the stable release, stalls like this are more common by design, not by accident — you're running code that hasn't been through the same broad testing as what ships to everyone else. Microsoft restructured the Insider Program in spring 2026: the old Dev and Canary channels are gone, replaced by Beta, Experimental, Experimental (26H1), Experimental (Future Platforms), and Release Preview. If you're seeing a hang on one of the newer Experimental channels specifically, that's the most bleeding-edge tier available, and a slower or stranger update process is genuinely more expected there than on Release Preview or the stable channel.

This is also, honestly, where this exact guide started. We watched Microsoft publicly own up to an update hang on a 2019 preview build in real time, and the update pipeline that hangs today is a descendant of the same one. Nobody solved this bug once and for all — it's a recurring category of problem in any system that pushes large binary updates to millions of different hardware configurations, and it shows up again every so often. If a guide ever tells you this has been "fixed permanently," be skeptical of it.

How to Tell Which Update You're Actually Waiting On

Not every stuck update is the same size, and knowing which kind you're dealing with tells you how long "normal" actually is. A monthly cumulative update — the small, routine kind Microsoft ships on Patch Tuesday — should realistically finish in well under an hour on a healthy PC. A full feature update, the kind that moves you between annual versions like 24H2 and 25H2, can legitimately take two to three hours even with nothing wrong, because it's effectively reinstalling large parts of the operating system rather than patching it in place.

You can check which one you're on before you even start troubleshooting: Settings > Windows Update > Update history shows the name and size of what's currently installing. If it says something like a "20xx-xx Cumulative Update," you're in the small, fast category, and a multi-hour hang is a real red flag. If it names a feature update by version number, budget far more patience before you start treating it as frozen. This single check resolves a huge share of "is this actually stuck" anxiety on its own, because most people assume every update is the small kind and panic at the two-hour mark when a feature update was always going to take that long.

Laptops, Tablets, and Machines You Can't Just Walk Up To

Laptops

Closing the lid mid-update can pause it rather than cancel it, but low battery is the real risk — plug in before starting any update you can't babysit, and disable sleep on lid-close from Settings > System > Power while an update is pending. A dead battery mid-write is a much worse day than a slow update.

Tablets and no-keyboard devices

Every step above still works with touch — Settings, the troubleshooter, and Automatic Repair's on-screen options are all touch-navigable. The power-button-hold for a forced restart works the same way; just be prepared to hold it slightly longer on some tablets, since the button often doubles as a screen-lock control.

Remote Desktop and VMs

Windows Update deliberately restarts the graphics and networking stack partway through certain updates, which can make a Remote Desktop session drop or a VM console go black for a few minutes even when the update is proceeding normally. Don't treat a dropped RDP session as proof of a hang — reconnect after five to ten minutes before concluding anything's wrong. If you genuinely can't reconnect at all, that's a different signal, and worth checking from the host's own console rather than over RDP.

Multi-monitor setups

A second monitor going black or losing signal during an update restart is normal — the display driver reloads as part of the process. Give it a full minute after the PC appears to have restarted before assuming the monitor itself has a problem.

Do You Need a Third-Party "Update Fixer" Tool?

Honestly, no — not for this. Every third-party "Windows Update repair" utility on the market ultimately automates the same handful of steps covered above: stopping the update services, clearing the SoftwareDistribution folder, and re-registering some system files. You lose nothing by doing it manually, and you avoid installing a program with system-level access from a vendor you have no ongoing reason to trust. The one place a dedicated tool earns its keep is disk health checking — if you suspect a failing drive is the real reason updates keep hanging, a drive-manufacturer's own diagnostic tool (not a generic "PC cleaner") is worth running, since a dying drive can absolutely masquerade as a stuck update.

Before You Hand a Stuck PC to Someone Else to Fix

This is the part Jake's shop deals with constantly: someone drops off a laptop stuck mid-update, and it's already signed into their Microsoft account, email, and every browser session. If a repair shop needs to force-restart or reset the machine, ask what happens to your sign-in sessions and whether they need your account password at all — the SoftwareDistribution reset covered above needs neither, since it's a local file operation, not an account-level one. If a tech asks for your Microsoft password to fix a stuck update, that's a reasonable moment to ask why, because none of the fixes in this guide require it.

Stopping This From Ambushing You Again

You can't prevent every hang, but you can stop it from catching you at the worst possible time.

• Set Active Hours realistically. Settings > Windows Update > Advanced options > Active hours tells Windows not to restart automatically during the window you actually use the PC. If you work irregular hours, set it generously rather than tightly.
• Never start a major update with under an hour of known free time and a low battery. This is the single most common way Jake sees customers turn a normal update into a "stuck" one — they start it and then need the laptop back before it's realistically done.
• Keep at least 20 GB free. A near-full drive is one of the most common causes of a "stuck" update that's actually silently failing to unpack files. If disk space is genuinely tight, this is exactly the kind of moment an external drive or a cloud backup service earns its cost — moving old photos and video off the main drive before an update, rather than during a crisis, buys you real headroom.
• Update one thing at a time. Don't kick off a Windows update and a large game or software install simultaneously — they'll compete for the same disk and network resources and each will look "stuck" when it's really just queued behind the other.

Once It's Finally Done, Do This Next

A stuck update usually isn't an isolated event — it's often the first sign of a drive filling up or a driver falling out of sync, and both tend to cause the exact same problem again next month if you don't check them now while you're already in the settings.

Check for a driver update the OS update was waiting on

Go to Settings > Windows Update > Advanced options > Optional updates and look under Driver updates. Occasionally a stuck update is actually waiting on a graphics or storage driver that's misbehaving; installing the pending driver update and then retrying resolves hangs that a cache clear alone doesn't touch.

Run Disk Cleanup on the leftover files

After a feature update finishes, Windows keeps a copy of the previous version for about ten days in case you need to roll back, which can eat 10-20 GB. Search for "Disk Cleanup," run it as administrator, and check "Previous Windows installation(s)" once you're confident everything's working — that space is exactly what you'll want free the next time an update needs room to stage itself.

For the Person Managing More Than One PC

If you're troubleshooting this across a handful of family or shop machines rather than just one, doing the cache-clear steps by hand on each one gets old fast. You can save the exact commands as a small batch file — right-click, "Run as administrator" — instead of retyping them:

Save that as a .bat file, and it becomes a one-click version of the manual steps from earlier — genuinely useful if you're the person everyone in the family or the shop calls when this happens, and considerably less error-prone than re-typing five commands under pressure while a customer waits at the counter.

Frequently Asked Questions

How long should I wait before I consider Windows Update actually stuck?

Roughly six hours with no real disk activity is a reasonable outer limit for a major update — that's in line with what Microsoft itself has quietly recommended in the past. If the disk is actively working, extend that further rather than interrupting a process that's making real progress.

Is it safe to force restart my PC during a Windows update?

It's safe once you've confirmed genuine inactivity, and it's the correct move at that point rather than a risky one. It's not safe to do at the five- or ten-minute mark, before you've checked whether anything is actually still happening.

Why does Windows Update freeze at the same percentage every time?

The progress percentage isn't a literal countdown of remaining work — it can sit still at a specific number for a long stretch and then jump forward, or hang there because of a specific stuck component that recurs on your setup. Clearing the update cache resolves most cases where the exact same number comes up repeatedly.

What is the SoftwareDistribution folder, and why do I need to clear it?

It's where Windows stages update files while they're being downloaded and prepared for installation. If a download in that folder gets corrupted or interrupted, Windows Update can keep trying to use the same broken files every time, which shows up as a repeated hang. Renaming the folder forces Windows to rebuild it from scratch.

Will clearing the update cache delete my files?

No. It only removes temporary update-installer files that Windows re-downloads automatically the next time it checks for updates. Your documents, photos, apps, and settings are untouched.

My PC keeps restarting into Automatic Repair — is that the update's fault?

Usually yes, if it started right after an interrupted update. It means the update was stopped at a point that left system files inconsistent. Startup Repair from the Automatic Repair screen resolves most cases; if it doesn't, that's a sign the issue has gone beyond what a stuck-update guide covers.

Can I just skip a stuck update entirely?

You can defer most feature updates for a while from Settings > Windows Update > Advanced options, but you can't permanently skip security updates without giving up on receiving them at all, which leaves the PC exposed. Deferring buys you time to troubleshoot at a better moment; it isn't a real substitute for eventually installing it.

Does closing my laptop lid pause or break the update?

It typically pauses it rather than breaking anything, but a dead battery mid-update is a real risk. Keep the laptop plugged in and the lid open, or at minimum disable sleep-on-lid-close, until the update finishes.

My Windows 10 PC is stuck installing an ESU update — is that different?

The stuck-update fix itself is the same, but confirm you're actually signed in with the Microsoft account used to enroll in Extended Security Updates first — enrollment problems can look identical to a stuck download but need a sign-in fix instead of a cache clear.

Should I run System Restore if the update is stuck?

Not as a first move. System Restore rolls back system files to an earlier point and can undo other changes you've made since, which is a bigger step than most stuck updates actually need. Try the cache clear first; save System Restore for after a failed update has left the system in a genuinely broken state.

Why does my update say 100% and then restart and start over?

Large updates apply in phases, and each phase can show its own 0-to-100% counter with a restart in between. Two or three restarts in sequence, each showing fresh progress, is normal. The same restart happening over and over with no new progress is the actual warning sign.

Is Windows 11's Insider Preview more likely to hang than the stable release?

Yes, and that's expected rather than a defect — preview builds, especially on the newer Experimental channels, haven't been through the same broad testing as the stable release. If reliability matters more to you than early access to new features, Release Preview or the stable channel is the lower-risk choice.

Do I need admin rights to clear the update cache?

Yes — stopping and starting the Windows Update and BITS services requires an administrator account. If you're on a work or family-managed PC without admin rights, you'll need to ask whoever manages it, or use the built-in troubleshooter instead, which can run some fixes without full admin access.

Can antivirus software cause updates to hang?

Third-party antivirus tools occasionally interfere with the update process by scanning or locking files the installer needs mid-write. If hangs happen consistently and you run third-party security software, temporarily disabling it during the update (never during general browsing) is worth testing — just re-enable it immediately afterward.

Should I disconnect from the internet if the update seems frozen?

No — most of the install phase happens locally from already-downloaded files, and cutting the connection won't unfreeze anything already in progress. It can, however, prevent a partially-downloaded update from completing at all. Leave the connection alone and use the disk-activity check instead.

How do I know if I'm installing a small update or a full feature update?

Check Settings > Windows Update > Update history before you panic. A named "Cumulative Update" is the small, routine kind and should finish quickly. A version-numbered feature update is a much bigger job and can reasonably take a couple of hours on its own.

My update finished, but now my PC feels slower than before — is that related?

Sometimes, briefly. The first login after a feature update often re-indexes files and finishes background driver installs, which can make the first 20-30 minutes feel sluggish. If it's still slow after that window, it's more likely a separate issue than a continuation of the update.

Revision note. Originally published in December 2019, when we covered Microsoft's own acknowledgment that a Windows 10 Insider Preview build was hanging for extended periods at points like 32% and 61%. Rewritten August 25, 2026 for Windows 11 and Windows 10, since that specific preview build is long retired but the same category of stall still shows up today. If you're the person watching a frozen progress bar right now wondering whether you just broke your own PC — you almost certainly didn't, and you're closer to done than it feels.