Reduce Windows 7 WinSxS Folder Size

Link：http://www.iishacks.com/2011/06/23/reduce-windows-7-winsxs-folder-size/

With Windows Vista, the WinSxS folder was able to be cleaned up via a third party tool (WinSxS Lite here – 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:\Windows>dism /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.