WinSXS Folder not actually consuming lots of space

LafinJack said:

Thanks pparks from ending this tail chasing!

Your welcome. After 10,000 views and not a single reply, I was wondering what was going on.

DalekOverSeer said:

yes winsxs my not actually using that amount of space, but the space is still reserved by windows none the less. the only way to free up that space for use is to use the one procedure to move the winsxs folder to another drive. the procedure is in no way for novice. i strongly recommend against doing it.

No, it is not used by Windows and reserved. You assume the space is used as right clicking on the folder and selecting properties says that it's X amount in size. But as I've shown above, if the folder "REALLY" had 270MB of stuff in it, then the 200MB hard drive would have been filled beyond capacity.

So, when I put in the 13MB file, Windows explorer showed that my D drive went from 200MB free to 187MB free. Once I created the 20 hardlinks, Windows explorer continued to show that my D drive had 187MB free. A command prompt showed 187MB free. But if you were to look at D:\winsxs with Explorer, windirstat or treesize free....it would "claim" that the folder was 270MB in size.

Edit: I am researching ctts.exe and it's ability to properly distinguish between hardlinks and real files. From initial observations, it appears that C:\windows\winsxs might be more real files and less hardlinks than originally expected. This would obviously impact my statements above.

Here was the guide used as reference at first;
Disk Space - Engineering Windows 7 - Site Home - MSDN Blogs

In this guide, it says this;

In practice, nearly every file in the WinSxS directory is a “hard link” to the physical files elsewhere on the system—meaning that the files are not actually in this directory. For instance in the WinSxS there might be a file called advapi32.dll that takes up >700K however what’s being reported is a hard link to the actual file that lives in the Windows\System32, and it will be counted twice (or more) when simply looking at the individual directories from Windows Explorer.

However, when you run something like ctts.exe...it seems to indicate that an overwhelming majority are "real" files and not hardlinks. In my case, out of nearly 6GB reported (somewhat erroneously by Windows Explorer), ctts.exe says that only 78MB are hardlinks. Well, that wouldn't jive with the MSDN blog article from above.

Alright, figured something out. Thanks to this thread ( Windows 7 Free Space - Neowin Forums - Page 2).

You have to run ctts.exe against C:\windows and not just C:\windows\winsxs.

The output for me against C:\windows says
13.2GB of total size in use. And TreeSize agrees that C:\windows is indeed 13.2GB. (We agree both will count hard links and inflate real number)
4.2GB of space is consumed by Hard Links
9.0GB of space is actually used by "real" files. ( I believe this is value of ctts.exe..."real files" here consume about 9.0GB of space.

But TreeSize Free, and Windows Explorer both say that my C:\windows\winsxs folder is 5.8GB in size.

Therefore, the conclusion would be that out of 5.8GB reported, nearly 4.2GB is coming from other areas within the the C:\windows directory. Thus, approx 75% of the space is represented by hard links.

So, I would maintain that if I flat out deleted C:\winSXS that I wouldn't get back 5.8GB of free space, but instead would get back (5.8 - 4.2) 1.6GB of space.

So, if you had a 20GB hard drive...even with the "appearance" of a 13.2GB C:\windows folder, I think actually 9.0GB of space is used, and you would really have yourself about 11GB free if you went to a command prompt and typed DIR. I think you could put about 11GB of more files onto that 20GB drive before it would truly be full. Even though, it would seem that counting up the Windows folder with Windows Explorer means that 13.2GB is used and thus only 20-13.2 = 6.8GB would really exist.

And that's what I showed with my example at the top. I could make it "appear" that D:\winsxs was almost 270MB in size..even though my hard drive itself was only 200MB. All of the tools said D:\winsxs was taking 270MB....but yet I could still copy about 187MB of more stuff onto the drive before it really was full.