some changes

Author: Deland-Han

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

@@ -5,22 +5,22 @@ ms.date: 04/08/2025
 manager: dcscontentpm
 audience: itpro
 ms.topic: troubleshooting
-ms.reviewer: ''
+ms.reviewer: scotro,mwesley
 ms.custom:
 - sap:windows servicing,updates and features on demand\windows update fails - installation stops with error
 - pcy:WinComm Devices Deploy
 ---
-# Troubleshoot Windows Update Error 0x80070490
+# Troubleshoot Windows update error 0x80070490
 
-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.
+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.
 
 :::image type="content" source="./media/troubleshoot-windows-update-error-0x80070490/update-error0x80070490-wusaerror.png" alt-text="Windows Update error 0x80070490":::
 
 ## Prerequisites
 
-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.
+Before proceeding with the mitigations, ensure you have backed up the OS disk. If you are using Windows in an Azure virtual machine, refer to the [Backup OS Disk](/azure/backup/backup-azure-vms) guide for detailed instructions.
 
-## Root Cause
+## Root cause
 
 The primary cause of error 0x80070490 is driver failure during Windows Update installations. This can occur due to:
 
@@ -29,7 +29,7 @@ The primary cause of error 0x80070490 is driver failure during Windows Update in
 - Corrupted or malformed SetupConfig.ini files.
 - Missing driver files or hardlinks in the system directories.
 
-## Symptom 1: Pending Update State
+## Symptom 1: Pending update state
 
 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:
 
@@ -42,7 +42,7 @@ Info CBS Failed initializing driver operation queue [HRESULT = 0x80070490 - ERRO
 Info CBS Perf: InstallUninstallChain complete.
 ```
 
-### Resolution: Resolve Pending Updates
+### Resolution: Resolve pending updates
 
 1. Remove the `1` folder from the registry path: `Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\DriverOperations\1`.
 2. Set the trusted installer to automatic state using the command:
@@ -51,9 +51,9 @@ Info CBS Perf: InstallUninstallChain complete.
    sc config trustedinstaller start= auto
    ```
 
-3. Attempt to install the updates again.
+3. Try install the updates again.
 
-## Symptom 2: Servicing Stack Update Failure
+## Symptom 2: Servicing stack update failure
 
 Servicing Stack Updates (SSU) may fail with error 0x80070490. Check the CBS.log for similar entries:
 
@@ -66,36 +66,36 @@ Info CBS Failed to execute execution chain. [HRESULT = 0x80070490 - ERROR_NOT_FO
 Error CBS Failed to process single phase execution. [HRESULT = 0x80070490 - ERROR_NOT_FOUND]
 ```
 
-### Resolution: Reinstall Servicing Stack Update
+### Resolution: Reinstall servicing stack update
 
 1. Export and delete the key at `HKLM\SOFTWARE\Microsoft\Windows\Currentversion\Component Based Servcing\Driver Operations\0`.
 2. Reinstall the Servicing Stack Update (SSU).
 
-## Symptom 3: Feature Update Installation Failure
+## Symptom 3: Feature update installation failure
 
 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:
 
 ```output
-08:16:58.62412 PM 1092 10968 downloadmanager_cpp16907 [DownloadManager] Preparing update for install, updateId = {0FFD49D9-5418-4D5E-9AA3-0163C0CCF57B}.202.
-08:16:58.62545 PM 11736 12104 uhwinsetup_cpp739 [Handler] * START * Windows Setup Install
-08:16:58.62545 PM 11736 12104 uhwinsetup_cpp741 [Handler] Updates to install = 1
-08:16:58.63458 PM 11736 12104 uhwinsetuppersisteddata_cpp233 [Handler] Loaded state. m_dwState now: Setup360_CompatToolPhase1(5)
-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
-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}
-08:16:58.63735 PM 11736 12104 uhwinsetupsession_cpp1673 [Handler] Successfully registered WinSetup COM server as CLSID {C8BD477B-2805-4B28-94FD-F99D02B19ED2}
-08:16:59.18463 PM 11736 12104 uhwinsetupsession_cpp458 [Handler] Installer completed. Process return code = 0x80070490, result = 0x80070490, callback pending = False
-08:16:59.18487 PM 11736 12104 setup360installer_cpp490 [Handler] Handler: Setup360 returned unknown error 80070490 for state 5, resetting state to Unknown
-08:16:59.18487 PM 11736 12104 uhwinsetuppersisteddata_cpp155 [Handler] State changed. was: Setup360_CompatToolPhase1(5), now: <invalid>(0)
-08:16:59.18546 PM 11736 12104 uhwinsetuppersisteddata_cpp296 [Handler] Saved state. m_dwState: <invalid>(0)
-08:16:59.18581 PM 11736 12104 uhwinsetup_cpp776 [Handler] Exit code = 0x80070490
+hh:mm:ss.fffff tt 1092 10968 downloadmanager_cpp16907 [DownloadManager] Preparing update for install, updateId = {0FFD49D9-5418-4D5E-9AA3-0163C0CCF57B}.202.
+hh:mm:ss.fffff tt 11736 12104 uhwinsetup_cpp739 [Handler] * START * Windows Setup Install
+hh:mm:ss.fffff tt 11736 12104 uhwinsetup_cpp741 [Handler] Updates to install = 1
+hh:mm:ss.fffff tt 11736 12104 uhwinsetuppersisteddata_cpp233 [Handler] Loaded state. m_dwState now: Setup360_CompatToolPhase1(5)
+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
+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}
+hh:mm:ss.fffff tt 11736 12104 uhwinsetupsession_cpp1673 [Handler] Successfully registered WinSetup COM server as CLSID {C8BD477B-2805-4B28-94FD-F99D02B19ED2}
+hh:mm:ss.fffff tt 11736 12104 uhwinsetupsession_cpp458 [Handler] Installer completed. Process return code = 0x80070490, result = 0x80070490, callback pending = False
+hh:mm:ss.fffff tt 11736 12104 setup360installer_cpp490 [Handler] Handler: Setup360 returned unknown error 80070490 for state 5, resetting state to Unknown
+hh:mm:ss.fffff tt 11736 12104 uhwinsetuppersisteddata_cpp155 [Handler] State changed. was: Setup360_CompatToolPhase1(5), now: <invalid>(0)
+hh:mm:ss.fffff tt 11736 12104 uhwinsetuppersisteddata_cpp296 [Handler] Saved state. m_dwState: <invalid>(0)
+hh:mm:ss.fffff tt 11736 12104 uhwinsetup_cpp776 [Handler] Exit code = 0x80070490
 ```
 
 ### Resolution: Fix SetupConfig.ini
 
 1. Remove or fix the `SetupConfig.ini` file located at `C:\Users\Default\AppData\Local\Microsoft\Windows\WSUS\SetupConfig.ini`.
 2. If the file is empty, add an entry such as `Show OOBE =None`.
 
-## Symptom 4: Cumulative Update Failure
+## Symptom 4: Cumulative update failure
 
 Cumulative updates may fail with error code 0x80070490 along with 0x8e5e03fa. Check the Setup Events logs for errors like:
 
@@ -107,7 +107,7 @@ Information XXXXX.corp. 3 Microsoft-Windows-Servicing N/A NT AUTHORITY\SYSTEM Pa
 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" ")
 ```
 
-### Resolution: Repair System Corruption
+### Resolution: Repair system corruption
 
 1. Start the corruption repair process:
 
@@ -137,7 +137,7 @@ Error XXXX.corp. 3 Microsoft-Windows-WUSA N/A CORP\xxa790741it5 Windows update "
 
 4. Install the patch.
 
-## Symptom 5: Monthly Rollup Update Failure
+## Symptom 5: Monthly rollup update failure
 
 Monthly rollup updates may fail with error code 0x80070490. Check the CBS log for entries like:
 
@@ -147,13 +147,13 @@ Info CBS Shtd: Rolling back KTM, because drivers failed.
 Info CBS Progress: UI message updated. Operation type: Update. Stage: 1 out of 1. Temporary Rollback.
 ```
 
-### Resolution: Address Missing Driver Files
+### Resolution: Address missing driver files
 
 1. Create the folder `wvms_pp.inf_amd64_81d18de8dedd4cc4` inside `C:\Windows\System32\DriverStore\FileRepository`.
 2. Copy all `.inf` files from `C:\Windows\WinSxS\amd64_wvms_pp.inf_31bf3856ad364e35_6.2.9200.22376_none_bc457897943a83fe`.
 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`.
 
-## Next Steps
+## Next steps
 
 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).