Windows 8 and 8.1 Forums


DISM - Fixing Component Store Corruption in Windows 8

Page 1 of 14 12311 ... LastLast
  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

    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





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

    1. Open an elevated command prompt.

    2. In the elevated command prompt, copy and paste the command below that you want to use.

    Note   Note
    Available Switch Options:

    /CheckHealth
    - This switch option only checks to see if a component corruption marker is already present in the registry. It is just a quick way to see if corruption currently exists, and to inform you if there is corruption. It does not fix anything or create a log. This should be finished almost instantaneous.

    /ScanHealth - This switch option does not fix any corruption. It only checks for component store corruption and records that corruption to the log file. This is useful for only logging what, if any, corruption exists. This should take around 5-10 minutes to finish.

    /RestoreHealth - (recommended) This switch option checks for component store corruption, records the corruption to the log file, and FIXES the image corruption using Windows Update. This should take around 10-15 minutes up to about an hour to finish depending on the level of corruption.


    Dism /Online /Cleanup-Image /CheckHealth

    Dism /Online /Cleanup-Image /ScanHealth

    Dism /Online /Cleanup-Image /RestoreHealth

    3. When finished, it is recommended to restart the PC to configure any updates that may have been affected by this.

    NOTE: Some scans may take a while to finish and may seem like it's hung at times, but let it sit running until finished.

    Click image for larger version

    Click image for larger version

    Click image for larger version






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

    1. Open an elevated PowerShell.

    2. In the elevated PowerShell, copy and paste the command below that you want to use.

    Note   Note
    Available Switch Options:

    -CheckHealth
    - This switch option only checks to see if a component corruption marker is already present in the registry. It is just a quick way to see if corruption currently exists, and to inform you if there is corruption. It does not fix anything or create a log. This should be finished almost instantaneous.

    -ScanHealth - This switch option does not fix any corruption. It only checks for component store corruption and records that corruption to the log file. This is useful for only logging what, if any, corruption exists. This should take around 5-10 minutes to finish.

    -RestoreHealth - (recommended) This switch option checks for component store corruption, records the corruption to the log file, and FIXES the image corruption using Windows Update. This should take around 10-15 minutes up to about an hour to finish depending on the level of corruption.


    Repair-WindowsImage -Online -CheckHealth

    Repair-WindowsImage -Online -ScanHealth

    Repair-WindowsImage -Online -RestoreHealth

    3. When finished, it is recommended to restart the PC to configure any updates that may have been affected by this.

    NOTE: Some scans may take a while to finish and may seem like it's hung at times, but let it sit running until finished.

    Click image for larger version

    Click image for larger version

    Click image for larger version





    That's it,
    Shawn


    Published by


    Brink's Avatar
    Administrator

    Join Date: Jul 2009
    Posts: 17,666



    Tutorial Tools


  2. #1



    Power User

    Join Date : Feb 2011
    bangalore
    Posts : 598
    Windows 8.1 professional x64 + WMC
    India


    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
    Brink's Avatar

    Administrator



    Join Date : Jul 2009
    Posts : 17,666
    64-bit Windows 8.1 Enterprise (RTM)
    us texas


    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



    New Member

    Join Date : May 2013
    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
    Brink's Avatar

    Administrator



    Join Date : Jul 2009
    Posts : 17,666
    64-bit Windows 8.1 Enterprise (RTM)
    us texas


    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



    Unstable Member

    Join Date : Sep 2013
    Posts : 18
    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
    Brink's Avatar

    Administrator



    Join Date : Jul 2009
    Posts : 17,666
    64-bit Windows 8.1 Enterprise (RTM)
    us texas


    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



    Unstable Member

    Join Date : Sep 2013
    Posts : 18
    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
    Brink's Avatar

    Administrator



    Join Date : Jul 2009
    Posts : 17,666
    64-bit Windows 8.1 Enterprise (RTM)
    us texas


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

  10. #9



    Junior Member

    Join Date : Sep 2013
    Posts : 30
    WIN8


    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 14 12311 ... LastLast
DISM - Fixing Component Store Corruption in Windows 8
Similar Threads
Tutorial Forum
DISM - Failed to create DismHostManager remote object General Support
IE 10 Desktop vs Windows Media Security Component Upgrade General Support
Hang ---> corruption BSOD Crashes and Debugging
Ex-Microsoft Employee Launches 'Fixing Windows 8' Campaign Windows 8 News
Eight Forums Android App Eight Forums IOS App Follow us on Facebook

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23