Skip to content

Commit 4952373

Browse files
committed
Updates from editor
1 parent e82f243 commit 4952373

2 files changed

Lines changed: 18 additions & 18 deletions

File tree

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: 18 additions & 18 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
@@ -14,24 +14,24 @@ ms.custom:
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
## Symptom 1: Pending update state
3333

34-
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:
34+
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:
3535

3636
```output
3737
Info CBS Failed reading Identity for driver operation sequenceID 1 [HRESULT = 0x80070490 - ERROR_NOT_FOUND]
@@ -45,17 +45,17 @@ Info CBS Perf: InstallUninstallChain complete.
4545
### Resolution: Resolve pending updates
4646

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

5050
```console
5151
sc config trustedinstaller start=demand
5252
```
5353

54-
3. Try install the updates again.
54+
3. Try to install the updates again.
5555

5656
## Symptom 2: Servicing stack update failure
5757

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

6060
```output
6161
Error CBS Doqi: Failed loading driver operations queue. [HRESULT = 0x80070490 - ERROR_NOT_FOUND]
@@ -66,14 +66,14 @@ Info CBS Failed to execute execution chain. [HRESULT = 0x80070490 - ERROR_NOT_FO
6666
Error CBS Failed to process single phase execution. [HRESULT = 0x80070490 - ERROR_NOT_FOUND]
6767
```
6868

69-
### Resolution: Reinstall servicing stack update
69+
### Resolution: Reinstall the SSU
7070

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

7474
## Symptom 3: Feature update installation failure
7575

76-
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:
76+
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:
7777

7878
```output
7979
hh:mm:ss.fffff tt 1092 10968 downloadmanager_cpp16907 [DownloadManager] Preparing update for install, updateId = {0FFD49D9-5418-4D5E-9AA3-0163C0CCF57B}.202.
@@ -92,7 +92,7 @@ hh:mm:ss.fffff tt 11736 12104 uhwinsetup_cpp776 [Handler] Exit code = 0x80070490
9292

9393
### Resolution: Fix SetupConfig.ini
9494

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

9898
## Symptom 4: Cumulative update failure
@@ -116,7 +116,7 @@ Error XXXX.corp. 3 Microsoft-Windows-WUSA N/A CORP\xxa790741it5 Windows update "
116116
SFC /Scannow
117117
```
118118

119-
2. Reset the content of the Catroot2 folder:
119+
2. Reset the contents of the **Catroot2** folder:
120120

121121
```console
122122
net stop cryptsvc
@@ -126,7 +126,7 @@ Error XXXX.corp. 3 Microsoft-Windows-WUSA N/A CORP\xxa790741it5 Windows update "
126126
net start cryptsvc
127127
```
128128

129-
3. Rename the Software Distribution folder:
129+
3. Rename the **Software Distribution** folder:
130130

131131
```console
132132
net stop wuauserv
@@ -149,10 +149,10 @@ Info CBS Progress: UI message updated. Operation type: Update. Stage: 1 out of 1
149149

150150
### Resolution: Address missing driver files
151151

152-
1. Create the folder `wvms_pp.inf_amd64_81d18de8dedd4cc4` inside `C:\Windows\System32\DriverStore\FileRepository`.
152+
1. Create the **wvms_pp.inf_amd64_81d18de8dedd4cc4** folder inside `C:\Windows\System32\DriverStore\FileRepository`.
153153
2. Copy all `.inf` files from `C:\Windows\WinSxS\amd64_wvms_pp.inf_31bf3856ad364e35_6.2.9200.22376_none_bc457897943a83fe`.
154-
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`.
154+
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`.
155155

156156
## Next steps
157157

158-
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).
158+
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).

0 commit comments

Comments
 (0)