0x80070490 Fix: Windows Error Explained

Windows error 0x80070490 usually appears during updates, app installations, or system repairs, and it means the Windows Component Store or the update components are corrupted or missing. The fix is to run the System Update Readiness Tool (DISM) and System File Checker (SFC) in a specific order, then reset Windows Update components if the error persists. This guide explains why the error occurs, the exact commands to run, and what to do when they don’t work.

What Error 0x80070490 Actually Means

The error code 0x80070490 translates to ERROR_NOT_FOUND (“The operation completed successfully, but the specified object was not found”). In the context of Windows, it typically points to a problem in the Component Store (C:\Windows\WinSxS) or the servicing stack that manages updates. When Windows tries to install an update or a new feature, it looks for a specific manifest or package file. If that file is missing or corrupted, the operation fails and you see 0x80070490.

Common scenarios where this error appears:

• Windows Update fails to install a cumulative update or a feature update.
• Installing or uninstalling a language pack, .NET Framework, or other optional features via “Turn Windows features on or off”.
• Running the System File Checker (sfc /scannow) and it reports that it cannot repair some files.
• Attempting to repair a corrupted system using the Windows Media Creation Tool or an in-place upgrade.

Why the Error Happens: The Component Store and Servicing Stack

Windows keeps every system file and update package in the Component Store (WinSxS). This folder contains all versions of system files, so that updates can be rolled back if needed. The servicing stack is the component that installs, uninstalls, and modifies these packages. If the servicing stack itself is damaged (e.g., a failed update left it in an inconsistent state), it cannot read or write the Component Store correctly, leading to error 0x80070490.

Another common cause is a corrupted Windows Update database (the SoftwareDistribution folder) or a misconfigured system file that the update process depends on. Third-party antivirus software, disk errors, or an interrupted update installation can all trigger this corruption. The error is not hardware-related; it is purely a software issue within Windows.

How to Fix 0x80070490: Step-by-Step Commands

Before starting, back up your important files. The commands below are safe and do not delete personal data, but they can take 15-30 minutes to run. You will need to run Command Prompt as Administrator.

1. Run DISM to repair the system image. Open Command Prompt as Administrator and type: DISM /Online /Cleanup-Image /RestoreHealth. This command uses Windows Update to download healthy files and replace corrupted ones in the Component Store. If you have no internet connection, you can use a Windows installation media: DISM /Online /Cleanup-Image /RestoreHealth /Source:C:\repairSource\install.wim /LimitAccess (replace the path with your actual source).
2. Run SFC to repair system files. After DISM finishes (it may say “The restore operation completed successfully” or “The system file repair was not completed”), type sfc /scannow and press Enter. This scans all protected system files and replaces corrupted ones with cached copies.
3. Restart your PC. Reboot after SFC completes. Many users find that the error is resolved after these two steps.
4. If the error persists, reset Windows Update components. Open Command Prompt as Administrator and run the following commands one by one, pressing Enter after each:
   net stop wuauserv
net stop cryptSvc
net stop bits
net stop msiserver
ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
ren C:\Windows\System32\catroot2 Catroot2.old
net start wuauserv
net start cryptSvc
net start bits
net start msiserver
5. Run the Windows Update Troubleshooter. Go to Settings > System > Troubleshoot > Other troubleshooters, select Windows Update, and run it. This tool automatically detects and fixes common update issues.

What to Do If the Standard Fix Fails

If the error still appears after DISM, SFC, and resetting update components, the corruption may be deeper or the update files themselves are problematic. Try these advanced steps:

• Perform an in-place upgrade. Download the Windows 10 or Windows 11 Media Creation Tool from Microsoft’s official website, run it, and choose “Upgrade this PC now”. This reinstalls Windows while keeping your files and installed applications. It repairs the system image without wiping your data.
• Check disk for errors. Run chkdsk /f /r in an elevated Command Prompt and restart. This scans for bad sectors and file system errors that could interfere with the update process.
• Manually download the update. If the error occurs with a specific update (e.g., a cumulative update), go to the Microsoft Update Catalog website, search for the KB number, download the standalone installer, and run it manually. This bypasses Windows Update’s internal logic.
• Use the System Update Readiness Tool (for Windows 7/8.1). For older Windows versions, Microsoft provides a standalone tool called “System Update Readiness Tool” (KB947821) that fixes servicing stack corruption. Download it from Microsoft’s official site and run it.

Common Misconceptions About 0x80070490

One common myth is that this error indicates a failing hard drive or RAM. While disk errors can contribute, the error code itself points to missing system components, not hardware failure. However, if you see this error repeatedly after a fresh Windows installation, it is worth running a memory diagnostic (Windows Memory Diagnostic tool) and checking the drive’s SMART status.

Another misconception is that you need to reinstall Windows to fix it. In most cases, the commands above resolve the issue. Reinstallation is a last resort, and an in-place upgrade is less disruptive than a full reset.

Some users also believe that disabling antivirus software is the fix. While third-party antivirus can interfere with updates, the error 0x80070490 is not specifically caused by antivirus. If you suspect it, temporarily disable your antivirus and run the update again, but the DISM and SFC steps are the primary solution.

How to Prevent This Error in the Future

Prevention is about keeping your system healthy:

• Always install updates properly. Do not force shutdown or restart during updates. Let them complete.
• Keep your disk healthy. Run chkdsk periodically and ensure you have enough free space (at least 20 GB for Windows updates).
• Use the Windows Update Troubleshooter regularly. It can catch minor issues before they become major.
• Create a system restore point before installing major updates. This allows you to roll back if something goes wrong.
• Keep your drivers updated. Outdated drivers can cause system instability, but they are not a direct cause of this error.

Comparing 0x80070490 with Similar Windows Errors

Windows has several error codes that look similar but have different meanings. Knowing the difference helps you choose the right fix:

• 0x80070002: “The system cannot find the file specified.” Often occurs when update files are missing from the SoftwareDistribution folder. The fix is to reset Windows Update components.
• 0x80070003: “The system cannot find the path specified.” Similar to 0x80070002, but usually related to a missing folder during update installation.
• 0x80070490: “Element not found.” Specifically points to a missing component in the Component Store or servicing stack.
• 0x80073712: “A component store corruption has been detected.” This is more specific and usually requires DISM to repair.

If you see 0x80070490 during a Windows Update, the DISM and SFC approach is the most effective. For other codes, you may need to try different steps.

Frequently Asked Questions

Does 0x80070490 mean my PC is broken?

No. It means that some Windows system files are missing or corrupted, but it is a software issue that can usually be fixed with the commands above. Your hardware is likely fine.

Can I ignore this error and continue using my PC?

You can, but you will not be able to install updates or new features, which leaves your system vulnerable to security issues. It is best to fix it as soon as possible.

Will running DISM and SFC delete my files?

No. These tools only repair system files. They do not touch your personal documents, photos, or installed programs. However, it is always a good habit to back up important data before running system repairs.

How long does the fix take?

DISM can take 10-30 minutes depending on your internet speed and system performance. SFC also takes about 10-20 minutes. The entire process may take up to an hour. Do not interrupt it.

I get the error when installing a game or app, not an update. What should I do?

If the error appears during app installation, it may be because the app requires a Windows feature that is missing. Try enabling the required feature via “Turn Windows features on or off” (e.g., .NET Framework 3.5). If that fails, run the same DISM and SFC commands to repair the system.

Is there a way to fix this without using Command Prompt?

You can use the Windows Update Troubleshooter and the Media Creation Tool, but the most reliable method is the Command Prompt commands. If you are uncomfortable with Command Prompt, you can follow the in-place upgrade route, which does not require typing commands.

Related

• WhatsApp: How to Block Unknown Numbers
• How to Exit Vi in Linux: A Simple Guide
• iPhone Stuck on Setting Up Apple ID: Fixes