Petrarca
May 21 2008, 08:13 PM
I've been trying out the Component cache (WinSxs) removal, but it is not working properly.
After install, I still have a WinSxs folder which is half a gigabyte, containing roughly 18k files

Now while this is much smaller than the size of the folder without using the removal, it makes me wonder why there is that much left?
dexter.inside
May 22 2008, 03:25 AM
That's not much, that's quite small actually
aviv00
May 22 2008, 09:53 AM
how much winsxs removal save in windows server in 64bit ?
Petrarca
May 22 2008, 01:05 PM
QUOTE (aviv00 @ May 22 2008, 05:53 PM)

how much winsxs removal save in windows server in 64bit ?
Quite a bit, actually. Before it was over 3gb, after only 0.5gb - but I wonder why this rest doesn't get removed as well.
aviv00
May 22 2008, 01:26 PM
i think net3 removal is make it 200mb im not sure
nuhi
May 22 2008, 01:51 PM
That portion is automatically saved depending on what vlite detects as hotfixes or parts of sp1 probably.
Also there are some runtimes that must not be deleted from sxs.
anarkhy
May 22 2008, 08:28 PM
is it ok to remove winsxs with vlite? will it remove only the trash or system files will gone too? I tried to manually delete all files but then my vista didn't boot anymore.
Witt3439
May 22 2008, 08:37 PM
The winsxs folder is similar to the i386 folder in XP. It contains drivers and other files necessary to make Windows run properly.
It is possible to delete files and folders from it, but it is one of those "If you don't know what you are doing, leave it alone!" folders.
anarkhy
May 22 2008, 08:59 PM
Thats what i want to know, which files are removed from winsxs? Is vlite smart to remove only unnecessary archives?
Volatus
Oct 16 2008, 07:29 AM
i386 is a folder in Windows XP that can safely be deleted... it's just a copy of the Setup files.
I'm in the same boat here... I did a super-lightweight Vista install - specifically for Folding@Home GPU processing (users claim that running Vista solves the 100% CPU problem and massively improves performance). It seems that even vLite's best efforts can't wrangle in the runaway, obscene bloat of Vista. I told vLite to ditch the "winsxs" folder, and yet, it was the source of a "Configuring updates: Stage 3 of 3" reboot loop on the first startup (300kb pending.xml in the WinSxS folder that I was surprised to even find).
My WinSxS folder is about the size of a full blown Windows XP installation - 11,000 files and 418mb. What the heck gives? With all the junctions running amok in Vista, are those files really there; are they the originals and there are other files on the hard drive that are merely "mirrors" of them, or is it really just a waste of space?
anonymous_user
Oct 18 2008, 11:19 PM
QUOTE (Volatus @ Oct 16 2008, 06:29 AM)

are they the originals and there are other files on the hard drive that are merely "mirrors" of them
Correct, or so I read:
http://www.neowin.net/forum/index.php?showtopic=590216
cdo5
Nov 1 2008, 11:13 AM
I am using vlite final release v1.2.
Where are you finding the "Component cache" removal tool?
I would VERY much like to reduce my winxsx folder to the size you describe
anonymous_user
Nov 1 2008, 01:35 PM
You have to run vLite with the "-extreme" switch.
The_Rebel
Nov 4 2008, 12:51 AM
@anonymous_user
how do we do that?
cmd > vlite.exe -extreme ?
anonymous_user
Nov 4 2008, 02:58 PM
Yeah or you can create a shortcut for vLite and add the switch:
toylet
Nov 5 2008, 05:42 AM
QUOTE (anonymous_user @ Nov 2 2008, 03:35 AM)

You have to run vLite with the "-extreme" switch.
What exactly does the -extreme option does?
MagicAndre1981
Nov 5 2008, 09:20 AM
when running vLite with the extreme parameter, some hidden features are visible so that you can remove them, but keep in mind, that removing one of the shown components can cause a lot of trouble
cdo5
Nov 7 2008, 04:03 PM
It looks to me as though the only to remove the component cache is to uncheck" "Windows Update" in the first section. I woud sure like to reduce the size of the component cache, butnot at the cost of losing windows update. Am I missing something here?
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please
click here.