Error 0x80070490 When Uninstalling Windows Update

Use this when Windows returns 0x80070490 while uninstalling an update.

Quick Read

Symptom: Use this when Windows returns 0x80070490 while uninstalling an update.
Check first: Confirm OS build, domain or workgroup state, local admin rights, and whether the host is managed by GPO, Intune, or another baseline.
Risk: Changes system state

Symptoms

Users encounter the error code 0x80070490 while attempting to uninstall certain Windows updates. This error code typically signifies potential corruption within essential system files or conflicts among Windows Update components. Failing to uninstall these updates can lead to various complications such as system instability, degraded performance, and software incompatibility. These issues not only hinder optimal operation but can also put the overall functionality of your operating system at risk. Therefore, it is imperative to diagnose and resolve this problem swiftly to safeguard your system's health.

Environment

Windows 10 and Windows 11 devices where Windows Update cannot install, uninstall, or service an update cleanly.

Most Likely Causes

Error 0x80070490 usually means Windows cannot find or use part of the servicing metadata it expects. Common causes include component store corruption, damaged update cache data, interrupted servicing operations, or policy/security tools blocking the update workflow.

What to Check First

Confirm OS build, domain or workgroup state, local admin rights, and whether the host is managed by GPO, Intune, or another baseline.
Collect the exact error code, Event Viewer entries, and the command or UI action that triggers the failure.
Check whether the issue follows the user profile, machine, network, or application package.

Insight Cluster

Parent question: How do we approach Windows recovery so evidence, repair-path choice, validation, and rollback are stronger than the outage pressure?

Planning Windows Recovery and Repair Without Making the Outage Worse (parent Insight)
Windows Evidence-First Recovery Workflow Before Repair Commands (supporting Insight)
Comparing Windows Repair Paths: SFC, DISM, Restore, Rollback, and Reinstall (supporting Insight)
Troubleshooting Windows 11 Restore Recovery Failures (tactical leaf)
In-Depth Troubleshooting of Windows 11 Update Errors (tactical leaf)
Troubleshooting: Unable to Exit S Mode on Windows 11 (tactical leaf)
Troubleshooting RDP Disconnections on Windows Server 2025 due to Security Group Misconfigurations (tactical leaf)
Troubleshooting RDS Broker Connection Issues on Windows Server (tactical leaf)

This Windows parent Insight is meant to keep the site from treating every repair command page as a top-level strategy article.
The supporting pages frame evidence collection and repair-path choice before operators drop into exact failure leaves.

Fix Steps

Run Windows Update Troubleshooter
Start diagnosing the issue with the built-in Windows Update Troubleshooter. This tool is specifically designed to identify and automatically resolve many common issues associated with Windows Updates, potentially offering a quick solution.
Example pattern only. Adjust for your environment before running.
```
Settings > Update & Security > Troubleshoot > Additional troubleshooters > Windows Update > Run the troubleshooter
```
Reset Windows Update Components
If the troubleshooter does not rectify the issue, you can manually reset the Windows Update components. This process involves stopping relevant services and deleting temporary files that could cause conflicts, thus ensuring a clean slate for the update system.
Example pattern only. Adjust for your environment before running.
```
net stop wuauserv
net stop cryptSvc
net stop bits
net stop msiserver
del %windir%\SoftwareDistribution\*.* /s /q
del %windir%\System32\catroot2\*.* /s /q
net start wuauserv
net start cryptSvc
net start bits
net start msiserver
```
Run DISM Tool
Utilize the Deployment Image Servicing and Management (DISM) tool to inspect and rectify any corrupted system images. DISM is particularly useful for addressing complex issues that may affect Windows components, offering a deeper level of diagnostic power.
Example pattern only. Adjust for your environment before running.
```
DISM /Online /Cleanup-Image /RestoreHealth
```
Run System File Checker
Employ the System File Checker (SFC) tool to scan for and repair missing or corrupt system files. This tool is essential for ensuring that foundational system files necessary for Windows Update and overall stability are intact.
Example pattern only. Adjust for your environment before running.
```
sfc /scannow
```
Check Windows Registry
Examine the Windows Registry for any corrupted or missing entries that may disrupt various Windows functionalities, including updates. Ensuring that registry settings are accurate and intact is critical for maintaining system integrity and functioning.
Example pattern only. Adjust for your environment before running.
```
regedit.exe
```

Validation

The failing Windows action completes after reboot or service restart if the remediation requires one.
Event Viewer stops logging the same error ID for the same component during a retest.
The fix works for the affected standard user context, not only for an elevated administrator session.

Logs to Check

Event Viewer: System, Application, Setup, WindowsUpdateClient, TerminalServices, or PowerShell logs as relevant.
CBS.log, DISM.log, or WindowsUpdate.log when servicing or feature installation is involved.
Security, RDP, or application-specific logs for authentication and session failures.

Rollback and Escalation

Record the original registry, service, feature, policy, or firewall value before changing it.
Undo temporary local policy, firewall, or service changes after validation.
Use a restore point, VM snapshot, or exported configuration when changing servicing, boot, or security settings.

Escalate When

Escalate if the same error persists after rollback and a clean retry from the original failing path.
Escalate if logs show authorization, data loss, certificate, replication, or production availability risk outside the local service owner scope.

Edge Cases

The error continues to persist even after implementing all suggested troubleshooting steps, indicating a more profound issue possibly requiring professional intervention.
Consider performing a repair installation of Windows if the problem persists after going through the entire troubleshooting process, which reinstalls Windows while keeping personal files intact.

Notes from the Field

If the machine is domain-managed, local fixes can be overwritten. Check the winning GPO or MDM policy before repeating the same change.
Prefer read-only collection first on Windows incidents because many repair commands change component store, services, or user profile state.