|
| 1 | +--- |
| 2 | +title: Error 0x80070003 at Startup after You Install a Windows Update |
| 3 | +description: Discusses how to fix Windows Update error 0x80070003. When this issue occurs, the update can't install correctly. After the computer restarts, the installation rolls back. |
| 4 | +manager: dcscontentpm |
| 5 | +audience: itpro |
| 6 | +ms.date: 12/30/2025 |
| 7 | +ai.usage: ai-assisted |
| 8 | +ms.topic: troubleshooting |
| 9 | +ms.reviewer: kaushika, dougking, v-appelgatet |
| 10 | +ms.custom: |
| 11 | +- sap:windows servicing,updates and features on demand\windows update fails - installation stops with error |
| 12 | +- pcy:WinComm Devices Deploy |
| 13 | +appliesto: |
| 14 | +- ✅ <a href=https://learn.microsoft.com/windows/release-health/supported-versions-windows-client target=_blank>Supported versions of Windows Client</a> |
| 15 | +- ✅ <a href=https://learn.microsoft.com/windows/release-health/windows-server-release-info target=_blank>Supported versions of Windows Server</a> |
| 16 | +- ✅ <a href=https://learn.microsoft.com/lifecycle/products/windows-365target=_blank>Supported versions of Windows 365</a> |
| 17 | +- <a href=https://learn.microsoft.com/lifecycle/products/azure-virtual-machine target=_blank>Supported versions of Azure Virtual Machine</a> |
| 18 | +--- |
| 19 | +# Error 0x80070003 at startup after you install a Windows update |
| 20 | + |
| 21 | +This article discusses how to fix Windows Update error 0x80070003. When this issue occurs, the update can't install correctly. After the computer restarts, the installation rolls back. |
| 22 | + |
| 23 | +## Symptoms |
| 24 | + |
| 25 | +When you try to install a Windows update, the installation fails, and you receive the following error message: |
| 26 | + |
| 27 | +> Some update files are missing or have problems. We'll try to download the update again later. Error code: (0x80070003). |
| 28 | +
|
| 29 | +## Cause |
| 30 | + |
| 31 | +This error typically means that driver files are missing or inaccessible. |
| 32 | + |
| 33 | +## Resolution |
| 34 | + |
| 35 | +> [!IMPORTANT] |
| 36 | +> |
| 37 | +> - If the affected computer is a Windows virtual machine (VM) that can't restart correctly or that you can't access by using SSH, make sure that you can use the Azure Serial Console to access the VM. |
| 38 | +> - Before you troubleshoot this issue, back up the operating system disk. For information about this process for VMs, see [About Azure Virtual Machine restore](/azure/backup/about-azure-vm-restore). |
| 39 | +
|
| 40 | +The most reliable way to fix this issue is to perform an in-place upgrade on the affected computer. |
| 41 | + |
| 42 | +> [!NOTE] |
| 43 | +> For more information about how to upgrade VMs, see one of the following articles: |
| 44 | +> |
| 45 | +> - [In-place upgrade for VMs running Windows Server in Azure](/azure/virtual-machines/windows-in-place-upgrade) |
| 46 | +> - [In-place upgrade for supported VMs running Windows in Azure (Windows client)](../../azure/virtual-machines/windows/in-place-system-upgrade.md) |
| 47 | +
|
| 48 | +If you experience error 0x80070003 during the in-place upgrade, see ["0x80070003" error and Windows upgrade fails during "Process Drivers for Migration"](../setup-upgrade-and-drivers/error-0x80070003-during-process-drivers-for-migration.md). |
| 49 | + |
| 50 | +If the issue persists, contact Microsoft Support. In the support request, share the path or file that isn't found. For information about how to identify this information, see the next section. |
| 51 | + |
| 52 | +## More information |
| 53 | + |
| 54 | +To identify the path that Windows Update can't find, follow these steps: |
| 55 | + |
| 56 | +1. On the affected computer, go to the %Windir%\logs\CBS folder (%Windir% represents the Windows directory on the computer's system drive). |
| 57 | +1. Use a text editor to open the most recent CBS.log file, and search for a ", error" string. |
| 58 | +1. Check the log entries that share the same timestamp as the error, and locate the path that's related to the error. |
| 59 | + |
| 60 | + For example, the following excerpt shows that the issue occurred during the installation of Ntprint.inf (the Windows printer driver): |
| 61 | + |
| 62 | + ```output |
| 63 | + 2017-12-06 15:30:46, Info CBS INSTALL index: 69, phase: 1, result 3, inf: ntprint4.inf |
| 64 | + 2017-12-06 15:30:46, Info CBS Doqe: Recording result: 0x80070003, for Inf: ntprint4.inf |
| 65 | + 2017-12-06 15:30:46, Info CBS DriverUpdateInstallUpdates failed [HRESULT = 0x80070003 - ERROR_PATH_NOT_FOUND] |
| 66 | + 2017-12-06 15:30:46, Info CBS Doqe: Failed installing driver updates [HRESULT = 0x80070003 - ERROR_PATH_NOT_FOUND] |
| 67 | + 2017-12-06 15:30:46, Info CBS Perf: Doqe: Install ended. |
| 68 | + 2017-12-06 15:30:46, Info CBS Failed installing driver updates [HRESULT = 0x80070003 - ERROR_PATH_NOT_FOUND] |
| 69 | + 2017-12-06 15:30:46, Error CBS Startup: Failed while processing non-critical driver operations queue. [HRESULT = 0x80070003 - ERROR_PATH_NOT_FOUND] |
| 70 | + 2017-12-06 15:30:46, Info CBS Startup: Rolling back KTM, because drivers failed. |
| 71 | + 2017-12-06 15:30:46, Info CBS Setting ExecuteState key to: CbsExecuteStateStageDrivers | CbsExecuteStateFlagRollback | CbsExecuteStateFlagDriversFailed |
| 72 | + 2017-12-06 15:30:46, Info CBS SetProgressMessage: progressMessageStage: -1, ExecuteState: CbsExecuteStateStageDrivers | CbsExecuteStateFlagRollback | CbsExecuteStateFlagDriversFailed, SubStage: 0 |
| 73 | + 2017-12-06 15:30:46, Info CBS Progress: UI message updated. Operation type: Update. Stage: 1 out of 1. Rollback. |
| 74 | + 2017-12-06 15:30:46, Info CBS Setting original failure status: 0x80070003, last forward execute state: CbsExecuteStatePrimitives |
| 75 | + 2017-12-06 15:30:46, Info CBS SetProgressMessage: progressMessageStage: -1, ExecuteState: CbsExecuteStateStageDrivers | CbsExecuteStateFlagRollback | CbsExecuteStateFlagDriversFailed, SubStage: 1 |
| 76 | + ``` |
![learn-build-service-prod[bot]](https://avatars.githubusercontent.com/in/237442?v=4&size=40){kind=avatar}
0 commit comments