You don't want to manually remove entries from those folders. Windows 7 saves it's installer packages (much like a c: i386 folder on an XP machine) locally so that you don't need to insert the win7 disk when installing updates or running repairs.
Cleanup the WinSxS Folder in Windows 7/8/10 In Windows 7 and Windows 8/10, there is a new folder under C: Windows called WinSxS, which basically stores dll and component files. It also stores older versions of all dll and component files and can grow to be quite large.
![Winsxslite Windows 7 Winsxslite Windows 7](http://www.iishacks.com/wp-content/uploads/2011/06/WinSXS4.jpg)
Also, Windows 7 uses a central directory to store most of the files that make up the operating system itself and then places what are essentially shortcuts or pointers to those files in the places where the files are actually used. This makes it pretty easy to maintain critical file versions and greatly simplifies updates. This also makes for a single very very large folder inside your Windows directory that you should not, ever, ever no never, modify or delete unless you want the wrath of the Gates to fall upon you. Or something like that.
All that being said, using CCleaner and selecting the option to remove Hotfix uninstallers should remove the uninstall packages for any patches you've installed. Since the patched files are already in the windows installer source directory, and as long as a recent patch hasn't bolluxed up your system, this may help get things cleaned up. One final not though: 20GB isn't all that much more than a standard Windows 7 install. It's unlikely you're going to get much smaller than this. UPDATE CCleaner revision: Ok, it appears as though, once Windows 7 applies the patches, the necessary source files are integrated into the windows files repository and any extraneous patch files are removed. So CCleaner does not have the 'Hotfix Uninstaller' option in Windows 7 that it has in XP.
The only thing I'd be careful of removing are the Windows Log Files. Everything else listed in CCleaner should be OK to be deleted so long as you know what it is you're deleting (if you rely on your jump lists or MRU logs, CCleaner only knows that if you tell it not to delete them. But like I said, those folder sizes are not outside the realm of normal in the Windows 7 world. DO NOT FOOL WITH WINSXS This ( ) website describes something that may be helpful regarding winsxs: The only way to safely reduce the size of the WinSxS folder is to reduce the set of possible actions that the system can take – the easiest way to do that is to remove the packages that installed the components in the first place. This can be done by uninstalling superseded versions of packages that are on your system. Which means uninstall programs I suppose. Also the following might help reduce winsxs folder size Service Pack 1 contains a binary called VSP1CLN.EXE, a tool that will make the Service Pack package permanent (not removable) on your system, and remove the RTM versions of all superseded components.
This can only be done because by making the Service Pack permanent we can guarantee that we won’t ever need the RTM versions. The WinSxS folder doesn't use 4GB. It's a summary list of installed DLLs, and those DLLs together are 4gb. Even if you'd remove the list in WinSxS, the files would still exist somewhere else on the disk, and still take up the same 4GB of space. The underlying technology is NTFS 'hard links' (as opposed to shortcuts, which are are considered 'soft links'). With hard links, one file can appear under multiple names in multiple directories.
If you delete one name, the file remains on disk; you need to delete all names to free the diskspace. The advantage for Microsoft is that they can more easily fix security risks this way. They only need to check WinSxS for bad DLL versions; if found there they can just overwrite that. All other names on disk will refer to the same bytes, and therefore are updated too.
Link: With Windows Vista, the WinSxS folder was able to be cleaned up via a third party tool ( – Vista only!). With the initial release of Windows 7, we lost that capability – but it has since returned with Service Pack 1.
The WinSxS folder is used to store install and uninstall files, windows packages (current and previous versions of a component) and out-of-band releases. You should not completely delete this folder. Post Windows 7 SP1, there is now a way to remove the unnecessary files from this folder using the command line (elevated/admin mode - Click Start - Type “cmd” in Search.
Right click on “cmd” and choose “Run as Administrator”). This is great for reducing the Windows folder size for SSDs and netbooks. In my case it saved 3.5GB of space.
Dism /online /cleanup-image /spsuperseded Before: After: Just ran ‘dism /online /cleanup-image /spsuperseded’ on Windows 7 Enterprise 64bit. Reduced ‘winsxs’ folder from 10.64gig down to 6.56gig Rebooted and all is fine.
Ok i’ve this error Microsoft Windows Version 6.1.7600 Copyright (c) 2009 Microsoft Corporation. All rights reserved. C: Windowsdism /online /cleanup-image /spsuperseded Deployment Image Servicing and Management tool Version: 6.1.7600.16385 Image Version: 6.1.7600.16385 Error: 87 The spsuperseded option is not recognized in this context.
For more information, refer to the help. The DISM log file can be found at C: Windows Logs DISM dism.log Err:87 is typically invalid parameter, did that install already have the files removed because it was installed with integrated media? Did you install with SP1 integrated media?
If so, this has already been done on the image. Version: 6.1.7600.xxxxx is the RTM build of Windows 7. This trick works with Windows 7 SP1 which should be version: 6.1.7601.xxxxx What you need to do is first change your UAC settings the default settings (move the slider up to the 2nd from the top).
Then, reboot! Then, right click on ‘cmd’ to run as administrator even if your current user has admin rights.
Then, follow instructions from above. Hope that solves things. I download the win7 sp1 from Microsoft website and install it. Then i run the clean command again, and i got the following infomation. So i restart my computer and do again. And i got it.