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

 

[brummyfan]

Thanks for saving a lot of time today :thumb:

 

[Brink]

You're most welcome Brummy. Glad it could help.

 

[ICit2lol]

Thanks Shawn this one got me out of trouble - machine slowing a bit and the SFC coming up corrupt - the other fixes didn't work but this one did although I got a bit concerned at how long it hung on 20% LOL!!

 

[Brink]

I'm glad it could help John. How long did it hang at 20%?

 

[ICit2lol]

About 7 - 8 minutes I had just started to think it has frozen on me when it flashed up the fixed message.

 

[Brink]

It would be nice to have some sort of better progress indicator than that. LOL

 

[ICit2lol]

Yep Shawn it was stuck on this till the end.

 

[yowanvista]

   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 C:\Windows\Logs\CBS\CBS.log. 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 C:\Windows\Logs\CBS\CBS.log, 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.

Should that part state "C:\Windows\Logs\DISM" instead of "C:\Windows\Logs\CBS\"? I just performed a health check and the log was saved in the DISM folder, not in the CBS one.

 

[Brink]

Hello Yowan,

Actually it should log to both, but I found that it often does to one or the other. I've changed to just say log file there, so that the two log file paths are shown in the Note box at the top of the tutorial instead.

 

[laurie]

I would like to say thank you for explaining in a way I understood. I discovered by doing scan for errors that there were errors in store then I found many messages in the event viewer back to nov and it seem I had a problem with updates and couldn't get pc to start. I ran the scanhealth it came back with problem but said it could be repaired then I ran repairhealth and it said it was repaired and no more messages in event viewer.

 

[Brink]

I would like to say thank you for explaining in a way I understood. I discovered by doing scan for errors that there were errors in store then I found many messages in the event viewer back to nov and it seem I had a problem with updates and couldn't get pc to start. I ran the scanhealth it came back with problem but said it could be repaired then I ran repairhealth and it said it was repaired and no more messages in event viewer.

I'm glad it could Laurie, and welcome to Eight Forums.

 

[popeye]

One of the best tutorials here. I thought I knew quite a bit until I came here. DISM is amazing.

Feel kind of ignorant compared to many of the people who help here.

 

[JohnBurns]

I really appreciate this site and this particular thread. The last 2 days, I couldn't get SFC Scandisk or DISM Scan to fix corruption - even tho I followed the directions completely. After System Restoring Windows and Restoring a backup I had saved, still no success. I am posting to let others know what finally succeeded for me. I used the Woindows 8 Action Center Troubleshooter. By troubleshooting Windows Update, the exact error I had been receiving in DISM was fixed and SFC Scannow disclosed no corruption. If anyone is at his or her wits end, you might want to give this a try. Needless to say, I haven't really paid much attention to this built-in tool, but I will in the future.

Update: It didn't fix DISM even tho it indicated DISM error had been fixed. I have posted situation in another post on 02/05/2014 (Post #77)

 

[Sandra Leigh]

Hi, All -

I have used the 'sfc /scannow' and 'dism /Online /Cleanup-Image /RestoreHealth' on a new laptop that was having issues, but I've never used it on a 'mature' computer with lots of programs installed and lots of data. Is it safe to run these commands and preserve the installed programs/files?

Thanks,

Sandy

 

[David Bailey]

Hi, All -

I have used the 'sfc /scannow' and 'dism /Online /Cleanup-Image /RestoreHealth' on a new laptop that was having issues, but I've never used it on a 'mature' computer with lots of programs installed and lots of data. Is it safe to run these commands and preserve the installed programs/files?

Thanks,

Sandy

Yes.

 

[Sandra Leigh]

Excellent! Thank you, David!

 

[David Bailey]

Excellent! Thank you, David!

You are welcome. +

 

[JohnBurns]

When I run DISM Scan, it indicates "The component store is repairable". Yet when I run DISM Restore Health, it can't repair and I get error 0x800f081f. I have searched and searched for an answer, but I am not technical enough to understand what my problem might be. SFC Scannow runs fine and no problems are found - likewise with DSKCHK. I am not presently having any problems that I am aware of - but this thing with DISM bothers me. Is there a site I can go to have my CBS and DISM Logs reviewed, to possibly find out what is going on?

 

[JohnBurns]

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.

crosspatch - I feel the way you do about this, but so far I find no answers. were you ever able to resolve this and get DISM Scan working properly again?

 

[Brink]

Hello John,

Usually if DISM fails, you'll need to either refresh, reset, or reinstall Window.

Since you are not having any problems, then there's really no need to do so unless you just really wanted to.