Enable Adobe Acrobat updates

​Hi @athletic_goal9770 ,

Thanks for the detailed write-up, that's a solid starting point.

A couple of things would help confirm the right path here: are these 35 devices running Acrobat Reader, or Acrobat Standard/Pro (the GUID and registry paths differ between them), and were they originally installed via the MSI or EXE installer? Also, does the AdobeARMservice Windows service actually exist on these machines currently, or is it missing entirely? That matters because if the original install used the DISABLE_ARM_SERVICE_INSTALL property, the update service was never installed, and just flipping registry values won't bring it back; you'd need to install it separately.

On what I can confirm: your bUpdater FeatureLockDown key and the general registry-based approach match Adobe's documented enterprise updater configuration. For the service specifically, if it's missing, it can be installed manually by running:

C:\Program Files (x86)\Common Files\Adobe\ARM\1.0\AdobeARMHelper.exe

Then confirm the AdobeARMservice service exists and is set to Automatic.

To manually trigger a check/update rather than waiting for the scheduled task, running the following works for both diagnostics and forcing the update:

C:\Program Files (x86)\Common Files\Adobe\ARM\1.0\AdobeARM.exe

For logs, once you run the above, check the user's Temp folder (%temp%) for a file named AdobeARM.log, and any MSIxxxxx.log created around the same time in the same folder, that's the update installer's own MSI log. For more detail than the default log, verbose logging can be enabled first via:

HKLM\SOFTWARE\WOW6432Node\Adobe\Adobe ARM\1.0\ARM, value iLogLevel = 1 (DWORD)

I don't want to confirm every one of your specific registry values (the Mode/iCheck/iCheckReader keys) without a definitive source in front of me, since getting this wrong at scale on 35 machines could cause more work, not less. It would be worth cross-checking those specific values against Adobe's Enterprise Toolkit Windows Registry Reference before rolling this out broadly: Enterprise Toolkit documentation

Let us know whether the service exists on these machines and what product/install method was used, and we can narrow this down further.

~Amal