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-installation-error-0x800f0831.md
+17-16Lines changed: 17 additions & 16 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,18 +11,20 @@ ms.custom:
11
11
- pcy:WinComm Devices Deploy
12
12
---
13
13
14
-
# Troubleshoot Windows Update error 0x800f0831
14
+
# Troubleshoot Windows Installation Error 0x800f0831
15
15
16
16
> [!WARNING]
17
17
> This error is flagged to have an IPU performed to recover the VM if the instructions do not resolve the issue.
18
18
19
19
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.
20
20
21
21
## Summary
22
+
22
23
When you install an update, you can get the following error 0x800f0831 (CBS_E_STORE_CORRUPTION.). This error occurs because an update did not install properly some mandatory manifest files for the package.
23
24
This TSG is designed to mitigate this issue and be able to install the updates needed.
24
25
25
26
## Symptom
27
+
26
28
When you try to install any patch using the standalone installer (.msu) or Windows Update and the update was not installed:
27
29
28
30
## Root cause
@@ -41,22 +43,21 @@ In order to see exactly what is happening, we need to open and check the CBS.log
41
43
2017-11-15 12:40:00, Info CBS Failed to resolve package [HRESULT = 0x800f0831 - CBS_E_STORE_CORRUPTION]
42
44
```
43
45
44
-
- For this specific scenario, it happens because there is an assembly missing or corrupted from the KB3192392, specifically "Package_123_for_KB3192392~31bf3856ad364e35~amd64~~6.3.1.4" these packages are located into the registy path: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages. An update may not have been installed at all, or it may have been installed without some packages being applied to the registry.
46
+
- For this specific scenario, it happens because there is an assembly missing or corrupted from the KB3192392, specifically "Package_123_for_KB3192392~31bf3856ad364e35~amd64~~6.3.1.4" these packages are located into the registy path: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages. An update either was not installed at all, or it was installed without applying some packages to the registry.
45
47
46
48
> [!IMPORTANT]
47
49
> This issue may vary depending on each case but the baseline of the issue is the same.
48
50
49
51
> [!NOTE]
50
-
> To get the CBS.log or logs you can use the TSSv2 to collect all the logs you need for such cases. The information in how to do it is be in https://aka.ms/dndlogs
52
+
> To get the CBS.log or logs, you can use the TSSv2 to collect all the logs you need for such cases. The information about how to do it is in https://aka.ms/dndlogs.
51
53
52
54
## Mitigation
53
55
54
56
### Backup
55
-
Before proceeding with the mitigation of this document, please follow the process to backup the OS disk: Back up OS Disk
57
+
Before proceeding with the mitigation of this document, follow the process to backup the OS disk: Back up OS Disk
56
58
57
59
## Online Mitigation
58
60
59
-
60
61
### Mitigation 1
61
62
62
63
We need to move to the plan, to either add or remove the culprit KB manually from the OS. It depends if the update was installed or not before:
@@ -68,13 +69,13 @@ We need to move to the plan, to either add or remove the culprit KB manually fro
68
69
69
70
### Instructions
70
71
71
-
1. Reproduce the issue by trying to install the patch or the feature with issues (we need to do this step to ensure that the latest data is logged into the latest CBS.log).
72
-
1.After identifying the package that the CBS process is complaining about, ensure you verify the KB as well.
73
-
1.Now in any web browser, go the Microsoft Update Catalog: https://www.catalog.update.microsoft.com/Home.aspx
72
+
1. Reproduce the issue by trying to install the patch or the feature with issues. We need to do this step to ensure that the latest data is logged into the latest CBS.log.
73
+
1.Identify the package that the CBS process is complaining about, ensure you verify the KB as well.
74
+
1.In any web browser, go the Microsoft Update Catalog: https://www.catalog.update.microsoft.com/Home.aspx
74
75
1. Search for the identified KB number.
75
76
1. Select and download the proper KB depending on the OS version and architecture
76
-
1.Once you download the KB, paste it into a temp folder in the C drive C:\temp
77
-
1.Once we have the KB there, we need to run the command in cmd as admin navigating to the folder itself
77
+
1.When you download the KB, paste it into a temp folder in the C drive C:\temp
78
+
1.When we have the KB there, we need to run the command in cmd as admin navigating to the folder itself
> The file name is just an example, use the name of the file downloaded.
87
+
> The file name is just an example. Use the name of the file downloaded.
87
88
88
-
8.Once you expand it, you can see several packages that are coming from the main package. Check the .cab file with the format "windows 10.0-KBxxxxxxx-x64.cab" (this file can vary depending on the OS version).
89
+
8.When you expand it, you can see several packages that are coming from the main package. Check the .cab file with the format "windows 10.0-KBxxxxxxx-x64.cab" (this file can vary depending on the OS version).
89
90
9. Then we need to run the command in cmd as admin:
**Awareness: If the mitigations given did not fix the issue, this specific Windows Update (WU) error code have been identified that may require an In-Place Upgrade (IPU) to recover the virtual machine (VM). For Windows on Azure (WOA) scenarios—especially in alignment with efforts to reduce days to closure—these WU errors have been reviewed and approved as eligible for IPU as a simplified recovery path. Customers encountering these specific issues can be confidently offered the in-place upgrade option as an effective resolution."**
135
+
**Awareness: If the mitigations given did not fix the issue, this specific Windows Update (WU) error code is identified that may require an In-Place Upgrade (IPU) to recover the virtual machine (VM). For Windows on Azure (WOA) scenarios—especially in alignment with efforts to reduce days to closure—these WU errors are reviewed and approved as eligible for IPU as a simplified recovery path. Customers encountering these specific issues can be confidently offered the in-place upgrade option as an effective resolution."**
0 commit comments