URGENT: 123 GB of Adobe .MSP Files Remain in Windows Installer Cache After Uninstall and Cleaner Tool — Windows Updates Blocked

Question

123 GB of Adobe Installer Patches Remain After Uninstall — Adobe Cleaner Tool Failed — Windows 11

Product: Adobe Acrobat Reader (64-bit)
Operating System: Windows 11 Home
Issue: 189 Adobe digitally signed .msp installer patches consuming approximately 123 GB in C:\Windows\Installer

Problem Description

I am experiencing an unusually large accumulation of Adobe-signed Windows Installer patch files on my Windows 11 desktop.

Using TreeSize Free and PowerShell, I identified 189 Adobe digitally signed .msp files totaling approximately 123 GB in the Windows Installer cache.

My C: drive has approximately 16 GB of free space remaining, and the storage shortage is interfering with my ability to install the latest Windows update.

I am seeking assistance determining why these files remain after Acrobat Reader was uninstalled and whether Adobe has a supported procedure for identifying and removing obsolete patches safely.

Troubleshooting Already Completed

Uninstalled Adobe Acrobat Reader (64-bit) normally through Windows.
Ran Adobe's official Acrobat Cleaner Tool.
Restarted Windows.
Confirmed that all 189 Adobe-signed .msp files remain in C:\Windows\Installer.
Searched several Windows Installer registry locations for matching LocalPackage references, without finding matches.
Backed up all 189 files to an external drive and verified the backups using SHA-256 hashes, with zero mismatches.

Despite these steps, approximately 123 GB of Adobe-signed installer patches remain.

I understand that a lack of matches in the registry locations searched does not conclusively establish that these files are orphaned.

Related Adobe Community Discussion

I discovered the existing discussion titled:

"We have a few computers with Literally hundreds of 1gb update MSI files downloading constantly"

In that discussion, an Adobe employee recommended creating a registry value named PatchCleanFlag, set to 1, under the appropriate Acrobat policy registry location.

For 64-bit Acrobat Reader, the recommended location was:

HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Adobe\Adobe Acrobat\DC\FeatureLockdown

However, another community member reported that the setting did not remove older cached installer files even after subsequent Adobe Reader updates.

Another participant asked what users should do if Acrobat had already been uninstalled but large numbers of installer files remained. That is precisely my situation.

I also noticed that an Adobe Community Manager recently indicated that the development team was being consulted about whether PatchCleanFlag remains supported in current and future updates.

I have not modified my registry or attempted this procedure because Reader has already been uninstalled and I do not know whether the setting would be applicable.

Microsoft Support Response

I contacted Microsoft Support for assistance determining whether Windows Installer still requires these cached patches.

Microsoft advised that it could not confirm whether the individual Adobe patches were orphaned or authorize their deletion, and referred me to Adobe.

Microsoft Support Case: 7111241435

Adobe's automated support assistant subsequently recommended uninstalling Reader, running the Cleaner Tool, and reinstalling the application. The first two steps have already been completed without resolving the problem.

Questions for Adobe's Technical Team

Is PatchCleanFlag still supported? Does it apply to current versions of 64-bit Acrobat Reader, and does it clean .msp files from C:\Windows\Installer?
What is the supported cleanup procedure after uninstallation? If Reader has already been uninstalled and the official Cleaner Tool has failed to remove these files, what does Adobe recommend?
Can Adobe provide a diagnostic method to determine whether these 189 Adobe-signed .msp files are still required by Windows Installer or are genuinely orphaned?
Could this indicate an Acrobat update-cache accumulation problem? Other community members have reported similar large collections of Adobe-signed installer files.
Can this issue be referred to Adobe's Acrobat installation or engineering team for investigation?

Important Safety Concern

I understand that manually deleting files from C:\Windows\Installer can damage software repair, update, or uninstallation functionality.

Although I have verified external backups of the files, I have not deleted or moved the originals.

I am specifically seeking a technically validated solution rather than instructions to indiscriminately remove Windows Installer cache files.

I would greatly appreciate a response from an Adobe employee or technical specialist familiar with Acrobat's Windows Installer patch management.

Thank you for your assistance.

Meenakshi Negi · Accepted Answer

Hielegant_Dream927c,Thank you for reaching out, and sorry for the trouble caused.Since Reader is already uninstalled, there is no need to create or modify any registry values. You can use the standalone patch cleanup utility instead. I have attached the file.Steps to run:Extract the ZIP file.Open Command Prompt as Administrator and run CPInstCU.exeto perform the cleanup.To preview the cleanup without deleting any files, runCPInstCU.exe simulateThe default log is available at C:\Windows\Temp\PatchCleanuplog.txt.Please try the steps suggested above and let us know how it goes.Thanks,Meenakshi

elegant_Dream927c · Answer

Hi Meenakshi,I wanted to follow up and let you know that the standalone Adobe Patch Cleanup Utility worked successfully!After downloading the utility you provided, I first ran it in simulation mode. It identified 189 orphaned Adobe Acrobat Reader patch files.Before proceeding, I backed up all 189 files to an external drive and verified that the backup copies matched the originals using SHA-256 hashes.I then ran CPInstCU.exe without the simulation argument. The cleanup log confirmed:Adobe orphaned patches found: 189Deleted/Marked: 189Cleanup completed successfullyFollowing the cleanup, I successfully restarted my computer and confirmed that the recovered disk space remained available. My C: drive now shows 148 GB free, compared with approximately 25 GB before the cleanup.Thank you very much for providing this utility and helping me resolve an issue that had been consuming more than half of my computer's storage capacity.I hope this information will help other users experiencing the same problem.Thank you again!