Windows 11 Update Stuck at 100% or Restart Loop: What to Do, in Order
If your screen has been sitting on "Working on updates, 100% complete. Don't turn off your computer" — or your PC has restarted into that same screen three or four times in a row — the fix is almost never to force a restart first. Work down a list from safest to most drastic: confirm there's actually no disk activity, force restart once if there truly isn't, reset the Windows Update components, uninstall the update that's causing it, and only then reset the PC. Here's the part nobody tells you: that scary 100% screen is frequently Windows finishing correctly on its own. The real damage in most of these stories gets done by an impatient forced shutdown during the one window where interrupting the process turns a slow update into a PC that won't boot at all.
Jake called me on a Tuesday because a customer's laptop had been sitting on that message since Saturday. Three days. He'd already pressed and held the power button twice, which is the instinct almost everyone has — the screen looks frozen, so you kill it. The problem is that "looks frozen" and "is frozen" are not the same thing, and telling those two apart is most of this article.
This guide covers both symptoms in the title, because they're really the same failure at two different moments: the update either won't finish (stuck at 100%, 0%, or somewhere in between) or it finishes badly and now the PC won't stay booted (the restart loop). Windows 11 gets its own section first, then Windows 10, because the steps aren't identical and mixing them just confuses whichever OS you're actually running.
Is it actually stuck, or just slow?
Before you touch the power button, check for two things: the drive activity light (if your PC has one), and whether the percentage or the spinning dots have moved at all in the last stretch you've been watching. A large cumulative update genuinely can sit at "100% complete" for a long stretch while Windows finishes installing files in the background — the percentage reaches 100 before the work behind it is actually done. That's confusing UI, not a bug you need to fix.
🙋♂️ Jake's Reality Check
"How am I supposed to know if it's actually broken or just slow? I don't have three days to sit and stare at a laptop screen for a customer."
You don't need to stare at it. Check the drive light, or leave it and check back in an hour instead of five minutes. If the light is blinking and the customer isn't in a screaming hurry, closing the lid (on a laptop that won't sleep mid-update) or just walking away is a legitimate step, not a cop-out. Come back later, not never.
There's no official cutoff for "too long" — it genuinely depends on the size of the update, your drive speed, and whether anything went wrong partway through. What you're watching for isn't a clock, it's activity. No disk light, no change in the percentage across repeated checks, and the fan has gone quiet: that's your signal to move to the fix list. Constant disk activity with the number occasionally flickering: that's your signal to leave it alone a while longer.
✅ Why this is the one to use first
Waiting costs nothing and risks nothing. Every step after this one carries at least a small chance of making things worse, so it belongs last in the queue, not first.
Windows 11: fix "stuck at 100%" (or 0%, or 51–99%), in order
These steps apply whether the number on screen is 0%, 100%, or anything in between — the underlying cause and the fix are the same regardless of which percentage it stalled on.
Step 1: force restart once
If you've confirmed there's no disk activity and it's genuinely been hours, hold the power button for about 10 seconds until the PC shuts off, wait a few seconds, then power it back on. This is the one force-shutdown that's reasonable to do without more evidence — the risk is small, and it's usually enough to knock a stalled update loose and let it either finish or roll itself back automatically.
Step 2: run the Windows Update troubleshooter
If the PC boots normally after Step 1, open the Get Help app and run the built-in Windows Update troubleshooter, or go to Settings > System > Troubleshoot > Other troubleshooters and select Run next to Windows Update. It runs automated diagnostics and can fix a chunk of common causes on its own before you touch anything manually.
Step 3: reset the Windows Update components
This is the step almost everyone skips because it looks intimidating, and it's usually the one that actually works. It renames the folders Windows uses to stage update files, forcing a clean re-download instead of retrying whatever got corrupted. Open Command Prompt as administrator (search for it, right-click, "Run as administrator") and run these commands one at a time, letting each finish before typing the next:
net stop bitsnet stop wuauservren %systemroot%\softwaredistribution softwaredistribution.bakren %systemroot%\system32\catroot2 catroot2.baknet start bitsnet start wuauserv
Close Command Prompt, restart, and check for updates again. Nothing personal gets touched by this — you're only renaming Windows's own cache folders, and it rebuilds them automatically.
Step 4: check disk space and disconnect extra hardware
A Windows 11 upgrade or large feature update needs meaningful free space — roughly 20 GB free for a 64-bit install — and it can stall silently if the drive is too full partway through. Unplug docks, external drives, printers, and anything else not needed to boot, then try again. Peripherals occasionally interfere with the update process in ways that have nothing to do with storage.
Step 5: run DISM and SFC
If it's still failing, corrupted system files are a likely culprit. From an administrator Command Prompt, run DISM.exe /Online /Cleanup-image /Restorehealth, wait for it to confirm success, then run sfc /scannow and let it reach 100%. Try Windows Update again once both finish.
| Symptom | Likely cause | Start with |
|---|---|---|
| Stuck at 0%, no movement | Download never started or a connectivity problem | Check Wi-Fi/Ethernet status, then Step 1 |
| Stuck between 51–99% | Large update genuinely still processing, or a stalled install step | Check for disk activity first, then re-check for updates |
| Stuck exactly at 100% | Percentage reached before background finishing work is complete, or a genuinely hung install | Confirm no disk activity, then Step 1 |
| Restarts and returns to the same screen | Installation failed and can't complete or roll back cleanly on its own | Restart loop section below |
| Brief error code flashes before restart (e.g. 0x800705b4, 0x80240034) | Interrupted install, or update service/database issue | Step 3 (reset update components) |
Windows 11: fix a restart loop
This is a different problem from "stuck at 100%," and it needs a different fix. The update didn't just stall — it failed partway through, and now the PC keeps trying (and failing) to either finish it or undo it, landing you back on the same screen every time it reboots.
🙋♂️ Jake's Reality Check
"It's rebooted four times now and shown me the exact same screen every single time. Do I just keep waiting?"
No — a genuine loop, where you're back on the same install screen after a full reboot cycle, is your cue to stop waiting and go straight to recovery. Waiting only helps when there's a chance the process is still progressing; a loop means it isn't.
Ethan's blunt about this one: "People treat WinRE like it's a last resort for a dead PC. It's not — it's a normal tool built specifically for exactly this situation, and getting into it is deliberately easy." You reach it one of two ways.
- If the PC still boots to the login screen or desktop: go to Settings > System > Recovery, then select Restart now next to Advanced startup.
- If it never gets past the update screen: force a shutdown (hold the power button 10 seconds), power back on, and repeat that two more times. Interrupting the boot process three times in a row is what tells Windows to automatically launch the Windows Recovery Environment (WinRE) on the next attempt.
- Once WinRE loads, select Troubleshoot > Advanced options > Startup Repair, then let it run. If you've encrypted the device, you'll be asked for your BitLocker recovery key before it can proceed — more on that below.
- If Startup Repair reports it couldn't fix the problem, go back to Advanced options and select it again. It's normal for it to need two or three attempts, restarting between each one, before it either succeeds or gives up for good.
If Startup Repair genuinely can't resolve it after a few tries, the next tool in WinRE is Uninstall Updates under Advanced options — covered in detail further down, since it's also the right move for a PC that boots fine but keeps failing the same update on every retry.
⚠️ What this actually breaks
Forcing a shutdown while Windows is genuinely still writing update files — not idle, not looping, actually working — is the thing that turns a slow update into a PC that won't boot at all. That's why "confirm no disk activity first" isn't a throwaway line in this article; skipping it is the single most common way people create a worse problem than the one they started with.
When Startup Repair asks for a BitLocker key you don't have
Since Windows 11 24H2, Device Encryption has been enabled by default on clean installs and new PCs, and Home edition users get it automatically even though they never see "BitLocker" as a name for it anywhere in the interface. That means a lot of people hit this recovery-key prompt with no idea they were ever encrypted in the first place.
The recovery key isn't stored on the PC — that would defeat the point of encryption — it's saved to the Microsoft account tied to the device. You can retrieve it from another device or phone by going to aka.ms/myrecoverykey and signing in with that same Microsoft account. If you genuinely can't find or access that account, we've written a full walkthrough on locating and using the key after an update: recovering your BitLocker key after a Windows update.
Be honest with yourself here: if you don't know the Microsoft account the PC is signed into, and you don't have access to it on any other device, Startup Repair and several of the WinRE recovery tools genuinely will not proceed past that prompt. That's not a bug to work around — it's encryption doing exactly what it's designed to do.
Uninstalling the update that's causing this
If the PC boots normally but the same update fails every single time you try it, the cause is usually the update itself — a driver conflict, a corrupted download, or a package that simply doesn't like something specific about that machine. Removing the update lets you use the PC again while you wait for a corrected version.
From a working desktop:
- Press Win + R, type
appwiz.cpl, and press Enter to open Programs and Features. - Select View installed updates in the left sidebar.
- Find the update that failed (check the date — it should match when the problem started), right-click it, and choose Uninstall.
- Restart the PC once the removal finishes.
From WinRE, if the PC won't boot far enough to reach the desktop: go to Troubleshoot > Advanced options > Uninstall Updates, and choose either the most recent quality update or, if the failure started with a feature update, the feature update option. This is a separate tool from Startup Repair and doesn't require the same troubleshooting attempts first.
✅ Why this is the one to reach for before a reset
Uninstalling the update keeps every file, app, and setting on the PC intact and takes minutes. A reset takes much longer and, even with "keep my files" selected, removes every installed program — Jake's point-of-sale software and receipt printer drivers included.
Reset this PC and clean reinstall — the last resort
If none of the above resolves it, Windows 11 offers a middle option before a full clean install: Settings > System > Recovery > Fix problems using Windows Update, then select Reinstall now. This downloads and reapplies a repair version of your last successfully installed update, targeting the specific system files and components involved, rather than wiping the whole drive. Keep the PC on power and connected to the internet the entire time.
If that also fails, or the corruption is too extensive for it to work, a clean installation using the media creation tool from Microsoft's software download page is the final option. It resolves essentially any software-level cause of this problem, because it starts over completely.
⚠️ What this actually breaks
"Reset this PC," even with "keep my personal files" selected, removes every installed application, and a clean install removes everything on the drive, personal files included. Back up documents, photos, and anything irreplaceable to a USB drive or cloud storage before you run either one — not after.
Windows 10: the same fixes, a different clock
Every fix above works the same way on Windows 10: force restart once, reset the Windows Update components with the same six commands, run DISM and SFC, uninstall the offending update, and use WinRE's Startup Repair for a loop. The menu paths differ slightly — Windows 10's update settings live under Settings > Update & Security > Windows Update rather than Windows 11's Settings > Windows Update — but nothing about the underlying process changes.
What's changed is the context you're troubleshooting in. Windows 10 reached the end of its support life on October 14, 2025. It still boots, still activates, and still runs — but without enrolling in Extended Security Updates (ESU), a device that's now stuck on a failing update is stuck without a safety net of ongoing security patches behind it.
🕐 What changed with consumer ESU
- Before: consumer ESU enrollment covered security updates through October 2026, one year past end of support.
- Now: Microsoft extended consumer ESU coverage by an additional year, running through October 2027 for enrolled devices, and enrollment was still open as of August 2026.
- What that means: if a Windows 10 PC is otherwise healthy and just fighting a bad update, ESU enrollment is worth doing before you reach for a clean install, not after.
To enroll, go to Settings > Update & Security > Windows Update and look for the "Enroll now" option; it requires the PC to be on version 22H2 and signed in with a Microsoft account rather than a local account. Enrollment is free if you sync your settings through Windows Backup, costs 1,000 Microsoft Rewards points, or is a one-time roughly $30 purchase, and covers up to 10 devices under one account.
One Windows 10-specific EOL note: if this stuck update is the update that would have moved you to Windows 11, and the PC meets Windows 11's requirements, that's a genuinely reasonable moment to stop fighting the Windows 10 install and move on instead, rather than repeatedly patching an operating system that's past its support window.
| Detail | Windows 11 | Windows 10 |
|---|---|---|
| Where to find Windows Update | Settings > Windows Update | Settings > Update & Security > Windows Update |
| Reset update components commands | Identical six commands | Identical six commands |
| Reaching WinRE via forced shutdowns | Same three-shutdown trigger | Same three-shutdown trigger |
| Security updates if this drags on unresolved | Continue as normal, in active support | Stopped unless enrolled in ESU; enrollment covers through October 2027 |
| Device Encryption default | On by default on many 24H2 clean installs, including Home | Not default the same way; varies by device and OEM setup |
Why this keeps happening
A handful of causes account for nearly every stalled or looping update: an interrupted download from a flaky connection, corrupted files sitting in the update cache, a driver — usually network or graphics — that the update doesn't get along with, not enough free disk space to complete the install, or simply an update that's large and legitimately slow on older hardware.
Large cumulative updates raise the odds of hitting this simply because there's more to go wrong. We covered one recent example in detail in our writeup of the August 2026 Windows 11 cumulative update, KB5121003 — worth a look if your stall started right around when that one shipped, since matching the timing to a known update is often the fastest way to confirm you're not dealing with something unique to your machine.
Is my drive dying?
It's worth ruling out. From an administrator Command Prompt, run chkdsk /f C:, which schedules a check and repair on the next restart. A drive with genuine hardware errors will surface them here; a drive that's simply slow or a PC that's simply older won't — that's a performance ceiling, not a fault to fix.
Do you need a third-party "update repair" tool?
Ethan's opinion here is short: "No. Every one of those tools is running some combination of the same steps in this article — clearing the update cache, running the troubleshooter, checking disk space — wrapped in a paid interface. You already have all of it built in for free."
Where third-party tools sometimes get pitched alongside this specific problem is data recovery, on the theory that a stuck update might have already cost you files. If you're at that point — the PC won't boot at all and you need to pull files off the drive before you try anything else — that's a real use case for recovery software, but it's a separate problem from the update being stuck, and it only applies once boot has actually failed, not while the update screen is simply sitting there.
Preventing this next time
Set Active hours (Settings > Windows Update > Advanced options > Active hours) so Windows never picks the exact moment you need the PC to restart and install updates. Keep at least 20 GB of drive space free on an ongoing basis, not just when an update is pending. And install updates when you actually have time to sit through a restart — not five minutes before you need to close out a sale or join a call, since that's exactly the situation that turns a routine wait into a forced, risky shutdown.
Frequently asked questions
How long should I wait before doing anything?
There's no fixed number of hours. Watch for disk activity instead of the clock: if the drive light is blinking and the fan is running, it's still working. No activity across repeated checks over a long stretch is your signal to move on to the fix steps.
Is it safe to force restart during "Working on updates 100% complete"?
It's reasonable to do once, and only after you've confirmed there's no disk activity. It's not safe to do repeatedly, or the moment the screen appears, since interrupting an update that's genuinely still writing files is what causes real boot failures.
Will I lose my files if I force restart?
A single force restart, done after confirming there's no disk activity, is unlikely to touch your personal files. The steps that carry real file risk are further down the list: Reset this PC and a clean install. Back up before those two regardless.
What if force restart doesn't get me back to the login screen?
That's a restart loop, not a stall, and it needs the WinRE steps: force shutdown three times in a row to trigger the recovery environment automatically, then run Startup Repair.
Is stuck at 0% the same problem as stuck at 100%?
The likely cause differs slightly — 0% often points to a download or connectivity issue, while 100% often means the install itself has hung — but the fix order is the same. Start by confirming disk activity, then work down the same list.
Is stuck on download different from stuck on install?
Yes, in cause but not in fix. A download stall usually traces back to your internet connection; an install stall usually traces back to disk space, corrupted cache files, or a driver conflict. Both respond to resetting the Windows Update components, so it's a reasonable first manual step either way.
My PC keeps restarting into the exact same "Working on updates" screen. What now?
That's a genuine loop. Stop waiting between reboots and go straight to WinRE: three forced shutdowns in a row to trigger it automatically, then Troubleshoot > Advanced options > Startup Repair.
Do I need my BitLocker recovery key?
Only if the device is encrypted, which is the default on many Windows 11 24H2 clean installs and new PCs even on Home edition. WinRE will ask for it before certain repair tools can proceed. Find it at aka.ms/myrecoverykey using the Microsoft account tied to the device.
What if I don't have my BitLocker key or access to the Microsoft account?
Then several WinRE repair paths genuinely will not proceed past that prompt. That's encryption working as intended, not a bug. Your options at that point are recovering account access first, or moving to Reset this PC only if you're prepared to lose data that isn't backed up elsewhere.
Can I skip or permanently avoid this specific update?
You can uninstall it once it's failed, and Windows Update will generally offer it again on its next check unless the underlying cause is fixed. There's no supported way to permanently block one specific update while staying current on everything else through the normal Windows Update mechanism.
Is my drive dying, or is this a normal update problem?
Run chkdsk /f C: from an administrator Command Prompt to check. If it comes back clean, this is a normal, common update problem, not a hardware failure.
Should I use a third-party "PC repair" or "update fix" tool?
Generally, no. Every legitimate fix these tools apply is a built-in Windows feature covered in this article, free, and without a paid wrapper around it.
What if Startup Repair says it couldn't repair the PC?
Run it again — it's normal for it to need two or three attempts, restarting between each. If it still fails after that, move to Uninstall Updates in WinRE, then the "Fix problems using Windows Update" reinstall option, then a clean install as the final step.
Is Windows 10 affected the same way as Windows 11?
The causes and fixes are the same; only the settings menu paths differ slightly. The added wrinkle on Windows 10 is that it's past end of support, so ESU enrollment status matters to how you prioritize fixing it versus moving on.
Should I enroll in ESU if this keeps happening on Windows 10?
If the PC is otherwise healthy and you plan to keep using Windows 10 for now, yes — consumer ESU enrollment (free with a Windows Backup sync, 1,000 Rewards points, or about $30) keeps security updates coming through October 2027 and was still open for enrollment as of August 2026.
How do I stop this from happening again?
Set Active hours so updates never restart the PC when you're mid-task, keep at least 20 GB of drive space free at all times, and install updates when you actually have time to sit through a restart rather than right before you need the machine.
Revision note. Written August 2026, covering Windows 11 latest and Windows 10 latest, including the post-end-of-support ESU extension through October 2027. This will need a refresh once Microsoft ships the next Windows 11 feature update or restructures ESU again. If you're reading this at 2 a.m. with a customer's laptop stuck on that screen, take a breath — in almost every case, the machine is fine, and you're going to get it back.