Adobe update files are filling up C:\Windows\Installer. What’s safe to do?

I would not delete files from that folder just because they look old or belong to Adobe. Windows Installer may still need cached packages for maintenance, and guessing from age or file size is not a reliable way to identify what is safe to remove.

For machines already badly affected, a controlled Adobe uninstall, cleanup, and reinstall has been reported to clear out accumulated files. Test that process on a small group first and confirm repair, update, and uninstall behavior before rolling it out widely.

Check PatchCleaner’s settings before writing it off. One report says Acrobat was excluded by default, so the tool skipped those files until that exclusion was changed. That does not mean every file it flags is safe to remove, though. Review what it identifies and test on a noncritical machine.

A registry comparison script or a dedicated Installer cleanup utility can be tempting, especially if this is happening across a lot of machines. Treat any automated cleanup as a risk, not a proven fix. Keep a record of what it would remove, trial it on a small set of devices, and check that Adobe updates and Windows Installer operations still work before scheduling it.

Some administrators report using file age or publisher signatures as filters, but those checks alone do not establish that a cached patch is orphaned.

There’s a real difference of opinion here. Some reports describe repeated Adobe patch files growing dramatically over time, while another administrator says their deployment has not had the same issue. I’d first confirm which files are consuming space and whether the Adobe version and update pattern match before assuming every machine needs the same cleanup.