Skip to content

Commit ea464d6

Browse files
committed
AB#7607: Troubleshoot Update Error 0x80070003 While Installing Windows Updates
New article for [CI 7607](https://dev.azure.com/KMOps/ContentExperience/_queries/edit/7607)
1 parent a9ec5ac commit ea464d6

1 file changed

Lines changed: 73 additions & 0 deletions

File tree

Lines changed: 73 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,73 @@
1+
---
2+
title: Error 0x80070003 when Windows Update Fails
3+
description: Learn how to resolve the update error 0x80070003 encountered during Windows update installations.
4+
manager: dcscontentpm
5+
audience: itpro
6+
ms.date: 12/30/2025
7+
ms.topic: troubleshooting
8+
ms.reviewer: kaushika, dougking, v-appelgatet
9+
ms.custom:
10+
- sap:windows servicing,updates and features on demand\windows update fails - installation stops with error
11+
- pcy:WinComm Devices Deploy
12+
appliesto:
13+
- ✅ <a href=https://learn.microsoft.com/windows/release-health/supported-versions-windows-client target=_blank>Supported versions of Windows Client</a>
14+
- ✅ <a href=https://learn.microsoft.com/windows/release-health/windows-server-release-info target=_blank>Supported versions of Windows Server</a>
15+
- ✅ <a href=https://learn.microsoft.com/lifecycle/products/windows-365target=_blank>Supported versions of Windows 365</a>
16+
- <a href=https://learn.microsoft.com/lifecycle/products/azure-virtual-machine target=_blank>Supported versions of Azure Virtual Machine</a>
17+
---
18+
# Error 0x80070003 when Windows Update fails
19+
20+
This article describes how to resolve Windows Update error 0x80070003, which causes the update to fail to install, or to roll back the installation after the computer restarts.
21+
22+
## Symptoms
23+
24+
When you install a Windows update, the update fails and you see the following error message:
25+
26+
> Some update files are missing or have problems. We'll try to download the update again later. Error code: (0x80070003).
27+
28+
## Cause
29+
30+
This error typically means that driver files are missing or inaccessible.
31+
32+
## Resolution
33+
34+
> [!NOTE]
35+
> If the affected computer is a Windows virtual machine (VM), and it can't restart correctly or if you can't use SSH to access it, make sure that you can use the Azure Serial Console to access it.
36+
37+
The most reliable way to fix this issue is to perform an in-place upgrade on the affected computer.
38+
39+
> [!NOTE]
40+
> For more information about upgrading VMs, see one of the following articles:
41+
42+
- [In-place upgrade for VMs running Windows Server in Azure](/azure/virtual-machines/windows-in-place-upgrade)
43+
- [In-place upgrade for supported VMs running Windows in Azure (Windows client)](../../../azure/virtual-machines/windows/in-place-system-upgrade.md)
44+
45+
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).
46+
47+
If the issue persists, contact Microsoft Support. List the path or file that wasn't found in the support request. For information about how to identify this information, see [More information](#more-information).
48+
49+
## More information
50+
51+
To identify the path that could not be accessed, follow these steps:
52+
53+
1. On the affected computer, go to the %Windir%\logs\CBS folder (%Windir% represents the Windows directory on the computer's system drive).
54+
1. Use a text editor to open the most recent CBS.log file, and search for a ", error" string.
55+
1. Check the log entries that share the same timestamp as the error and look for the path that is related to the error.
56+
57+
For example, the following excerpt shows that the issue occurred during the installation of ntprint.inf (the Windows printer driver):
58+
59+
```output
60+
2017-12-06 15:30:46, Info CBS INSTALL index: 69, phase: 1, result 3, inf: ntprint4.inf
61+
2017-12-06 15:30:46, Info CBS Doqe: Recording result: 0x80070003, for Inf: ntprint4.inf
62+
2017-12-06 15:30:46, Info CBS DriverUpdateInstallUpdates failed [HRESULT = 0x80070003 - ERROR_PATH_NOT_FOUND]
63+
2017-12-06 15:30:46, Info CBS Doqe: Failed installing driver updates [HRESULT = 0x80070003 - ERROR_PATH_NOT_FOUND]
64+
2017-12-06 15:30:46, Info CBS Perf: Doqe: Install ended.
65+
2017-12-06 15:30:46, Info CBS Failed installing driver updates [HRESULT = 0x80070003 - ERROR_PATH_NOT_FOUND]
66+
2017-12-06 15:30:46, Error CBS Startup: Failed while processing non-critical driver operations queue. [HRESULT = 0x80070003 - ERROR_PATH_NOT_FOUND]
67+
2017-12-06 15:30:46, Info CBS Startup: Rolling back KTM, because drivers failed.
68+
2017-12-06 15:30:46, Info CBS Setting ExecuteState key to: CbsExecuteStateStageDrivers | CbsExecuteStateFlagRollback | CbsExecuteStateFlagDriversFailed
69+
2017-12-06 15:30:46, Info CBS SetProgressMessage: progressMessageStage: -1, ExecuteState: CbsExecuteStateStageDrivers | CbsExecuteStateFlagRollback | CbsExecuteStateFlagDriversFailed, SubStage: 0
70+
2017-12-06 15:30:46, Info CBS Progress: UI message updated. Operation type: Update. Stage: 1 out of 1. Rollback.
71+
2017-12-06 15:30:46, Info CBS Setting original failure status: 0x80070003, last forward execute state: CbsExecuteStatePrimitives
72+
2017-12-06 15:30:46, Info CBS SetProgressMessage: progressMessageStage: -1, ExecuteState: CbsExecuteStateStageDrivers | CbsExecuteStateFlagRollback | CbsExecuteStateFlagDriversFailed, SubStage: 1
73+
```

0 commit comments

Comments
 (0)