Skip to content

Commit 2c8e2ae

Browse files
committed
Updated-6940
updated images
1 parent cf71acf commit 2c8e2ae

5 files changed

Lines changed: 17 additions & 17 deletions

File tree

Binary file not shown.
33.9 KB
Loading

SharePoint/SharePointOnline/Media/retry-deba.jpg renamed to support/windows-server/installing-updates-features-roles/media/retry-deba-new.jpg

File renamed without changes.

SharePoint/SharePointOnline/Media/windows-update.jpg renamed to support/windows-server/installing-updates-features-roles/media/windows-update-new.jpg

File renamed without changes.

support/windows-server/installing-updates-features-roles/troubleshoot-windows-installation-error.md

Lines changed: 17 additions & 17 deletions
Original file line numberDiff line numberDiff line change
@@ -14,24 +14,24 @@ ms.custom:
1414
# Troubleshoot Windows Installation Error 0x800f0831
1515

1616
> [!WARNING]
17-
> This error is flagged to have an IPU performed to recover the VM if the instructions do not resolve the issue.
17+
> This error is flagged to have an IPU performed to recover the VM if the instructions don't resolve the issue.
1818
1919
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.
2020

2121
## Summary
2222

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+
When you install an update, you can get the following error 0x800f0831 (CBS_E_STORE_CORRUPTION.). This error occurs because an update did'nt install properly some mandatory manifest files for the package.
2424
This TSG is designed to mitigate this issue and be able to install the updates needed.
2525

2626
## Symptom
2727

28-
:::image type="content" source="../../../SharePoint/SharePointOnline/Media/download-and-install-updates .jpg" alt-text="Download and install error":::
28+
:::image type="content" source="media/install-error-new.jpg" alt-text="Install error":::
2929

30-
:::image type="content" source="../../../SharePoint/SharePointOnline/Media/windows-update.jpg" alt-text="Windows update error message"::::
30+
:::image type="content" source="media/windows-update-new.jpg" alt-text="Windows update error":::
3131

32-
:::image type="content" source="../../../SharePoint/SharePointOnline/Media/retry-deba.jpg" alt-text="Retry screenshot":::
32+
:::image type="content" source="media/retry-deba-new.jpg" alt-text="Retry screenshot":::
3333

34-
When you try to install any patch using the standalone installer (.msu) or Windows Update and the update was not installed:
34+
When you try to install any patch using the standalone installer (.msu) or Windows Update and the update was'nt installed:
3535

3636
## Root cause
3737

@@ -49,13 +49,13 @@ In order to see exactly what is happening, we need to open and check the CBS.log
4949
2017-11-15 12:40:00, Info CBS Failed to resolve package [HRESULT = 0x800f0831 - CBS_E_STORE_CORRUPTION]
5050
```
5151

52-
- 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.
52+
- 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'nt installed at all, or it was installed without applying some packages to the registry.
5353

5454
> [!IMPORTANT]
5555
> This issue may vary depending on each case but the baseline of the issue is the same.
5656
5757
> [!NOTE]
58-
> To get the CBS.log or logs, you can use the TSSv2 to collect all the logs you need for such cases. For more information see, [CBS logs](https://aka.ms/dndlogs).
58+
> To get the CBS.log or logs, you can use the TSSv2 to collect all the logs you need for such cases. For more information, see, [CBS logs](https://aka.ms/dndlogs).
5959
6060
## Mitigation
6161

@@ -70,18 +70,18 @@ We need to move to the plan, to either add or remove the culprit KB manually fro
7070

7171
### If KB was installed:
7272

73-
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.
74-
1. If you found that the KB was installed, you need to remove it, the best approach is the following steps:
73+
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 isn't installed, proceed to the "If KB was'nt installed" steps.
74+
1. If you find that the KB was installed, you need to remove it. The best approach is the following steps:
7575

7676
### Instructions
7777

7878
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.
7979
1. Identify the package that the CBS process is complaining about, ensure you verify the KB as well.
80-
1. In any web browser, go to [Microsoft Update Catalog](https://www.catalog.update.microsoft.com/Home.aspx).
80+
1. On any web browser, go to [Microsoft Update Catalog](https://www.catalog.update.microsoft.com/Home.aspx).
8181
1. Search for the identified KB number.
8282
1. Select and download the proper KB depending on the OS version and architecture
83-
1. When you download the KB, paste it into a temp folder in the C drive C:\temp
84-
1. When we have the KB there, we need to run the command in cmd as admin navigating to the folder itself
83+
1. Download the KB, paste it into a temp folder in the C drive C:\temp
84+
1. Run the command in cmd as admin navigating to the folder itself
8585

8686
```output
8787
cd \
@@ -100,9 +100,9 @@ Dism /online /remove-package /packagepath:C:\temp\windows10.0-kb4462937-x64.cab
100100
```
101101

102102
> [!NOTE]
103-
> We are using KB4462937 as an example, remember to use the KB extracted into the c:\temp folder
103+
> We're using KB4462937 as an example, remember to use the KB extracted into the c:\temp folder
104104
105-
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:
105+
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:
106106

107107
```output
108108
Dism /online /add-package /packagepath:C:\temp\windows10.0-kb4462937-x64.cab
@@ -111,7 +111,7 @@ Dism /online /add-package /packagepath:C:\temp\windows10.0-kb4462937-x64.cab
111111
11. Reboot the machine
112112
12. Try again to install the update or feature
113113

114-
### If KB was not installed:
114+
### If KB was'nt installed:
115115

116116
1. Download the KB that we identified from [Microsoft Update Catalog](https://www.catalog.update.microsoft.com/Home.aspx).
117117
1. When you have it move it to a temp folder in the C drive C:\temp
@@ -139,4 +139,4 @@ Dism /online /add-package /packagepath:C:\temp\windows10.0-kb4462937-x64.cab
139139
### IPU Process (In-place Upgrade)
140140

141141
> [!NOTE]
142-
> 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.
142+
> Awareness: If the mitigations given did'nt 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

Comments
 (0)