gabrielgbs97
New member
- Aug 8, 2024
- 1
I’ve recently encountered some ‘unrepairable’ component stores. Despite this, the systems are functioning as expected and no critical issues have been identified for their intended purposes. The ‘only’ problem is that DISM is flagging a few packages as corrupt due to hash mismatches. I suspect that some of these may stem from partially installed/uninstalled Windows updates, or transactions that were not 100% successful.
I managed to automatically fix some corruptions using DISM and SFC. However, when performing subsequent
Before creating threads for each individual case, I wanted to find out if there’s a straightforward way to get the related KB of a CSI package and perform a reinstall or uninstall. This approach worked for me with packages that had the KB embedded in the name. For instance, installing a past and superseded LCU .cab resolved a Component Store issue.
I’ve also encountered cases where corruption was flagged in a very few DLLs, but after a
Given my limited understanding of Windows Update and Component Store, I have a few questions:
- Superseded SxS components can also flag corrruption errors in CBS log?
- Is it wise to try
- Given a corrupted patch/package, for example:
How can I determine the KB of every one of this packages?, in order to try a reinstall? Is there a straighforward method?
Thanks in advance,
Gabriel
I managed to automatically fix some corruptions using DISM and SFC. However, when performing subsequent
dism … /restorehealth
operations, some packages could not be found on Windows Update or a healthy, clean, non-domain-joined, and updated C:\Windows
share.Before creating threads for each individual case, I wanted to find out if there’s a straightforward way to get the related KB of a CSI package and perform a reinstall or uninstall. This approach worked for me with packages that had the KB embedded in the name. For instance, installing a past and superseded LCU .cab resolved a Component Store issue.
I’ve also encountered cases where corruption was flagged in a very few DLLs, but after a
dism … /StartComponentCleanup
, subsequent /scanhealth or SFC operations did not report any corruption.Given my limited understanding of Windows Update and Component Store, I have a few questions:
- Superseded SxS components can also flag corrruption errors in CBS log?
- Is it wise to try
dism ... /StartComponentCleanup
?, of course never /ResetBase. I understand that in theory, it is not harmful other than performance impact on patch uninstall.- Given a corrupted patch/package, for example:
Code:
== f! Mark Count Mismatch ==
amd64_mscorlib_b77a5c561934e089_10.0.17763.110_none_589ca53607d90344 has 14 f! marks, expected 13
amd64_microsoft-windows-ie-htmlrendering_31bf3856ad364e35_11.0.17763.55_none_d48cfb30afc4555e has 4 f! marks, expected 3
amd64_microsoft-windows-mfcore_31bf3856ad364e35_10.0.17763.107_none_65ce6f8fdcb94c41 has 2 f! marks, expected 1
Thanks in advance,
Gabriel
Last edited: