Somewhat theoretical answer: if the MSPs are well designed, nothing should break just from running that script, unless you later uninstall patches (either manually or some automated process does it) in which case you'll find out if the patches were well designed.Īs Heath (MSFT) explains, if you remove superseded patches, what can happen is that if the 'top patch' is then manually removed too, you're left with a much older (and buggy) version of the app than you might expect. I noticed no ill effects: there are no new updates offered if you check for updates after running the script, so it doesn't remove anything essential and Office still runs and can be serviced (add/remove components works). (I made the script output to a log as well: it removed about 700 patches.) but the script created 20GB of logs in temp, so this isn't very practical if you're running out of space. The gain was about 9GB of disk space from all those intermediate Office patches removed.

The major downside of this script is the runtime: slightly over two hours even though this (i3) PC had a SSD. Well, I ran this as an experiment on an old office computer with Win7 and Office 2010.

Windows installer cleanup