windirstart showing ssd being take over by application extension files?

Ketchup

Elite Member
Sep 1, 2002
14,559
248
106
Maybe I was going through those articles too quickly, but I don't see the actual explanation of the why the Winsxs folder appears so large, mainly just how to clean up unneeded files. Here is why that directory looks so large (hint: it isn't really).

The component store contains all the files that are required for a Windows installation. And, any updates to those files are also held within the component store as the updates are installed. This causes the component store to grow over time as more updates, features, or roles are added to the installation. The component store uses NTFS hard links between itself and other Windows directories to increase the robustness of the Windows platform.

The component store will show a large directory size because of how the Windows Explorer shell accounts for hard links. The Windows shell will count each reference to a hard link as a single instance of the file for each directory in which the file resides. For example, if a file that is named advapi32.dll is 700 KB and is contained in the component store and in the \Windows\system32 directory, Windows Explorer would inaccurately report that the file consumes 1,400 KB of hard disk space.

http://support.microsoft.com/kb/2795190
 

bbhaag

Diamond Member
Jul 2, 2011
7,209
2,687
146
It does seem excessively large. His Windows folder is much larger than mine though. Here's a comparison shot from my system.
Do you think he would benefit from running the Dism.exe /online /Cleanup-Image /StartComponentCleanup /ResetBase command to help clean it up a little?
dism_zpsf69bb14d.jpg
 
Last edited:

RampantAndroid

Diamond Member
Jun 27, 2004
6,591
3
81
Maybe I was going through those articles too quickly, but I don't see the actual explanation of the why the Winsxs folder appears so large, mainly just how to clean up unneeded files. Here is why that directory looks so large (hint: it isn't really).



http://support.microsoft.com/kb/2795190

I think the wording there is a little wrong/confusing; Windows doesn't think the file itself consumes 1400k, it thinks that there are multiple copies of that file, each consuming 700k - even though in reality the file exists in one place and is linked to from multiple places. :)