Skip to content

Commit 38250ec

Browse files
committed
Merge branch 'v-debapsaha-6940' of https://github.com/MicrosoftDocs/SupportArticles-docs-pr into v-debapsaha-6940
2 parents 18afb56 + b35b641 commit 38250ec

1 file changed

Lines changed: 81 additions & 81 deletions

File tree

Lines changed: 81 additions & 81 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
22
title: Troubleshoot Windows Installation Error 0x800f0831
3-
description: Learn how to resolve Windows installation error 0x800f0831.
3+
description: Learn how to resolve Windows Update installation error 0x800f0831.
44
ms.date: 07/31/2025
55
manager: dcscontentpm
66
audience: itpro
@@ -11,36 +11,48 @@ ms.custom:
1111
- pcy:WinComm Devices Deploy
1212
---
1313

14-
# Troubleshoot Windows Installation Error 0x800f0831
14+
# Troubleshoot Windows Update installation error 0x800f0831
1515

1616
> [!WARNING]
17-
> This error is flagged to have an IPU performed to recover the VM if the instructions don't resolve the issue.
17+
> This error is flagged to prompt an in-place upgrade to recover the virtual machine (VM) if these instructions don't resolve the issue.
1818
19-
The Windows Update error 0x800f0831 typically occurs when an update fails to install required manifest files correctly. Understanding the root causes and following the appropriate troubleshooting steps can help resolve this issue effectively.
20-
21-
This article helps you understand the root cause and the necessary steps required to mitigate the issue and install the updates effectively.
19+
Windows Update error 0x800f0831 typically occurs if an update doesn't install the required manifest files correctly. This article helps you understand the root cause of the issue and the necessary steps to resolve it effectively.
2220

2321
## Prerequisites
2422

25-
Before proceeding with the mitigation of this document, follow the process to back up the OS disk: Back up OS Disk.
23+
Before you troubleshoot, follow the steps in [this article](https://supportability.visualstudio.com/AzureIaaSVM/_wiki/wikis/AzureIaaSVM/495352/Network-Level-Authentication_RDP-SSH?anchor=%3Cspan-class%3D%22mw-customtoggle-mydivision%22%3Ebackup-os-disk%3C/span%3E) to back up the OS disk.
24+
25+
## Symptoms
26+
27+
When you try to install any update by using the standalone installer (.msu), or you try to install a Windows update, you receive one of the following error messages:
28+
29+
> Some updates were not installed
2630
27-
## Symptom
31+
:::image type="content" source="media/install-error-new.jpg" alt-text="Screenshot of the installation error message.":::
2832

29-
The following error message appears when you try to install any patch using the standalone installer (.msu) or try to install a Windows update:
33+
> Updates failed
3034
31-
:::image type="content" source="media/install-error-new.jpg" alt-text="Install error":::
35+
:::image type="content" source="media/windows-update-new.jpg" alt-text="Screenshot of the Windows Update error message.":::
3236

33-
:::image type="content" source="media/windows-update-new.jpg" alt-text="Windows update error":::
37+
> Retry
3438
35-
:::image type="content" source="media/retry-deba-new.jpg" alt-text="Retry screenshot":::
39+
:::image type="content" source="media/retry-deba-new.jpg" alt-text="Screenshot of the Retry error message.":::
3640

37-
## Root cause
41+
## Cause
3842

39-
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:
43+
The issue might occur for one of the following reasons:
4044

41-
Navigate to C:\windows\logs\CBS to open and check the CBS.log. You’ll be able to find out what’s causing the error.
45+
- An assembly from the KB3192392 update (specifically: "Package_123_for_KB3192392~31bf3856ad364e35~amd64~~6.3.1.4") is missing or corrupted.
46+
- The update was never installed. Or, the update is installed but some packages aren't applied to the registry.
47+
48+
To locate the installation packages in the system, search for the following registry subkey:
49+
50+
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages
51+
52+
> [!IMPORTANT]
53+
> This issue might vary depending on each case, but the baseline of the issue remains the same.
4254
43-
## CBS logs
55+
To investigate the cause further, examine the CBS.log file (C:\windows\logs\CBS), and search for output that resembles the following example:
4456

4557
```output
4658
Info CBS Store corruption, manifest missing for package: Package_123_for_KB3192392~31bf3856ad364e35~amd64~~6.3.1.4
@@ -52,93 +64,81 @@ Info CBS Mark store corruption flag because of package: Package_123_for_KB319239
5264
Info CBS Failed to resolve package [HRESULT = 0x800f0831 - CBS_E_STORE_CORRUPTION]
5365
```
5466

55-
The issue can occure due to the following scenarios:
56-
57-
- This issue is occurring due to a missing or corrupted assembly from KB3192392, specifically: "Package_123_for_KB3192392~31bf3856ad364e35~amd64~~6.3.1.4"
58-
- This can also happen if the update was never installed. In some cases even if the installation happened, some packages were'nt applied to the registry.
59-
60-
To locate these packages in the system: Go the registry path:
61-
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages
62-
63-
64-
> [!IMPORTANT]
65-
> This issue may vary depending on each case, but the baseline of the issue remains the same.
66-
6767
> [!NOTE]
68-
> For more information on how to collect the CBS.log or just logs using TSSv2, see, [CBS logs](https://aka.ms/dndlogs).
68+
> 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).
6969
70-
## Adding or removing the culprit KB manually
70+
## Resolution
7171

72-
Add or remove the culprit KB manually from the OS. You have to consider if the update has been installed before or not:
72+
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.
7373

74-
### If KB was installed:
74+
### If the update is installed
7575

76-
1. Reproduce the issue by trying to install the patch or the feature with issues. This action ensures that the latest data is logged into the latest CBS.log.
77-
1. Verify the KB after you have identified the package that the CBS process is complaining about.
78-
1. Navigate to [Microsoft Update Catalog](https://www.catalog.update.microsoft.com/Home.aspx) and search for the KB number you have identified.
79-
1. Select the KB and download it, depending on the OS version and architecture.
80-
1. Paste the downloaded KB into a temporary folder in the C drive: C:\temp.
81-
1. Run the following command in cmd as admin navigating to the folder.
76+
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.
77+
1. Verify that you have the correct update after you identify the package that the CBS process is calling out.
78+
1. Navigate to [Microsoft Update Catalog](https://www.catalog.update.microsoft.com/Home.aspx), and search for the KB number that you identified.
79+
1. Select the appropriate KB version for the OS version and architecture, and then download the file to a temporary folder ("temp") on drive C.
80+
1. Open an administrative Command Prompt window, and run the following command on the folder:
8281

83-
```output
84-
cd \
85-
cd temp
86-
expand -F:* windows10.0-kb4462937-x64_9e250691ae6d00cdf677707e83435a612c3264ea.msu C:\temp
87-
```
82+
```output
83+
cd \
84+
cd temp
85+
expand -F:* windows10.0-kb4462937-x64_9e250691ae6d00cdf677707e83435a612c3264ea.msu C:\temp
86+
```
8887

89-
> [!NOTE]
90-
> This is just an example of how you should name the file. In your case, use the name of downloaded file.
88+
**Note:** In this command, substitute the actual name of the downloaded file.
9189

92-
8. On expanding, you’ll see several packages 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).
93-
9. Run the below following command in cmd as admin:
90+
1. In the expanded packages, locate the .cab file that uses the following format, depending on the OS version:
9491

95-
```output
96-
Dism /online /remove-package /packagepath:C:\temp\windows10.0-kb4462937-x64.cab
97-
```
92+
windows 10.0-KB*xxxxxxx*-x64.cab
93+
94+
1. Run the following command at an administrative command prompt:
9895

99-
> [!NOTE]
100-
> We're using KB4462937 as an example. Remember to use the KB extracted into the c:\temp folder.
96+
```output
97+
Dism /online /remove-package /packagepath:C:\temp\windows10.0-kb4462937-x64.cab
98+
```
10199

102-
10. If you're asked to reboot, do it and then run the command in a cmd with administrator privileges. If the reboot isn't required, just run the command in a cmd with administrator privileges:
100+
**Note:** In this command, substitute the actual name of the .cab file.
103101

104-
```output
105-
Dism /online /add-package /packagepath:C:\temp\windows10.0-kb4462937-x64.cab
106-
```
102+
1. Restart the computer if you're prompted to do that.
103+
2. Run the following command at an administrative command prompt:
107104

108-
11. Reboot the machine
109-
12. Try again to install the update or feature
105+
```output
106+
Dism /online /add-package /packagepath:C:\temp\windows10.0-kb4462937-x64.cab
107+
```
110108

111-
### If KB isn't installed:
109+
1. Restart the computer.
110+
1. Try again to install the update or feature.
112111

113-
1. Download the KB that we identified from [Microsoft Update Catalog](https://www.catalog.update.microsoft.com/Home.aspx).
114-
1. Paste the downloaded KB into a temporary folder in the C drive: C:\temp.
115-
1. Run the following command in cmd as admin navigating to the folder..
112+
### If the update isn't installed
116113

117-
```output
118-
cd \
119-
cd temp
120-
expand -F:* windows10.0-kb4462937-x64_9e250691ae6d00cdf677707e83435a612c3264ea.msu C:\temp
121-
```
114+
1. Navigate to the [Microsoft Update Catalog](https://www.catalog.update.microsoft.com/Home.aspx), and download the update to a temporary folder ("temp") on drive C.
115+
1. At an administrative command prompt, run the following command on the folder:
122116

123-
> [!NOTE]
124-
> This is just an example of how you should name the file. In your case, use the name of downloaded file.
117+
```output
118+
cd \
119+
cd temp
120+
expand -F:* windows10.0-kb4462937-x64_9e250691ae6d00cdf677707e83435a612c3264ea.msu C:\temp
121+
```
125122

126-
4. On expanding, you can see several packages coming from the main package.
127-
5. Run the following command in cmd as admin:
123+
**Note:** In this command, substitute the actual name of the downloaded file.
124+
125+
1. In the expanded packages, locate the .cab file that uses the following format, depending on the OS version:
128126

129-
```output
130-
Dism /online /add-package /packagepath:C:\temp\windows10.0-kb4462937-x64.cab
131-
```
127+
windows 10.0-KB*xxxxxxx*-x64.cab
128+
129+
1. At an administrative command prompt, run the following command:
132130

133-
> [!NOTE]
134-
> We're using KB4462937 as an example. Remember to use the KB extracted into the c:\temp folder
131+
```output
132+
Dism /online /add-package /packagepath:C:\temp\windows10.0-kb4462937-x64.cab
133+
```
134+
135+
**Note:** In this command, substitute the actual name of the .cab file.
135136

136-
7. Reboot the machine
137+
1. Restart the computer.
137138

138-
8. Try again to install the update or feature.
139+
1. Try again to install the update or feature.
139140

140-
### IPU Process (In-place Upgrade)
141+
### In-place upgrade process
141142

142143
> [!NOTE]
143-
> Awareness: If the suggested fixes don’t resolve the issue, this specific Windows Update (WU) error code may require an In-Place Upgrade (IPU) to recover the virtual machine (VM). For Windows on Azure (WOA) scenarios, especially when trying to resolve issues quickly, these types of WU errors are reviewed and approved as eligible for IPU.
144-
> This means that if customers face this error, you can confidently recommend an In-Place Upgrade as a simple and effective solution.
144+
> 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.

0 commit comments

Comments
 (0)