DISM - Fixing Component Store Corruption in Windows 8

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

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:

• Fixing component store corruption in Windows 8 and Windows Server 2012 - The Windows Servicing Guy - Site Home - TechNet Blogs
• How to Repair a Windows Image

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

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

   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

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

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)

:ar: Dism /Online /Cleanup-Image /CheckHealth





4. To Use DISM /ScanHealth Command

   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)

:ar: Dism /Online /Cleanup-Image /ScanHealth





5. To Use DISM /RestoreHealth Command

   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)

:ar: Dism /Online /Cleanup-Image /RestoreHealth





6. To Use DISM /RestoreHealth /Source:wim Command

   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 you want to use, press Enter, and go to step 7 below. (see screenshot below)

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

OR

(To prevent DISM from using Windows Update for online images)
:ar: Dism /Online /Cleanup-Image /RestoreHealth /Source:wim:Full Path to install.wim file:1 /limitaccess

For example:

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





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

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)

Repair-WindowsImage /Cleanup-Image /CheckHealth





4. To Use DISM /ScanHealth Command

   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)

Repair-WindowsImage /Cleanup-Image /ScanHealth





5. To Use DISM /RestoreHealth Command

   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)

Repair-WindowsImage /Cleanup-Image /RestoreHealth





6. To Use DISM /RestoreHealth /Source:wim Command

   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 you want to use, press Enter, and go to step 7 below. (see screenshot below)

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

OR

(To prevent DISM from using Windows Update for online images)
:ar: Dism /Online /Cleanup-Image /RestoreHealth /Source:wim:Full Path to install.wim file:1 /limitaccess

For example:

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





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

Related Tutorials

---

• How to Run the "SFC /SCANNOW" Command at Boot or in Windows 8 and 8.1
• How to Do a Repair Install of Windows 8 and 8.1 without Losing Anything
• How to Reset Windows Update in Vista, Windows 7, and Windows 8
• How to Refresh Windows 8 and 8.1
• How to Reset Windows 8 and 8.1
• How to Do a System Restore in Windows 8 and 8.1
• How to Determine Size and if you should Clean Up Component Store (WinSxS folder) in Windows 8.1
• How to Clean Up the WinSxS Folder (Component Store) in Windows 8.1

 

[Brink]

You would use the one for what you currently have installed.

 

[remriel]

Windows 8.1 has been acting very strangely. No apps will open. The splash screen opens, then it minimizes. I get errors opening Event Viewer, Powershell, and sometimes random programs.

PC settings wasn't opening until I ran another hotfix. When I try to update or reinstall the apps from the Store, they all fail with some different error for each.

I ran DISM and I get an error. I run sfc, I get an error.
Version: 6.3.9600.17031


Image Version: 6.3.9600.17031


[==========================100.0%==========================]
The restore operation failed. Either the repair source was not found or the comp
onent store cannot be repaired.


Error: 0x800f081f


DISM failed. No operation was performed.
For more information, review the log file.


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

 

[Brink]

Hello Remriel, and welcome to Eight Forums.

That pretty much means that you will need to refresh or reinstall Windows.

 

[remriel]

Yep, I figured. I just did a refresh and got an error: No changes were made. No system restore points. I'm pretty much screwed. I just downloaded CrashPlan. Screw Windows 8. Back to 7.

 

[kyleseeman]

I tried to run the Dism /Online /Cleanup-Image /RestoreHealth and received Error: 0x800f081f ; source files could not be found, says to use "Source"option to specify the location of the files that are required to restore the feature.
it ran 100%

Tried Running Dism /Online /Cleanup-Image /CheckHealth and says Component store is repairable.


Any help what to do next?

 

[Brink]

Hello Kyle,

See if cleaning up the component store first with the command below will allow the /RestoreHealth command successfully run afterwards.

Dism.exe /online /Cleanup-Image /StartComponentCleanup

http://www.eightforums.com/tutorials/44351-winsxs-folder-component-store-clean-up-windows-8-1-a.html

 

[Baplus]

Thanks for the guide Brink.

I am having issues with the System Restore (0x81000204) and No audio after sleep (Windows 8 Dell Laptop, no error message). chkdsk says everything is fine, however running the SFC /Scannow showed there were some errors and fixed some of them. The rest got fixed with DISM.

I want to know if the fixings done with DISM will stay if I restore my system? I have my eyes on a suspicious windows update that might have started all of this...

So attempt System Restore? or would that just put me back with all the corrupted files?

 

[Brink]

Hello Baplus, and welcome to Eight Forums.

You are correct. If you do a system restore, it will restore the system files back to how they were when the restore point was created.

Now if they were corrupted or not at that time will be determined afterwards though.

 

[Baplus]

I see...

Again. Many thanks for the guide. It has saved my life and laptop!

 

[Mooly]

Great tutorial as ever Shawn.

I've just had to use the "restore health" option but the reasons why are strange for those interested...


I've done a clean W8.1 install, followed by installing drivers from USB and only then allowing Windows Update. All good. I ran disk clean + clean system files. That was OK and freed nearly 1Gb. Still all good and SFC reports all OK. I install two programmes reboot and again run SFC. Still all good and so I run the disk clean + clean system files once more and reboot. SFC now reports non fixable errors that fortunately the DISM on line checker was able to repair.

I have confirmed (by backtracking with Acronis images) that running the disk clean after installing these programmes corrupts the file store. How can that be though ?

 

[Brink]

Great tutorial as ever Shawn.

I've just had to use the "restore health" option but the reasons why are strange for those interested...


I've done a clean W8.1 install, followed by installing drivers from USB and only then allowing Windows Update. All good. I ran disk clean + clean system files. That was OK and freed nearly 1Gb. Still all good and SFC reports all OK. I install two programmes reboot and again run SFC. Still all good and so I run the disk clean + clean system files once more and reboot. SFC now reports non fixable errors that fortunately the DISM on line checker was able to repair.

I have confirmed (by backtracking with Acronis images) that running the disk clean after installing these programmes corrupts the file store. How can that be though ?

Hello Mooly,

It cleaned unneeded files that also prevented SFC from being able to repair them unless you use DISM to allow SFC to afterwards.

 

[Mooly]

Thanks for the explanation Shawn.

(I'm still very much finding my way around W8.1 and I can tell you my heart sank when I saw those unfixable errors... but thanks to this a quick fix was possible)

 

[Brink]

You're welcome. Yeah, cleaning is a toss up of freeing up more space, or keeping them in case SFC may need them.

 

[kyleseeman]

Brink,
I ran the component restore as you said, then ran the restore health command and I still cannot refresh or reset my computer. Any steps else to do?

Hello Kyle,

See if cleaning up the component store first with the command below will allow the /RestoreHealth command successfully run afterwards.

Dism.exe /online /Cleanup-Image /StartComponentCleanup

http://www.eightforums.com/tutorials/44351-winsxs-folder-component-store-clean-up-windows-8-1-a.html

 

[Brink]

In that case you may need to do a clean install of Windows instead.

 

[kyleseeman]

In that case you may need to do a clean install of Windows instead.

Can you direct to where I can find how to do that?

 

[Brink]

Sure thing.

http://www.eightforums.com/tutorials/2299-clean-install-windows-8-a.html

OR

http://www.eightforums.com/tutorial...e-firmware-interface-install-windows-8-a.html

 

[mklassy]

I am having the CBS.log file issue as well however when I run the dism command it tells me the dism commands are unknown. What do you suggest?

 

[Brink]

Hello mklassy, and welcome to Eight Forums.

See if running a sfc /scannow command may help if it's just a corrupted system file at fault. If any issues are found and repaired, then try the dism command again.

 

[David Bailey]

I am having the CBS.log file issue as well however when I run the dism command it tells me the dism commands are unknown. What do you suggest?

A full screenshot of the command window with the dism error message would help.