You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: support/windows-server/installing-updates-features-roles/troubleshoot-windows-update-error-0x80070002.md
+11-5Lines changed: 11 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -28,9 +28,15 @@ The error 0x80070002 is primarily caused by missing or corrupt files that are ne
28
28
- Missing DLLs or system files in critical directories.
29
29
- Registry entries pointing to nonexistent services or files.
30
30
31
+
## CBS logs
32
+
33
+
When troubleshooting Windows Update issues, CBS logs are helpful for identifying the root cause.
34
+
35
+
The CBS logs locates at the `C:\Windows\Logs\CBS\CBS.log`. The log can roll over from CBS.log to the CBSpersisttXXXXXXXXXXXXX.log or CBSpersisttXXXXXXXXXXXXX.cab.
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.
39
+
If the Security Monthly Rollup fails to install with error 0x80070002, check the CBS logs. You might find entries indicating missing files or services that failed to start.
34
40
35
41
```output
36
42
Info CSI 000000fb Begin executing advanced installer phase 50 (0x00000032) index 0 (sequence 0)
@@ -57,7 +63,7 @@ Check the directory `C:\Windows\Microsoft.NET\Framework\v4.0.30319` to confirm i
57
63
58
64
## Symptom 2: Update installation failure
59
65
60
-
If you encounter error 0x80070002 during update installation, review the **CBS.log** file for entries like the following:
66
+
If you encounter error 0x80070002 during update installation, review the CBS logs for entries like the following:
61
67
62
68
```output
63
69
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)
@@ -71,15 +77,15 @@ Copy the **System Tools** folder from a working machine to the affected machine,
71
77
72
78
## Symptom 3: Missing DLLs in C:\Windows\WinSxS
73
79
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`.
80
+
Monthly rollups might fail with error 0x80070002 due to missing DLLs in the Side-by-Side store. Check the **WindowsUpdate.log** and CBS logs for missing files like `DWrite.dll` and `FntCache.dll`.
75
81
76
82
```output
77
83
Info CBS Failed to find file: x86_microsoft-windows-directwrite_31bf3856ad364e35_7.1.7601.23545_none_229deeb1ba2a85d3DWrite.dll [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
78
84
```
79
85
80
86
### Resolution: Restore missing DLLs
81
87
82
-
1. Identify missing DLLs from the **CBS logs** file.
88
+
1. Identify missing DLLs from the CBS logs.
83
89
2. Source these files from a working server and place them in the correct directories. To do so, run the following commands:
84
90
85
91
```console
@@ -122,7 +128,7 @@ Description:
122
128
Installation Failure: Windows failed to install the following update with error 0x80070002: Security Update for Windows (KB4586793).
123
129
```
124
130
125
-
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:
131
+
The failure is caused by an issue during update drivers operation. For example, the following entries in the CBS logs indicates the `flpydisk.inf` driver is the cause:
126
132
127
133
```output
128
134
Info CBS INSTALL index: 55, phase: 2, result 2, inf: flpydisk.inf
0 commit comments