Skip to content

Commit 6a3d4ee

Browse files
Deland-HanDeland-Han
committed
update
1 parent c102764 commit 6a3d4ee

3 files changed

Lines changed: 168 additions & 0 deletions

File tree

‎support/windows-server/installing-updates-features-roles/media/troubleshoot-windows-update-error-0x80070490/update-error0x80070490-wusaerror.png‎

72 KB
Loading

‎support/windows-server/installing-updates-features-roles/troubleshoot-windows-update-error-0x80070490.md‎

Lines changed: 166 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,166 @@
1+
---
2+
title: Troubleshoot Windows Update Error 0x80070490
3+
description: Learn how to resolve Windows Update error 0x80070490, which occurs due to driver failures during update installations.
4+
ms.date: 04/08/2025
5+
manager: dcscontentpm
6+
audience: itpro
7+
ms.topic: troubleshooting
8+
ms.reviewer: ''
9+
ms.custom:
10+
- sap:add_sap
11+
- pcy:add_pcy
12+
---
13+
# Troubleshoot Windows Update Error 0x80070490
14+
15+
Windows Update error 0x80070490 typically occurs due to driver failures when users or administrators attempt to install updates. This document provides a comprehensive guide to identifying and resolving this error, which can manifest in various symptoms such as pending updates, failed servicing stack updates, and feature update installation failures.
16+
17+
:::image type="content" source="./media/troubleshoot-windows-update-error-0x80070490/update-error0x80070490-wusaerror.png" alt-text="Windows Update error 0x80070490":::
18+
19+
## Prerequisites
20+
21+
Before proceeding with the mitigations, ensure you have backed up the OS disk. Refer to the [Backup OS Disk](https://learn.microsoft.com/azure/backup/backup-azure-vms) guide for detailed instructions.
22+
23+
## How to Identify the Issue
24+
25+
### Symptom 1: Pending Update State
26+
27+
When an update is in an Install Pending state, the driver operation may fail due to an inability to read the identity for driver operation sequence ID 1. Check the CBS logs at `C:\Windows\Logs\CBS\CBS.log` for entries like:
28+
29+
```output
30+
Info CBS Failed reading Identity for driver operation sequenceID 1 [HRESULT = 0x80070490 - ERROR_NOT_FOUND]
31+
Info CBS Failed loading a driver operation [HRESULT = 0x80070490 - ERROR_NOT_FOUND]
32+
Error CBS Doqi: Failed loading driver operations queue. [HRESULT = 0x80070490 - ERROR_NOT_FOUND]
33+
Info CBS Failed loading driver operation queue [HRESULT = 0x80070490 - ERROR_NOT_FOUND]
34+
Info CBS Failed initializing driver operation queue [HRESULT = 0x80070490 - ERROR_NOT_FOUND]
35+
Info CBS Perf: InstallUninstallChain complete.
36+
```
37+
38+
### Symptom 2: Servicing Stack Update Failure
39+
40+
Servicing Stack Updates (SSU) may fail with error 0x80070490. Check the CBS.log for similar entries:
41+
42+
```output
43+
Error CBS Doqi: Failed loading driver operations queue. [HRESULT = 0x80070490 - ERROR_NOT_FOUND]
44+
Info CBS Failed initializing driver operation queue [HRESULT = 0x80070490 - ERROR_NOT_FOUND]
45+
Info CBS Perf: InstallUninstallChain complete.
46+
Info CSI 000013c6@2020/2/6:18:53:04.849 CSI Transaction @0x1d2174564c0 destroyed
47+
Info CBS Failed to execute execution chain. [HRESULT = 0x80070490 - ERROR_NOT_FOUND]
48+
Error CBS Failed to process single phase execution. [HRESULT = 0x80070490 - ERROR_NOT_FOUND]
49+
```
50+
51+
### Symptom 3: Feature Update Installation Failure
52+
53+
Feature updates may fail with error code 0x80070490. This behavior can be observed through "Check for updates" and in Software Center (WSUS). Review the WindowsUpdate.log for entries like:
54+
55+
```output
56+
08:16:58.62412 PM 1092 10968 downloadmanager_cpp16907 [DownloadManager] Preparing update for install, updateId = {0FFD49D9-5418-4D5E-9AA3-0163C0CCF57B}.202.
57+
08:16:58.62545 PM 11736 12104 uhwinsetup_cpp739 [Handler] * START * Windows Setup Install
58+
08:16:58.62545 PM 11736 12104 uhwinsetup_cpp741 [Handler] Updates to install = 1
59+
08:16:58.63458 PM 11736 12104 uhwinsetuppersisteddata_cpp233 [Handler] Loaded state. m_dwState now: Setup360_CompatToolPhase1(5)
60+
08:16:58.63518 PM 11736 12104 uhwinsetupsession_cpp322 [Handler] Starting Windows Setup with command line = "C:\Windows\SoftwareDistribution\Download\4222e87ece5856088671b07affd003c5\WindowsUpdateBox.exe" /ClassId c8bd477b-2805-4b28-94fd-f99d02b19ed2 /ReportId {0FFD49D9-5418-4D5E-9AA3-0163C0CCF57B}.202 /PreDownload /Update /ClientId ce729943-30ea-47ab-8f3b-24890a4c3e14 /CorrelationVector cFZ4O8G6gEWSekro.2.1.2
61+
08:16:58.63519 PM 11736 12104 uhwinsetupsession_cpp1655 [Handler] Registering WinSetup COM server as CLSID {C8BD477B-2805-4B28-94FD-F99D02B19ED2} and APPID {71ABC735-F46A-46BC-95B3-7E435F84FC19}
62+
08:16:58.63735 PM 11736 12104 uhwinsetupsession_cpp1673 [Handler] Successfully registered WinSetup COM server as CLSID {C8BD477B-2805-4B28-94FD-F99D02B19ED2}
63+
08:16:59.18463 PM 11736 12104 uhwinsetupsession_cpp458 [Handler] Installer completed. Process return code = 0x80070490, result = 0x80070490, callback pending = False
64+
08:16:59.18487 PM 11736 12104 setup360installer_cpp490 [Handler] Handler: Setup360 returned unknown error 80070490 for state 5, resetting state to Unknown
65+
08:16:59.18487 PM 11736 12104 uhwinsetuppersisteddata_cpp155 [Handler] State changed. was: Setup360_CompatToolPhase1(5), now: <invalid>(0)
66+
08:16:59.18546 PM 11736 12104 uhwinsetuppersisteddata_cpp296 [Handler] Saved state. m_dwState: <invalid>(0)
67+
08:16:59.18581 PM 11736 12104 uhwinsetup_cpp776 [Handler] Exit code = 0x80070490
68+
```
69+
70+
### Symptom 4: Cumulative Update Failure
71+
72+
Cumulative updates may fail with error code 0x80070490 along with 0x8e5e03fa. Check the Setup Events logs for errors like:
73+
74+
```output
75+
Information XXXXXXX.corp. 1 Microsoft-Windows-Servicing N/A NT AUTHORITY\SYSTEM Initiating changes for package KB5004122. Current state is Resolved. Target state is Installed. Client id: WindowsUpdateAgent.
76+
Information XXXXX.corp. 3 Microsoft-Windows-Servicing N/A NT AUTHORITY\SYSTEM Package KB5004122 failed to be changed to the Installed state. Status: 0x8e5e03fa.
77+
Information XXXXX.corp. 1 Microsoft-Windows-Servicing N/A NT AUTHORITY\SYSTEM Initiating changes for package KB5004298. Current state is Resolved. Target state is Installed. Client id: WindowsUpdateAgent.
78+
Information XXXXX.corp. 3 Microsoft-Windows-Servicing N/A NT AUTHORITY\SYSTEM Package KB5004298 failed to be changed to the Installed state. Status: 0x8e5e03fa.
79+
Error XXXX.corp. 3 Microsoft-Windows-WUSA N/A CORP\xxa790741it5 Windows update "Security Update for Windows (KB5004298)" could not be installed because of error 2388526074 "" (Command line: ""C:\Windows\system32\wusa.exe" "C:\Users\XXXXX\Desktop\WS2012R2-072021\windows8.1-kb5004298-x64_e98bbac284034aac90559c0d311967d97ebfc0e5.msu" ")
80+
```
81+
82+
### Symptom 5: Monthly Rollup Update Failure
83+
84+
Monthly rollup updates may fail with error code 0x80070490. Check the CBS log for entries like:
85+
86+
```output
87+
Error CBS Shtd: Failed while processing non-critical driver operationsqueue. [HRESULT = 0x80070490 – ERROR_NOT_FOUND]
88+
Info CBS Shtd: Rolling back KTM, because drivers failed.
89+
Info CBS Progress: UI message updated. Operation type: Update. Stage: 1 out of 1. Temporary Rollback.
90+
```
91+
92+
## Root Cause
93+
94+
The primary cause of error 0x80070490 is driver failure during Windows Update installations. This can occur due to:
95+
96+
- Pending updates that block new installations.
97+
- Stale or incorrect registry entries related to driver operations.
98+
- Corrupted or malformed SetupConfig.ini files.
99+
- Missing driver files or hardlinks in the system directories.
100+
101+
## Resolution or Troubleshooting Steps
102+
103+
### Mitigation 1: Resolve Pending Updates
104+
105+
1. Remove the `1` folder from the registry path: `Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\DriverOperations\1`.
106+
2. Set the trusted installer to automatic state using the command:
107+
108+
```bash
109+
sc config trustedinstaller start= auto
110+
```
111+
112+
3. Attempt to install the updates again.
113+
114+
### Mitigation 2: Reinstall Servicing Stack Update
115+
116+
1. Export and delete the key at `HKLM\SOFTWARE\Microsoft\Windows\Currentversion\Component Based Servcing\Driver Operations\0`.
117+
2. Reinstall the Servicing Stack Update (SSU).
118+
119+
### Mitigation 3: Fix SetupConfig.ini
120+
121+
1. Remove or fix the `SetupConfig.ini` file located at `C:\Users\Default\AppData\Local\Microsoft\Windows\WSUS\SetupConfig.ini`.
122+
2. If the file is empty, add an entry such as `Show OOBE =None`.
123+
124+
### Mitigation 4: Repair System Corruption
125+
126+
1. Start the corruption repair process:
127+
128+
```bash
129+
DISM /Online /Cleanup-Image /RestoreHealth
130+
SFC /Scannow
131+
```
132+
133+
2. Reset the content of the Catroot2 folder:
134+
135+
```bash
136+
net stop cryptsvc
137+
md %systemroot%\system32\catroot2.old
138+
xcopy %systemroot%\system32\catroot2 %systemroot%\system32\catroot2.old /s
139+
del %systemroot%\system32\catroot2\* /q
140+
net start cryptsvc
141+
```
142+
143+
3. Rename the Software Distribution folder:
144+
145+
```bash
146+
net stop wuauserv
147+
cd %systemroot%
148+
ren SoftwareDistribution SoftwareDistribution.old
149+
net start wuauserv
150+
```
151+
152+
4. Install the patch.
153+
154+
### Mitigation 5: Address Missing Driver Files
155+
156+
1. Create the folder `wvms_pp.inf_amd64_81d18de8dedd4cc4` inside `C:\Windows\System32\DriverStore\FileRepository`.
157+
2. Copy all `.inf` files from `C:\Windows\WinSxS\amd64_wvms_pp.inf_31bf3856ad364e35_6.2.9200.22376_none_bc457897943a83fe`.
158+
3. Load the driver hive and check for the driver `wvms_pp.inf` in the registry path: `HKEY_LOCAL_MACHINE\<Driver Hive>\DriverDatabase\DriverInfFiles\wvms_pp.inf`.
159+
160+
## Next Steps
161+
162+
If the issue persists, consider engaging with the WSUS team for further assistance. You can also explore additional resources on Windows Update troubleshooting on [Microsoft Learn](https://learn.microsoft.com/windows/deployment/update/windows-update-troubleshoot).
163+
164+
**Partial Use of AI disclaimer**
165+
166+
Certain sections of this document have been generated or enhanced using artificial intelligence (AI) technology.

‎support/windows-server/toc.yml‎

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -3047,6 +3047,8 @@ items:
30473047
href: ./installing-updates-features-roles/wsus-clients-cant-install-updates.md
30483048
- name: Windows Update fails - installation stops with error
30493049
items:
3050+
- name: Troubleshoot Windows Update Error 0x80070490
3051+
href: installing-updates-features-roles/troubleshoot-windows-update-error-0x80070490.md
30503052
- name: 'Troubleshooting guidance: Windows Server update'
30513053
href: ./installing-updates-features-roles/troubleshoot-windows-server-update-guidance.md
30523054
- name: CBS.log file contains entries that some files aren't repaired

0 commit comments

Comments
 (0)