Author Topic: Windows 7 Component Store Repair  (Read 14071 times)

0 Members and 1 Guest are viewing this topic.

Offline jaqsol

  • Newbie
  • *
  • Join Date: Sep 2013
  • Posts: 2
  • Karma: 0
    • View Profile
    • JaQ Computer Solutions
Windows 7 Component Store Repair
« on: September 24, 2013, 06:04:06 am »
Does anyone know how to repair the Windows 7 component store? So far, the only repair for this that I know of is a repair install or a clean install of Windows 7.

Offline Shane

  • Administrator
  • Hero Member
  • *****
  • Join Date: Sep 2011
  • Posts: 9281
  • Location: USA
  • Karma: 137
  • "Knowledge should be shared not hidden."
    • View Profile
Re: Windows 7 Component Store Repair
« Reply #1 on: September 25, 2013, 02:32:59 pm »
Repair install is normally what I would do. I havent been able to find any info on how to rebuild the component store, which is something Windows does during the setup phase.

Shane

Offline jaqsol

  • Newbie
  • *
  • Join Date: Sep 2013
  • Posts: 2
  • Karma: 0
    • View Profile
    • JaQ Computer Solutions
Re: Windows 7 Component Store Repair
« Reply #2 on: September 25, 2013, 05:43:20 pm »
Thank you. My original problem was that System File Checker had found some corrupt files but was unable to repair them. I used the Tweaking.com repair tool with no success in fixing this. A repair install of Windows 7 cured the problem. I noticed during the installation, Windows repaired .NET Framework 4. This may have been the cause of the problem. In which case, repairing .NET Framework 4 may have been the cure for the SFC problem. I will check into that the next time I find a similar problem.

Offline Shane

  • Administrator
  • Hero Member
  • *****
  • Join Date: Sep 2011
  • Posts: 9281
  • Location: USA
  • Karma: 137
  • "Knowledge should be shared not hidden."
    • View Profile
Re: Windows 7 Component Store Repair
« Reply #3 on: September 27, 2013, 06:39:10 pm »
For .net I use the .net removal tool, it gets rid of it all, and then I install .net fresh. Works great when fixing .net :-)
http://blogs.msdn.com/b/astebner/archive/2008/08/28/8904493.aspx

Shane