Skip to content

Commit 247fd74

Browse files
Update error-invalid-data-startup-installing-updates.md
1 parent faa24f5 commit 247fd74

1 file changed

Lines changed: 2 additions & 2 deletions

File tree

support/windows-server/installing-updates-features-roles/error-invalid-data-startup-installing-updates.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -40,7 +40,7 @@ You might encounter entries in the Component-Based Servicing (CBS) log file (usu
4040
20xx-xx-06 xx:51:15, Info CBS Failed to verify manifest against catalog, mark store as corrupt. [HRESULT = 0x8007000d - ERROR_INVALID_DATA]
4141
20xx-xx-06 xx:51:15, Info CBS Failed to begin deployment installation for Update: 4584642-1_neutral [HRESULT = 0x8007000d - ERROR_INVALID_DATA]
4242
```
43-
In this case, the error happens because the system can't verify if catalog file C:/WINDOWS/Servicing/Packages/Package_1_for_KB4584642~31bf3856ad364e35~amd64~~10.0.1.0.cat is valid, which means the package is likely corrupt. See [Mitigation 1: File and Registry Corruption](#mitigation-1-file-and-registry-corruption) for more details.
43+
In this case, the error happens because the system can't verify if catalog file C:/WINDOWS/Servicing/Packages/Package_1_for_KB4584642~31bf3856ad364e35~amd64~~10.0.1.0.cat is valid, which means the package is likely corrupt. See [Resolution or troubleshooting steps](#resolution-or-troubleshooting-steps) for more details.
4444

4545
### Symptom 2: Registry errors
4646

@@ -56,7 +56,7 @@ Another symptom may involve registry errors. From the CBS log file, you might se
5656
20xx-xx-24 05:13:10, Info CBS Failed to find or add the component family [HRESULT = 0x8007000d - ERROR_INVALID_DATA]
5757
```
5858

59-
This indicates registry issues. See [Mitigation 1: File and Registry Corruption](#mitigation-1-file-and-registry-corruption) for more details.
59+
This indicates registry issues. See [Resolution or troubleshooting steps](#resolution-or-troubleshooting-steps) for more details.
6060

6161
### Symptom 3: Driver update failure
6262

0 commit comments

Comments
 (0)