Skip to content

Commit 74bd5ec

Browse files
authored
Updates from editor
1 parent 3d3c1fb commit 74bd5ec

1 file changed

Lines changed: 17 additions & 17 deletions

File tree

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

Lines changed: 17 additions & 17 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: Troubleshoot Windows Update Error 0x80070002
33
description: Learn how to resolve the Windows Update error 0x80070002, which occurs due to missing or corrupt files or incomplete updates.
4-
ms.date: 04/08/2025
4+
ms.date: 04/16/2025
55
manager: dcscontentpm
66
audience: itpro
77
ms.topic: troubleshooting
@@ -10,7 +10,7 @@ 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 0x80070002
13+
# Troubleshoot Windows Update error 0x80070002
1414

1515
The Windows Update error 0x80070002 typically occurs because of missing or corrupt files necessary for the update or incomplete previous updates. Understanding the root causes and following the appropriate troubleshooting steps can help resolve this issue effectively.
1616

@@ -20,17 +20,17 @@ The Windows Update error 0x80070002 typically occurs because of missing or corru
2020

2121
Before proceeding with the troubleshooting steps, ensure you have backed up your operating system (OS) disk. This precautionary step is crucial to prevent data loss during the resolution process.
2222

23-
## Root cause for Windows update error 0x80070002
23+
## Root cause
2424

2525
The error 0x80070002 is primarily caused by missing or corrupt files that are necessary for the update process. This issue can occur due to:
2626

2727
- Incomplete previous updates that left the system in an inconsistent state.
2828
- Missing DLLs or system files in critical directories.
29-
- Registry entries pointing to non-existent services or files.
29+
- Registry entries pointing to nonexistent services or files.
3030

3131
## Symptom 1: Security monthly rollup installation failure
3232

33-
If the Security Monthly Rollup fails to install with error 0x80070002, check the CBS.log located at `C:\Windows\Logs\CBS\CBS.log`. You might find entries indicating missing files or services that failed to start.
33+
If the Security Monthly Rollup fails to install with error 0x80070002, check the **CBS.log** file located at `C:\Windows\Logs\CBS\CBS.log`. You might find entries indicating missing files or services that failed to start.
3434

3535
```output
3636
Info CSI 000000fb Begin executing advanced installer phase 50 (0x00000032) index 0 (sequence 0)
@@ -57,7 +57,7 @@ Check the directory `C:\Windows\Microsoft.NET\Framework\v4.0.30319` to confirm i
5757

5858
## Symptom 2: Update installation failure
5959

60-
If you encounter error 0x80070002 during update installation, review the CBS.log for entries like the following:
60+
If you encounter error 0x80070002 during update installation, review the **CBS.log** file for entries like the following:
6161

6262
```output
6363
Error CSI 00000e47 (F) STATUS_OBJECT_NAME_NOT_FOUND #13367681# from Windows::Rtl::SystemImplementation::DirectFileSystemProvider::SysCreateFile(flags = (AllowSharingViolation), handle = {provider=NULL, handle=0, name= ("null")}, da = (SYNCHRONIZE|FILE_READ_ATTRIBUTES), oa = @0xa130e9e088->OBJECT_ATTRIBUTES {s:48; rd:NULL; on:[69]"\??\C:\ProgramData\Microsoft\Windows\Start Menu\Programs\System Tools"; a:(OBJ_CASE_INSENSITIVE)}, iosb = @0xa130e9e068, as = (null), fa = 0, sa = (FILE_SHARE_READ|FILE_SHARE_WRITE|FILE_SHARE_DELETE), cd = FILE_OPEN, co = (FILE_SYNCHRONOUS_IO_NONALERT|0x00004000), eab = NULL, eal = 0, disp = Invalid)
@@ -67,19 +67,19 @@ Verify the existence of the folder `C:\ProgramData\Microsoft\Windows\Start Menu\
6767

6868
### Resolution: Copy missing folders
6969

70-
Copy the folder "System Tools" from a working machine to the affected machine, ensuring all shortcuts are included.
70+
Copy the **System Tools** folder from a working machine to the affected machine, ensuring all shortcuts are included.
7171

7272
## Symptom 3: Missing DLLs in C:\Windows\WinSxS
7373

74-
Monthly rollups may fail with error 0x80070002 due to missing DLLs in the Side-by-Side store. Check the WindowsUpdate.log and CBS.log for missing files like `DWrite.dll` and `FntCache.dll`.
74+
Monthly rollups might fail with error 0x80070002 due to missing DLLs in the Side-by-Side store. Check the **WindowsUpdate.log** and **CBS.log** for missing files like `DWrite.dll` and `FntCache.dll`.
7575

7676
```output
7777
Info CBS Failed to find file: x86_microsoft-windows-directwrite_31bf3856ad364e35_7.1.7601.23545_none_229deeb1ba2a85d3DWrite.dll [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
7878
```
7979

8080
### Resolution: Restore missing DLLs
8181

82-
1. Identify missing DLLs from the CBS logs.
82+
1. Identify missing DLLs from the **CBS logs** file.
8383
2. Source these files from a working server and place them in the correct directories. To do so, run the following commands:
8484

8585
```console
@@ -88,7 +88,7 @@ Info CBS Failed to find file: x86_microsoft-windows-directwrite_31bf3856ad364e35
8888
cd c:\windows\winsxs
8989
```
9090

91-
Then, run the `mkdir` command to create a folder for the missing DLL file. For example, if the file x86_microsoft-windows-directwrite_31bf3856ad364e35_7.1.7601.23545_none_229deeb1ba2a85d3DWrite.dll is missing, run the following command:
91+
Then, run the `mkdir` command to create a folder for the missing DLL file. For example, if the file **x86_microsoft-windows-directwrite_31bf3856ad364e35_7.1.7601.23545_none_229deeb1ba2a85d3DWrite.dll** is missing, run the following command:
9292

9393
```console
9494
mkdir x86_microsoft-windows-directwrite_31bf3856ad364e35_7.1.7601.23545_none_229deeb1ba2a85d3
@@ -106,7 +106,7 @@ Info CBS Failed to find file: x86_microsoft-windows-directwrite_31bf3856ad364e35
106106

107107
If a cumulative update on Windows Server rolls back after a restart, check the Event Viewer for error 0x80070002 and review the CBS logs for driver update issues.
108108

109-
Here is a sample of the event log:
109+
Here's a sample of the event log:
110110

111111
> Log Name: System
112112
> Source: Microsoft-Windows-WindowsUpdateClient
@@ -120,7 +120,7 @@ Here is a sample of the event log:
120120
> Description:
121121
> Installation Failure: Windows failed to install the following update with error 0x80070002: Security Update for Windows (KB4586793).
122122
123-
The failure is caused by an issue during update drivers operation. For example, the following CBS.log indicates the driver flpydisk.inf is the cause:
123+
The failure is caused by an issue during update drivers operation. For example, the following **CBS.log** file indicates the `flpydisk.inf` driver is the cause:
124124

125125
```output
126126
Info CBS INSTALL index: 55, phase: 2, result 2, inf: flpydisk.inf
@@ -129,16 +129,16 @@ Info CBS Doqe: Failed installing driver updates [HRESULT = 0x80070002 - ERROR_FI
129129

130130
### Resolution: Import registry keys
131131

132-
To fix the issue, you need to export the registry keys for the driver on a working computer, and then import them on the computer that have the issue.
132+
To fix the issue, you need to export the registry keys for the driver on a working computer, and then import them on the computer that has the issue.
133133

134-
The resolution depends on what is missing. For example, to fix the issue with flpydisk.inf, which we listed as an example in the symptom section, export and import the following two registry keys.
134+
The resolution depends on what is missing. For example, to fix the issue with `flpydisk.inf`, which is listed as an example in the symptom section, export and import the following two registry keys.
135135

136-
1. `HKLM\System\CurrentControlSet\Services\flpydisk`
137-
2. `HKLM\System\CurrentControlSet\Services\sfloppy`
136+
- `HKLM\System\CurrentControlSet\Services\flpydisk`
137+
- `HKLM\System\CurrentControlSet\Services\sfloppy`
138138

139139
## Symptom 5: Windows upgrade failure
140140

141-
For Windows upgrade failures with error 0x80070002, examine the Setupact.log for issues related to mounting WIM files.
141+
For Windows upgrade failures with error 0x80070002, examine the **Setupact.log** file for issues related to mounting WIM files.
142142

143143
```output
144144
Warning SP Failed to get WimMount ImagePath, 0x80070002

0 commit comments

Comments
 (0)