Windows Update error 0x80080005 is generally associated with corrupted files or incorrect system configuration. Confirm that exact code in Settings > Windows Update > Update history, then work through the repairs in order: run the Windows Update troubleshooter, repair the Windows image with DISM, run SFC, reset the update cache and services, and finally investigate storage, services, drivers, security software, or repair media.
What error 0x80080005 means
Microsoft groups 0x80080005 with 0x80070057 under “corrupted files or incorrect system configurations.” That classification describes the type of failure, not one proven universal cause. The code can appear when Windows Update cannot read a required component, when update services or their cached files are stuck, or when system configuration prevents installation.
| # | Preview | Product | Price | |
|---|---|---|---|---|
| 1 |
|
Microsoft Windows 11 (USB) | $128.99 | Buy on Amazon |
| 2 |
|
Microsoft System Builder | Windоws 11 Home | Intended use for new systems | Install on a new PC |... | Buy on Amazon |
As an Amazon Associate I earn from qualifying purchases.
The title is often written as 0X8008005, with one zero missing. Microsoft’s Windows Update documentation uses 0x80080005. Before changing anything, verify the code shown on your own computer. A different code may require a different procedure.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Confirm the code and prepare Windows
Check Update history
- Open Start > Settings.
- In Windows 11, select Windows Update. In Windows 10, open Update & Security > Windows Update.
- Open Update history and expand the failed update entry.
- Write down the exact hexadecimal code, the update’s knowledge-base number if shown, and whether the failure occurs during download, installation, or restart.
If the history entry shows 0x80080005, continue with the sequence below. If it shows another code, do not assume these steps address that error.
#1 Best Overall
- Less chaos, more calm. The refreshed design of Windows 11 enables you to do what you want effortlessly.
- Biometric logins. Encrypted authentication. And, of course, advanced antivirus defenses. Everything you need, plus more, to protect you against the latest cyberthreats.
- Make the most of your screen space with snap layouts, desktops, and seamless redocking.
- Widgets makes staying up-to-date with the content you love and the news you care about, simple.
- Stay in touch with friends and family with Microsoft Teams, which can be seamlessly integrated into your taskbar. (1)
Protect your work and check basic conditions
- Save open documents and make sure you can restart the computer without losing unsaved work.
- Use an account with administrator rights. DISM, SFC, and service-reset commands require an elevated Command Prompt.
- Keep the computer connected to reliable power, especially during an image repair or restart.
- Check free space on the Windows drive. A nearly full drive can prevent an update from staging files; Microsoft notes that devices with small hard drives may need a USB drive during an update.
- Disconnect unnecessary external devices while troubleshooting. Leave connected hardware that Windows needs for input, networking, or storage.
Step 1: Run the Windows Update troubleshooter
Start with Microsoft’s automated diagnostic because it can identify common update-service and configuration problems without changing system files manually.
- Open Start > Settings > System > Troubleshoot > Other troubleshooters.
- Find Windows Update and select Run.
- Apply each repair the troubleshooter offers and allow it to finish.
- Restart Windows if prompted.
- Return to Windows Update and select Check for updates, then retry the failed update.
A successful troubleshooter run does not prove that every damaged component has been repaired. If 0x80080005 returns, proceed to image and system-file repair.
Step 2: Repair Windows with DISM, then SFC
DISM repairs the Windows component store and can obtain replacement files from Windows Update. SFC checks protected system files against that repaired component store. Microsoft’s order is important: run DISM first, then SFC.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Scan for outdated or missing drivers - takes under a minute3Clear out junk files and repair common Windows errorsOpen an elevated Command Prompt
- Open Start and type
Command Prompt. - Right-click Command Prompt and select Run as administrator.
- Approve the User Account Control prompt.
If the window title does not indicate administrator access, close it and repeat the process. The commands may otherwise fail with an access error.
Run the DISM repair
Enter this command exactly, then press Enter:
DISM.exe /Online /Cleanup-image /RestorehealthDISM can take time and may appear paused at a percentage for several minutes. Do not close the window merely because progress is slow. Wait for a completion message. Microsoft documents successful completion with text such as “The restore operation completed successfully” or “The operation completed successfully.” Those messages report the command’s result; they do not guarantee that 0x80080005 or every pending update has been fixed.
Run System File Checker
After DISM finishes, run:
sfc /scannowAllow the scan to reach 100 percent. Closing the window early can leave the verification incomplete. Restart Windows when the scan finishes, then try Windows Update again.
If DISM cannot obtain repair files
By default, DISM uses Windows Update as its source for necessary files. If Windows Update itself is damaged or unavailable, DISM may report that source files could not be found. In that case, use a valid Windows installation source from installation media, a network share, or removable media.
The source must match the installed Windows version and edition. A mismatched source can produce another servicing error or repair the wrong component set. Use the source path supplied by your organization or created from installation media, and apply the path in the documented pattern:
DISM.exe /Online /Cleanup-Image /RestoreHealth /Source:<verified-source-path> /LimitAccess/LimitAccess tells DISM not to contact Windows Update while it uses the specified source. Replace the code-formatted path with a real, verified path; do not type the angle brackets literally. After DISM succeeds, run sfc /scannow again and retry the update.
Step 3: Reset Windows Update components
If the update still fails, its download cache or service state may be stuck. Microsoft documents resetting the relevant services and renaming two cache folders. Renaming preserves the old folders as backups while forcing Windows to create fresh ones.
Stop the update services
Open an elevated Command Prompt again and run each command separately:
Recommended Free Tools
net stop wuauserv
net stop bits
net stop cryptSvcEach service should report that it was stopped. If a service refuses to stop, restart Windows and repeat the commands before moving on. Do not rename the folders while the associated services are still actively using them.
Rename the cached folders
ren %windir%SoftwareDistribution SoftwareDistribution.old
ren %windir%System32catroot2 catroot2.oldSoftwareDistribution stores Windows Update download and staging data. catroot2 stores catalog information used to verify update packages. Renaming, rather than deleting, lets you recover the old folders if a separate issue requires them. Windows creates new folders when the services start again.
Start the services and restart
net start cryptSvc
net start bits
net start wuauserv- Confirm that each service starts without an error.
- Restart Windows.
- Open Settings > Windows Update and select Check for updates.
- Retry the update that produced 0x80080005.
The reset changes update caches and service state; it does not erase your personal files. If an old cache is no longer needed, Windows can leave it in place until you have confirmed that updates work.
Step 4: Check services, storage, and software conflicts
Verify that required services are not disabled
Open the Windows Services management console and review the services involved in updating, including Windows Update, Background Intelligent Transfer Service, and Cryptographic Services. A service that is disabled, repeatedly stopping, or unable to start can reproduce the error after a cache reset. Restore the service to its normal Windows configuration rather than choosing a random startup type, then restart and test again.
Rank #2
- STREAMLINED & INTUITIVE UI, DVD FORMAT | Intelligent desktop | Personalize your experience for simpler efficiency | Powerful security built-in and enabled.
- OEM IS TO BE INSTALLED ON A NEW PC with no prior version of Windows installed and cannot be transferred to another machine.
- OEM DOES NOT PROVIDE SUPPORT | To acquire product with Microsoft support, obtain the full packaged “Retail” version.
- PRODUCT SHIPS IN PLAIN ENVELOPE | Activation key is located under scratch-off area on label.
- GENUINE WINDOWS SOFTWARE IS BRANDED BY MIRCOSOFT ONLY.
If a service stops immediately, note the exact message in its properties or in Windows Event Viewer. That symptom points to a broader system or policy problem rather than a simple update-cache failure.
Free enough storage for staging
Check the available space on the drive containing Windows. Updates need room for downloaded packages, temporary extraction, and rollback data. Remove only files you recognize, empty temporary locations using Windows’ own storage controls, or attach approved external storage when Windows specifically requests it. A USB drive can help when the device has very little free space, but it is not a universal fix for 0x80080005.
Try a clean restart
Third-party startup software can interfere with update services. A clean restart starts Windows with a minimal set of non-Microsoft startup programs and services so you can test whether a background application is involved. After the test, restore normal startup settings; leaving diagnostic startup configuration enabled can prevent other applications or services from running normally.
Review security software and drivers
Microsoft recommends considering interference from third-party security software or drivers when updates continue to fail. Temporarily test with nonessential security or system-tuning components disabled only if your organization’s policy allows it, and re-enable protection immediately after the test. Do not remove security software solely because the error code appears. Also check whether a recently installed or updated driver coincided with the failure; obtain drivers from the hardware maker or Windows Update rather than from an unverified download.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Do you need a USB drive?
No. Most 0x80080005 repairs use the installed Windows environment, an administrator account, and an internet connection for the troubleshooter and online DISM source.
A USB flash drive becomes relevant in two situations:
- DISM source failure: Windows Update cannot supply the repair files, so you provide matching Windows installation media as the
/Sourcelocation. - Insufficient storage: Microsoft notes that a device with a small hard drive may need removable storage to complete an update.
Microsoft does not specify one USB brand or capacity for this error. The important requirement is a valid installation or repair source that matches the installed Windows version and edition. Verify the media before pointing DISM at it. A USB containing unrelated files, or media for a different edition, will not repair the component store.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Compare the repair paths
| Path | Personal-file risk | Internet required | Administrator rights | Installation media | What it does |
|---|---|---|---|---|---|
| Windows Update troubleshooter | Low; diagnoses and applies targeted settings | Usually helpful, but availability depends on the diagnostic | Windows may request approval | No | Diagnoses common update conditions and applies offered repairs |
| DISM online repair | Low; repairs Windows components | Normally yes, because Windows Update supplies files | Yes | No, unless the online source fails | Repairs the Windows image/component store |
| SFC scan | Low; replaces protected system files when possible | Not necessarily after DISM has a valid source | Yes | No | Checks and repairs protected system files |
| Component reset | Low for personal files; rebuilds update caches | No for the reset itself; internet is needed to download the update again | Yes | No | Stops services and recreates SoftwareDistribution and catroot2 |
| DISM with alternate source | Low when the source matches the installation | No if the source is local and /LimitAccess is used |
Yes | Often; a USB, mounted ISO, or network share can provide it | Supplies replacement files from verified installation media |
What to do when a command reports an error
DISM says source files could not be found
Confirm that Windows Update is working well enough to provide files. If it is not, repeat DISM with a verified installation source and /LimitAccess. Check the Windows edition and version represented by the source before retrying. Do not treat a successful command with an unmatched source as a reliable repair.
SFC reports that it could not repair some files
Run DISM again, wait for a successful completion message, restart, and run SFC once more. If SFC still cannot repair protected files, the problem extends beyond the update cache. Record the final SFC message and move to Microsoft’s support or repair-installation options rather than repeatedly running the same scan without a new source.
A service will not stop or start
Restart Windows and repeat the service commands from an elevated prompt. If the service remains unavailable, inspect its configuration and related Event Viewer entries. Persistent service failures can indicate damaged system components, policy restrictions, or interference from third-party software.
The update downloads but fails during installation
Repeat the DISM/SFC sequence, reset the update components, check storage, and test after a clean restart. The phase matters: a download failure points more strongly toward connectivity or cache problems, while an installation or reboot failure can involve component servicing, drivers, or insufficient staging space.
The same update fails after every repair
Confirm that the code is still 0x80080005 and that the failed update is not superseded by a newer package. Review the update history for a consistent failure phase, verify services and storage, and check for driver or security-software conflicts. If the component store and caches have been repaired but the update still fails, use Microsoft support or an in-place Windows repair/installation path appropriate for your edition. Back up important files before any installation operation and follow the option’s prompts carefully.
Windows 10 timing matters
Microsoft states that after October 14, 2025, it no longer provides free Windows 10 software updates, technical assistance, or security fixes through Windows Update. On a Windows 10 device in October 2026, a missing update may therefore reflect the end of support rather than a repairable 0x80080005 condition. Confirm the Windows edition and support status before spending time on a package that is no longer offered. Windows 11 devices follow their own servicing and eligibility rules.
When to stop troubleshooting manually
Escalate when the exact code changes, DISM cannot complete even with a matching source, SFC repeatedly reports unrepaired files, services cannot be restored, or the computer shows broader instability such as repeated crashes or failed restarts. Keep the following information for support:
- The exact code and failed update identifier from Update history.
- The Windows edition and version.
- The phase at which the update fails.
- The final DISM and SFC messages.
- Whether resetting SoftwareDistribution and catroot2 changed the behavior.
- Available storage and any recent driver, security-software, or system changes.
These details distinguish an update-specific problem from a wider Windows servicing failure and prevent repeating repairs that have already been completed.
Quick Recap
As an optional shortcut after the manual steps, Outbyte PC Repair can address more than 100 common Windows issues where possible, including broken system elements and shared DLL files, while also offering settings tweaks, temporary-file cleanup, vulnerability checks, and an app-crash log. It runs on Windows 11, 10, 8, and 7; its free trial lasts at least two days before a paid subscription. It complements antivirus software rather than replacing it, and results vary—no tool repairs every update failure.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minutePC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
