If there is no better alternative to the superseded Office patches cleanup and the script is given all clear, I would suggest that this script should be given more attention and made a sticky or a reference in any other way on this forum. Otherwise it will get lost among other less relevant threads. I know of few other alternatives to clean superseded msp/msi, one which I mentioned here, but this script seems to be the most complete way to clean up Office patches as far as I know. For Windows we have the official way, but not for Office.
Saving whatever amount of GBs is always good. Specially for those like me who relies on imaging (system image). Less R/W to the HDD, cool.
Tried it on O2013x86 and Win81x64 - works well - ran as cscript c:\temp\clean.vbs On most msi stores it gave a 1646 return code and I recovered about 15 GB When used with O2010 the return code is almost always 0...
I'm going to add permanent update detection when i have time. Then it should skip them and not give error 1646. Or, given how patch sequencing works (content of superseded updates is completely disregarded when doing any repair on the product, therefore their uninstall is almost a no-op) i could add a “dangerous” option that would mark such an update as uninstallable and then uninstall it. I have for now tested this manually with adobe reader and it still worked afterwards.
Updated tha script to add permanent patch detection and (optional) “force” removal for all yer Silverlight and Adobe Reader goodness.
Out of curiosity, is this better than doing ... ? Code: DISM /Online /Cleanup-Image /SPSuperseded and/or Code: DISM /Online /Cleanup-Image /StartComponentCleanup /ResetBase