Main Forum > General Computer Support

SFC log

<< < (4/4)

peter915:

Shane
So are you saying then that this problem was due mainly to poor house keeping by MS?
Or was it due to some malicious virus or ? or both?
Peter

Shane:
Poor house keeping yes, but the winsxs folder is easy to break.

They introduced the winsxs folder starting in vista, and it always grew with every update or program install and never shrank.
http://blogs.technet.com/b/askcore/archive/2008/09/17/what-is-the-winsxs-directory-in-windows-2008-and-windows-vista-and-why-is-it-so-large.aspx

So systems that did a lot had huge winsxs folders and MS gave no way to clean it up other than a reinstall of Windows. SO finally in 8 they offered a way to clean it up removing old copys of files. Which if a old copy of a file was causing the problem then that would fix it.

When you have a folder with that many files and such it will only take 1 file to make the sfc complain, and it never gives you a reason error message and leaves it up to the user to go through a hugh log file trying to determine exactly what went wrong.

I HATE the winsxs folder, when it breaks it can create a lot of trouble.

Shane

jraju:
Which part of the tool in your latest edition has this fix. From the tools, which one to select to have the correct size of winsxs folder

Shane:
Repair Windows 8 Component Store :-D

Remember each repair in the program has a info file for it.


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

--- End quote ---

Shane

Navigation

[0] Message Index

[*] Previous page