Skip to content

Commit a8c0db5

Browse files
committed
Updated-6940
updated changes
1 parent 1cd32d7 commit a8c0db5

1 file changed

Lines changed: 8 additions & 8 deletions

File tree

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

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -22,11 +22,11 @@ This article helps you understand the root cause and the necessary steps require
2222

2323
## Prerequisites
2424

25-
Before proceeding with the mitigation of this document, follow the process to backup the OS disk: Back up OS Disk.
25+
Before proceeding with the mitigation of this document, follow the process to back up the OS disk: Back up OS Disk.
2626

2727
## Symptom
2828

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::
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:
3030

3131
:::image type="content" source="media/install-error-new.jpg" alt-text="Install error":::
3232

@@ -55,7 +55,7 @@ Info CBS Failed to resolve package [HRESULT = 0x800f0831 - CBS_E_STORE_CORRUPTIO
5555
The issue can occure due to the following scenarios:
5656

5757
- 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 and in some cases even if the installation happened, some packages were not applied to the registry.
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.
5959

6060
To locate these packages in the system: Go the registry path:
6161
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages
@@ -69,16 +69,16 @@ HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Ser
6969
7070
## Adding or removing the culprit KB manually
7171

72-
Add or remove the culprit KB manually from the OS. You’ll have to consider if the update has been installed before or not:
72+
Add or remove the culprit KB manually from the OS. You have to consider if the update has been installed before or not:
7373

7474
### If KB was installed:
7575

76-
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.
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.
7777
1. Verify the KB after you have identified the package that the CBS process is complaining about.
7878
1. Navigate to [Microsoft Update Catalog](https://www.catalog.update.microsoft.com/Home.aspx) and search for the KB number you have identified.
7979
1. Select the KB and download it, depending on the OS version and architecture.
8080
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.
81+
1. Run the following command in cmd as admin navigating to the folder.
8282

8383
```output
8484
cd \
@@ -123,15 +123,15 @@ expand -F:* windows10.0-kb4462937-x64_9e250691ae6d00cdf677707e83435a612c3264ea.m
123123
> [!NOTE]
124124
> This is just an example of how you should name the file. In your case, use the name of downloaded file.
125125
126-
4. On expanding, you can see several packages that are coming from the main package.
126+
4. On expanding, you can see several packages coming from the main package.
127127
5. Run the following command in cmd as admin:
128128

129129
```output
130130
Dism /online /add-package /packagepath:C:\temp\windows10.0-kb4462937-x64.cab
131131
```
132132

133133
> [!NOTE]
134-
> We are using KB4462937 as an example. Remember to use the KB extracted into the c:\temp folder
134+
> We're using KB4462937 as an example. Remember to use the KB extracted into the c:\temp folder
135135
136136
7. Reboot the machine
137137

0 commit comments

Comments
 (0)