valistral Contributor Joined Mar 26, 2019 Posts 52 Nov 20, 2019 #1 For some reason that I yet have to determine, either a power failure or something else, the component store hive got corrupted and then automatically rebuilt by the system in the event logs it was also reported that some data was lost. Now running SFC /scannow and DISM /online /cleanup-image /scanhealth show no corruption whatsoever but when the system attempts to perform the automatic cleanup of the store, scavenging fails due to component store corruption. I'm attaching the CBS log the failures are shown at the end of the file, I was at least able to fix the corruption regarding: Code: 2019-11-20 04:30:04, Info CSI 00000084 Delta store baseline version missing for: [ml:280{140},l:180{90}]"amd64_microsoft-windows-activexproxy_31bf3856ad364e35_6.3.9600.19463_none_02e0f096be3255db" The others I'm unable to, canonicaldata Keys either in catalog or deployment are all missing. As usual any help is appreciated, thanks. Best regards. Attachments CbsPersist_20191120064051.zip 4.3 MB · Views: 1
For some reason that I yet have to determine, either a power failure or something else, the component store hive got corrupted and then automatically rebuilt by the system in the event logs it was also reported that some data was lost. Now running SFC /scannow and DISM /online /cleanup-image /scanhealth show no corruption whatsoever but when the system attempts to perform the automatic cleanup of the store, scavenging fails due to component store corruption. I'm attaching the CBS log the failures are shown at the end of the file, I was at least able to fix the corruption regarding: Code: 2019-11-20 04:30:04, Info CSI 00000084 Delta store baseline version missing for: [ml:280{140},l:180{90}]"amd64_microsoft-windows-activexproxy_31bf3856ad364e35_6.3.9600.19463_none_02e0f096be3255db" The others I'm unable to, canonicaldata Keys either in catalog or deployment are all missing. As usual any help is appreciated, thanks. Best regards.
valistral Contributor Joined Mar 26, 2019 Posts 52 Nov 20, 2019 #2 Follow up, trying to run DISM /Online /Cleanup-Image /Startcomponentcleanup will fail with error 0x8000ffff CBS log attached Attachments CBS.zip 393 KB · Views: 0
Follow up, trying to run DISM /Online /Cleanup-Image /Startcomponentcleanup will fail with error 0x8000ffff CBS log attached
valistral Contributor Joined Mar 26, 2019 Posts 52 Nov 21, 2019 #3 Managed to (partially at least?) fix the registry and push the component cleanup process to the end. Will run SFC/DISM to see if there's any other issue popping up.
Managed to (partially at least?) fix the registry and push the component cleanup process to the end. Will run SFC/DISM to see if there's any other issue popping up.
valistral Contributor Joined Mar 26, 2019 Posts 52 Nov 21, 2019 #4 SFC is clean while now DISM shows 3 corrupt payloads which is unable to find on Windows Update and replace being: Code: Checking System Update Readiness. (p) CSI Payload Corrupt wow64_microsoft-windows-ieframe_31bf3856ad364e35_11.0.9600.18283_none_72c7637ec56c23ed\ieframe.dll Repair failed: Missing replacement payload. (p) CSI Payload Corrupt x86_microsoft-windows-ie-vgx_31bf3856ad364e35_11.0.9600.18283_none_94e8c2741349def5\VGX.dll Repair failed: Missing replacement payload. (p) CSI Payload Corrupt x86_microsoft-windows-ie-vgx_31bf3856ad364e35_11.0.9600.18161_none_94f1bf5c13435d14\VGX.dll Repair failed: Missing replacement payload. Summary: Operation: Detect and Repair Operation result: 0x800f0906 Last Successful Step: Entire operation completes. Total Detected Corruption: 3 CBS Manifest Corruption: 0 CBS Metadata Corruption: 0 CSI Manifest Corruption: 0 CSI Metadata Corruption: 0 CSI Payload Corruption: 3 Total Repaired Corruption: 0 CBS Manifest Repaired: 0 CSI Manifest Repaired: 0 CSI Payload Repaired: 0 CSI Store Metadata refreshed: True I already tried to clear the WU cache but the problem persists, attached is also the CBS.log Attachments CBS.zip 677.2 KB · Views: 1
SFC is clean while now DISM shows 3 corrupt payloads which is unable to find on Windows Update and replace being: Code: Checking System Update Readiness. (p) CSI Payload Corrupt wow64_microsoft-windows-ieframe_31bf3856ad364e35_11.0.9600.18283_none_72c7637ec56c23ed\ieframe.dll Repair failed: Missing replacement payload. (p) CSI Payload Corrupt x86_microsoft-windows-ie-vgx_31bf3856ad364e35_11.0.9600.18283_none_94e8c2741349def5\VGX.dll Repair failed: Missing replacement payload. (p) CSI Payload Corrupt x86_microsoft-windows-ie-vgx_31bf3856ad364e35_11.0.9600.18161_none_94f1bf5c13435d14\VGX.dll Repair failed: Missing replacement payload. Summary: Operation: Detect and Repair Operation result: 0x800f0906 Last Successful Step: Entire operation completes. Total Detected Corruption: 3 CBS Manifest Corruption: 0 CBS Metadata Corruption: 0 CSI Manifest Corruption: 0 CSI Metadata Corruption: 0 CSI Payload Corruption: 3 Total Repaired Corruption: 0 CBS Manifest Repaired: 0 CSI Manifest Repaired: 0 CSI Payload Repaired: 0 CSI Store Metadata refreshed: True I already tried to clear the WU cache but the problem persists, attached is also the CBS.log
valistral Contributor Joined Mar 26, 2019 Posts 52 Nov 22, 2019 #5 Uninstalling superseeded KBs 3124275 and 3148198 resolved the last issue.
S Sysnative Windows Update Inactive Joined Oct 9, 2014 Posts 773 Nov 22, 2019 #6 Thanks for letting us know.