• This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn more.

Solved How to Repair Corrupt Component Store


Posts
4
#1
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:

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.
 

Attachments

My Computer

System One

  • OS
    windows 8.1 64-bit
    Computer type
    Laptop
    System Manufacturer/Model Number
    Dell Inspiron 15 (3521)
    Other Info
    Running Windows 8 Release Preview Build 8400 as VM on VBox 4.2.6

axe0

BSOD Kernel Dump Analyst
VIP Member
Pro User
Posts
2,379
#2
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.
 

My Computer

System One

  • OS
    Windows 10 Pro
    Computer type
    PC/Desktop
    System Manufacturer/Model Number
    Custom build
    CPU
    i5-6500 @3.20GHz
    Motherboard
    Gigabyte B150-HD3P-CF
    Memory
    16GB DDR4 2133 Crucial Ballistix Sport LT
    Graphics Card(s)
    MSI GeForce GTX 1060 GAMING X 6G
    Sound Card
    Built-in
    Monitor(s) Displays
    Liyama ProLite XB2483HSU-B2
    Screen Resolution
    1920 x 1080
    Hard Drives
    Crucial MX200 500GB & Toshiba DT01ACA300 3TB
    PSU
    Corsair RM550x
    Case
    Fractal Design Define S
    Cooling
    Cooler Master TX3 i
    Keyboard
    Func KB-460 (MX Red)
    Mouse
    Corsair Gaming M65 RGB
    Browser
    Google Chrome
    Antivirus
    Bitdefender Total Security 2017 + MBAM Pro + MBAE Pro
    Other Info
    Creative Sound Blaster Tactic3D Rage V2 headset
Posts
4
#3
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.
 

My Computer

System One

  • OS
    windows 8.1 64-bit
    Computer type
    Laptop
    System Manufacturer/Model Number
    Dell Inspiron 15 (3521)
    Other Info
    Running Windows 8 Release Preview Build 8400 as VM on VBox 4.2.6

Steve C

Member
Power User
UK

Posts
275
#4
You could try an in place repair install.
 

My Computer

System One

  • OS
    Windows 8.1 64 bit
    Computer type
    PC/Desktop
    System Manufacturer/Model Number
    Home Build
    CPU
    Intel i3570K
    Motherboard
    Gigabyte GA-77X-UD5H
    Memory
    16 GB
    Graphics Card(s)
    Sapphire R9 280X Toxic
    Sound Card
    Realtek on motherboard
    Monitor(s) Displays
    Viewsonic VP2770
    Screen Resolution
    2560 x 1440
    Hard Drives
    Intel 520 180GB SSD
    Seagate 2T HDD
    Seagate external 1T USB HDD
    PSU
    XFX 850W
    Case
    Nanoxia Deep Silence 1
    Cooling
    Noctua NH-D14
    Keyboard
    Microsoft
    Mouse
    Microsoft
    Internet Speed
    50Mbps
    Browser
    Chrome