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-installation-error-corruption.md
+11-8Lines changed: 11 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -31,16 +31,17 @@ When you try to install any update by using the standalone installer (.msu), or
31
31
32
32
## Cause
33
33
34
-
The issue might occur for one of the following reasons:
34
+
This error can occur for one of the following reasons:
35
+
36
+
- The update was never installed.
37
+
- The update is installed but some packages aren't applied to the registry.
35
38
36
-
- An assembly from the KB3192392 update (specifically: "Package_123_for_KB3192392~31bf3856ad364e35~amd64~~6.3.1.4") is missing or corrupted.
37
-
- The update was never installed. Or, the update is installed but some packages aren't applied to the registry.
38
39
39
40
To locate the installation packages in the system, search for the following registry subkey:
40
41
41
42
```output HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages```
42
43
43
-
To investigate the cause further, examine the CBS.log file (C:\windows\logs\CBS), and search for output that resembles the following example:
44
+
To investigate the cause further, examine the CBS.log file (C:\windows\logs\CBS), and search for output that similar to the following example:
44
45
45
46
```output
46
47
Info CBS Store corruption, manifest missing for package: Package_123_for_KB3192392~31bf3856ad364e35~amd64~~6.3.1.4
@@ -51,15 +52,17 @@ Info CBS Mark store corruption flag because of package: Package_123_for_KB319239
51
52
52
53
Info CBS Failed to resolve package [HRESULT = 0x800f0831 - CBS_E_STORE_CORRUPTION]
53
54
```
54
-
55
+
> [!NOTE]
56
+
> The package and error details may vary depending on the OS version and the KB update. However, when this error is logged, the recommended solution in this article will apply.
55
57
> [!NOTE]
56
58
> For more information about how to collect the CBS.log file or any log that uses the TroubleShootingScript (TSS) tool version 2, see, [CBS logs](https://aka.ms/dndlogs).
57
59
58
60
## Resolution
59
61
60
-
To resolve this issue, manually add the problematic update to the system or remove it from the system, depending on whether the update is installed.
62
+
If the update is installed, remove and reinstall it. If the update is not installed install it.
63
+
61
64
62
-
### If the update is installed
65
+
### Here are the steps to remove and install the update
63
66
64
67
1. Reproduce the issue by trying to install the update or feature that's experiencing issues. This action logs the latest data into the CBS log.
65
68
1. Verify that you have the correct update after you identify the package that the CBS process is calling out.
@@ -129,4 +132,4 @@ To resolve this issue, manually add the problematic update to the system or remo
129
132
### In-place upgrade process
130
133
131
134
> [!NOTE]
132
-
> If the suggested fixes don’t resolve the issue, this specific Windows Update (WU) error code might require an in-place upgrade (IPU) as a simple and effective solution to recover the VM. For Windows on Azure (WOA) scenarios, these kinds of WU errors are reviewed and approved as eligible for IPU. This is especially true if you're trying to resolve issues quickly.
135
+
> If the suggested fixes don’t resolve the issue, this specific Windows Update (WU) error code might require an in-place upgrade (IPU) as a simple and effective solution to recover the VM. For Windows on Azure (WOA) scenarios, these kinds of WU errors are reviewed and approved as eligible for In-place updgrade. This is especially true if you're trying to resolve issues quickly.
0 commit comments