Windows 11 Update Failed to Install? Fix It (8 Methods)
—
If Windows Update keeps failing to install on Windows 11 or 10, the fix is almost always one of three things: free up disk space (Windows needs real breathing room to stage an update, especially a feature update), clear the update download cache in the SoftwareDistribution folder, or—if this is a Windows 10 machine—check whether it has quietly stopped receiving updates altogether because support for Windows 10 ended in October 2025 and the device was never enrolled in Extended Security Updates. Here's the part almost nobody expects: the update almost never fails because your PC is broken. In the years since we first wrote about a Windows 10 update failing, we've watched this exact problem stay the single most common thing readers write in about—and it is nearly always solved without reinstalling anything.
Which of these is happening to you?
Jake called it "the spinning circle of doom." Before you touch a single setting, figure out which of these you're actually looking at—the fix is different for each one.
If the update downloads, gets to a percentage, and then throws an error code and rolls back—that's a failed install, and it's almost always disk space or a corrupted cache file. If it downloads, sits at one percentage for hours with the fan silent and no disk activity—that's a hung install, and it needs a service restart, not more patience. If Windows Update simply says you're up to date when you know you aren't, or won't offer a feature update at all—that's an eligibility block, usually hardware requirements on Windows 11 or an expired support window on Windows 10. Keep that distinction in mind; we'll come back to it in every section below.
♂️ Jake's Reality Check
"A customer brought in a laptop that had been stuck at 47% since the night before. He was convinced the update had wrecked the drive. I almost told him to back up and reinstall Windows."
It was full. 1.2 GB free on a drive that needed room to stage a feature update. Fifteen minutes of deleting old downloads and it finished on its own. No reinstall, no data loss, no charge to the customer — and that's the visit Jake tells people about, because it cost him nothing and saved the relationship.
Fixing failed updates on Windows 11
Work through these in order. Most people are fixed by step two or three and never need to reach the repair commands.
Step 1: Free up real disk space
Open Settings (press Win + I, the shortcut that opens the Settings app directly instead of digging through the Start menu), then go to System → Storage. Windows will show you what's eating the drive. Look at Temporary files first—this is a safe bucket to clear and often reclaims several gigabytes on its own.
A monthly cumulative update needs modest headroom. A feature update (a whole new build of Windows, not just a patch) is a different story—Windows briefly keeps a copy of your current system alongside the incoming one while it swaps over, so it wants meaningfully more room. Give it at least 20 GB free before you try again. If you're close to full, an external drive or a quick move of large media files to cloud storage is often the fastest unblock, and it's honestly not a bad habit for a machine that's chronically tight on space regardless of updates.
⚠️ What this actually breaks
Don't use "storage sense" auto-cleanup or a third-party cleaner mid-update. If Windows is actively partway through staging files, deleting things out from under it can turn a recoverable stuck update into one that needs a repair install. Free space up first, then start (or retry) the update — not while it's already running.
Step 2: Clear the SoftwareDistribution download cache
This is the fix that solves a corrupted download, which is the second most common cause after disk space. Windows Update keeps the files it downloads in a folder before installing them; if that download gets interrupted or corrupted, Update will keep trying to install the same broken files and keep failing the same way.
Press Win + R to open the Run box—a small dialog that lets you launch a program or open a folder by typing its name directly, faster than clicking through File Explorer. Type services.msc and press Enter. Find Windows Update in the list, right-click it, and choose Stop. Do the same for Background Intelligent Transfer Service (BITS)—this is the service that actually handles the download in the background, and it needs to let go of the files too.
With both stopped, open File Explorer and go to C:\Windows\SoftwareDistribution\Download. Select everything inside that Download folder (not the SoftwareDistribution folder itself) and delete it. This only removes already-downloaded update files—none of your personal files, installed programs, or settings live here, so there's nothing to back up first.
Go back to services.msc, right-click Windows Update and BITS again, and choose Start. Reopen Settings → Windows Update and check for updates again. Windows redownloads the update fresh, and a fresh download fixes a corrupted one almost every time.
✅ Why this is the one to use first
It's reversible, it touches nothing but a download cache, and it fixes both the "stuck at a percentage" hang and the "downloads then errors out" failure. Reach for the disk cleanup and DISM steps only if this doesn't clear it.
Step 3: Run the built-in Windows Update Troubleshooter
Settings → System → Troubleshoot → Other troubleshooters → find Windows Update in the list and run it. It automates a version of the same checks in this guide—service state, corrupted files, pending restarts—and will apply straightforward fixes on its own. It won't catch everything, but it's worth a couple of minutes before you move to manual repair commands.
Step 4: Repair system files with DISM and SFC
If the update still fails after clearing the cache, the problem may be a corrupted system file, not the download. Open Command Prompt as administrator (right-click the Start button, or search "cmd" and choose Run as administrator) and run:
DISM /Online /Cleanup-Image /RestoreHealth
Let it finish—it can take fifteen to thirty minutes and will sit at certain percentages for a while, which is normal for this specific command, unlike a genuinely hung update. Once it completes, run:
sfc /scannow
This checks protected system files against known-good versions and repairs anything DISM's repair made available. Restart the PC, then try the update again.
What changed since we first wrote this
- Then: back in 2017, forcing a Windows 10 feature update onto a PC that hadn't been offered it yet meant creating an OSUpgrade registry key by hand—a workaround for how Microsoft staggered that specific rollout.
- Now: Windows Update no longer works that way. Feature updates are offered based on hardware eligibility and rollout pacing that you can't unlock with a registry key, and Microsoft has closed most of the old bypass tricks entirely.
- What that means for you: if Windows Update won't offer a feature update, the cause today is almost always eligibility (see the box below), not a rollout you need to force your way into.
Step 5: Check whether your PC is actually eligible
Sometimes "Windows Update won't install" really means "Windows Update won't offer it in the first place," and that's a different problem entirely. Windows 11 checks hardware before it lets a feature update through: TPM 2.0 (the security chip Windows uses to protect encryption keys—most PCs from the last several years have it built into the firmware, called fTPM or PTT, even if it's switched off by default), a CPU from Microsoft's approved list, UEFI firmware with Secure Boot support, and on newer builds specifically, CPU instruction support (POPCNT and SSE4.2) that only very old processors lack.
If any one of those is missing, Windows Update will quietly decline to offer the feature update rather than downloading it and failing partway through. That's worth knowing, because it changes what you're actually troubleshooting—there's nothing to "fix" in the update process itself if the hardware simply isn't on the list.
You don't have to guess which box is unchecked. Press Win + R, type tpm.msc, and press Enter to see your TPM version directly. For Secure Boot, run msinfo32 the same way and look for "Secure Boot State" under System Summary—it will say On, Off, or Unsupported. Microsoft's free PC Health Check app checks all of this in one pass and, when a PC doesn't qualify, tells you plainly which specific requirement it's failing rather than leaving you to guess.
♂️ Jake's Reality Check
"So you're telling me the update isn't broken, my computer just isn't good enough anymore?"
Basically, yes. Ethan's answer to that is blunt: there's no setting that fixes a missing security chip. If your PC is right at that edge, it's worth knowing sooner rather than later, especially with Windows 10's support window already closed and the clock now running on how much longer the current Windows 11 version you're on stays serviced.
A Windows 11 trap worth knowing about
People go looking for the Windows Update troubleshooter in Control Panel out of habit, since that's where it used to live. Control Panel still exists in Windows 11—you can still open it and find things like advanced power plans there—but most day-to-day settings, including update troubleshooting, moved into the Settings app years ago. If a walkthrough you find elsewhere tells you to open Control Panel for this, it's describing an older version of Windows; go through Settings → System → Troubleshoot instead.
Fixing failed updates on Windows 10
Everything in Step 1 through Step 4 above works exactly the same way on Windows 10—the disk space check, the SoftwareDistribution cache clear, the DISM and SFC commands, all identical. There's no need to repeat those steps here. What's different on Windows 10 is a fact that changes the whole picture: Windows 10 reached the end of its support life on October 14, 2025. That's not a warning label, it's the actual reason a lot of Windows 10 update failures happen at all in 2026.
Check whether your PC is even enrolled for updates anymore
Since the support cutoff, Windows 10 22H2 no longer receives free security updates unless the device is enrolled in Extended Security Updates (ESU), a paid-or-free continuation program. Go to Settings → Windows Update and look for an Enroll now option. You'll need the 22H2 update already installed and to be signed in with a Microsoft account—a local account won't let you enroll.
Enrollment costs nothing if you turn on Windows Backup to sync your settings, or you can redeem 1,000 Microsoft Rewards points instead, or pay a one-time fee around $30 (pricing varies a little by region, and some regions get it free without the backup requirement). One Microsoft account covers up to 10 devices. As of mid-2026, Microsoft extended the consumer ESU program by an extra year, so enrolled devices are covered through October 2027, and enrollment itself is still open—you haven't missed the window if you're only finding this out now.
If Windows Update on a Windows 10 machine has simply stopped finding anything to install, or errors out every time, checking enrollment status is worth doing before anything else in this guide. A device that isn't enrolled and is past the cutoff genuinely has nothing new to offer it outside of ESU coverage, and no cache clear or repair command changes that.
What changed since we first wrote this
- Then: in 2017, Windows 10 was brand new and every reader on this page was fighting to get the latest feature update to land.
- Now: Windows 10 itself is the thing winding down. The update problem has flipped from "how do I get the newest version" to "is this machine even eligible for updates at all anymore."
- What that means: if you're on Windows 10 and none of the technical fixes above change anything, ESU enrollment status is likely the real answer, not a bug.
♂️ Jake's Reality Check
"A regular came in furious that his 'update was broken.' He'd been ignoring the Windows 10 support-ending notices for months and just assumed Windows Update itself had a bug."
It didn't. His machine was fully capable of running Windows 11, and the honest advice Ethan gave him was to stop patching around a Windows 10 install he'd have to keep paying to secure and put the free upgrade path to use instead, since his hardware qualified anyway.
When it's not actually the update's fault
A few situations get blamed on "Windows Update is broken" when the update is actually doing exactly what it's supposed to.
It's just slow, not stuck
A feature update genuinely takes longer than the monthly patches most people are used to, because it's effectively installing a new build of Windows on top of the old one. If there's still disk activity, if the percentage has moved at all in the last hour, or if it's a laptop that's been asleep rather than plugged in and actively working—give it real time before assuming it's frozen. Overnight, plugged in, is the honest advice here, not a countdown.
Third-party antivirus is interfering
Security software that hooks deeply into the system—some third-party antivirus suites do this more aggressively than others—can block or slow the file operations an update needs mid-install. If updates fail specifically and repeatedly on a machine running non-Microsoft antivirus, temporarily disabling real-time protection for the duration of a single update attempt (then turning it back on immediately after) is a reasonable diagnostic step, not a long-term habit.
A pending restart is blocking everything behind it
If a previous update installed but never got the restart it needed, later updates can queue up behind it and appear to fail when they're really just waiting. Restart the PC on its own, outside of any update attempt, before troubleshooting further—it costs nothing and clears this specific case immediately.
The bad advice you'll find elsewhere
Two pieces of "advice" show up constantly in forum threads on this exact problem, and both are wrong. The first is turning off Windows Update permanently through Group Policy or a registry tweak so the errors stop appearing. Ethan's opinion on that one is blunt: "That's not a fix, that's covering the smoke detector." It silences the symptom while quietly leaving the PC without security patches, and it usually just delays a bigger, harder update down the line instead of avoiding it. The second is disabling antivirus entirely and leaving it off, rather than just pausing it for a single update attempt as described above. Neither of those addresses disk space, a corrupted cache, or eligibility—the actual three causes—so neither one is doing anything except removing a safeguard.
If nothing above works: repair install or reset
Most people never need to reach this section. If the fixes above haven't cleared it after a genuine attempt at each one, here's the order to escalate in—least drastic first.
In-place repair install
This reinstalls Windows over itself using the Windows 11 (or 10) Installation Assistant or a downloaded ISO you mount and run setup.exe from, while keeping your files, apps, and settings in place. It resolves corruption that DISM and SFC can't reach, because it replaces the entire system image rather than patching pieces of it. It takes longer than the steps above—usually an hour or more—but it's the strongest fix short of starting over, and for most stubborn cases it's the one that finally works.
Reset this PC
Settings → System → Recovery → Reset this PC, with the option to keep your personal files. This is more aggressive than a repair install—it removes installed programs and most settings, though your documents, photos, and other personal files stay. Use this only after a repair install hasn't worked, since it costs you your installed software and you'll need to set those back up.
⚠️ What this actually breaks
"Keep my files" genuinely keeps your personal files in nearly every case, but it is not a substitute for a real backup, and it removes every installed program along with any settings tied to them. Before you run a reset, back up anything you can't easily redownload or reinstall to an external drive or cloud storage—treat the "keep my files" promise as a safety net, not a reason to skip backing up.
Laptops, VMs, and other setups that behave differently
Not every PC in Jake's shop is a standard desktop, and updates behave a little differently depending on the hardware and setup.
Laptops with small SSDs. Budget laptops with 128 GB or 256 GB drives run into the disk-space cause far more often than desktops with roomy storage, simply because there's less slack to begin with. These are the machines where Step 1 above matters most, and where it's worth checking storage before a feature update even starts rather than after it fails.
Virtual machines. A VM update failure is very often a resource problem, not a Windows problem—check that the VM has enough allocated disk space and RAM for the host, since a feature update inside a VM needs the same headroom a physical machine does, and a thin-provisioned virtual disk that's actually full on the host will fail an update the same way a full physical drive does.
Remote Desktop sessions. Feature updates generally shouldn't be run over an active Remote Desktop connection to the machine being updated—the update process needs to restart the machine, which will drop your session mid-install. If you manage machines remotely, trigger the update and then disconnect, checking back after the expected restart rather than staying connected through it.
Multi-monitor and docking station setups. A PC docked to two or three external displays can look "frozen" during an update restart simply because the monitors take longer to wake than the built-in laptop screen does—the PC may already be back up and waiting at the sign-in screen behind a dark external monitor. Before assuming a hang, undock the laptop or check its own screen directly.
Tablets and 2-in-1 devices without a keyboard attached. The touch keyboard can be slow to appear during certain update screens that expect a physical keyboard for troubleshooting prompts. If a repair step in this guide calls for typing a command and there's no visible way to bring up the keyboard, tapping the text field directly usually summons it; if it doesn't, connecting a keyboard temporarily is the fastest way past that specific screen.
If you manage more than one PC: automate it
Jake keeps a handful of shop machines and a couple of loaner laptops, and running through Step 2 by hand on each one gets old fast. A short script saves the repetitive part. From an administrator PowerShell window:
net stop wuauserv
net stop bits
Remove-Item -Path "$env:windir\SoftwareDistribution\Download\*" -Recurse -Force
net start wuauserv
net start bits
That's the manual cache-clear from Step 2, in five lines instead of five separate menu trips. Save it as a .ps1 file and it becomes a one-click first move whenever an update stalls—run it, then check for updates again. It doesn't replace the disk-space check or the eligibility check, but it removes the most tedious repair step from the rotation.
One thing to check before you trust an "update fix" tool
A failed update is exactly the kind of frustrating, urgent-feeling problem that scam software targets. If a search for "fix Windows Update" leads you to a downloadable "repair tool" that asks for payment before it will actually fix anything, or that wants broad system permissions up front, treat it with real suspicion. Everything in this guide uses tools already built into Windows—Settings, Command Prompt, PowerShell—and none of it requires installing anything new or handing over payment details to a program you've never heard of.
✅ Why this is the one to use
Ethan's take on third-party "Windows fixer" utilities is unambiguous: "If it's not something Microsoft built or something you can type into Command Prompt yourself, I don't trust it near a system-level process." The built-in troubleshooter and the manual steps above cover the same ground without the risk.
Method comparison
| Method | Works on Home? | Use it when |
|---|---|---|
| Free up disk space | Yes | Always try this first, especially before a feature update |
| Clear SoftwareDistribution cache | Yes | Update downloads then errors out, or hangs at a percentage |
| Windows Update Troubleshooter | Yes | You want an automated first pass before manual steps |
| DISM + SFC repair | Yes | Cache clear didn't fix it — suspected system file corruption |
| Check ESU enrollment (Windows 10) | Yes | Windows 10, past October 2025, nothing else changes the result |
| Check hardware eligibility (Windows 11) | Yes | Feature update never gets offered at all, not just fails |
| In-place repair install | Yes | Everything above failed and it's likely system file corruption |
| Reset this PC | Yes | A repair install didn't fix it and you've backed up first |
Frequently asked questions
Why does Windows Update keep failing to install?
Most of the time it's one of three things: not enough free disk space to stage the update, a corrupted download sitting in the update cache, or—on Windows 10—the device no longer being enrolled for updates at all now that support has ended. Fewer failures than people assume trace back to a genuinely broken PC.
How much free space does Windows actually need to install an update?
A monthly cumulative update needs modest room. A full feature update wants considerably more, since Windows briefly keeps both the old and new system files during the swap—aim for at least 20 GB free before starting one.
Is it safe to delete the SoftwareDistribution folder?
Yes. It only holds already-downloaded update files, not your personal data or installed programs. Clearing the Download subfolder forces a fresh redownload, which fixes a corrupted file without touching anything of yours.
What does error 0x80070070 mean on Windows Update?
It means Windows doesn't have enough free disk space to complete the operation—one of the oldest, most stable error codes in Windows, and it means exactly what it says. Free up space and retry.
Why did my Windows 10 PC stop getting updates in 2026?
Windows 10 support ended on October 14, 2025. Without ESU enrollment, the device no longer receives security updates, and Windows Update may show nothing to install or fail when it tries.
How do I enroll in Windows 10 ESU?
Settings → Windows Update → Enroll now. You need 22H2 installed and a Microsoft account signed in—not a local account. One account covers up to 10 devices, and as of mid-2026 coverage runs through October 2027.
Does Windows 10 ESU cost money?
It can be free if you sync settings through Windows Backup, or you can redeem 1,000 Microsoft Rewards points, or pay a one-time fee around $30. Businesses use a separate paid commercial program.
Why won't my PC upgrade to Windows 11 even though I click Update?
Windows 11 checks hardware eligibility first: TPM 2.0, an approved CPU, UEFI with Secure Boot, and on newer builds, specific CPU instruction support. If any is missing, the feature update simply won't be offered.
How do I check if my PC has TPM 2.0 and Secure Boot enabled?
Run tpm.msc from the Run box (Win + R) to see your TPM version, and msinfo32 the same way to check "Secure Boot State" under System Summary. Microsoft's free PC Health Check app checks both at once and names the exact requirement you're failing, if any.
My update gets stuck at a percentage and never moves. What now?
Give it real time first, especially overnight while plugged in—large updates can hold at one percentage for a long stretch while working. If it's genuinely frozen for hours with zero disk activity, restart and clear the update cache.
Should I use a third-party Windows Update fixer tool?
Generally no. The built-in troubleshooter and the manual steps above cover the same ground most paid or free fixer tools claim to, without adding another program that needs its own permissions and updates.
Is it safe to permanently disable Windows Update?
No. It stops the errors from showing, but it also stops security patches, and a PC that goes long enough without them becomes a real risk—plus it usually just delays a bigger, harder update rather than avoiding one. Fixing the actual cause is better than muting the symptom.
What is the last resort if nothing fixes a failing update?
An in-place repair install using the Windows Installation Assistant or a mounted ISO reinstalls Windows over itself while keeping your files, apps, and settings. It resolves corruption that DISM and SFC can't reach, and it's a safer last resort than a full reset or clean install.
Can a failed update damage my files?
A failed install typically rolls back cleanly on its own. The real risk is a forced shutdown mid-update—never cut power to a PC that's mid-install, even if it looks frozen.
Do I need to run SFC and DISM every time an update fails?
No. Try disk space and the cache clear first. Reach for DISM and SFC when those don't work, since they fix deeper system file corruption a cache clear can't touch.
Will restarting the Windows Update service fix a stuck update?
Often, yes. Restarting the Windows Update service and BITS forces a hung process to let go and start clean—one of the most reliable fixes for an update that hangs rather than errors immediately.
Is it normal for Windows 11 updates to take longer than Windows 10 did?
Feature updates can take noticeably longer than the monthly patches most people are used to, since a feature update effectively installs a new build of Windows on top of the old one. A long install time on its own isn't a failure.
Error 0x800f0922 — EFI Partition Space Issue (May–August 2026)
If your update fails at around 35% with error
0x800f0922, this is a known Microsoft-confirmed issue — not a problem with your PC. The cause is insufficient free space on the EFI System Partition (a small hidden boot partition most users never see). Devices with 10 MB or less free space are most likely to hit this. The fix for most users is simply installing the optional update KB5089573 via Windows Update, which Microsoft released on May 26, 2026 specifically to resolve this. If your update keeps failing even after that, open an elevated Command Prompt and run:dism /online /remove-package /packagename:Package_for_RollupFix~31bf3856ad364e35~amd64~~26100.1742.1.10— then retry Windows Update. The same EFI space issue has also been reported with the August 2026 update (KB5121003), so the same fixes apply.
Revision note. Originally published March 30, 2017, covering a registry workaround for that year's Windows 10 Creators Update rollout. Rewritten August 14, 2026 for Windows 11 and Windows 10. The specific fix has moved on—Microsoft closed the old registry bypass years ago, and the update mechanism itself works very differently now—but the underlying problem readers keep landing here for, an update that simply won't finish installing, hasn't gone anywhere. If you're staring at a stuck progress bar right now, take a breath: it's very likely a full disk or a bad download, not a broken computer, and either one is fixable tonight.