Skip to main content
D
devon_62
Participating Frequently
April 13, 2020
Question

Force updates on Acrobat Reader DC?

  • April 13, 2020
  • 4 replies
  • 16296 views

Hey Everyone,

In my work environment we currently have 1500 installs of Acrobat Reader DC that are out of date. I have been researching a way to try and get these up to date since their version has a security vulnerability. I've been looking for some form of registry edit that could force all of these to get up to date, I am finding that it seems like they're not up to date because adobe was never launched on these machines, currently i am trying to test if pushing an "Accept EULA" registry edit will allow those updates to start. is there any advice that someone could give me on this? the majority of the out of date installs are version 18.009.20044

 

Thanks

This topic has been closed for replies.

4 replies

JR Boulay
Community Expert
JR BoulayCommunity Expert
Community Expert
May 12, 2022

MOVED TO THE ACROBAT READER FORUM

Acrobate du PDF, InDesigner et Photoshopographe
V
Vraj23565700b6qj
Participant
May 12, 2022

Hello, We are having a smilar issue with Adobe reader DC not updating over a year. The update task seems to run but nothing happens. We have deployed this via Intune package to arpund 700 devices. 

 

Can someone help please?

 

thanks 

L
LeoUpdaterX
Participating Frequently
May 12, 2022

You will have to provide updater verbose log file, please check the beginning of this thread for instructions.

Do not post log file here, just send me in the private message.

The most common reasons for a product not being automatically updated are:

Product deployed from patched Admin Install Point

Updater Service is disabled or not installed

Updater is disabled by policy

V
Vraj23565700b6qj
Participant
May 12, 2022

Thanks, I have just sent you the log file. we did notice the bprotectmode is set to 0. Do we need to enable this to 1 to allow for auto update?

 

T
Test Screen Name
Legend
April 29, 2020

How did the 1500 installs get there? I wonder if they were deployed in a way that prevented automatic updating, and in the expectation that updates would be pushed?

D
devon_62Author
Participating Frequently
April 29, 2020

Hey There,

 

For the most part they would get automaticaly installed via Labtech or WDS (it differes per customer) we did expect them to receive updates however this seems to not be the case. The issue is that since they were installed as part of the default computer build it seems that some users have adobe and don't even use it. From the testing that I have done it seems like the automatic updates don't start until the EULA is accepted. In the version that was installed on most computers it seems like they do not have a EULA registry. I will provide the available registries.

 

 

 

Thanks,

Devon

 

L
LeoUpdaterX
Participating Frequently
April 30, 2020

Hi Devon,

Log confirms that Updater will not proceed because of EULA 

[2020-04-29 16:34:52:0560] EULA not yet accepted

 

Do you know how to deal with this or need help?

L
LeoUpdaterX
Participating Frequently
April 13, 2020

To investigate why exactly Reader is not updated, you will need to provide verbose Updater log file.

Please enable Updater verbose logging, use Updater to try to update again, collect and send me AdobeARM.log file from User Temp folder.
To enable Updater verbose logging set iLogLevel REG_DWORD value to 1 in the registry below
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Adobe\Adobe ARM\1.0\ARM on 64 bit OS
HKEY_LOCAL_MACHINE\SOFTWARE\Adobe\Adobe ARM\1.0\ARM on 32 bit OS
D
devon_62Author
Participating Frequently
April 29, 2020

Hey Leo,

 

Apologies for the delay but i was pulled to a different project. I had to create the registries since they did not exist. where would this update log file be generated? and how would I generate it?

Thanks,

Devon

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