Windows updates aren’t exactly famous for going smoothly. One minute you’re installing something routine, the next you’re staring at a cryptic error like 0x80070490. No warning, no context, just an update that fails and leaves you wondering what went wrong.
This error doesn’t always mean something is seriously broken. In fact, most of the time, it’s linked to update conflicts, damaged files, or driver issues that Windows just doesn’t handle very gracefully. The good news? You don’t have to call in IT support or wipe your machine to deal with it.
We’ll walk through what this code means, why it shows up, and how you can fix it using simple, clear steps – no tech jargon, no guesswork.
What Is Error Code 0x80070490?
The short version: it’s a Windows Update failure, often tied to driver-related issues or corrupted update files. But it can also involve registry errors, malformed configuration files, or missing system components.
In most cases, this error comes with no clear explanation. The update fails, the system rolls back, and you’re left guessing. What sets 0x80070490 apart from other update errors is how frequently it appears during major Windows feature upgrades, monthly rollup updates, servicing stack updates (SSUs), and general Windows patch installations.
Common Triggers for 0x80070490
This error doesn’t always stem from the same issue. Below are the most common reasons it might appear:
- Pending updates interfering with new ones.
- Corrupted or missing driver files.
- Registry keys left behind by failed installations.
- Broken or incomplete SetupConfig.ini files.
- Issues in the Component-Based Servicing (CBS) stack.
- Conflicts from previous update attempts.
Symptoms: How the Error Manifests
You’ll typically notice one of these behaviors:
- The update seems to install, then fails midway and rolls back.
- Windows Update shows “Install pending” or “Retry” next to the failed patch.
- Windows logs display repeated 0x80070490 entries in CBS or Setup logs.
- The update installer (e.g. WindowsUpdateBox.exe) exits with this error code.
Fixes Based on the Scenario
Windows 0x80070490 can appear in a few different contexts, and the fix depends on which type of update is failing. Below are targeted solutions based on real symptoms seen in Microsoft’s official guidance.
1. If the Update Is Stuck in “Pending” State
Sometimes a failed driver operation gets stuck and blocks the rest of the update chain. You’ll usually find entries like this in the CBS.log file:
Failed reading Identity for driver operation sequenceID 1 [HRESULT = 0x80070490 – ERROR_NOT_FOUND]
What to do:
- Open Registry Editor. Navigate to
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\DriverOperations\1 - Right-click on the 1 key and delete it. Then run this command in an elevated Command Prompt
sc config trustedinstaller start=auto - Restart the computer and try the update again from Windows Update.
2. If the Servicing Stack Update (SSU) Is Failing
Servicing Stack Updates are required before other updates can be installed. If the SSU itself fails, other updates may get stuck behind it.
What to do:
- Check the CBS.log file to confirm errors like
Failed loading driver operations queue [HRESULT = 0x80070490 – ERROR_NOT_FOUND] - Open Registry Editor.
- Go to
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\DriverOperations\0 - Export the key as a backup, then delete the 0 key – only if CBS.log confirms it’s causing the error.
- Download the latest Servicing Stack Update (SSU) from the Microsoft Update Catalog.
- Install the SSU, reboot the system, and retry the updates.
3. If Feature Updates Are Not Installing
Feature updates (like version upgrades) may fail with error 0x80070490 if the SetupConfig.ini file is missing, malformed, or improperly configured.
What to do:
- Check if the following file exists
C:\Users\Default\AppData\Local\Microsoft\Windows\WSUS\SetupConfig.ini - If it’s present and either empty or misconfigured, remove it or insert the following valid line
ShowOOBE=None - Make sure there are no spaces before or after the equals sign.
- Save the file and retry the upgrade via Windows Update or ISO.
4. If Cumulative Updates Fail
Cumulative updates may return 0x80070490 (often alongside 0x8e5e03fa) and fail during installation or rollback unexpectedly.
What to do?
Open Command Prompt as administrator, then run:
DISM /Online /Cleanup-Image /RestoreHealth
SFC /Scannow
Then reset the update components:
net stop cryptsvc
md %systemroot%\system32\catroot2.old
xcopy %systemroot%\system32\catroot2 %systemroot%\system32\catroot2.old /s
del %systemroot%\system32\catroot2\* /q /f
net start cryptsvc
net stop wuauserv
ren %systemroot%\SoftwareDistribution SoftwareDistribution.old
net start wuauserv
Reboot and attempt the update again.
5. If Monthly Rollups Fail (Especially on Older Servers)
On older systems like Windows Server 2012 R2, rollup updates can fail due to missing or corrupted driver files required during servicing.
What to do:
- Manually create the missing driver folder:
C:\Windows\System32\DriverStore\FileRepository\wvms_pp.inf_amd64_81d18de8dedd4cc4 - Then copy all .inf files from this source directory (adjust path for your system):
C:\Windows\WinSxS\amd64_wvms_pp.inf_* - Open Command Prompt and load the driver hive if needed:
reg load HKLM\DriverHive C:\Windows\System32\Config\DRIVERS - Then verify the driver is properly registered by checking this registry path:
HKEY_LOCAL_MACHINE\DriverHive\DriverDatabase\DriverInfFiles\wvms_pp.inf - Don’t forget to unload the hive when finished:
reg unload HKLM\DriverHive
Additional Tips Before You Try Again
Sometimes, the fix is about doing the basics right. Before diving into deeper troubleshooting, make sure you’ve taken these smart precautions.
Back Up First, Always
Before editing the registry or changing system folders, back up your system. Even experienced users can make a mistake, and having a restore point or system image means you’re not stuck if something unexpected breaks. It’s a quick step that can save hours of recovery time later.
Use Azure’s Built-In Backup (If Applicable)
If you’re working on a Windows Server or machine in Azure, take advantage of the snapshot feature. You can back up the entire VM directly from the Azure portal before making any changes. If anything goes wrong, rolling back is fast and painless.
Reboot Before You Retry
Run updates after a fresh reboot. It might seem obvious, but it matters. Some background processes from previous update attempts or software conflicts can quietly interfere. Starting clean gives Windows the best shot at getting through the update without issues.
Don’t Multitask During the Update
Avoid running heavy apps or tools while installing updates. It’s not always the cause of failure, but it can lead to slowdowns or memory conflicts that get in the way. Let the update do its thing without distractions.
Try the Microsoft Update Catalog
If you’ve tried everything and Windows Update still fails, go manual. Head to the Microsoft Update Catalog, search for the KB number of the update you need, and download the standalone installer. It’s a direct way to apply the patch without relying on Windows Update.
When to Involve Support
If you’ve already tried:
- Resetting update components
- Running DISM and SFC
- Registry edits or file replacements,
…and you’re still stuck, it might be time to contact Microsoft support or escalate via WSUS (if you’re in an enterprise environment). Make sure you include logs from:
- CBS.log
- WindowsUpdate.log
- Setupact.log
Quick Recap: Fix Checklist
If you’ve made it this far, you’ve seen how many different things can trigger error 0x80070490. To make things easier, here’s a no-fluff checklist of the main fixes we covered. You don’t have to try every single one, but this list gives you a clear order to work through based on the symptoms you’re seeing:
- Remove stale driver operations from the registry.
- Repair SSU with a fresh install.
- Edit or remove SetupConfig.ini.
- Run DISM and SFC tools.
- Reset Catroot2 and SoftwareDistribution.
- Restore missing driver files (if needed).
- Try manual installation from Microsoft Update Catalog.
Tackle them one at a time, check for progress after each step, and don’t rush. Fixing update errors can be a bit of a process, but most people don’t need to go beyond this list.
Final Thoughts
The 0x80070490 error is annoying, yes, but it’s not permanent. It’s a symptom of a deeper conflict inside Windows Update’s dependency chain. Whether it’s a driver file that’s missing, a registry key that’s blocking progress, or a corrupted config file, the fix is usually well within reach once you know where to look.
You don’t need advanced tools or expensive software. Most of the time, solving it just takes a bit of patience and knowing which part of the update process to check first.
FAQ
What does Windows error code 0x80070490 actually mean?
It usually means something went wrong during a Windows update, often related to drivers or corrupted update files. It doesn’t necessarily point to one specific issue, which is why it’s so frustrating. Think of it more like a generic “update failed” flag, and less like a precise diagnosis.
Can I fix error 0x80070490 without using third-party software?
Yes, absolutely. Everything you need is already built into Windows. Most fixes involve using tools like Command Prompt, checking the registry, or adjusting system files. You don’t need to download anything sketchy or pay for a repair tool.
Is it safe to delete registry keys as part of the fix?
It’s safe if you know exactly which key to remove and why. In this case, Microsoft’s own documentation recommends deleting specific DriverOperations keys that are left behind after failed updates. Just make sure to export a backup of any registry folder before making changes.
I ran DISM and SFC, but the error is still there. Now what?
If DISM and SFC didn’t clear it up, it usually means there’s a deeper issue, like a broken configuration file or missing driver reference. At that point, go one layer deeper: check for an invalid SetupConfig.ini file, or reset the Windows Update components manually. Those fixes often do the trick when the basic repair tools don’t.
Do I need to reinstall Windows if I keep getting this error?
Not unless everything else fails. Reinstalling Windows is kind of the nuclear option, and in most cases, not necessary. Try every targeted fix first – removing stale registry entries, fixing corrupted system files, and resetting update folders. Most people get the issue resolved long before needing a full reinstall.
How do I know which type of update is failing?
You can usually tell by where the error appears. If it’s during a feature update, the setup tool will crash and show the code. If it’s a monthly patch, you’ll see “failed” or “install pending” in Windows Update history. You can also check CBS.log or WindowsUpdate.log for more detailed clues.