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
title: Update Installation Error 0x800f0831 CBS E STORE CORRUPTION_Windows
3
-
description: Learn how to resolve Windows Update error 0x800f0831, indicating that access to an unmanaged server isn't allowed.
3
+
description: Learn how to resolve Windows installation error 0x800f0831.
4
4
ms.date: 07/31/2025
5
5
manager: dcscontentpm
6
6
audience: itpro
@@ -14,26 +14,20 @@ ms.custom:
14
14
# Troubleshoot Windows Update error 0x800f0831
15
15
16
16
> [!WARNING]
17
-
> This error has been flagged to have an IPU performed to recover the VM if the instructions below do not resolve the issue.
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
-
When you install an update you can get the following error 0x800f0831 (CBS_E_STORE_CORRUPTION.).This happens because an update did not install properly some mandatory manifest files for the package..
22
+
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
23
This TSG is designed to mitigate this issue and be able to install the updates needed.
24
24
25
25
## Symptom
26
26
When you try to install any patch using the standalone installer (.msu) or Windows Update and the update was not installed:
27
27
28
-
:::image type="content" source="../../../SharePoint/SharePointOnline/Media/download and install updates .jpg" alt-text="download and install updates":::
In order to see exactly what is happening we need to open and check the CBS.log (location C:\windows\logs\CBS) it will look similar to the following output:
30
+
In order to see exactly what is happening, we need to open and check the CBS.log (location C:\windows\logs\CBS) it looks similar to the following output:
37
31
38
32
## CBS logs
39
33
@@ -47,40 +41,40 @@ In order to see exactly what is happening we need to open and check the CBS.log
47
41
2017-11-15 12:40:00, Info CBS Failed to resolve package [HRESULT = 0x800f0831 - CBS_E_STORE_CORRUPTION]
48
42
```
49
43
50
-
- For this specific scenario, this is happening 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. This can happen if the update was never installed or was installed but some packages were not applied into the registry.
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.
51
45
52
46
> [!IMPORTANT]
53
-
> This may vary depending on each case but the baseline of the issue will be the same.
47
+
> This issue may vary depending on each case but the baseline of the issue is the same.
54
48
55
49
> [!NOTE]
56
-
> To get the CBS.log or logs you can use the TSSv2 to collect all the logs that you need for these type of cases, the information in how to do it will be in https://aka.ms/dndlogs
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
57
51
58
52
## Mitigation
59
53
60
54
### Backup
61
-
Before proceeding with the mitigation of this document, please follow the process to backup the OS disk: Backup OS Disk
55
+
Before proceeding with the mitigation of this document, please follow the process to backup the OS disk: Back up OS Disk
62
56
63
57
## Online Mitigation
64
58
65
59
66
60
### Mitigation 1
67
61
68
-
We will need to move to the plan that is to add or remove the culprit KB manually from the OS, it depends if the update has been installed or not before:
62
+
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:
69
63
70
64
### If KB was installed:
71
65
72
-
1. Check if the complaining KB that we took from the first step to identify the KB is installed or not in the machine, if it is not installed proceed to the "If KB was not installed" steps below.
73
-
1. If you found that the KB was installed we need to remove it, the best approach is the following:
66
+
1. Check if the complaining KB that we took from the first step to identify the KB is installed or not in the machine. If it is not installed proceed to the "If KB was not installed" steps.
67
+
1. If you found that the KB was installed, you need to remove it, the best approach is the following steps:
74
68
75
69
### Instructions
76
70
77
-
1. Reproduce the issue by trying to install the patch or the feature with issues (we need to do this to ensure that the latest data is logged into the latest CBS.log).
78
-
1.Now that we have identified the package that the CBS process is complaining about, ensure you have verified the KB as well.
79
-
1. Now in any web browser go the Microsoft Update Catalog: https://www.catalog.update.microsoft.com/Home.aspx
80
-
1. Search for the KB number we have already identified
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
74
+
1. Search for the identified KB number.
81
75
1. Select and download the proper KB depending on the OS version and architecture
82
-
1. Once you have downloaded the KB, paste it into a temp folder in the C drive C:\temp
83
-
1. Once we have the KB there we need to run the below command in cmd as admin navigating to the folder itself
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
> The file name is just an example, please use the name of the file downloaded.
86
+
> The file name is just an example, use the name of the file downloaded.
93
87
94
-
8. Once we have expanded it, we will 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).
95
-
9. Then we need to run the below command in cmd as admin:
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
+
9. Then we need to run the command in cmd as admin:
> We are using KB4462937 as an example, remember to use the KB extracted into the c:\temp folder
103
97
104
-
10. If you are asked to reboot, please do it and then run the below command in a cmd with administrator privileges. If the reboot is not required, just run the below command in a cmd with administrator privileges:
98
+
10. If you are asked to reboot, do it and then run the command in a cmd with administrator privileges. If the reboot is not required, just run the command in a cmd with administrator privileges:
**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."**
134
+
**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."**
0 commit comments