Windows Update Not Working? Troubleshoot Any Update Error

If Windows Update is stuck, stuck at a percentage, or fails and restarts every time, the fix in almost every case is the same: run the built-in Windows Update troubleshooter first, then restart the Windows Update service, then clear the SoftwareDistribution folder if it keeps re-downloading from zero, and treat DISM and SFC as the next step if the update itself, not just the service, looks damaged. Here's the part most guides skip: the single most common move people make when an update looks frozen -- force-restarting the PC -- is often the exact thing that turns a slow update into a genuinely broken one, because a normal install and a frozen one can look identical for 20 to 40 minutes, and the only honest way to tell them apart is to wait and watch the disk activity light, not the percentage.

Which update problem do you actually have?

Jake runs a small phone and computer repair shop, and the week before he messaged me about this, he'd told a customer to come back the next day because "the update was stuck." It wasn't stuck. It was 34 minutes into a Windows 11 feature update, the percentage hadn't moved because it was mid-way through a driver swap, and the customer's laptop was fine the whole time. The shop lost a walk-in sale over a PC that needed nothing but ten more minutes.

That's the split worth making before you touch anything:

• The percentage hasn't moved, but the disk activity light is still blinking. This is a working update. Leave it. Large updates commonly sit at a number for 20 to 40 minutes during a driver install or a "Working on updates" restart.
• The percentage hasn't moved for over an hour and the disk light is dark. This is genuinely stuck. Go to the Windows 11 or Windows 10 section below.
• The update downloads, fails, and starts over from 0% every time. Skip straight to clearing SoftwareDistribution.
• You have a specific error code on screen. Jump to what the common codes mean.
• The troubleshooter says "no problems found" but updates still won't install. Go straight to DISM and SFC — that's a system file problem, not an update service problem.

Fixing Windows Update problems in Windows 11

Windows 11's current mainstream version is 25H2, and these fixes apply whether you're on 25H2 or the older but still-serviced 24H2. The steps themselves are simple; the friction is almost always finding where Windows 11 moved the setting.

Method 1: Run the Windows Update troubleshooter

Go to Settings (Win + I) > System > Troubleshoot > Other troubleshooters, then find Windows Update in the list and select Run. This is the built-in tool Microsoft ships specifically for this problem: it restarts the Windows Update service and everything that depends on it, resets the transfer queue that downloads sit in, clears out any download data that got corrupted mid-transfer, and checks the update database for damage. It doesn't touch your files or installed programs.

Run this first, every time, before anything more involved. It fixes the majority of routine stuck-or-failing updates on its own, and it's the safest possible starting point because there's nothing here that can make things worse.

Method 2: Restart the Windows Update service manually

If the troubleshooter didn't fix it, the next step is restarting the Windows Update service (its internal name is wuauserv) directly. Open the Start menu, type PowerShell, then right-click it and choose Run as administrator — Windows will ask for confirmation through a User Account Control prompt, which you accept. PowerShell itself is just a command-line window; typing a line of text into it and pressing Enter runs that command instantly, the same way clicking a button does, just without the button.

Type this and press Enter:

Restart-Service wuauserv

It runs silently with no confirmation message if it worked. Close PowerShell, reopen Windows Update, and select Check for updates again. This clears out a service that's gotten wedged into a bad state without touching any downloaded files, which is why it's worth trying on its own before the more disruptive step of deleting the download folder.

Method 3: Clear the SoftwareDistribution download folder

This is the fix for one specific symptom: an update that downloads, fails, and restarts the download from 0% every single time. It's not a general first move — it deletes Windows' cached download data, so if you use it when that's not the actual problem, all you've done is force a bigger re-download for nothing.

1. Open File Explorer (the Win + E shortcut, or the folder icon on the taskbar).
2. In the address bar, go to C: > Windows > SoftwareDistribution > Download.
3. Select everything inside that Download folder (Ctrl + A) and delete it (Shift + Delete to skip the Recycle Bin, or just Delete).
4. Restart your PC and check for updates again.

If Windows won't let you delete some of the files because they're "in use," that means the Windows Update service is still holding onto them — stop it first from an administrator PowerShell window with Stop-Service wuauserv, delete the files, then start it again with Start-Service wuauserv.

Method 4: Run DISM and SFC when it's a system file problem, not a service problem

If the troubleshooter reports no problems, the service restart didn't help, and clearing the download folder didn't help either, the fault usually isn't Windows Update at all — it's damage to the underlying Windows system files that updates rely on. That's a job for two different tools used in sequence.

From an administrator PowerShell or Command Prompt window, run these one at a time, letting each finish before starting the next:

DISM /Online /Cleanup-Image /RestoreHealth

DISM stands for Deployment Image Servicing and Management. This command checks Windows' own core files against a known-good copy (pulled from Windows Update itself, which is why it needs a working internet connection) and repairs anything damaged. It can take 10 to 20 minutes and will appear to pause at certain percentages — that's normal, not a second stuck update.

Once DISM finishes, run:

sfc /scannow

SFC (System File Checker) scans protected system files individually and replaces any damaged ones using the source DISM just repaired. Running SFC before DISM is a common mistake — SFC has nothing good to copy from yet, so it often reports it "could not fix all found corruptions." DISM first, SFC second, in that order.

Method 5: The full manual reset, for when the individual fixes above don't stick

Occasionally none of the individual steps above hold on their own — the service restarts fine, but the same download fails again an hour later. When that happens, it's usually because several of the pieces the earlier methods each touch separately are all in a bad state at once: the update service, the download queue, and the certificate store Windows Update relies on to verify signed files. This method resets all three together, in order, from an administrator PowerShell window.

1. Stop the three services involved: Stop-Service wuauserv, bits, cryptsvc
2. Rename the download folder so Windows rebuilds it fresh: in File Explorer, go to C:\Windows\SoftwareDistribution and rename the folder itself to SoftwareDistribution.old (not just the Download subfolder inside it, as in Method 3 — the whole folder this time).
3. Rename the certificate cache the same way: go to C:\Windows\System32\catroot2 and rename it to catroot2.old.
4. Restart the same three services: Start-Service wuauserv, bits, cryptsvc
5. Restart the PC and check for updates. Windows rebuilds both folders automatically the first time it needs them, with no extra steps.

This is a heavier version of Method 3, not a replacement for it — try Method 3 first, and only reach for this if the same failure keeps recurring after a service restart. If Windows won't let you rename either folder because it's "in use," that confirms the services from step 1 weren't fully stopped; wait a few seconds after stopping them before renaming.

The Windows 11 traps that make this harder than it should be

Three things specific to Windows 11's redesign trip people up on this exact problem:

• File Explorer's default view is "Home," not "This PC." When these steps say open File Explorer and go to the C: drive, you may land on a Home screen showing pinned and recent files instead. Click "This PC" in the left sidebar first.
• The classic right-click menu is hidden. If you're trying to right-click a file in the SoftwareDistribution folder for an older-style option, Windows 11's condensed menu only shows a handful of icons by default — click Show more options (or press Shift + F10) to get the full menu back.
• Settings has been reorganized more than once. If a path in this guide doesn't match exactly what you see, search "Windows Update" directly in the Settings search box (top of the Settings window) — it's faster than hunting through menus that Microsoft periodically reshuffles.

Fixing Windows Update problems in Windows 10

Windows 10's free support ended on October 14, 2025. Windows 10 22H2 still runs, still updates its browser and Defender definitions, and the troubleshooting steps below work exactly the same as they always have — but it no longer receives free security patches, and that matters for a post specifically about keeping Windows Update healthy. If you're still on Windows 10, the ESU note near the end of this section is worth reading even if your immediate problem is a stuck update.

These steps are the same as Windows 11

The troubleshooter, the PowerShell service restart, clearing SoftwareDistribution, and running DISM and SFC are identical commands and identical folder paths on Windows 10. What's different is only where you click to start:

• Troubleshooter: Settings > Update & Security > Troubleshoot > Additional troubleshooters > Windows Update > Run the troubleshooter.
• PowerShell service restart: right-click the Start button (not Start itself) and choose Windows PowerShell (Admin), then run the same Restart-Service wuauserv command.
• SoftwareDistribution folder and DISM/SFC: identical paths and identical commands to Windows 11.

If you've read the Windows 11 section above, you already know how to fix this on Windows 10 — just start from Control Panel-style Settings instead of the redesigned one.

The honest Windows 10 end-of-support line

Windows 10 reaching end of support doesn't mean it stops working, and it doesn't mean Windows Update itself breaks. It means Microsoft stopped shipping free security patches for it as of October 14, 2025. If you want to keep getting those specifically, Microsoft's Consumer Extended Security Updates (ESU) program is still open for enrollment through Settings > Windows Update > Enroll now (you'll need to be on version 22H2 and signed in with a Microsoft account, not a local one). Enrollment is free if you turn on Windows Backup to sync your settings, costs 1,000 Microsoft Rewards points, or a one-time roughly $30, and — as of an extension Microsoft announced in June 2026 — coverage now runs through October 2027 instead of stopping a year after end of support.

None of that is required to fix a stuck or failing update today; it's a separate, longer-term decision about security patching. But if you're troubleshooting Windows Update on a Windows 10 machine anyway, it's worth checking whether you've enrolled.

What the common error codes actually mean

An error code narrows down which of the fixes above is worth trying first, instead of running through all of them in order.

If the troubleshooter already ran and reported the specific code as fixed but the update still fails on retry with the same code, that's the signal to move to DISM and SFC rather than repeating the troubleshooter a second or third time.

When the fix doesn't work: what that actually tells you

Every method above fixes something specific. When it doesn't work, the way it fails tells you what to try next.

The troubleshooter says "we couldn't automatically fix all issues"

This isn't a dead end, it's a diagnostic result. It means the service-level problems it can fix are cleared, but something deeper — usually system file corruption — is still there. Go straight to DISM and SFC rather than re-running the troubleshooter.

DISM fails with an error of its own

DISM needs a working path to good source files, normally Windows Update itself. If DISM fails, the most common cause is the same network or firewall block that produces the 0x8024xxxx codes above — check your connection before assuming DISM itself is broken.

The update installs, then rolls back at the very end with "we couldn't complete the updates, undoing changes"

This is almost always a driver or third-party software conflict discovered late in the install, not a corrupted download. Updating your drivers first (especially graphics and network drivers) and temporarily disabling third-party antivirus before retrying resolves this more often than repeating any of the earlier steps.

Nothing above works at all

At that point, an in-place repair install is the honest next step, not a fifth attempt at the same fixes. Download the Media Creation Tool from Microsoft, run it, and choose "Keep personal files and apps." It reinstalls Windows over your existing setup, rebuilding the update components from the ground up, while leaving your files, programs, and most settings in place. It takes longer than anything else in this guide — expect 30 minutes to over an hour — which is exactly why it belongs at the end of the list, not the start of it.

Laptops, VPNs, and other setups that change the answer

A handful of setups add a step none of the above covers on its own:

• Laptops on battery: some feature updates refuse to start, or pause partway, below a certain battery threshold or when not plugged in. Plug in before retrying a failed update, not just before starting one.
• Corporate VPN or a locked-down work network: these commonly block the ports and domains Windows Update needs, which shows up as a timeout-style error rather than an obvious "no internet" message. Disconnect the VPN and try on a different network before assuming the PC itself is at fault.
• Metered connections: Windows treats a connection marked as metered as a signal to hold back larger downloads to save data. Check Settings > Network & internet for your active connection and make sure it isn't set to metered if updates seem to sit without downloading at all.
• Remote desktop and virtual machines: updates that need a restart can get interrupted if the remote session or VM host restarts the connection mid-install. Where possible, apply updates from a direct console session rather than over remote desktop, and let a VM finish its restart cycle uninterrupted.
• Multiple monitors: not a common culprit, but a display driver update tied into a larger cumulative update occasionally causes one monitor to go black during the post-update restart. Give it two or three minutes before assuming it's failed; the display usually comes back once the driver finishes reinitializing.
• Dual-boot systems and extra internal drives: updates that need to modify the boot loader can behave oddly if a second operating system or an unusual partition layout is involved. If update failures started right after setting up dual-boot, that timing is the more likely cause than anything covered above — worth checking before spending time on DISM or SFC.

Popular advice that's wrong, or at least overkill

A few fixes keep circulating in forum threads and comment sections for this exact problem. Some are outdated, some are just aimed at the wrong symptom.

• "Permanently disable your antivirus." Third-party antivirus occasionally conflicts with an update mid-install, which is real — but the fix is disabling it temporarily for that one retry, not leaving your PC unprotected going forward. If you forget to turn it back on, you've traded a stuck update for a much bigger problem.
• "Reset the whole PC." A full reset (Settings > Recovery > Reset this PC) does rebuild Windows Update along with everything else, but it also removes every app you've installed and can take hours. Reach the in-place repair install covered above first — it fixes the same update components without removing your programs.
• "Turn off your firewall entirely." If a firewall is genuinely the cause of a 0x8024xxxx code, the fix is a temporary check or a specific rule, not leaving Windows Defender Firewall off. Most home routers and ISPs don't block Windows Update traffic at all, so this rarely applies outside corporate or school networks.
• "Just keep clicking Check for updates until it works." If the underlying cause is a network block, a full disk, or file corruption, repeating the same check changes nothing. It costs nothing to try once more after a genuine wait, but past that it's just delaying the actual fix.

Once updates are working again

Getting the current update to install is the immediate goal, but two follow-up checks catch problems before they turn into the same stuck-update headache again next month.

Check for optional and driver updates separately

Windows Update's main "Check for updates" button installs required cumulative and security updates automatically, but driver updates and less critical fixes usually sit under a separate "Optional updates" or "View optional updates" link on the same page. A graphics or network driver update sitting there unnoticed is a common cause of the next update's rollback-at-the-end failure covered above.

Read your Update history before you close this tab

Settings > Windows Update > Update history lists every update Windows has attempted recently, success or failure, each with its own status and date. If today's fix worked, it's worth a quick scroll to check nothing else has been silently failing in the background for weeks — a second update quietly stuck behind the one you just noticed is more common than it sounds, especially on a PC that hasn't been checked on in a while. If you ever need to uninstall a specific update that turns out to be the actual cause of a new problem, the "Uninstall updates" link at the top of that same page is where that lives, separate from anything covered above.

Keep some breathing room on your main drive

If freeing space was part of what got you here, it's worth staying above that line going forward rather than refilling the drive back to nearly full. A PC that's chronically low on space is one of the more common repeat customers for this exact problem, and it's also usually the moment Jake's customers ask about an SSD upgrade or an external drive for backups — a genuinely useful next step for anyone whose "stuck update" turns out to be a "no room left" update.

Automating the routine check with a scheduled script

For anyone comfortable with PowerShell and managing more than one machine, the DISM and SFC combination above can be wrapped into a short script and set to run monthly through Task Scheduler, so system file corruption gets caught before it turns into a failed update rather than after:

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

Save that as a .ps1 file, then create a monthly Task Scheduler entry that runs PowerShell with that script as an administrator. It's overkill for a single home PC, but genuinely useful for anyone maintaining several — including a repair shop bench running preventive checks between customer pickups.

One more thing worth a moment before you close this tab: only ever download the Windows Update troubleshooter or the Media Creation Tool from a microsoft.com link, never from a third-party mirror or a link in an unsolicited email — "update fixer" is one of the more common disguises for malware precisely because everyone eventually searches for it.

Two smaller privacy habits worth building into this routine while you're already in Settings. First, if you're posting a screenshot of an error code to a forum or sending it to someone for help (Jake does this constantly for customers), crop it to just the error itself — the full Windows Update screen often shows your device name and build number in the background, which is harmless on its own but adds up when it's sitting in a public thread indefinitely. Second, Settings > Privacy & security > Diagnostics & feedback controls how much usage data Windows sends back to Microsoft; it's unrelated to whether updates install, so there's no troubleshooting reason to change it one way or the other here, but it's a reasonable moment to glance at it since you're already in the Settings app for the update itself.

Frequently asked questions

Why does Windows Update get stuck at a percentage and just sit there?

Most of the time it isn't actually frozen. Windows writes progress in bursts, so the number on screen can hold still for 20 to 40 minutes during a large download or a driver install while real work continues in the background. It only counts as genuinely stuck once the percentage hasn't moved and the disk activity light has been idle for well over an hour.

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

Only once you've confirmed it's genuinely frozen using the check above. Force-restarting an update that's actually still installing is one of the more common causes of the rollback and corruption errors people then come back to fix, which is why it belongs at the end of the process, not the start of it.

What does the Windows Update troubleshooter actually fix?

It restarts the update service and everything it depends on, clears out corrupted download data, resets the transfer queue, and checks the update database for damage. It won't fix a bad internet connection or a full drive on its own, but it catches most routine failures without you needing to run a single command.

Do I need to delete the SoftwareDistribution folder every time an update fails?

No — save it for the specific symptom of an update that restarts its download from zero every attempt. If the problem is something else, clearing that folder just forces a bigger re-download without fixing anything extra.

What's the difference between fixing update problems in Windows 11 and Windows 10?

The actual fixes are identical: the same PowerShell command, the same folder path, the same DISM and SFC commands. What differs is only the click-path to reach the troubleshooter, since Windows 11 reorganized Settings and hid some legacy right-click options under "Show more options."

Can I still get help with Windows 10 updates now that Windows 10 has reached end of support?

Yes, for security patches specifically, through Microsoft's Consumer Extended Security Updates program, still open for enrollment via Settings > Windows Update. General bug fixes and feature updates have stopped regardless of ESU enrollment.

What is DISM and when should I use it instead of the troubleshooter?

DISM repairs Windows' own system image, which is a different layer than the update service. Use it when the troubleshooter finds nothing wrong but updates still fail, especially with corruption-related error codes.

What does SFC /scannow do and do I need it too?

It scans and repairs individual protected system files, using the source DISM just fixed. Run DISM first and SFC second — SFC on its own often can't fully repair what it finds.

Why does my update fail with a specific code like 0x80070002 or 0x8024402f?

0x8024xxxx codes point at a network or firewall block; 0x80070002 and similar point at missing or corrupted update files, which is exactly what clearing SoftwareDistribution addresses.

My update says it needs more disk space. How much do I actually need?

Freeing at least 15 to 20 GB gives most feature updates and larger cumulative updates enough room, since Windows also keeps a temporary rollback copy in case the install fails.

Should I use a third-party tool to fix Windows Update problems?

Not for this. The built-in troubleshooter and the manual steps here cover the same ground without installing anything or risking bundled adware.

Will resetting Windows Update delete my files?

No. Every fix here only touches Windows' own update and system files, never your personal documents, photos, or installed programs.

What if none of these fixes work and updates still fail?

An in-place repair install through the Media Creation Tool is the honest last resort — it rebuilds the update components from scratch while keeping your files and apps.

Can a VPN or work network cause Windows Update to fail?

Yes — corporate VPNs and locked-down networks commonly block the ports Windows Update needs, showing up as a timeout error rather than an obvious network message.

Does a metered connection stop updates from installing?

It can delay larger downloads, since Windows automatically holds back big updates on a connection marked metered to save data.

Revision note. Originally published December 22, 2016. Rewritten August 16, 2026 for Windows 11 and Windows 10. The commands and folder paths in the original guide — restarting the Windows Update service and clearing the SoftwareDistribution folder — still work exactly as they did then; what's changed is where Microsoft tucked the troubleshooter after redesigning Settings, and the fact that Windows 10 now runs past its own end of support. If you landed here at 11 PM with a stuck update and a deadline in the morning, run the troubleshooter first, breathe for the next twenty minutes, and you'll very likely be back up before you needed to be.