<

Windows 8 and 8.1 Forums


DISM - Fixing Component Store Corruption in Windows 8

  1. #1
    DISM - Fixing Component Store Corruption in Windows 8

    DISM - Fixing Component Store Corruption in Windows 8
    How to Use DISM to Fix Component Store Corruption in Windows 8 and Windows Server 2012
    Published by Brink is offline
    12 Jun 2013
    Default DISM - Fixing Component Store Corruption in Windows 8

    Published by


    Brink's Avatar
    Administrator

    Join Date: Jul 2009
    Posts: 20,449

    How to Use DISM to Fix Component Store Corruption in Windows 8 and Windows Server 2012

    information   Information
    One of the most used tools when fixing corruption for Vista, Windows 7, Windows Server 2008 and Windows Server 2008 R2 was the System Update and Readiness Tool (KB947821), commonly called CheckSUR. The CheckSUR tool was an excellent way for most people to see what corruption had happened on their store, and potentially fix that corruption if the tool contained the payload to do so.

    In Windows 8/8.1 and Windows Server 2012, this has changed. Itís called Inbox Corruption Repair and it brings the functionality of CheckSUR into Windows rather than requiring a separate download to get the utility like you do now. This is exposed in two ways, the first is really unseen by the end user and happens when Windows detects a corrupted state when attempting to install fixes via Windows Update. When this happens, Windows fix the corruption silently and then re-install the prior packages. The manual way to use this tool is via DISM (Deployment Imaging and Servicing Management). The way this is exposed is via the DISM /Cleanup-Image functionality.

    If a Windows image (Windows component store) becomes unserviceable, you can use the Deployment Imaging and Servicing Management (DISM) tool to update the files and correct the problem.

    For example:

    • To use to fix Windows component store corruption when a SFC /SCANNOW command is unable to repair corrupted system files because the store (source) is corrupted, then run the SFC command again.
    • To use to fix Windows component store corruption when the same Windows Updates continue to appear to be available to install even though they already show successfully installed in update history.


    For more information, see:




    This tutorial will show you how to do an Inbox Corruption Repair with the DISM /Cleanup-Image tool to fix component store corruption in Windows 8 and Windows Server 2012.

    You must be signed in as an administrator to be able to do an Inbox Corruption Repair with the Deployment Imaging and Servicing Management (DISM) tool.

    Note   Note
    The DISM /Cleanup-Image tool saves it's log files in the file locations below. To be able to view these logs, you would need to copy them from the locations below to your desktop, then open them from your desktop.

    C:\Windows\Logs\CBS\CBS.log

    C:\Windows\Logs\DISM\dism.log



    Click image for larger version

    Click image for larger version

    Tip   Tip
    If you get an error like below when running a DISM command in an option below, then run the command below and try again afterwards.

    Dism.exe /online /Cleanup-Image /StartComponentCleanup


    Note   Note
    Error: 0x80240021

    Failure DISM. No operation was performed.


    CONTENTS:

    • Option One: To Run "DISM /Cleanup-Image" tool in an Elevated Command Prompt
    • Option Two: To Run "DISM /Cleanup-Image" tool in an Elevated PowerShell







    OPTION ONE
    To Run "DISM /Cleanup-Image" tool in an Elevated Command Prompt

    1. Open an elevated command prompt.

    2. Do step3, step 4, step 5, or step 6 below for what DISM command you would like to use.


    3. To Use DISM /CheckHealth Command
    Note   Note
    You would use /CheckHealth to only check whether the image has been flagged as corrupted by a failed process and whether the corruption can be repaired. This is just a quick way to see if corruption currently exists, and to inform you if there is corruption. This does not fix anything or create a log. This will finish running almost instantly.


    A) In the elevated command prompt, copy and paste the command below, press Enter, and go to step 7 below. (see screenshot below)

    Dism /Online /Cleanup-Image /CheckHealth

    Click image for larger version


    4. To Use DISM /ScanHealth Command
    Note   Note
    You would use /ScanHealth to scan the image for component store corruption. This option does not fix any corruption. It only checks for component store corruption and records that corruption to the log file. This can take around 5-10 minutes to finish. It will stay at 20% for a while before continuing.


    A) In the elevated command prompt, copy and paste the command below, press Enter, and go to step 7 below. (see screenshot below)

    Dism /Online /Cleanup-Image /ScanHealth

    Click image for larger version


    5. To Use DISM /RestoreHealth Command
    Note   Note
    (recommended) You would use /RestoreHealth to scan the image for component store corruption, perform repair operations automatically, and records that corruption to the log file. This can take around 10-15 minutes up to a few hours to finish depending on the level of corruption. It will stay at 20% for a while before continuing.


    A) In the elevated command prompt, copy and paste the command below, press Enter, and go to step 7 below. (see screenshot below)

    Dism /Online /Cleanup-Image /RestoreHealth

    Click image for larger version


    6. To Use DISM /RestoreHealth /Source:wim Command
    Note   Note
    You would use /Source with /RestoreHealth to specify the location of an install.wim file as the source of known good versions of files that can be used for the repair. This can take around 10-15 minutes up to a few hours to finish depending on the level of corruption. It will stay at 20% for a while before continuing.

    This can be useful if step 5 above was not able to repair the Windows image (component store).


    The install.wim file will be in the Sources folder of a mounted Windows 8.1 ISO file.


    A) In the elevated command prompt, type the command below, press Enter, and go to step 7 below. (see screenshot below)

    Dism /Online /Cleanup-Image /RestoreHealth /Source:wim:Full Path to install.wim file:1 /limitaccess

    For example:

    Dism /Online /Cleanup-Image /RestoreHealth /Source:wim:D:\sources\install.wim:1 /limitaccess

    Click image for larger version


    7. If you did step 5 or step 6 above, it is recommended to restart the computer to fully apply.






    OPTION TWO
    To Run "DISM /Cleanup-Image" tool in an Elevated PowerShell

    1. Open an elevated PowerShell.

    2. Do step3, step 4, step 5, or step 6 below for what DISM command you would like to use.


    3. To Use DISM /CheckHealth Command
    Note   Note
    You would use /CheckHealth to only check whether the image has been flagged as corrupted by a failed process and whether the corruption can be repaired. This is just a quick way to see if corruption currently exists, and to inform you if there is corruption. This does not fix anything or create a log. This will finish running almost instantly.


    A) In the elevated command prompt, copy and paste the command below, press Enter, and go to step 7 below. (see screenshot below)

    :arrow: Repair-WindowsImage /Cleanup-Image /CheckHealth

    Click image for larger version


    4. To Use DISM /ScanHealth Command
    Note   Note
    You would use /ScanHealth to scan the image for component store corruption. This option does not fix any corruption. It only checks for component store corruption and records that corruption to the log file. This can take around 5-10 minutes to finish. It will stay at 20% for a while before continuing.


    A) In the elevated command prompt, copy and paste the command below, press Enter, and go to step 7 below. (see screenshot below)

    :arrow: Repair-WindowsImage /Cleanup-Image /ScanHealth

    Click image for larger version


    5. To Use DISM /RestoreHealth Command
    Note   Note
    (recommended) You would use /RestoreHealth to scan the image for component store corruption, perform repair operations automatically, and records that corruption to the log file. This can take around 10-15 minutes up to a few hours to finish depending on the level of corruption. It will stay at 20% for a while before continuing.


    A) In the elevated command prompt, copy and paste the command below, press Enter, and go to step 7 below. (see screenshot below)

    :arrow: Repair-WindowsImage /Cleanup-Image /RestoreHealth

    Click image for larger version


    6. To Use DISM /RestoreHealth /Source:wim Command
    Note   Note
    You would use /Source with /RestoreHealth to specify the location of an install.wim file as the source of known good versions of files that can be used for the repair. This can take around 10-15 minutes up to a few hours to finish depending on the level of corruption. It will stay at 20% for a while before continuing.

    This can be useful if step 5 above was not able to repair the Windows image (component store).


    The install.wim file will be in the Sources folder of a mounted Windows 8.1 ISO file.


    A) In the elevated command prompt, type the command below, press Enter, and go to step 7 below. (see screenshot below)

    Dism /Online /Cleanup-Image /RestoreHealth /Source:wim:Full Path to install.wim file:1 /limitaccess

    For example:

    Dism /Online /Cleanup-Image /RestoreHealth /Source:wim:D:\sources\install.wim:1 /limitaccess

    Click image for larger version


    7. If you did step 5, step 6, or step 7 above, it is recommended to restart the computer to fully apply.





    That's it,
    Shawn


  2. #1


    bangalore
    Posts : 634
    Windows 8.1 professional x64 + WMC


    Hi,

    I tried the sfc scannow and it was stuck at 100%. In MS site they mentioned it was caused due to a update

    KB2821895 Windows 8 x64 Update 06.11.2013 problem - Microsoft Community


    I tried to execute the restore health command but I get error message saying that the operation has failed error code 3017

    Here is the DISM log. Please help me out

    http://www.filedropper.com/newwinzipfile

      My System SpecsSystem Spec

  3. #2


    Posts : 20,449
    64-bit Windows 10 build 10166


    Hell Manjunath,

    If you haven't already, you could try uninstalling that Windows Update, or doing a system restore using a restore point dated before this to see if you may be able to run SFC or DISM afterwards.

    Hope this may help for now.
      My System SpecsSystem Spec

  4. #3


    Posts : 1
    windows 8 X64


    Hello Brink
    and really thanks for this forium web and your usefull tut
    I scan my windows 8.1 by sfc/scannow and give me this error in 72% procces :

    "Windows Resource Protection found corrupt files but was unable to fix someof them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For
    example C:\Windows\Logs\CBS\CBS.log. Note that logging is currently not
    supported in offline servicing scenarios."

    I scan my windows because the windows charms search bar hanging after I run it and force me to restart just with power key
    could you please help me to resolve this problem and fix CBS.log file
    thanks
    have fun time
      My System SpecsSystem Spec


  5. #4


    Posts : 20,449
    64-bit Windows 10 build 10166


    Hello Amirchermahini, and welcome to Eight Forums.

    That means that SFC was unable to repair some of the files since the files needed to repair them with in the component store are also corrupted.

    You could run the command below in this tutorial to repair the component store. Afterwards try running the SFC scan again to see if it's able to repair the corrupted system files it found.

    Dism /Online /Cleanup-Image /RestoreHealth


    Hope this helps,
    Shawn
      My System SpecsSystem Spec

  6. #5


    Posts : 23
    Windows 8.1 Pro x64


    I'm stuck. I used to run the Dism /Online /Cleanup-Image /RestoreHealth command relatively frequently, and it always worked fine. Now, I'm getting the following error after running it:

    The restore operation failed. Either the repair source was not found or the component store cannot be repaired.

    I searched for a solution, and found advice to use the /LimitAccess switch. I never had to use that before, however, and it didn't help now. I'm doing this on my home PC, not in any sort of enterprise or other managed environment.

    When I run the Dism /Online /Cleanup-Image /ScanHealth and Dism /Online /Cleanup-Image /CheckHealth commands, I get:

    The component store is repairable.
    The operation completed successfully.

    When I run sfc /ScanNow, I get:

    Windows Resource Protection did not find any integrity violations.

    Can anyone help me get Dism to run as it should?
      My System SpecsSystem Spec

  7. #6


    Posts : 20,449
    64-bit Windows 10 build 10166


    Hello crosspatch, and welcome to Eight Forums.

    If SFC didn't find any issues, then you should be good to go and don't need to run Dism.
      My System SpecsSystem Spec

  8. #7


    Posts : 23
    Windows 8.1 Pro x64


    Thank you. I understand that there is no corruption now, but I want Dism to work if/when I need it to in the future. And since it always used to run without a problem, this bothers me.
      My System SpecsSystem Spec

  9. #8


    Posts : 20,449
    64-bit Windows 10 build 10166


    Usually when Dism fails, you'll need to reinstall Windows.
      My System SpecsSystem Spec

  10. #9


    hi guys

    i ve followed the option one got errors ,and then tried the powershell method again error,
    please see the attached screencopy

    any way to sort this out?

    thanks
    Click image for larger version
      My System SpecsSystem Spec

Page 1 of 24 12311 ... LastLast
DISM - Fixing Component Store Corruption in Windows 8

Similar Threads
Tutorial Forum
WinSxS Folder (Component Store) - Analyze in Windows 8.1
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...
Tutorials
DISM says "component store is repairable"
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...
Performance & Maintenance
WinSxS Folder (Component Store) - Clean Up in Windows 8.1
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...
Tutorials
Component Store corruption Win 8.1
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!
Software and Apps
DISM tool continually finds corruption
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...
General Support
Windows Update kb2919355 causes component store corruption
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...
Windows Updates & Activation
Why am I denied access to CBS.log file- fixing corruption?
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....
General Support

Eight Forums Android App Eight Forums IOS App Follow us on Facebook