Solved How to Repair Corrupt Component Store

[claytoncarney]

While attempting to install Visual Studio 2015, I encountered an error stating the component store is corrupt. After searching, I was lead to these helpful posts:

• http://www.eightforums.com/tutorials/26512-dism-fixing-component-store-corruption-windows-8-a.html
• http://www.eightforums.com/performa...hen-trying-restore-post459105.html#post459105

So I run this command:

C:\Users\Administrator>dism /online /cleanup-image /checkhealth

Deployment Image Servicing and Management tool
Version: 6.3.9600.17031

Image Version: 6.3.9600.17031

[B]The component store is repairable.[/B]
The operation completed successfully.

Great, I can fix this, right? Next I run:

C:\Users\Administrator>dism /online /cleanup-image /startcomponentcleanup

Deployment Image Servicing and Management tool
Version: 6.3.9600.17031

Image Version: 6.3.9600.17031

[==========================100.0%==========================]
The operation completed successfully.

Now, as I understand David Bailey's post, SFC should come up clean. However:

C:\Users\Administrator>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.

For the hell of it, I decided to try Step 2:

[C:\Users\Administrator>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

Damn, back to Square One.

I had never heard of dism before today and I've never really understood how to decipher cbs.log files. It seems the problem is related to the .NET Framework, but I have no clue how to repair this. Any help is greatly appreciated.

 

[axe0]

Whenever you perform sfc/scannow reboot to let it repair the problems and try sfc/scannow again.
It may take a few tries to repair the problems.

When sfc/scannow is unable to repair the problems, then its best to use the dism commands.

 

[claytoncarney]

Oh, yes, been through MANY cycles of sfc and reboot. The corruption just never gets fixed.

As Brink has stated in several threads, at some point the corruption gets so bad that the only option is Refresh Windows 8. So that's what I'm doing now. Funny. I've NEVER had to reinstall a Linux OS, but with Windows it's almost a given. Guess while I'm at it I'll go ahead and move to Windows 10...

Thanks to all who looked at this. Hoped that someone might have known a way to fix the corruption manually. But, Windows is as Windows does.

 

[Steve C]

You could try an in place repair install.

 

[Wanyiri]

While attempting to install Visual Studio 2015, I encountered an error stating the component store is corrupt. After searching, I was lead to these helpful posts:

• DISM - Fixing Component Store Corruption in Windows 8
• Solved - DISM Source files could not befound when trying to restore

So I run this command:

C:\Users\Administrator>dism /online /cleanup-image /checkhealth

Deployment Image Servicing and Management tool
Version: 6.3.9600.17031

Image Version: 6.3.9600.17031

[B]The component store is repairable.[/B]
The operation completed successfully.

Great, I can fix this, right? Next I run:

C:\Users\Administrator>dism /online /cleanup-image /startcomponentcleanup

Deployment Image Servicing and Management tool
Version: 6.3.9600.17031

Image Version: 6.3.9600.17031

[==========================100.0%==========================]
The operation completed successfully.

Now, as I understand David Bailey's post, SFC should come up clean. However:

C:\Users\Administrator>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.

For the hell of it, I decided to try Step 2:

[C:\Users\Administrator>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

Damn, back to Square One.

I had never heard of dism before today and I've never really understood how to decipher cbs.log files. It seems the problem is related to the .NET Framework, but I have no clue how to repair this. Any help is greatly appreciated.

This worked like magic..just the first command. Then start the command: dism /online /cleanup-image /checkhealth
Waited for it to complete, then: manually started the TrustedInstaller process (somehow it was stopped)
and Voila!