● UK tech experts · info@vividrepairs.co.uk
Vivid Repairs
Windows Update error 0x80070490 message displayed on laptop screen during failed system update installation process on modern desk
Fix It Yourself · Troubleshooting

Windows Update error 0x80070490 component store corruption

Updated 21 May 20269 min read
As an Amazon Associate, we may earn from qualifying purchases. Our ranking is independent.

You're trying to install updates and Windows throws error 0x80070490 at you. Could be a driver, could be the monthly rollup. Either way, your system won't move forward. This error means Windows Update can't find files it needs, usually because something's corrupted in the component store. I've fixed this hundreds of times via remote support, and the good news is it's almost always fixable without nuking your system.

TL;DR

Windows Update error 0x80070490 happens when component store files go missing or corrupt. Fix it by running DISM.exe /Online /Cleanup-Image /RestoreHealth (20-45 minutes), then sfc /scannow (15-30 minutes), then restart. If that fails, stop Windows services, rename the SoftwareDistribution and catroot2 folders, restart services, and try updating again.

⏱️ 14 min read✅ 70-80% success rate📅 Updated May 2026

Key Takeaways

  • Error 0x80070490 means Windows can't locate critical system files needed for updates
  • Component store corruption is the most common cause, especially after failed updates
  • DISM and SFC repairs fix 70-80% of cases without data loss
  • Windows Update component reset recovers from severe cache corruption
  • Prevention requires regular SFC scans, adequate disk space, and proper antivirus configuration

At a Glance

  • Difficulty: Intermediate
  • Time Required: 45-90 mins
  • Success Rate: 70-80% with first method

What Causes Windows Update error 0x80070490?

The component-based servicing (CBS) store in Windows holds every system component, driver metadata, and update file your OS needs. When error 0x80070490 shows up, it's because Windows Update went looking for something in that store and came up empty. This happens for four main reasons, and understanding which one applies to you changes how we fix it.

Component store corruption is the big one. Unlike typical file damage, the CBS store can develop invisible inconsistencies that don't show obvious symptoms until you try to install an update. A sudden power loss, an interrupted update process, or aggressive antivirus blocking file access can all leave the store in a confused state. Windows knows something's wrong but can't find what it needs to proceed.

Failed previous updates cause this constantly. If an update installation got interrupted, force-shut down mid-process, or installed only partially, the next update sees a broken system state. The files from the failed update are still hanging around, registry entries don't match actual files, and when Windows tries to build on top of that wreckage, error 0x80070490 appears. It's like trying to build a second floor on a foundation with missing bricks.

Driver updates are particularly vulnerable because they require registry metadata that identifies the driver's architecture (x86, x64, ARM). Virtual machine environments see this constantly because their driver metadata often goes missing or becomes corrupted. Without that metadata, Windows literally cannot find the driver file even if it exists on disk.

Finally, corrupted Windows Update services themselves can trigger this error. The WUAUSERV service, BITS, Cryptographic Services, and their cache directories can get damaged by malware, aggressive antivirus rules, or just plain filesystem corruption. If the service that manages updates is broken, every update attempt fails with the same error code.

Windows Update error 0x80070490 Quick Fix

Start with the DISM and SFC repair sequence. This fixes 70-80% of cases and takes roughly 90 minutes. It works because DISM rebuilds the corrupted component store by downloading clean files from Microsoft's servers, then SFC verifies everything else is intact. Most people succeed on the first try, even with severe corruption.

1

DISM and SFC Repair Sequence Intermediate

  1. Open Command Prompt as Administrator
    Right-click the Start menu and select 'Command Prompt (Admin)' or 'Windows PowerShell (Admin)'. A window opens with administrator privileges.
  2. Run DISM RestoreHealth
    Type exactly: DISM.exe /Online /Cleanup-Image /RestoreHealth and press Enter. This takes 20-45 minutes. Your internet connection must stay stable. Do not close the window or restart your computer. DISM scans the component store and downloads replacement files for anything corrupted. You'll see progress updates as it works.
  3. Run System File Checker
    After DISM finishes (it tells you when), type: sfc /scannow and press Enter. This takes 15-30 minutes. SFC verifies every protected system file using the component store that DISM just repaired. If it finds issues, it fixes them automatically.
  4. Restart the computer
    Type shutdown /r /t 0 or restart normally. The system reboots with repaired components in place.
  5. Test Windows Update
    After restart, open Settings > Update & Security > Windows Update and click 'Check for updates'. If error 0x80070490 is gone, you're done.
If updates install successfully, the component store is repaired. Do not proceed to other methods.
Do not interrupt DISM or SFC. Killing the process mid-scan leaves the system unstable. If your internet drops during DISM, it fails completely and you'll need to restart and try again. Make sure you have stable connectivity before starting.

More Windows Update error 0x80070490 Solutions

If DISM and SFC didn't work, the next step is resetting the Windows Update components themselves. This clears corrupted cache files and forces Windows to rebuild its update infrastructure from scratch. Success rate drops to 65-80%, but this catches cases where the service corruption is severe.

2

Windows Update Component Reset Intermediate

  1. Open Command Prompt as Administrator
    Right-click Start menu, select 'Command Prompt (Admin)' or 'Windows PowerShell (Admin)'.
  2. Stop Windows Update services
    Execute these commands one at a time, pressing Enter after each: net stop wuauserv net stop cryptsvc net stop bits net stop msiserver Each service stops. If a command fails, note which one and continue anyway. Most will stop without error.
  3. Rename corrupted update folders
    Execute these commands: ren C:\\Windows\\SoftwareDistribution SoftwareDistribution.old ren C:\\Windows\\System32\\catroot2 catroot2.old These folders contain cached updates and cryptographic signatures. Renaming them forces Windows to create fresh copies next time the services start.
  4. Restart the services
    Execute these commands one at a time: net start wuauserv net start cryptsvc net start bits net start msiserver Services restart and automatically create new, clean folders. If a service fails to start, you may need to use Services.msc (search 'Services' in Windows) to restart it manually.
  5. Restart and test
    Restart your computer. Open Settings > Update & Security > Windows Update and check for updates. Windows will re-download pending updates into the fresh folders.
If updates now install, the corrupted cache was the problem. The system will need to download all pending updates again, which may take time on slower connections.
Do not restart the computer between stopping and restarting the services. If you do, those services won't be running when Windows boots, and updates will fail. Type the commands carefully. If you make a typo, the service may not restart properly. Test by going to Services.msc (search in Windows) and confirming Windows Update, BITS, and Cryptographic Services are all running.

If both DISM/SFC and the component reset fail, you have a few options. System Restore can work if you have a restore point from before the error appeared. Component store issues similar to this one sometimes appear in Store and driver updates, suggesting the corruption runs deeper. A repair installation (in-place upgrade using Windows installation media) can fix severe corruption that these methods cannot touch. If you want to avoid that complexity,

can help identify and fix the underlying filesystem or registry issues automatically.

Advanced Windows Update error 0x80070490 Fixes

For stubborn cases where DISM, SFC, and component reset haven't worked, System Restore is your next weapon. This rolls your system back to a point before the error appeared, removing whatever change triggered the corruption. It works best if you have a restore point from the last few weeks and the corruption is relatively recent.

3

System Restore to Pre-Error State Easy

  1. Open System Restore
    Search Windows for 'Create a restore point' and open it. In the System Protection tab, click the 'System Restore' button. A wizard opens.
  2. Choose a restore point
    Select 'Choose a different restore point' if available. Pick a point dated before error 0x80070490 started. You can click 'Scan for affected programs' to see what will be uninstalled. Choose a point that's old enough to predate the issue but recent enough that you won't lose critical software.
  3. Confirm restoration
    Click 'Next', review the restore point details, then click 'Finish'. Your system restarts automatically and restores to that point. This removes updates, drivers, and software installed after that date.
  4. Verify updates work
    After restart, go to Settings > Update & Security > Windows Update and check for updates. The error should be gone since you've removed whatever caused it.
  5. Reinstall necessary software
    Reinstall any programs or drivers that were removed. Do this carefully and test updates between reinstalls to identify what caused the original problem.
System Restore is non-destructive for personal files. Documents, photos, and user data remain intact. Only programs and OS changes after the restore point are removed.
System Restore cannot be undone once you confirm. If the restore point you choose is too old, you'll lose recent work or software. If there are no restore points available, System Restore cannot help. Restore points require System Restore to be enabled on your drive (right-click drive in File Explorer, Properties, System Protection tab).

If System Restore succeeds but the same error reappears after reinstalling software, you've identified the culprit. Similar driver-related Windows Update errors sometimes come from specific driver packages or firmware updates. Test each reinstalled program or driver independently and run Windows Update between each to find what triggers the error.

For cases where all methods fail, a repair installation is the final option. This reinstalls Windows over itself without touching your files or programs, but it requires Windows installation media and is time-consuming. Before attempting that, consider whether professional remote support makes more sense. If the system-level corruption is beyond these fixes, a technician with remote access can diagnose deeper issues like filesystem damage or malware-caused corruption and often resolve it faster than trial-and-error approaches.

Preventing Future Windows Update error 0x80070490

Once you've fixed this error, preventing it means keeping your component store healthy. Run System File Checker quarterly. Open Command Prompt as Administrator and type sfc /scannow. It takes 20-30 minutes, but catching file corruption early prevents it from spreading to the update system. Make this routine. Seriously.

Disk space matters more than you think. Windows Update needs at least 10GB free to download and stage updates safely. If you're below 15% free space, updates fail or corrupt. Check your drive: right-click it in File Explorer, Properties, and see free space. If it's tight, delete old files, uninstall unused programs, or move media to external storage.

Antivirus configuration is critical. Some antivirus programs block access to Windows Update folders thinking they're malware. Go into your antivirus settings and exclude these directories: C:\\Windows\\SoftwareDistribution C:\\Windows\\System32\\catroot2 Also exclude the Windows Update service itself (WUAUSERV). This prevents the antivirus from interrupting update operations.

Enable System Restore and create restore points before major changes. When you go to install drivers or enable Windows features, create a manual restore point first (search 'Create a restore point', then click 'Create' in that dialog). If something breaks, you can roll back instantly.

Install updates promptly instead of delaying them. Deferred updates accumulate, and a huge batch of stacked updates is more likely to fail than monthly installations. Go to Settings > Update & Security > Windows Update regularly and install updates when prompted. Don't put it off.

Avoid force-shutdown during updates. Never pull the power or hard-reset your computer while Windows Update is running. Let it finish, even if it takes a while. A killed update process is one of the top triggers for component store corruption.

Keep drivers current. Use Device Manager (right-click Start, select Device Manager) to check for outdated drivers monthly. Or go to manufacturer websites for critical drivers like chipset, GPU, and network adapters. Outdated drivers are a common reason driver updates fail with error 0x80070490.

Windows Update error 0x80070490 Summary

Windows Update error 0x80070490 means your component store is corrupted or Windows can't find files it needs. DISM RestoreHealth rebuilds the store from Microsoft's servers, then SFC checks for other system file damage. This fixes 70-80% of cases. If that fails, reset Windows Update components by stopping services and renaming cache folders. For stubborn corruption, System Restore to a pre-error point works well if you have a restore point available. Once fixed, prevent recurrence by running quarterly SFC scans, maintaining 15% free disk space, excluding Windows Update from antivirus scanning, and installing updates promptly. Component store corruption can feel like a dead end, but it's almost always fixable with patience and the right tools. Most people get updates working again in under two hours.

Frequently Asked Questions

Error 0x80070490 is ERROR_NOT_FOUND, meaning Windows Update cannot locate critical files or components needed to install updates. This happens due to component store corruption, missing registry entries, or damaged system files that prevent the update process from completing.

Your computer will keep running, but ignoring this error leaves you vulnerable. You won't receive critical security patches, and the underlying corruption may spread to other system functions over time. It's worth fixing properly rather than leaving your system exposed.

DISM typically takes 20-45 minutes, while SFC takes 15-30 minutes. Total time including restart and testing is usually 45-90 minutes. Speed varies based on system performance, corruption severity, and internet connection quality during DISM's file downloads.

No. DISM, SFC, and the Windows Update component reset only affect system files and update components. Your documents, photos, and personal data remain untouched. System Restore also preserves files but uninstalls programs installed after the restore point date.

Driver updates require specific registry metadata like architecture information (x86, x64, ARM) to install correctly. When this metadata is missing or corrupted, Windows can't find or install the driver, triggering the error. Virtual machine environments are especially prone to this issue.