Skip to main content
Participating Frequently
July 9, 2020
Question

bUpdater registry key is reset to 0 after autoupdate

  • July 9, 2020
  • 1 reply
  • 14760 views

We recently rolled out an autoupdate version of the Adobe Acrobat Reader DC on a few testclients. Before that we used fixed versions where the update feature was disabled via the FeatureLockDown settings.

After the installation of the autoupdate version the registry keys needed for autoupdate are all set to 1 (as intended):

HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Policies\Adobe\Acrobat Reader\DC\FeatureLockDown\bUpdater
HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Policies\Adobe\Acrobat Reader\DC\FeatureLockDown\cServices\bUpdater

HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Adobe\Acrobat Reader\DC\FeatureLockDown\bUpdater
HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Adobe\Acrobat Reader\DC\FeatureLockDown\cServices\bUpdater

 

And this works fine for the first update. The reader updates itself to the newest version after some time. The problem is that the bUpdater values are reset to 0 after the update, thus preventing future autoupdates.

Is there a setting in the Adobe Reader to prevent this behaviour?

This topic has been closed for replies.

1 reply

Participant
August 26, 2020

We're having the same issue. Have you found anything to resolve this?
(We deployed with a custom transform, but now we want to change to aut-update.)

Participating Frequently
August 26, 2020

You cannot change this without complete product uninstall.

Transforms are registered by Windows Installer Service with initial install of a product and always applied during Repair or Update transactions. It is standard MSI functionality.

Participant
August 26, 2020

That's unfortunate. We were hoping to avoid that across 20,000+ computers. 😞