Recover disk space from orphaned Adobe Acrobat .msp files inside
C:\Windows\Installer.
If your C:\Windows\Installer folder is using 50 GB, 100 GB, 300 GB or more,
and contains hundreds of large Adobe Acrobat MSP patch files, this tool can:
- detect orphaned Adobe MSP files
- verify they are no longer registered with Windows Installer
- identify Adobe-signed patches
- safely remove them
- recover tens or hundreds of gigabytes of disk space
Warning
C:\Windows\Installer is not a temporary folder.
Blindly deleting files here will permanently break application updates, software repairs, and uninstallations.
This tool provides a safe cleanup mode that only removes .msp files that are both no longer registered with Windows Installer and explicitly signed by Adobe Inc. A destructive "delete everything" mode exists for advanced users, but it is heavily gated to prevent accidental system damage.
Windows Installer caches copies of installation and patch packages. Usually, this is expected behavior. However, old patch files—especially from Adobe Acrobat—can become orphaned, swelling the directory with dozens of dead 1GB+ files until the folder consumes upwards of 100 GB of drive space.
- 📊 Analyze: Break down the entire Windows Installer directory by size and file type.
- 🧩 Detect: Identify
.msppatches no longer registered with Windows. - 🏢 Target: Filter orphaned patches specifically signed by Adobe Inc.
- ⚡ Speed: Scan massive files efficiently using PowerShell 7 parallel threading.
- 📝 Audit: Generate detailed CSV and text log reports for every operation.
- 🛡️ Safety: Leaves non-Adobe and actively registered patches completely untouched.
- Windows 10 or 11
- PowerShell 7+ (Download)
- Administrator privileges (only required for actual cleanup)
- Clone or extract this repository.
- Run
CleanupMenu.bat. - Choose an option from the menu.
1. Inspect C:\Windows\Installer (Read-only)
Displays total files, folder size, file extensions, and the 30 largest files. Recommended as a harmless first step to see what is eating your storage.
2. Scan for Adobe patches (Read-only)
Cross-references files against the Windows Registry to find unregistered Adobe .msp patches and calculates exactly how much space can be safely recovered.
3. Scan and delete Adobe orphan patches (Safe Cleanup)
Deletes an .msp file only if it is unregistered and signed by Adobe. Registered files, unreadable files, and non-Adobe patches are strictly ignored.
4. Delete ALL MSP files (Danger Zone)
Caution
Deletes every single *.msp file in the Installer folder. This will break future updates and uninstallations. Requires explicit typed confirmation. Not recommended.
- Registry Verification: The script queries
HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\*\Patches\*. If a file is actively listed here, it is skipped. - Parallel Certificate Reading: To handle gigabytes of patches quickly, PowerShell 7's
ForEach-Object -Parallelreads embedded Authenticode certificates across 12 threads, looking specifically forO=Adobe Inc.. - No Online Validation: Full network certificate revocation checks are bypassed in favor of reading the embedded identity directly. This intentional tradeoff makes scanning hundreds of massive files exponentially faster.
- Inspect folder
- Scan Adobe usage
- Review the
logs\directory - Run safe Adobe cleanup
- Reboot Windows
- Verify applications still function correctly
This tool may help if you searched for:
C:\Windows\Installer hugeWindows Installer folder 100GBWindows Installer folder 300GBAdobe MSP files taking up disk spaceAdobe Acrobat filling Windows Installerorphaned MSP files Windows InstallerC:\Windows\Installer cleanupAdobe Acrobat patch cache huge
The tool was originally created after discovering approximately 117 GB of orphaned Adobe MSP files on one Windows installation.
A second tested PC contained approximately 300 GB of orphaned Adobe Acrobat patch files, which were successfully identified and removed.
No tool modifying the Windows Installer cache is entirely without risk. Before running cleanup operations, ensure critical work is saved and consider creating a Windows Restore Point.
Provided as-is under the MIT License. The authors are not responsible for broken installers, failed updates, or data loss. Use at your own risk.