Author Topic: DISM Repair added as a Step after the SFC scan to add repair for corrupted files  (Read 5677 times)

0 Members and 1 Guest are viewing this topic.

Offline Cigam

  • Newbie
  • *
  • Join Date: Jun 2013
  • Posts: 23
  • Karma: 2
    • View Profile
On Windows 8+ computers it has the built in options for DISM which can help repair numerous corrupt files in the system that sfc cannot fix, or may not detect. I had to use this on a few computers at work to repair the computer before running tweaking. Could you add this as a step after the sfc scan to help do some extra repairs before the full tweaking repair?

the commands are specified in detail on this page:
http://www.eightforums.com/tutorials/26512-dism-fixing-component-store-corruption-windows-8-a.html

###################
the first set of commands are run in admin command prompt
###################
Dism /Online /Cleanup-Image /CheckHealth
This switch option only checks to see if a component corruption marker is already present in the registry. It is just a quick way to see if corruption currently exists, and to inform you if there is corruption. It does not fix anything or create a log. This should be finished almost instantaneous.

Dism /Online /Cleanup-Image /ScanHealth
This switch option does not fix any corruption. It only checks for component store corruption and records that corruption to the log file. This is useful for only logging what, if any, corruption exists. This should take around 5-10 minutes to finish.

Dism /Online /Cleanup-Image /RestoreHealth
(recommended) This switch option checks for component store corruption, records the corruption to the log file, and FIXES the image corruption using Windows Update. This should take around 10-15 minutes up to about an hour to finish depending on the level of corruption.

###################
The second set of commands need to be run in an admin powershell
###################
Repair-WindowsImage -Online -CheckHealth
This switch option only checks to see if a component corruption marker is already present in the registry. It is just a quick way to see if corruption currently exists, and to inform you if there is corruption. It does not fix anything or create a log. This should be finished almost instantaneous.

Repair-WindowsImage -Online -ScanHealth
This switch option does not fix any corruption. It only checks for component store corruption and records that corruption to the log file. This is useful for only logging what, if any, corruption exists. This should take around 5-10 minutes to finish.

Repair-WindowsImage -Online -RestoreHealth
(recommended) This switch option checks for component store corruption, records the corruption to the log file, and FIXES the image corruption using Windows Update. This should take around 10-15 minutes up to about an hour to finish depending on the level of corruption.


###################
Previous versions of windows I think uses CheckSUR
###################
http://support.microsoft.com/kb/947821
http://www.thewindowsclub.com/checksur-system-update-readiness-tool
http://windows.microsoft.com/en-GB/windows7/What-is-the-System-Update-Readiness-Tool
http://blogs.technet.com/b/joscon/archive/2010/05/26/using-checksur-and-update-packages-to-fix-corruption.aspx


Offline Shane

  • Top Geek, err uh Dog.
  • Administrator
  • Hero Member
  • *****
  • Join Date: Sep 2011
  • Posts: 9280
  • Location: USA
  • Karma: 138
  • "Knowledge should be shared not hidden."
    • View Profile
    • Tweaking.com
Program already does that, but it is one of the repairs :wink:

"Repair Windows 8 Component Store"

This is the repair info about the repair in the program.

Quote
Repair Windows 8 Component Store

The following commands are done.

Dism /Online /Cleanup-Image /StartComponentCleanup
Dism /Online /Cleanup-Image /RestoreHealth

The first command cleans up the component store (WinSxS Folder) in windows, reducing it size and removing old entries.

The 2nd command is used to repair corrupt files and corrupt entries in the component store.

Reasons for this repair:
Used to fix Windows component store corruption when a SFC /SCANNOW command is unable to repair corrupted system files because the store (source) is corrupted, then run the SFC command again.
Used to fix Windows component store corruption when the same Windows Updates continue to appear to be available to install even though they already show successfully installed in update history.

More information on these commands can be found here:
http://technet.microsoft.com/en-us/library/hh824869.aspx
and
http://www.eightforums.com/tutorials/26512-dism-fixing-component-store-corruption-windows-8-a.html

Shane
PLEASE EDIT YOUR TOPIC AND PUT (SOLVED) IF YOU ARE ALL FIXED.

(My weekends belong to my wife and kids, I will try my best to answer all posts daily during the work week)

(About Shane)
Site Owner, Top Admin, Lead Programmer, Wife & 5 kids, Needs a lot more coffee.

When people ask "Why fix what isn't broken?" I reply "To make it better."
"Only a life lived for others is a life worthwhile"
Honor & Respect is all that matters.

Owner & Programmer of: www.pcwintech.com & www.tweaking.com