When Windows Update won't cooperate, the fastest path is to work from the outside in: check the network and date first, then the update service, the component store, and only then the update history. Microsoft's own support site at support.microsoft.com hosts the canonical troubleshooting pages, and the sequence below mirrors how Microsoft's troubleshooters are ordered β€” because most failed updates are caused by a stalled service, a skewed clock, or a corrupted component store rather than a broken Windows install. The one condition that changes everything is a cap on metered connections, which silently blocks downloads on laptops and tablets until you remove it.

Start With the Network and Date Because Both Fake a Failed Update

Microsoft lists "check your network connection" and "make sure your device is connected to the internet" as the first steps on its Windows Update troubleshooting pages for a reason: a dropped connection produces the same error screens as a corrupted update cache. A Wi-Fi link that stays up but routes traffic poorly will let Windows reach the update servers, begin a download, and stall halfway. Testing a second network β€” a phone hotspot is enough for a single download β€” separates a local router problem from a Windows problem in under five minutes.

Time is the second silent failure. Windows Update validates certificates against the system clock, and a device whose date is off by more than a few minutes can receive a certificate error that reads like a server problem. Microsoft's guidance to sync the clock is buried in the "Windows Update: FAQ," not the main troubleshooter, which is why so many people miss it. Open Settings > Time & language > Date & time and switch on "Set time automatically" and "Set time zone automatically," then press the "Sync now" button if it appears.

Metered connections deserve their own look. On Windows 10 and Windows 11, Settings > Network & internet > Wi-Fi > your network name carries a "Set as metered connection" toggle, and while it's on, Windows defers most downloads. On a laptop that once joined a phone hotspot and inherited the setting, updates can appear permanently paused with no error at all. Turn the toggle off on your home network and retry before you touch anything else.

If neither the network nor the clock explains the failure, note the exact error code shown under Settings > Windows Update. Codes such as 0x80070002 (file not found) or 0x800f081f (.NET or feature source missing) point to different repair paths, and Microsoft's "Windows Update troubleshooter" page maps them. Writing the code down now saves you from guessing later.

Run the Built-In Windows Update Troubleshooter Before Editing Services

Before Windows 11, the path was Settings > Update & Security > Troubleshoot > Additional troubleshooters > Windows Update. On Windows 11 22H2 and later, the same tool sits under Settings > System > Troubleshoot > Other troubleshooters, where "Windows Update" appears in the list with a "Run" button. Microsoft's support article "Windows Update troubleshooter" documents both placements, and the tool itself has not changed in behavior: it restarts the update services, clears the temporary download folder, and resets the components it can reach.

Run it once, not five times. The troubleshooter detects a limited set of conditions β€” stopped services, a full update cache, a broken BITS queue β€” and repeated runs on the same broken state return the same "couldn't identify the problem" message. If the first run finds nothing, move to manual service checks rather than looping. The tool logs what it changed under %SystemRoot%\System32\LogFiles\WindowsUpdate, which is useful when you escalate to Microsoft support.

Expect the troubleshooter to restart Windows Update, Background Intelligent Transfer Service (BITS), and Cryptographic Services. Those restarts are why a run can take five to ten minutes even when nothing is found. Don't close the window mid-run; an interrupted reset can leave the update cache in a half-cleared state that produces a new error code.

A clean run that still fails points at corruption the troubleshooter can't repair, such as a damaged component store. That's the signal to jump to the DISM and SFC section rather than running the troubleshooter a second time. Microsoft's documentation says the same thing in less direct language: the troubleshooter fixes configuration, not files.

Reset the Update Components Manually With Four Commands and a Folder Rename

The manual reset is the workhorse fix, and it works identically on Windows 10 and Windows 11. Open Command Prompt as administrator (search "cmd," right-click, "Run as administrator"), then run the four commands below one at a time, waiting for each to finish. Microsoft's "Additional resources for Windows Update" page and the KB articles linked from it describe these services, though the step-by-step order is scattered across several pages.

1: Type net stop wuauserv and press Enter. This stops the Windows Update service; a "service is not started" message is fine. 2: Type net stop bits and press Enter. BITS handles background downloads and must stop before the cache can be renamed. 3: Type net stop cryptsvc and press Enter. Cryptographic Services must stop so the catroot2 folder can be rebuilt. 4: Type ren C:\Windows\SoftwareDistribution SoftwareDistribution.old and press Enter. This renames the download cache; Windows recreates the folder on the next update check. 5: Type ren C:\Windows\System32\catroot2 catroot2.old and press Enter. This rebuilds the signature database. 6: Type net start wuauserv and press Enter, then repeat for net start bits and net start cryptsvc.

Failure handling matters here. If any stop command returns "Access is denied," you didn't open the elevated prompt β€” close the window and reopen it with administrator rights. If the rename fails with "The system cannot find the file specified," the folder is already gone or was never created, and you can skip that step. If the rename fails with "The process cannot access the file," a service you stopped didn't actually stop; run net stop wuauserv again and check for a progress bar in Settings that has to be cancelled first.

After the services restart, open Settings > Windows Update and click "Check for updates." Windows rebuilds SoftwareDistribution from scratch, which can take several minutes on a slow drive. If the same error returns immediately, the problem lives deeper than the cache and you should run the DISM and SFC scans next.

Repair the Component Store With DISM, Then SFC, in That Order

Microsoft's official sequence on the "Use the System File Checker tool to repair missing or corrupted system files" page is DISM first, SFC second, and the order is not arbitrary. DISM repairs the component store that SFC reads from; running SFC against a damaged store can report errors it can't fix. Open an elevated Command Prompt and run DISM /Online /Cleanup-Image /RestoreHealth. It contacts Windows Update for replacement files, so a working network connection is required.

On Windows 10 and Windows 11, DISM's output ends with "The operation completed successfully" or an error code such as 0x800f0906, which means the source files are unavailable. That code commonly appears when a Group Policy or registry setting has redirected Windows Update to an internal WSUS server that doesn't host the needed payload β€” a corporate-laptop scenario Microsoft documents under "Windows Update error 0x800f0906." Home users who see it usually have a third-party "update blocker" tool installed.

Once DISM finishes, run sfc /scannow and let it complete. SFC takes 5 to 15 minutes depending on drive speed and reports one of three results: no integrity violations, violations repaired, or violations found that couldn't be repaired. The third result means the corruption is beyond the offline repair path, and a Windows reinstall (in-place upgrade keeps files) becomes the practical next step.

These two scans together fix the largest share of stubborn update failures that survive the component reset, but they don't touch driver-level issues or disk errors. If DISM itself fails with "The component store is repairable" but never completes, check the drive with chkdsk C: /f from an elevated prompt after a reboot. Microsoft's DISM documentation lists the error codes worth matching to the drive-check path.

Clear the Windows Update Download Cache Without Breaking Installed Updates

Renaming SoftwareDistribution during the manual reset clears the download cache, but a second cache path often survives: the Delivery Optimization cache, which stores update pieces shared between local devices. Windows 11's Settings > System > Storage > Temporary files includes "Delivery Optimization Files" as a checkbox; on Windows 10 it sits under Settings > System > Storage > "Configure Storage Sense or run it now" > Temporary files. Clearing it frees space and removes stale chunks that can cause a "download stuck at 0%" loop.

Don't delete the whole SoftwareDistribution folder. Renaming it, as in the command sequence above, lets Windows rebuild it safely. Deleting the folder outright, which some forum posts recommend, can leave the update client in a state where the next check returns error 0x80248007 ("the update was not found in the data store") for every update. If you've already deleted it, running the four-command reset plus the troubleshooter restores it.

Installed updates are not stored inside SoftwareDistribution in any recoverable form, so clearing caches never removes an update you already applied β€” but it can remove an update that downloaded and hadn't installed yet. On a metered or slow connection, that means the next attempt redownloads the full package, which for a cumulative update on Windows 11 is typically several hundred megabytes. Microsoft's update history page under Settings > Windows Update > Update history shows what's pending, so check there before clearing.

A cleaner alternative for one stubborn package is the Microsoft Update Catalog. Search the specific KB number (visible in update history), download the standalone .msu file, and double-click it. This bypasses the Windows Update client entirely and is Microsoft's documented fallback for update-agent failures on older builds.

Recognize the Windows 10 Support Deadline and the Windows 11 Hardware Boundary

Windows 10 reached its end of support on October 14, 2025, per Microsoft's lifecycle page. That date changes the troubleshooting question: a Windows 10 PC that fails to update in late 2026 may be blocked because the update channel itself has narrowed to security-only releases for Extended Security Updates (ESU) customers. Business and education ESU ran to October 2026; consumer ESU enrollment through Microsoft's consumer program extends further but requires a Microsoft account. If your Windows 10 machine fails and shows no error code, check whether updates are even being offered in Settings > Windows Update > Update history β€” a blank history on an ESU-eligible device is a licensing problem, not a corruption problem.

Windows 11 has its own boundary. The TPM 2.0 and Secure Boot requirements from Microsoft's "Windows 11 system requirements" page can cause feature updates (the annual version upgrades) to fail with error 0xC1900101, which means a driver or hardware check failed during the upgrade phase. The bulky cumulative monthly updates install on most compliant hardware; the yearly version upgrade is where the hardware checks bite.

For a device that fails the Windows 11 compatibility check, Microsoft's PC Health Check app (downloadable from Microsoft's Windows 11 page) reports the specific blocking component β€” TPM version, Secure Boot state, or CPU generation. That report is the definitive answer on whether an upgrade is possible. It matters because a machine that isn't Windows 11-compatible can still receive Windows 10 security updates only while ESU coverage lasts.

None of this is a reason to skip the standard fixes. A Windows 10 machine with a corrupted cache will fail on ESU-delivered updates exactly the way it failed before the deadline, so run the troubleshooters first. Only after they produce a clean run with no updates offered should you check the licensing and lifecycle angle.

Use the Microsoft Update Catalog and Support Pages When Settings Gives Up

Settings > Windows Update is a front end. The underlying service is visible through services.msc, and the update client's log is at C:\Windows\WindowsUpdate.log on older builds or %windir%\Logs\WindowsUpdate on Windows 10 1809 and later. Microsoft's "Windows Update log files" support article explains this relocation and how to read the log with the Get-WindowsUpdateLog PowerShell cmdlet β€” the single most useful diagnostic when Settings shows a generic error.

Microsoft's support site organizes this material in three layers, and knowing which layer to open saves time. The "Windows Update: FAQ" answers common questions (how to check version, how to pause updates, how to free space). The "Troubleshoot problems updating Windows" page walks through the troubleshooter and manual reset. The "Windows Update error codes" article maps specific codes to specific fixes. If a code isn't in the article, Microsoft's support virtual agent accepts a typed code and returns the matching KB article.

A 2023 change worth knowing: Microsoft moved many Windows Update troubleshooting articles to the "Windows client" section and retired some older pages, so a bookmark from 2019 may redirect. If a support.microsoft.com link 404s, search the KB number directly on support.microsoft.com; the KB article is usually still live under a new path.

Expect one more behavior in Windows 11: "Get the latest updates as soon as they're available" is a toggle Microsoft added in 2023. Leaving it on installs feature updates as they pass the phased-rollout gate, which is why some machines jump to a new Windows version months before others. Turning it off doesn't stop security updates; it only holds back the yearly version upgrade. That's the toggle to reach for when a feature update fails repeatedly and you'd rather stay on the current build while Microsoft fixes the roll-out issue.

Fix the Specific Errors You See Rather Than Applying Every Fix at Once

Microsoft's error-code article is long, and matching the code to the cause is faster than running the full reset sequence on every failure. The table below pairs the common codes with the fix that addresses them, based on Microsoft's published error-code documentation and the update-history behavior each code describes.

Error code Meaning in plain terms First fix to try
0x80070002 Update files not found on disk or server Run the manual component reset, then the troubleshooter
0x800f081f Feature source files missing (.NET, optional features) DISM /RestoreHealth, then install from the Microsoft Update Catalog
0x80070643 Update installer crashed mid-installation Run the Windows Update troubleshooter, then retry
0x80248007 Update missing from local data store Stop services, rename SoftwareDistribution, restart
0xC1900101 Driver or hardware failed during upgrade Check PC Health Check and update or remove the named driver
0x80073712 Component store corrupted DISM, then SFC

That table is a decision aid, not a guarantee. Microsoft's article notes that the same code can have more than one cause, and the update history entry usually carries more detail than the Settings banner. Open Settings > Windows Update > Update history and click the failed update to see the full message before picking a row.

The 0x800f081f row is the most commonly misdiagnosed. On machines where a Group Policy has redirected update sources to WSUS, DISM's /RestoreHealth can't reach Microsoft servers and the error persists through every reset. Checking gpresult /r in an elevated Command Prompt reveals a WSUS assignment; if one exists, ask the IT administrator before editing anything, since a manual source switch may be reverted at the next policy refresh.

Windows 11's error 0xC1900101 is the second most misdiagnosed. It's an upgrade-phase failure, not a normal update failure, and the failed driver is named in the update history entry β€” an outdated audio or GPU driver is the usual culprit. Updating that driver from the PC maker's support page, not Windows Update, is the documented fix. Applying the manual reset to a 0xC1900101 failure changes nothing because the download completed fine; the failure happens after the install begins.

FAQ

How long should a Windows Update check take before I assume it's stuck?

A check that returns no progress for more than 30 minutes is effectively stuck, because Microsoft's update client contacts servers within seconds and downloads begin within a minute on a working connection. The most common cause is a half-stopped service inside the manual reset sequence, so cancel the check and rerun the four-command reset cleanly. If the check then completes but shows a 0% download for over an hour, the Delivery Optimization cache is likely the blocker and clearing it frees the queue.

Does the Windows Update troubleshooter fix corrupted system files?

No β€” the troubleshooter resets update configuration and services, but it does not repair damaged files in the component store. Microsoft's own support pages direct you to System File Checker and DISM for file-level repair, and those are separate tools. If you've run the troubleshooter three times with the same result, switch to an elevated Command Prompt and run DISM /Online /Cleanup-Image /RestoreHealth, then sfc /scannow. A 0x80073712 error alongside a clean troubleshooter is the classic signature of store corruption the tool can't touch.

Can I still get Windows 10 updates after October 2025?

Only through Extended Security Updates, which require an enrollment path β€” consumer ESU through a Microsoft account, or a commercial ESU license for businesses, per Microsoft's Windows 10 lifecycle page. Standard Windows Update on Windows 10 stopped delivering feature and non-security updates on October 14, 2025; what arrives afterward is ESU-delivered security content. If Settings shows no updates at all, check ESU enrollment status before assuming a cache problem, because no amount of troubleshooting restores updates Microsoft no longer publishes to that channel.

Why does my update get stuck at 0% and then fail with 0x80248007?

That combination usually means the SoftwareDistribution folder was deleted rather than renamed, leaving Windows Update with no local data store to register the download. The fix is the full four-command reset with the rename step, run from an elevated prompt, followed by a troubleshooter run to let Windows recreate the folder. If the folder already exists and the error still appears, Delivery Optimization is the next suspect β€” clear it under Storage > Temporary files. A standalone .msu from the Microsoft Update Catalog is the fastest workaround when the client stays broken.

What's the difference between the Windows Update troubleshooter and the Get Help app?

The troubleshooter is the automated reset tool built into Settings under System > Troubleshoot > Other troubleshooters on Windows 11, while Get Help (formerly "Contact Support") is Microsoft's live chat and virtual-agent app, preinstalled on Windows 11 and available from the Microsoft Store. Get Help connects you to a support agent or a virtual agent that can read a typed error code; it does not reset update services automatically. For a stuck download, the troubleshooter is the faster move; for a code the troubleshooter can't fix, the virtual agent in Get Help is Microsoft's documented escalation path.

Does a VPN or third-party antivirus stop Windows Update?

Yes, in specific configurations. A VPN that blocks Microsoft's update endpoints or enforces a captive-portal check will stall downloads, and some third-party security suites intercept HTTPS traffic in ways that break certificate validation for update payloads, producing certificate errors that look like clock problems. Microsoft's "Windows Update: FAQ" recommends disconnecting the VPN and temporarily disabling the security suite's web shield when errors persist. This is the third common cause after network and time, and it's the one most people overlook because the browser works fine.

What should I do if DISM keeps failing with "The component store is repairable"?

That message means the store's corruption is fixable, but the repair needs source files Windows can't reach β€” typically because a WSUS policy, a third-party update blocker, or a missing WinSxS payload is in the way. First run gpresult /r to confirm no update-source policy is assigned; on a home machine, uninstall any update-blocking utility. If the failure persists, run chkdsk C: /f after a reboot, since a bad sector in the component store is a known cause of repeated DISM failures, then retry the DISM command. Microsoft's DISM documentation lists the remaining error codes if none of these apply.

Can I install a failed update manually from Microsoft's site?

Yes β€” the Microsoft Update Catalog hosts standalone .msu packages for most cumulative and security updates, searchable by the KB number shown in your update history under Settings > Windows Update > Update history. Download the package matching your Windows version and architecture (x64 or ARM64), double-click it, and let the installer run; it bypasses the Windows Update client entirely. Feature updates (the yearly version upgrades) are not usually distributed this way, so a manually installed .msu can fix a monthly cumulative update but not a failed Windows 11 version jump.