DISM - Fixing Component Store Corruption in Windows 8

Brink · Aug 21, 2015

Nar, it has to be a .wim or .esd file specified. If the USB doesn't have it, then you'll need to download an ISO file to use.

jumanji · Aug 21, 2015

OK, The ISO download is in progress.

I may also draw your attention to this TechNet article based on which I wanted to try Dism /Online /Cleanup-Image/RestoreHealth /Source:I:\sources\sxs /LimitAccess

https://technet.microsoft.com/en-us/library/hh825020.aspx Configure a Windows Repair Source

Extract from that article for your ready perusal:

"You can use a mounted Windows image from a WIM file as a source to restore optional features and repair a corrupted operating system. For example, c:\test\mount\Windows. For more information about capturing a Windows image as a WIM file, see Capture Images of Hard Disk Partitions Using DISM.You can use a running Windows installation as a source to restore optional features by sharing the c:\Windows folder on your network.

You can use a Windows side-by-side folder from a network share or from a removable media, such as the Windows DVD, as the source of the files. For example, z:\sources\SxS.

You can use a Windows image (.wim) file on a network share as a source to restore optional features. You must specify the index of the Windows image in the .wim file that you want to use and you must use a Wim: prefix in the path to identify this file format. For example, to specify index 3 in a file named contoso.wim, type: Wim:\\network\images\contoso.wim:3."

Not sure whether I have misunderstood the context in which the above is made.

Anyway, once the ISO is downloaded successfully, I shall keep it in reserve and try Dism /Online /Cleanup-Image/RestoreHealth /Source:I:\sources\sxs /LimitAccess first. If it is not successful,I will then try the ISO.

Thanks for your time.

Brink · Aug 21, 2015

I've never tried the "I:\sources\sxs" method, but found the .wim or .esd to work well.

Please let us know how it went.

David Bailey · Aug 21, 2015

I found that option #3 in the offered program worked well using an install.esd instead of an install.wim.
Check it out.
Read the entire thread please.

Posted wrong thing. :cry:

This is the correct thread-

http://www.eightforums.com/performa...-dism-restorehealth-repair-corrupt-files.html

jumanji · Aug 22, 2015

Thanks, David Bailey, I had seen that thread even three days back and what caught my attention was your post
http://www.eightforums.com/performa...health-repair-corrupt-files-2.html#post521787 which in effect said that install.wim is no longer supplied and it is only install.esd now.

I thought I should first try to use the available tool DISM , rather than downloading another software to run it. I shall revert back after my experiment with DISM.

jumanji · Aug 22, 2015

Brink said:
Nar, it has to be a .wim or .esd file specified. If the USB doesn't have it, then you'll need to download an ISO file to use.

The downloaded ISO file when mounted has the same set of files as written on the USB drive and still install.esd only and no install .wim. Expected.

I then used this command Dism /Online /Cleanup-Image /RestoreHealth/Source:I:\sources\sxs /limitaccess. No luck.

Then tried the following commands.
Dism /Online /Cleanup-Image /RestoreHealth/Source:wim:I:\sources\install.esd:1 /limitaccess
Dism /Online /Cleanup-Image /RestoreHealth /Source:esd:I:\sources\install.esd:1 /limitaccess

Still the same error.

So then I have to find a way out to restore health.

The DISM log:

sfc /scannow however gives a clean chit. No integrity violations. All OK.

@David Bailey, I tried Image Health by KHIY. It worked taking in the install.esd but finally cannot repair. I shall post it under the thread http://www.eightforums.com/performa...rehealth-repair-corrupt-files.html#post512565 perhaps tomorrow.

Cliff S · Aug 22, 2015

jumanji said:
Brink said:

Nar, it has to be a .wim or .esd file specified. If the USB doesn't have it, then you'll need to download an ISO file to use.

Click to expand...

The downloaded ISO file when mounted has the same set of files as written on the USB drive and still install.esd only and no install .wim. Expected.

I then used this command Dism /Online /Cleanup-Image /RestoreHealth/Source:I:\sources\sxs /limitaccess. No luck.
View attachment 65009

Then tried the following commands.
Dism /Online /Cleanup-Image /RestoreHealth/Source:wim:I:\sources\install.esd:1 /limitaccess
Dism /Online /Cleanup-Image /RestoreHealth /Source:esd:I:\sources\install.esd:1 /limitaccess

Still the same error.

View attachment 65010

So then I have to find a way out to restore health.

The DISM log:

View attachment 65011

sfc /scannow however gives a clean chit. No integrity violations. All OK.

@David Bailey, I tried Image Health by KHIY. It worked taking in the install.esd but finally cannot repair. I shall post it under the thread http://www.eightforums.com/performa...rehealth-repair-corrupt-files.html#post512565 perhaps tomorrow.

You could try:
Dism /Online /Cleanup-Image /RestoreHealth /Source:I:\sources\install.esd

David Bailey · Aug 22, 2015

@David Bailey, I tried Image Health by KHIY. It worked taking in the install.esd but finally cannot repair. I shall post it under the thread SFC SCANNOW and DISM RESTOREHEALTH - Repair Corrupt Files perhaps tomorrow.

I just posted it because it worked for me.

Glad you tried it.
Sometimes what works for one will not work for another.

jumanji · Aug 22, 2015

Cliff S said:
..........You could try:
Dism /Online /Cleanup-Image /RestoreHealth /Source:I:\sources\install.esd

Tried. Same error.

David Bailey · Aug 22, 2015

jumanji said:
Cliff S said:

..........You could try:
Dism /Online /Cleanup-Image /RestoreHealth /Source:I:\sources\install.esd

Click to expand...

Tried. Same error.

View attachment 65015

Maybe you needed to add the "limit access" part ?

David Bailey · Aug 22, 2015

Just a thought.

If Microsoft supplies sfc & dism to fix things, they should work flawlessly.

Either online with Windows Update or from install.esd or install.wim.

I can only surmise Microsoft wants people to call them for an ungodly fee to get help.

Not a good way to do business.

Cliff S · Aug 22, 2015

Thank you David!

Brink · Aug 22, 2015

jumanji said:
Cliff S said:

..........You could try:
Dism /Online /Cleanup-Image /RestoreHealth /Source:I:\sources\install.esd

Click to expand...

Tried. Same error.

View attachment 65015

Jumanji,

If nothing is helping, then you could also do a repair install that should sort it without losing anything.

http://www.eightforums.com/tutorials/26095-repair-install-windows-8-a.html

brokensoftware · Aug 29, 2015

I've tried the /Source argument with various subarguments and it's always given the "can't find source files" even though the sources for sure are there. I wonder if the syntax of this argument is causing a problem somewhere deeper than "cmd.exe" and "dism.exe" for some (most?) of us out here?

Cliff S · Aug 29, 2015

brokensoftware said:
I've tried the /Source argument with various subarguments and it's always given the "can't find source files" even though the sources for sure are there. I wonder if the syntax of this argument is causing a problem somewhere deeper than "cmd.exe" and "dism.exe" for some (most?) of us out here?

I don't know, the one I posted worked always for me since the early preview versions, even when it didn't for some of the other insiders. I mean it works for some, but not for others.

brokensoftware · Aug 29, 2015

Cliff S said:
I don't know, the one I posted worked always for me since the early preview versions, even when it didn't for some of the other insiders. I mean it works for some, but not for others.

At the moment my system is almost catatonic as the DISM command is sitting there doing no apparent disk accessing, File Explorer is nonresponding, and Avast may or may not be causing programs like Process Explorer and Task Manager to NOT start up (at least their GUI parts), so I can't go into the DISM log file and see what's what - it's about an hour+ old, though, as of the last time I could use File Explorer (...) so I think DISM has gone south, too.

Next time I try all this I'll be sure to stop AVAST =first=, nt after I've already started up DISM...

Have a keyboard way to kill DISM? - CTRL-C in the command window sure didn't.

About ready to hit a reboot button...

----

Post-post edit: did hit the reboot button - will start up DISM again using the full /Source argument with an install.esd as the source - the command line showed up fine in the dism.log file last time so I'm expecting the same this time, however I fully expect the same error w.r.t. THAT source - however, I tweaked the Group Policy to use Windows Update as the 1st source per instructions around here so maybe THAT source will come through. Anyway, will start this all up and leave for an hour or so - will repost if things turned out okay. The DISM command line I'm using with a mounted Windows.ISO file is:

Code:

Dism  /Online /Cleanup-Image /RestoreHealth /Source:esd:G:\sources\install.esd:1 /limitaccess

Wish me luck!

brokensoftware · Aug 29, 2015

Okay, I'm back and the DISM command as copy-n-pasted above broke again - from the dism.log here's what DISM thought I told it to do:

Code:

2015-08-29 13:45:27, Info                  DISM   DISM.EXE: <----- Starting Dism.exe session ----->
2015-08-29 13:45:27, Info                  DISM   DISM.EXE: 
2015-08-29 13:45:27, Info                  DISM   DISM.EXE: Host machine information: OS Version=6.3.9600, Running architecture=amd64, Number of processors=4
2015-08-29 13:45:27, Info                  DISM   DISM.EXE: Dism.exe version: 6.3.9600.17031
2015-08-29 13:45:27, Info                  DISM   DISM.EXE: Executing command line: [COLOR=#ff0000]Dism  /Online /Cleanup-Image /RestoreHealth /Source:esd:G:\sources\install.esd:1 /limitacces[/COLOR][COLOR=#ff0000]s[/COLOR]

and here is what DISM finally failed with:

Code:

2015-08-29 15:45:06, Warning               DISM   DISM Package Manager: PID=4892 TID=980 [COLOR=#ff0000]CBS AddSource failed with HRESULT=0x8007007b![/COLOR] - CDISMPackageManager::Internal_Finalize
2015-08-29 15:45:06, Info                  DISM   DISM Package Manager: PID=4892 TID=980 CBS session options=0x28100! - CDISMPackageManager::Internal_Finalize
2015-08-29 16:14:59, Info                  DISM   DISM Package Manager: PID=4892 TID=2428  Error in operation: source for package or file not found, ResolveSource() unsuccessful. (CBS HRESULT=0x800f081f) - CCbsConUIHandler::Error
2015-08-29 16:14:59, Error                 DISM   DISM Package Manager: PID=4892 TID=980 Failed finalizing changes. - CDISMPackageManager::Internal_Finalize(hr:0x800f081f)
2015-08-29 16:14:59, Error                 DISM   DISM Package Manager: PID=4892 TID=980 The source files could not be found; their location must be specified using the /source option to restore the feature. - GetCbsErrorMsg
2015-08-29 16:14:59, Error                 DISM   DISM Package Manager: PID=4892 TID=980 Failed processing package changes with session option CbsSessionOptionRepairStoreCorruption - CDISMPackageManager::RestoreHealth(hr:0x800f081f)
2015-08-29 16:14:59, Error                 DISM   DISM Package Manager: PID=4892 TID=980 The source files could not be found; their location must be specified using the /source option to restore the feature. - GetCbsErrorMsg
2015-08-29 16:14:59, Error                 DISM   DISM Package Manager: PID=4892 TID=980 Failed to restore the image health. - CPackageManagerCLIHandler::ProcessCmdLine_CleanupImage(hr:0x800f081f)
2015-08-29 16:14:59, Error                 DISM   DISM Package Manager: PID=4892 TID=980 Failed while processing command cleanup-image. - CPackageManagerCLIHandler::ExecuteCmdLine(hr:0x800f081f)

This is an interesting response - more so because HERE is a snippet of the CBS.log file showing that the path I gave to DISM has been totally munged by the time it got to CBS:

Code:

2015-08-29 15:45:06, Info                  CBS    Session: 30466707_885613462 initialized by client DISM Package Manager Provider.
2015-08-29 15:45:06, Info                  CBS    Exec: Addsource called, Session: 30466707_885613462, Client: DISM Package Manager Provider, from GPO: No, [COLOR=#ff0000]Path: C:\WINDOWS\system32\esd:G:\sources\install.esd:1[/COLOR]
2015-08-29 15:45:06, Warning               CBS    The alternate source path directory could not be accessed [HRESULT = 0x8007007b - ERROR_INVALID_NAME]
2015-08-29 15:45:06, Info                  CBS    Failed to add new file source [HRESULT = 0x8007007b - ERROR_INVALID_NAME]
2015-08-29 15:45:06, Info                  CBS    Failed to add alternate file source [HRESULT = 0x8007007b - ERROR_INVALID_NAME]
2015-08-29 15:45:06, Info                  CBS    Failed adding alternate source directory [HRESULT = 0x8007007b - ERROR_INVALID_NAME]
2015-08-29 15:45:06, Info                  CBS    Failed to Add Source using worker session [HRESULT = 0x8007007b]

so it is not surprising the source directory caused a "Huh? That doesn't exist!" response from CBS which told DISM "Fail!".

Since I've now set up DISM to go directly to Windows Update for the "sources", I think I'll try again without specifying a "/source" argument and see if DISM/CBS goes out on the Net to find the good stuff.

It's interesting how the path got totally destroyed, huh? How come this didn't happen to "Cliff S"? Why does it happen to some but not others? WHAT caused this destruction? Perhaps an environment variable that's getting tacked onto the beginning before something has a chance to parse the "esd:" stuff? Or maybe AFTER? This is a bizarro thing to happen in any case.

Well, whatever - I'll try again with NO sources and see if DISM/CBS is smart enough to pay attention to the Policy change to use the Windows Update site itself.

brokensoftware · Aug 29, 2015

Okay, last update for tonight - tried the DISM command without a "/source" argument and the fix failed again:

Code:

C:\WINDOWS\system32>sfc /scannow

Beginning system scan.  This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection found corrupt files but was unable to fix some
of 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.

C:\WINDOWS\system32>Dism  /Online /Cleanup-Image /RestoreHealth

Deployment Image Servicing and Management tool
Version: 6.3.9600.17031

Image Version: 6.3.9600.17031

[==========================100.0%==========================]

Error: 0x800f0906

The source files could not be downloaded.
Use the "source" option to specify the location of the files that are required t
o restore the feature. For more information on specifying a source location, see
 http://go.microsoft.com/fwlink/?LinkId=243077.

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

C:\WINDOWS\system32>

The DISM log shows it TRIED to "execute the command" but CBS broke again:

Code:

2015-08-29 19:09:29, Info                  DISM   DISM Package Manager: PID=1908 TID=4144 Processing the top level command token(cleanup-image). - CPackageManagerCLIHandler::Private_ValidateCmdLine
2015-08-29 19:09:29, Info                  DISM   DISM Package Manager: PID=1908 TID=4144 Attempting to route to appropriate command handler. - CPackageManagerCLIHandler::ExecuteCmdLine
2015-08-29 19:09:29, Info                  DISM   DISM Package Manager: PID=1908 TID=4144 Routing the command... - CPackageManagerCLIHandler::ExecuteCmdLine
2015-08-29 19:09:29, Info                  DISM   DISM Package Manager: PID=1908 TID=4144 CBS session options=0x48100! - CDISMPackageManager::Internal_Finalize
2015-08-29 19:35:17, Info                  DISM   DISM Package Manager: PID=1908 TID=4944  Error in operation: (null) (CBS HRESULT=0x800f0906) - CCbsConUIHandler::Error
2015-08-29 19:35:17, Error                 DISM   DISM Package Manager: PID=1908 TID=4144 Failed finalizing changes. - CDISMPackageManager::Internal_Finalize(hr:0x800f0906)
2015-08-29 19:35:17, Error                 DISM   DISM Package Manager: PID=1908 TID=4144 The source files could not be found and download failed. Their location can be specified using the /source option to restore the feature. - GetCbsErrorMsg
2015-08-29 19:35:17, Error                 DISM   DISM Package Manager: PID=1908 TID=4144 Failed processing package changes with session option CbsSessionOptionRepairStoreCorruption - CDISMPackageManager::RestoreHealth(hr:0x800f0906)

and CBS itself said:

Code:

2015-08-29 19:34:32, Info                  CBS    Repr: CSI meta data corruption found, will commit repair transaction if repair is asked.
2015-08-29 19:34:33, Info                  CSI    0000000e@2015/8/29:23:34:32.991 CSI Transaction @0xa4323b0370 initialized for deployment engine {d16d444c-56d8-11d5-882d-0080c847b195} with flags 00000002 and client id [26]"TI5.30466735_3258249215:1/"

2015-08-29 19:34:33, Info                  CSI    0000000f@2015/8/29:23:34:33.022 CSI Transaction @0xa4323b0370 destroyed
2015-08-29 19:34:33, Info                  CBS    Repr: CSI Store check completes
2015-08-29 19:34:33, Info                  CBS    Exec: Manual Repair feasibility evaluation, continue on download evaluation.
2015-08-29 19:34:33, Info                  CBS    Exec: Clients specified using Windows Update.
2015-08-29 19:34:43, Info                  CBS    WU: Update service is not default AU service, skip. URL: https://fe2.ws.microsoft.com/v6/, Name: Windows Store
2015-08-29 19:34:43, Info                  CBS    WU: Microsoft Update service is the default, URL: (null), Name: Windows Update
2015-08-29 19:34:43, Info                  CBS    Repr: Group policy setting Repair Content Server Source to: 2

Though this is somewhat obscure from a naive viewer's perspective, it LOOKS to this naive viewer that this part may be okay - but, admittedly, I sure don't like that "null" URL...

Anyway, the errors found by SFC were the standard false alarms having to do with "utc" and "telemetry" somethings so DISM could not fix those. But nothing was fixed with my setup - I was hoping for lots of things being found, lots of things being fixed, my Windows Store app updates to fly on by, etc etc etc.

Nope...no joy.

KYHI · Aug 30, 2015

/limitaccess = prevent access to MS Update Service (Downloads)

the Sources\SXS folder on setup media only contains limited windows features - Not a good repair source..

the Repair /source is a MOUNTED windows Image file

a mounted windows image file does not contain any windows updates that may have been downloaded via windows update..

So it is very possible none of the repair source files are present within the mounted windows image..
It is possible the component store (winsxs) also has a corrupt repair file source
which only leaves MS Download as the repair source - or use the files from another Host OS
But you need to know what files are at fault..

Dism /Online /Cleanup-Image /ScanHealth

post dism log

brokensoftware · Aug 30, 2015

My ultimate desire is to get Store updates to install and for the false errors ("utc"/"telemetry" ones) to go away. Right now I have about 20 Store updates already downloaded ready to install and my system is saying "No updates available" - this is about a month-long "feature" that I want to go away (since the system has downloaded the same updates about 479 times, each time then saying "no updates available" when the install phase comes around).

In pursuit of a "fix" for this I have done all the regular things - "sfc", "dism" "Windows update fix tool" "Windows store fix tool", etc ad nauseum.

So I thought I'd give it another go with pseudo-miracle-worker DISM and try to get it to check my system against a new ISO created the other day but, as you can see above, that breaks horribly and strangely when the proper argument is given to DISM, DISM acknowledges the command line, then SOMETHING breaks between it and CBS and the argument (path) is completely munged rather than being parsed and used correctly.

So I had to give up on that style for the time being and tried to use Windows Update as a source of correct files; that wasn't productive though, admittedly, I don't know if it succeeded or failed to use the Windows Update source due to the obscure log entries (see above).

Anyway, the DISM.log file I just made in response to the above request is uninteresting but attached anyway - it shows what I believe are false positives and nothing more - but that certainly is not all that's wrong with my current system state since those Windows Store updates are simply not updating.

[this post SAYS it has an attachment but I cannot see it...]

DISM - Fixing Component Store Corruption in Windows 8

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

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

Attachments

Administrator

Member

Administrator

Banned

Member

Member

Missing my GIF avatars:(

Banned

Member

Banned

Banned

Missing my GIF avatars:(

Administrator

Member

Missing my GIF avatars:(

Member

Member

Member

Well-Known Member

Member

Attachments

Similar threads