Updated-6940

changes done as per review

Author: debapsaha

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

@@ -16,72 +16,69 @@ ms.custom:
 > [!WARNING]
 > This error is flagged to have an IPU performed to recover the VM if the instructions don't resolve the issue.
 
-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.
+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.
 
-## Summary
+This article helps you understand the root cause and the necessary steps required to mitigate the issue and install the updates effectively.
 
-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.
-This TSG is designed to mitigate this issue and be able to install the updates needed.
+## Prerequisites
+
+Before proceeding with the mitigation of this document, follow the process to backup the OS disk: Back up OS Disk.
 
 ## Symptom
 
+The following error message appears when you try to install any patch using the standalone installer (.msu) or try to install a Windows update::
+
 :::image type="content" source="media/install-error-new.jpg" alt-text="Install error":::
 
 :::image type="content" source="media/windows-update-new.jpg" alt-text="Windows update error":::
 
 :::image type="content" source="media/retry-deba-new.jpg" alt-text="Retry screenshot":::
 
-When you try to install any patch using the standalone installer (.msu) or Windows Update and the update was'nt installed:
-
 ## Root cause
 
-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:
+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:
+
+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. 
 
 ## CBS logs
 
 ```output
-2017-11-15 12:40:00, Info CBS Store corruption, manifest missing for package: Package_123_for_KB3192392~31bf3856ad364e35~amd64~~6.3.1.4
+Info CBS Store corruption, manifest missing for package: Package_123_for_KB3192392~31bf3856ad364e35~amd64~~6.3.1.4
 
-2017-11-15 12:40:00, Error CBS Failed to resolve package 'Package_123_for_KB3192392~31bf3856ad364e35~amd64~~6.3.1.4' [HRESULT = 0x800f0831 - CBS_E_STORE_CORRUPTION]
+Error CBS Failed to resolve package 'Package_123_for_KB3192392~31bf3856ad364e35~amd64~~6.3.1.4' [HRESULT = 0x800f0831 - CBS_E_STORE_CORRUPTION]
 
-2017-11-15 12:40:00, Info CBS Mark store corruption flag because of package: Package_123_for_KB3192392~31bf3856ad364e35~amd64~~6.3.1.4. [HRESULT = 0x800f0831 - CBS_E_STORE_CORRUPTION]
+Info CBS Mark store corruption flag because of package: Package_123_for_KB3192392~31bf3856ad364e35~amd64~~6.3.1.4. [HRESULT = 0x800f0831 - CBS_E_STORE_CORRUPTION]
 
-2017-11-15 12:40:00, Info CBS Failed to resolve package [HRESULT = 0x800f0831 - CBS_E_STORE_CORRUPTION]
+Info CBS Failed to resolve package [HRESULT = 0x800f0831 - CBS_E_STORE_CORRUPTION]
 ```
 
-- 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.
+The  issue can occure due to the following scenarios:
 
-> [!IMPORTANT]
-> This issue may vary depending on each case but the baseline of the issue is the same.
-
-> [!NOTE]
-> 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).
+- This issue is occurring due to a missing or corrupted assembly from KB3192392, specifically: "Package_123_for_KB3192392~31bf3856ad364e35~amd64~~6.3.1.4"
+- This can also happen if the update was never installed and in some cases even if the installation happened, some packages were not applied to the registry.
 
-## Mitigation
+To locate these packages in the system: Go the registry path:
+HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages
+ 
 
-Backup
-Before proceeding with the mitigation of this document, follow the process to backup the OS disk: Back up OS Disk
+> [!IMPORTANT]
+> This issue may vary depending on each case, but the baseline of the issue remains the same.
 
-## Online Mitigation
+> [!NOTE]
+> For more information on how to collect the CBS.log or just logs using TSSv2, see, [CBS logs](https://aka.ms/dndlogs).
 
-### Mitigation 1
+## Adding or removing the culprit KB manually
 
-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:
+Add or remove the culprit KB manually from the OS. You’ll have to consider if the update has been installed before or not:  
 
 ### If KB was installed:
 
-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.
-1. If you find that the KB was installed, you need to remove it. The best approach is the following steps:
-
-### Instructions
-
-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.
-1. Identify the package that the CBS process is complaining about, ensure you verify the KB as well.
-1. On any web browser, go to [Microsoft Update Catalog](https://www.catalog.update.microsoft.com/Home.aspx).
-1. Search for the  identified KB number. 
-1. Select and download the proper KB depending on the OS version and architecture
-1. Download the KB, paste it into a temp folder in the C drive C:\temp
-1. Run the command in cmd as admin navigating to the folder itself
+1. Reproduce the issue by trying to install the patch or the feature with issues. This ensures that the latest data is logged into the latest CBS.log.
+1. Verify the KB after you have identified the package that the CBS process is complaining about.
+1. Navigate to [Microsoft Update Catalog](https://www.catalog.update.microsoft.com/Home.aspx) and search for the KB number you have identified.
+1. Select the KB and download it, depending on the OS version and architecture.
+1. Paste the downloaded KB into a temporary folder in the C drive: C:\temp.
+1. Run the following command in cmd as admin navigating to the folder. 
 
 ```output
 cd \
@@ -90,17 +87,17 @@ expand -F:* windows10.0-kb4462937-x64_9e250691ae6d00cdf677707e83435a612c3264ea.m
 ```
 
 > [!NOTE]
-> The file name is just an example. Use the name of the file downloaded.
+> This is just an example of how you should name the file. In your case, use the name of downloaded file.
 
-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).
-9. Then we need to run the command in cmd as admin:
+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).
+9. Run the below following command in cmd as admin:
 
 ```output
 Dism /online /remove-package /packagepath:C:\temp\windows10.0-kb4462937-x64.cab
 ```
 
 > [!NOTE]
-> We're using KB4462937 as an example, remember to use the KB extracted into the c:\temp folder
+> We're using KB4462937 as an example. Remember to use the KB extracted into the c:\temp folder.
 
 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:
 
@@ -111,11 +108,11 @@ Dism /online /add-package /packagepath:C:\temp\windows10.0-kb4462937-x64.cab
 11. Reboot the machine
 12. Try again to install the update or feature
 
-### If KB was'nt installed:
+### If KB isn't installed:
 
 1. Download the KB that we identified from [Microsoft Update Catalog](https://www.catalog.update.microsoft.com/Home.aspx).
-1. When you have it move it to a temp folder in the C drive C:\temp
-1. When we have it, we need to run the command in cmd as admin navigating to the folder itself.
+1. Paste the downloaded KB into a temporary folder in the C drive: C:\temp.
+1. Run the following command in cmd as admin navigating to the folder..
 
 ```output
 cd \
@@ -124,19 +121,24 @@ expand -F:* windows10.0-kb4462937-x64_9e250691ae6d00cdf677707e83435a612c3264ea.m
 ```
 
 > [!NOTE]
-> The file name is just an example, use the name of the file downloaded.
+> This is just an example of how you should name the file. In your case, use the name of downloaded file.
 
-4. When you expand it, you can see several packages that are coming from the main package.
-5. Then we need to run the command in cmd as admin:
+4. On expanding, you can see several packages that are coming from the main package.
+5. Run the following command in cmd as admin:
 
 ```output
 Dism /online /add-package /packagepath:C:\temp\windows10.0-kb4462937-x64.cab
 ```
 
 > [!NOTE]
-> We are using KB4462937 as an example, remember to use the KB extracted into the c:\temp folder 7. Reboot the machine 8. Try again to install the update or feature.
+> We are using KB4462937 as an example. Remember to use the KB extracted into the c:\temp folder 
+
+7. Reboot the machine
+
+8. Try again to install the update or feature.
 
 ### IPU Process (In-place Upgrade)
 
 > [!NOTE]
-> Awareness: If the mitigations given didn't 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.
+> 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.
+> This means that if customers face this error, you can confidently recommend an In-Place Upgrade as a simple and effective solution.