Solved How to Repair Corrupt Component Store

• 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

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.

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.

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.

[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

claytoncarney said:

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:

Code:

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:

Code:

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:

Code:

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:

Code:

[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.

Click to expand...