The ability to roll back a update is a nifty idea. The theory is that you installed something that broke your platform. You can now just ‘undo’ the install.
In practice, it’s a feature that next to nobody uses. It requires a deep-faith in the programmers of the rollback logic to return the system to it’s initial state. If they missed a single file or java class, it could land up affecting the entire system. The user is then left with a question “Is the environment broken or is there a bug in the platform?”. In order to resolve this question, they will uninstall and re-install the product.
Therefore, if you know that you will never bother to rollback, why are you dedicating disk space for the installation manager to rollback? Yup, that’s the default setting. Every old version of every plugin in every product you’ve ever installed is still there needlessly. For people like me who work in virtual machines, disk space is precious.
You can turn this open off by clicking File -> Preferences.
You can turn off the check box to preclude future saving. You can also click the Delete saved Files button to remove any current old versions.
Before I clicked the button, it told me I had 1.6G of files saved.