Skip to content

Commit 93e95d0

Browse files
committed
Merge branch 'cmpy-branch-ci4643' of https://github.com/Deland-Han/SupportArticles-docs-pr into cmpy-branch-ci4643
2 parents 5dc2a01 + e9f201a commit 93e95d0

File tree

3 files changed

+24
-24
lines changed

3 files changed

+24
-24
lines changed

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

File renamed without changes.

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

Lines changed: 23 additions & 23 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: Troubleshoot Windows Update Error 0x80070490
33
description: Learn how to resolve Windows Update error 0x80070490, which occurs due to driver failures during update installations.
4-
ms.date: 04/08/2025
4+
ms.date: 04/15/2025
55
manager: dcscontentpm
66
audience: itpro
77
ms.topic: troubleshooting
@@ -10,23 +10,23 @@ ms.custom:
1010
- sap:windows servicing,updates and features on demand\windows update fails - installation stops with error
1111
- pcy:WinComm Devices Deploy
1212
---
13-
# Troubleshoot Windows update error 0x80070490
13+
# Troubleshoot Windows Update error 0x80070490
1414

1515
Windows Update error 0x80070490 typically occurs due to driver failures when users or administrators try 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.
1616

17-
:::image type="content" source="./media/troubleshoot-windows-update-error-0x80070490/update-error0x80070490-wusaerror.png" alt-text="Windows Update error 0x80070490":::
17+
:::image type="content" source="./media/troubleshoot-windows-update-error-0x80070490/wusa-error-0x80070490.png" alt-text="Screenshot showing the Windows Update error 0x80070490." lightbox="./media/troubleshoot-windows-update-error-0x80070490/wusa-error-0x80070490.png":::
1818

1919
## Prerequisites
2020

21-
Before proceeding with the mitigations, ensure you have backed up the OS disk. If you're using Windows in an Azure virtual machine, refer to the [Backup OS Disk](/azure/backup/backup-azure-vms) guide for detailed instructions.
21+
Before proceeding with the mitigations, ensure you have backed up the OS disk. If you're using Windows in an Azure virtual machine (VM), refer to [Back up an Azure VM from the VM settings ](/azure/backup/backup-azure-vms) for detailed instructions.
2222

2323
## Root cause
2424

25-
The primary cause of error 0x80070490 is driver failure during Windows Update installations. This failure can occur due to:
25+
The primary cause of error 0x80070490 is driver failures during Windows Update installations. This failure can occur due to:
2626

2727
- Pending updates that block new installations.
2828
- Stale or incorrect registry entries related to driver operations.
29-
- Corrupted or malformed SetupConfig.ini files.
29+
- Corrupted or malformed **SetupConfig.ini** files.
3030
- Missing driver files or hard links in the system directories.
3131

3232
## CBS logs
@@ -37,7 +37,7 @@ The CBS logs locates at the `C:\Windows\Logs\CBS\CBS.log`. The log can roll over
3737

3838
## Symptom 1: Pending update state
3939

40-
When an update is in an Install Pending state, the driver operation might 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:
40+
When an update is in an "Install Pending" state, the driver operation might fail due to an inability to read the identity of the driver operation sequence ID 1. Check the CBS logs at `C:\Windows\Logs\CBS\CBS.log` for entries like:
4141

4242
```output
4343
Info CBS Failed reading Identity for driver operation sequenceID 1 [HRESULT = 0x80070490 - ERROR_NOT_FOUND]
@@ -51,17 +51,17 @@ Info CBS Perf: InstallUninstallChain complete.
5151
### Resolution: Resolve pending updates
5252

5353
1. Remove the `1` folder from the registry path: `Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\DriverOperations\1`.
54-
2. Set the trusted installer to automatic state using the command:
54+
2. Set the trusted installer to the automatic state using the command:
5555

5656
```console
5757
sc config trustedinstaller start=demand
5858
```
5959

60-
3. Try install the updates again.
60+
3. Try to install the updates again.
6161

6262
## Symptom 2: Servicing stack update failure
6363

64-
Servicing Stack Updates (SSU) might fail with error 0x80070490. Check the CBS.log for similar entries:
64+
Servicing stack updates (SSUs) might fail with error 0x80070490. Check the **CBS.log** file for entries like:
6565

6666
```output
6767
Error CBS Doqi: Failed loading driver operations queue. [HRESULT = 0x80070490 - ERROR_NOT_FOUND]
@@ -72,23 +72,23 @@ Info CBS Failed to execute execution chain. [HRESULT = 0x80070490 - ERROR_NOT_FO
7272
Error CBS Failed to process single phase execution. [HRESULT = 0x80070490 - ERROR_NOT_FOUND]
7373
```
7474

75-
### Resolution: Reinstall servicing stack update
75+
### Resolution: Reinstall the SSU
7676

7777
1. Export and delete the key at `HKLM\SOFTWARE\Microsoft\Windows\Currentversion\Component Based Servcing\Driver Operations\0`.
78-
2. Reinstall the Servicing Stack Update (SSU).
78+
2. Reinstall the SSU.
7979

8080
## Symptom 3: Feature update installation failure
8181

82-
Feature updates might 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:
82+
Feature updates might fail with error code 0x80070490. This behavior can be observed through **Check for updates** and in the Software Center (WSUS). Review the **WindowsUpdate.log** file for entries like:
8383

8484
```output
85-
hh:mm:ss.fffff tt 1092 10968 downloadmanager_cpp16907 [DownloadManager] Preparing update for install, updateId = {0FFD49D9-5418-4D5E-9AA3-0163C0CCF57B}.202.
85+
hh:mm:ss.fffff tt 1092 10968 downloadmanager_cpp16907 [DownloadManager] Preparing update for install, updateId = {UpdateID}.202.
8686
hh:mm:ss.fffff tt 11736 12104 uhwinsetup_cpp739 [Handler] * START * Windows Setup Install
8787
hh:mm:ss.fffff tt 11736 12104 uhwinsetup_cpp741 [Handler] Updates to install = 1
8888
hh:mm:ss.fffff tt 11736 12104 uhwinsetuppersisteddata_cpp233 [Handler] Loaded state. m_dwState now: Setup360_CompatToolPhase1(5)
89-
hh:mm:ss.fffff tt 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
90-
hh:mm:ss.fffff tt 11736 12104 uhwinsetupsession_cpp1655 [Handler] Registering WinSetup COM server as CLSID {C8BD477B-2805-4B28-94FD-F99D02B19ED2} and APPID {71ABC735-F46A-46BC-95B3-7E435F84FC19}
91-
hh:mm:ss.fffff tt 11736 12104 uhwinsetupsession_cpp1673 [Handler] Successfully registered WinSetup COM server as CLSID {C8BD477B-2805-4B28-94FD-F99D02B19ED2}
89+
hh:mm:ss.fffff tt 11736 12104 uhwinsetupsession_cpp322 [Handler] Starting Windows Setup with command line = "C:\Windows\SoftwareDistribution\Download\4222e87ece5856088671b07affd003c5\WindowsUpdateBox.exe" /ClassId <ClassID> /ReportId {ReportID}.202 /PreDownload /Update /ClientId <ClientID> /CorrelationVector cFZ4O8G6gEWSekro.2.1.2
90+
hh:mm:ss.fffff tt 11736 12104 uhwinsetupsession_cpp1655 [Handler] Registering WinSetup COM server as CLSID {CLSID} and APPID {APPID}
91+
hh:mm:ss.fffff tt 11736 12104 uhwinsetupsession_cpp1673 [Handler] Successfully registered WinSetup COM server as CLSID {CLSID}
9292
hh:mm:ss.fffff tt 11736 12104 uhwinsetupsession_cpp458 [Handler] Installer completed. Process return code = 0x80070490, result = 0x80070490, callback pending = False
9393
hh:mm:ss.fffff tt 11736 12104 setup360installer_cpp490 [Handler] Handler: Setup360 returned unknown error 80070490 for state 5, resetting state to Unknown
9494
hh:mm:ss.fffff tt 11736 12104 uhwinsetuppersisteddata_cpp155 [Handler] State changed. was: Setup360_CompatToolPhase1(5), now: <invalid>(0)
@@ -98,7 +98,7 @@ hh:mm:ss.fffff tt 11736 12104 uhwinsetup_cpp776 [Handler] Exit code = 0x80070490
9898

9999
### Resolution: Fix SetupConfig.ini
100100

101-
1. Remove or fix the `SetupConfig.ini` file located at `C:\Users\Default\AppData\Local\Microsoft\Windows\WSUS\SetupConfig.ini`.
101+
1. Remove or fix the **SetupConfig.ini** file located at `C:\Users\Default\AppData\Local\Microsoft\Windows\WSUS\SetupConfig.ini`.
102102
2. If the file is empty, add an entry such as `Show OOBE =None`.
103103

104104
## Symptom 4: Cumulative update failure
@@ -122,7 +122,7 @@ Error XXXX.corp. 3 Microsoft-Windows-WUSA N/A CORP\xxa790741it5 Windows update "
122122
SFC /Scannow
123123
```
124124

125-
2. Reset the content of the Catroot2 folder:
125+
2. Reset the contents of the **Catroot2** folder:
126126

127127
```console
128128
net stop cryptsvc
@@ -132,7 +132,7 @@ Error XXXX.corp. 3 Microsoft-Windows-WUSA N/A CORP\xxa790741it5 Windows update "
132132
net start cryptsvc
133133
```
134134

135-
3. Rename the Software Distribution folder:
135+
3. Rename the **Software Distribution** folder:
136136

137137
```console
138138
net stop wuauserv
@@ -155,10 +155,10 @@ Info CBS Progress: UI message updated. Operation type: Update. Stage: 1 out of 1
155155

156156
### Resolution: Address missing driver files
157157

158-
1. Create the folder `wvms_pp.inf_amd64_81d18de8dedd4cc4` inside `C:\Windows\System32\DriverStore\FileRepository`.
158+
1. Create the **wvms_pp.inf_amd64_81d18de8dedd4cc4** folder inside `C:\Windows\System32\DriverStore\FileRepository`.
159159
2. Copy all `.inf` files from `C:\Windows\WinSxS\amd64_wvms_pp.inf_31bf3856ad364e35_6.2.9200.22376_none_bc457897943a83fe`.
160-
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`.
160+
3. Load the driver hive and check for the `wvms_pp.inf` driver in the registry path: `HKEY_LOCAL_MACHINE\<Driver Hive>\DriverDatabase\DriverInfFiles\wvms_pp.inf`.
161161

162162
## Next steps
163163

164-
If the issue persists, consider engaging with the WSUS team for further assistance. You can also explore additional resources on Windows Update troubleshooting on [Guidance for troubleshooting Windows Server update](troubleshoot-windows-server-update-guidance.md).
164+
If the issue persists, consider engaging with the WSUS team for further assistance. You can also explore additional resources on Windows Update troubleshooting in the [Windows Server update troubleshooting guidance](troubleshoot-windows-server-update-guidance.md).

support/windows-server/toc.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -3047,7 +3047,7 @@ 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
3050+
- name: Troubleshoot Windows Update error 0x80070490
30513051
href: installing-updates-features-roles/troubleshoot-windows-update-error-0x80070490.md
30523052
- name: 'Troubleshooting guidance: Windows Server update'
30533053
href: ./installing-updates-features-roles/troubleshoot-windows-server-update-guidance.md

0 commit comments

Comments
 (0)