Windows 8 and 8.1 Forums

DISM - Fixing Component Store Corruption in Windows 8

  1. #30

    Posts : 22,503
    64-bit Windows 10

    You're welcome John. I'm glad it was able to help.

      My System SpecsSystem Spec

  2. #31

    Posts : 5
    Win8.1 Pro 64bit

    DISM and SFC have become schizoid

    I've been accustomed to regularly running both sfc and DISM on Win8, regardless of whether sfc finds corruption or not, the same as I did with Vista and Win7, but then with sfc and KB947821. The nice difference about Win8 is that even if sfc could not fix some of the corrupt files, DISM would always fix them, so that a successive sfc run would then find no corrupt files.
    Although sfc usually tells me--"Windows Resource Protection did not find any integrity violations"--running DISM.exe immediately thereafter has started giving me this, using the Restorehealth switch:
    The restore operation failed. Either the repair source was not found or the component store cannot be repaired.
    Error: 0x800f081f
    DISM failed. No operation was performed.
    For more information, review the log file."

    That made me wonder, so I ran DISM.exe with the ScanHealth switch and got the message,
    The component store is repairable.
    The operation completed successfully."

    Before, with no corrupted files, it would at least give me the message that it had repaired the non-existent corrupt files, which I always found humorous: "The restore operation completed successfully. The component store corruption was repaired. The operation completed successfully."

    Since the version of DISM.exe is still the same--6.2.9200.16384--it doesn't seem reasonable that Microsoft might have merely updated the tool so that it won't run if sfc or its own Scanhealth have not found corruption, although that possibility did occur to me.

    So the question is, what is going on? The component store can be repaired, so, according to DISM, the only explanation is that the repair source cannot be found. On the other hand, it's giving me conflicting information as to whether anything is really corrupt. Yes, it's the metadata, or, no it isn't.

    I've found that particular error discussed in a number of forums, with no workable fix; usually, though, it's in relation to updates failing to install. In this case, updates install just fine. This is a new installation of an oem Windows, and I did have to install some updates manually in getting Windows current, which hasn't happened before with Win8. Checking out
    dism.exe /online /cleanup-image /restore health failed - Microsoft Community, for instance, gives a couple of suggestions, one being to run the Windows troubleshooter on Windows Update, which does give a clue:

    "The troubleshooter made some changes to your system. Try attempting the task you were trying to do before.
    Problems found
    Windows Update components must be repaired Fixed"
    However, it does find issues "not present" as "Default Windows Update data locations have changed" and "Potential windows Update Database error detected None."
    Unfortunately, whatever the troubleshooter thinks it "fixed" does not fix the problem.

    Another suggestion in that particular Microsoft Answer, to create and run a particular batch file, does not solve the problem of the DISM error either.

    The log gives this for sfc: "Error DISM DISM Package Manager: PID=8764 TID=5864 Failed while processing command cleanup-image. - CPackageManagerCLIHandler::ExecuteCmdLine(hr:0x800f081f)".
    Also, no corruption, but metadata corruption (?!):
    "2013-10-01 08:18:05, Info CSI 00000009 CSI Store 724735956064 (0x000000a8bda11460) initialized
    2013-10-01 08:18:05, Info CSI 0000000a StoreCorruptionRepair transaction begun. WcpVersion: [l:74{37}]"6.2.9200.16683 (win8_gdr.130806-1503)".
    2013-10-01 08:18:05, Info CSI 0000000b@2013/10/1:13:18:05.170 Starting corruption detection (InnerFlags=5)
    2013-10-01 08:21:07, Info CSI 0000000c@2013/10/1:13:21:07.942 Corruption detection complete. numCorruptions = 0, Disp = 1.
    2013-10-01 08:21:07, Info CBS Repr: CSI meta data corruption found, will commit repair transaction if repair is asked.
    2013-10-01 08:21:07, Info CBS Repr: CSI Store check completes
    2013-10-01 08:21:07, Info CBS Exec:Only CSI metadata corruption found, Process CSI repair.
    2013-10-01 08:21:07, Info CSI 0000000d Creating NT transaction (seq 2), objectname [6]"(null)"
    2013-10-01 08:21:07, Info CSI 0000000e Created NT transaction (seq 2) result 0x00000000, handle @0x5f4
    2013-10-01 08:21:07, Info CSI 0000000f@2013/10/1:13:21:07.943 Beginning NT transaction commit...
    2013-10-01 08:21:07, Info CSI 00000010@2013/10/1:13:21:07.954 CSI perf trace:
    2013-10-01 08:21:07, Info CSI 00000011 StoreCorruptionRepair transaction completed.
    2013-10-01 08:21:07, Info CBS Repr: Finished repairing CSI store."
    Additionally, "Checking System Update Readiness.
    Operation: Detect and Repair
    Operation result: 0x0
    Last Successful Step: Entire operation completes.
    Total Detected Corruption: 0
    CBS Manifest Corruption: 0
    CBS Metadata Corruption: 0
    CSI Manifest Corruption: 0
    CSI Metadata Corruption: 0
    CSI Payload Corruption: 0
    Total Repaired Corruption: 0
    CBS Manifest Repaired: 0
    CSI Manifest Repaired: 0
    CSI Payload Repaired: 0
    CSI Store Metadata refreshed: True"

    Running the restorehealth from powershell gives a modified version of the error:
    PS C:\Windows\system32>
    PS C:\Windows\system32> Repair-WindowsImage -Online -RestoreHealth
    Repair-WindowsImage : The restore operation failed. Either the repair source was not found or the component store
    cannot be repaired.
    At line:1 char:1
    + Repair-WindowsImage -Online -RestoreHealth
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo : NotSpecified: ([Repair-WindowsImage], COMException
    + FullyQualifiedErrorId : Microsoft.Dism.Commands.RepairWindowsImageCommand
    Last edited by ParrotSlave; 01 Oct 2013 at 13:19.
      My System SpecsSystem Spec

  3. #32

    Posts : 22,503
    64-bit Windows 10

    Hello ParrotSlave, and welcome to Eight Forums.

    Just to help clarify: SFC repairs system files by replacing any corrupted ones found with copies from the component store. DISM only repairs the component store, and not system files. This way if SFC cannot repair files due to a corrupted component store, DISM will hopefully fix the component store to then allow SFC to be able to repair the system files.

    I'm afraid that I'm not familiar with that error either. Usually when DISM fails to repair the component store, it's time to reinstall Windows.
      My System SpecsSystem Spec

  4. #33

    Posts : 5
    Win8.1 Pro 64bit

    This is a fresh install

    The problem is that this is a fresh reinstall. I just got the laptop back from Asus Wednesday, and have been reinstalling a myriad of programs, carefully, and making a ludicrous number of system images during the process. I have two omg images, and five Windows Image Backups at the moment, although Windows does not "see" all of its backups. (It used to only see the one in the folder named "WindowsImageBackup", so you could keep it from deleting old images merely by renaming the folders, but now it is seeing its images even if they have been renamed, or, at least, most of them.) I could save the current image one way or another and then restore the older images to see when the problem began. The hassle is, depending on how far back I have to go, in activating all the third-party programs, which I just got through doing. The software companies think that we're giving away their software on street corners when they get multiple re-activation requests, apparently.
    I did copy the oem's install.wim file from the recovery partition (by using DiskImage to copy the partition, then mounting it and copying the file), which is different from the one that came with the laptop in November, and I also made my own install.wim on Saturday, and put it in a custom-refresh folder in the hope of being able to do a "refresh" to that image, but refresh does not work on this laptop via any method, the oem F9 or the advanced startup options or via any alternate boot mechanism. (Curiously, it will not boot from any Windows repair disks via WindowsImageBackup either.) It will "reset," though, since I tried that out just to see.
    I'm sorely tempted to install Windows 7 and wait a year or so for Win8 to become more stable. It is fast, but it's worse than Vista (or WinMe) when it comes to causing all-nighters.

    Is there a way to use DISM to find out if the component store in a mounted image is corrupt? What would the syntax be if, say, I had an image mounted as L:?
      My System SpecsSystem Spec

  5. #34

    Posts : 22,503
    64-bit Windows 10

    Not sure it's possible to check for a mounted image unless it was running in a virtual machine.
      My System SpecsSystem Spec

  6. #35

    Posts : 5
    Win8.1 Pro 64bit

    I had the crazy idea that I should compare the WinSxS folders between this installation and one from about three weeks ago, when DISM was working perfectly, but before Asus restored the OS (with a different base image, though.) I was thinking that, maybe, there would just be a few differences, and I could take ownership of the folder and replace any files that were different with the ones from three weeks ago. So, for the heck of it, I mounted the three-week old image and copied the WinSxS folder out of it, and used FolderMatch to compare it with the OS's WinSxS folder. Click image for larger version The file differences are astounding, and, unfortunately, it's not just one or two that are different. FolderMatch says that there are 12,684 identical folders, 2760 different folders, and 1010 orphan folders.

    However, I can get a good component store from the install.wim file, which will open with 7-Zip, so I could copy the WinSxS folder from the install.wim of the oem image and see what differences there are, since that image is only two weeks old. The problem is that Windows Update would have changed some of the files, but I'd feel safe in replacing all those with the same dates. I'm tempted to replace the entire folder except keep the orphan files in the new folder. I've replaced a few individual files in the past, when SFC reported that it couldn't fix a particular component because of a problem with a store component. In this case, SFC doesn't "know" since the files it's looking at are, so far, not corrupt. It won't know until it has to replace a corrupt file and then discovers that the store's file is also corrupt.
      My System SpecsSystem Spec

  7. #36

    Hi All,

    I have typed in the /Scanhealth command and it has been running for a lot longer than the suggested 5 - 10 minutes.. been almost 30 min and its still going.

    Is this [or any relation to] the Windows Module Installer Worker ???
      My System SpecsSystem Spec

  8. #37

    Posts : 22,503
    64-bit Windows 10

    Hello SoiCBoy,

    If you still have hard drive activity from DISM working, then it would be best to wait a bit longer to see if it may finish.
      My System SpecsSystem Spec

  9. #38

    Hey Brink

    I waited for over 30min and off memory I think there was HDD activity.

    As per my other post, does it have any relation to "Windows Module Installer Worker" as I noticed both were using about 17% of CPU.

    Anyway, I figure it was either looping or stuck and just closed the command prompt and proceed to shutdown. Then a strange thing happened, I got the message "Preparing to configure windows, do not turn off your computer". This took about 40 min and it finally shutdown, but I now wonder why the hell it took so long to configure and what was it configuring. I know it was not any window updates as I have it set to let me choose when to DL and install them. I also checked when the last updates where installed and they were dated yesterday, so it's got me stumped as to what it was that took so long??

    Any ideas as I have never experienced this on Windows 7 and to be honest, I kind of like Windows 8
      My System SpecsSystem Spec

  10. #39

    Posts : 22,503
    64-bit Windows 10

    It sounds like something may have interfered with DISM.

    Yes, "Windows Module Installer Worker" is part of what DISM and Windows Update uses. The configuring you had seen may have been for DISM repairing the component store.

    Is everything working properly now though?
      My System SpecsSystem Spec

Page 4 of 33 FirstFirst ... 2345614 ... LastLast
DISM - Fixing Component Store Corruption in Windows 8
Related Threads
How to Determine Size and if you should Clean Up Component Store (WinSxS folder) in Windows 8.1 The WinSxS folder is located in the Windows folder, for example c:\Windows\WinSxS. Itís the location for Windows Component Store files. The Windows Component Store is used to support the functions...
Solved DISM says "component store is repairable" in Performance & Maintenance
Hi guys, I recently did a routine maintenance of my computer and after running Dism /Online /Cleanup-Image /CheckHealth command, it reported that the component store is repairable. Then, I immediately followed it up with sfc /scannow and it reported no integrity violations. I was just wondering...
How to Clean Up the WinSxS Folder (Component Store) in Windows 8.1 The WinSxS folder is located in the Windows folder, for example C:\Windows\WinSxS. Itís the location for Windows Component Store files. The Windows Component Store is used to support the functions needed for the customization...
I am getting repeated Component store corruptions after any security updates. No metro apps will open yet an icon appears on the Taskbar. I have been able to repair it with DISM every time but that is beside the point. I want to know why!
A friend has been having an intermittant issue with a Win 8 app so I've run the DISM tool. When I run it, it says it completed successfully, and "the component store corruption was repaired". But if I run it again immediately, it gives the same message. I've rebooted too, same result, four times...
Hi. I've been having problems with my laptop recently. I actually care less when it comes to updates since it's automatic, but I noticed that it refuses to install any drivers (which means I cannot access any USB drives or install programs that requites drivers) or updates, after searching for...
I fixed corrupt files with the help of Brink's brilliant tutorial: 'How to use DISM to fix Component, etc, etc.......... I then wanted to see what they were in C:\Windows\Logs\CBS\CBS.log. I got as far as CBS.log, but Notepad opened & stated that I was denied access. Why? I am the Administrator....
Eight Forums Android App Eight Forums IOS App Follow us on Facebook