8

My WinSxS cleanup task was giving the "Last Run Result" of The component store has been corrupted. (0x80073712). No problem, to elevated command prompt and DISM.

>DISM /Online /Cleanup-Image /ScanHealth

Deployment Image Servicing and Management tool
Version: 6.3.9600.17031

Image Version: 6.3.9600.17031

[==========================100.0%==========================]
No component store corruption detected.
The operation completed successfully.

OK Great, should be ready to clean.

>DISM /Online /Cleanup-Image /StartComponentCleanup

Deployment Image Servicing and Management tool
Version: 6.3.9600.17031

Image Version: 6.3.9600.17031

[==========================100.0%==========================]

Error: 14098

The component store has been corrupted.

The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log

Odd, let's fix that up.

>DISM /Online /Cleanup-Image /RestoreHealth

Deployment Image Servicing and Management tool
Version: 6.3.9600.17031

Image Version: 6.3.9600.17031

[==========================100.0%==========================]
The restore operation completed successfully. The component store corruption was repaired.
The operation completed successfully.

Let's be safe and re-scan.

>DISM /Online /Cleanup-Image /ScanHealth

Deployment Image Servicing and Management tool
Version: 6.3.9600.17031

Image Version: 6.3.9600.17031

[==========================100.0%==========================]
No component store corruption detected.
The operation completed successfully.

And on to cleanup

>DISM /Online /Cleanup-Image /StartComponentCleanup

Deployment Image Servicing and Management tool
Version: 6.3.9600.17031

Image Version: 6.3.9600.17031

[==========================100.0%==========================]

Error: 14098

The component store has been corrupted.

The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log

I'm totally at a loss. How can it report as non-corrupted, repaired and corrupted all in quick succession?

Anyone considering relation of this question, sfc is of no use either.

>sfc /scannow

Beginning system scan.  This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection did not find any integrity violations.

TL;DR: My SxS store is non-corrupt, repaired and corrupted. At the same time. Unsure how to fix.

4
  • Any further clues in the log files as to what is going on? C:\Windows\Logs\CBS\CBS.log & C:\Windows\Logs\DISM\dism.log... Have you tried to repair using the Powershell command Repair-WindowsImage (not sure of the switches off the top of my head sorry..)
    – CharlesH
    Jun 26 '14 at 11:44
  • 1
    upload the CBS and DISM log files, I'll take a look at them later. Jun 26 '14 at 14:02
  • As totally non-helpful as it is, I decided I should have posted the outcome. I rebooted and it worked fine. Pride a little damaged I didn't try that before posting, but there you go. Sorry all for the delay!
    – LuckySpoon
    Jan 5 '15 at 6:31
  • You should post your own answer and accept that as the answer so it's clear in case others ever find this helpful and that there is a clear answer. Dec 26 '15 at 2:38
1

The original poster fixed the problem by rebooting - dism /Online /Cleanup-Image /RestoreHealth is indeed the command that needs to be run for Windows 8 and newer.


There is another tool that can be helpful in this kind of situation: CheckSUR, also known as the System Update Readiness Tool. You can download it for Windows 7 and before from KB947821.

According to this Microsoft blog post, CheckSUR can usually fix corruption in the component store, but when it can't, it's still possible to use it to identify the affected components. Near the end of the CheckSUR log is a list of packages; these entries correspond to Windows updates and KB articles. Get the MSU from https://support.microsoft.com/kb/NUMBER-HERE and place it in the \Windows\CheckSur\packages folder, which you may have to create. Re-run CheckSUR after you've done that for each package.

Note that CheckSUR may take a while to do its thing.

1
  • While I wasn't able to test this out it sounds like a good solution so I'll mark accepted
    – LuckySpoon
    Jan 17 '16 at 22:36
0

Had same issue. Mine was caused by an Antivirus Conflict

It was ESET File Security for Microsoft Windows Server v.6.3.12010.0

Added an exclusion for C:\Windows\WinSxS

Also added an exclusion for process dism.exe


2
  • Issue came back again. At a loss.
    – Marc
    Jul 16 '17 at 19:12
  • Add the exclusions again and see if that resolves like you said it did the first time Jul 16 '17 at 21:21

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.