Fix Acrobat Pro DC Disappearing from SCCM After Updates
Question details
SCCM fails to detect Acrobat Pro DC 2019 after it checks for updates, despite the application being fully installed and functional.

- Product
- Adobe Acrobat Pro DC / SCCM
- Device & OS
- not provided
- Scenario
- Managing and monitoring software deployments and updates via System Center Configuration Manager (SCCM).
- Observed behavior
- The application disappears from SCCM detection following an update check, likely due to a mismatch in the MSI product code or version rules.
Ensure you have administrative access to the SCCM console and a test client machine to verify registry paths, file versions, and application detection methods.
Update SCCM Detection Method to Use File System Version
Bypassing the rigid MSI product code detection in favor of a file-based version check ensures updates do not break SCCM detection.
When Acrobat Pro DC updates itself, the MSI product code or minor version numbers can change. If SCCM is strictly looking for the original MSI code, it will falsely report the application as uninstalled. Using a File System rule targeting the main executable provides a more robust detection method.
Open the SCCM console, navigate to your Acrobat Pro DC application, select the 'Deployment Types' tab, and click 'Edit'.
Go to the 'Detection Method' tab and remove the existing MSI product code rule.
Click 'Add Clause', set the setting type to 'File System', and browse to the installation path (e.g., C:\Program Files (x86)\Adobe\Acrobat DC\Acrobat). Set the file or folder name to 'Acrobat.exe'.
Select 'The file system setting must satisfy the following rule to indicate the presence of this application'. Set the property to 'Version', operator to 'Greater than or equal to', and enter the base version number of your Acrobat installation.

Update SCCM Detection Rule Using Registry Keys
Alternatively, you can use registry keys that persist across updates to confirm the application's presence.
Simplify Document Management with WPS Office
If managing complex deployments and updates for tools like Adobe Acrobat and Microsoft Office is causing SCCM detection issues, consider switching to WPS Office. It provides a lightweight, highly compatible alternative with built-in PDF editing, word processing, spreadsheets, and presentations, saving you time and deployment headaches.
- 1. Download the Installer: Visit the official WPS Office website and download the free, lightweight installer package.
- 2. Install WPS Office: Run the installation package. The process is quick and sets up Word, Excel, Presentation, and PDF tools simultaneously.
- 3. Start Managing Documents: Open WPS Office to effortlessly handle PDFs and Microsoft Office formats with no complex SCCM detection hurdles.

Frequently Asked Questions
Why does Acrobat Pro DC disappear from SCCM after a standard update?
Adobe sometimes releases updates that alter the underlying MSI product code or specific version strings. If SCCM's detection method relies strictly on the original MSI code, it will no longer recognize the updated application.
How can I force SCCM to recognize the updated detection rule immediately?
On the client machine, open the Configuration Manager from the Control Panel, navigate to the Actions tab, and manually run the 'Application Deployment Evaluation Cycle' and the 'Machine Policy Retrieval & Evaluation Cycle'.
Which SCCM detection method is most reliable for applications that self-update?
A File System detection rule checking if the main executable (.exe) version is 'greater than or equal to' the deployed version is generally the most resilient method for self-updating applications.




