Going a bit beyond the winSXS conversation
The Windows 7 Disk Cleanup utility when run as a simple batch with the sageset/sagerun command, as mentioned by northwood2222:
Untitled.jpg%SystemRoot%\System32\Cmd.exe /c Cleanmgr /sageset:65535 & Cleanmgr /sagerun:65535
Will provide the option(s) of doing a deeper clean than that which would normally be effected from the use of Disk Cleanup
without the sageset/sagerun commands. This indirectly contributes to reducing the size of the SXS folder.
There is the option to remove Service Pack installation setup files if one had installed them in the first place, thereby
making any service pack permanent, and also indirectly reducing the SXS footprint.
I've run the above previously on many occasions, so that the;
"C:WindowsSystem32DISM /online /Cleanup-Image /SpSuperseded"
command seemed to have had little effect, if any at all.
DISM as a whole on the otherhand, sounds a bit more complicated. If I'm not mistaken in my readings regarding this, might it open up
a whole new way of tailor hacking Windows 7? Might it be possible to remove considerable bloat in terms of generic drivers support
that the operating system installs for compatibility purposes, many of which, once a system is set up, could be nit-picking-ly
removed if not needed. This is something that MS would never mention directly as it would obviously break the os and lead to
numerous support calls.
I still think that there is so much more that could be done to remove bloat overall in Windows 7 that DISM needs to be explored.
I invite Fred Langa to delve further into Deployment Image Servicing and Management.