Skip to main content
A
andrea5CD4
Participant
March 5, 2025
Question

problem update acrobat

  • March 5, 2025
  • 2 replies
  • 247 views

Hello
we found that we have more than 300 pc that not auto update even update is enabled. All pc have 21.001.20135 version.

All pc were distributed with sccm and acrobat is installed during osd task. The installer is 21.001.20135 but the normal behaviour is that after some time acrobat reader auto update to latest version. For some reason this not happen anymore.

I already updated the adobe installer in sccm, but I would like to resolve the issue in these 300 pc.

I enabled verbose log and I try to start an update search from acrobat reader gui: the response is always no update are available.

Is there a way to force update from 21.001 version or i need to force a new install?

2 replies

AnandSri
Community Manager
AnandSriCommunity Manager
Community Manager
March 18, 2025

Hello Andrea!

 

I hope you're doing well, and we apologize for the delayed response and the trouble.

 

As correctly suggested by our product community expert, The most effective solution would be to use SCCM to deploy a script that uninstalls the current version of Adobe Acrobat Reader and then installs the updated package you've prepared. For detailed information, please see this article: https://adobe.ly/4hElv47

 

Thanks,

Anand Sri.

creative explorer
Community Expert
creative explorerCommunity Expert
Community Expert
March 17, 2025

@andrea5CD4  It appears you're facing a widespread issue with Adobe Acrobat Reader's auto-update functionality across your 300+ PCs, despite having updates enabled. The fact that the update search consistently returns "no updates available" despite being on version 21.001.20135 suggests a potential corruption or misconfiguration in the existing installations. Given the scale of the problem, a simple force update might not be feasible or reliable. The most efficient solution would likely be to deploy a script via SCCM to uninstall the existing Adobe Acrobat Reader version and then push the updated installer package you've already prepared. This ensures a clean installation and should restore the auto-update functionality. Before deploying to all 300 machines, test the script on a small subset to verify its effectiveness and minimize potential disruptions. Good luck!

m
Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices