(Re-)Enable Silent Automatic Updates for Adobe Acrobat Reader DC

In some environments, silent automatic updates for Adobe Acrobat Reader DC may have been disabled during a previous installation or enforced via Group Policy (GPO).
This article explains how to re-enable silent automatic updates in a supported and reliable way.

Overview

To restore silent auto-update functionality, the following steps are required:

1. Install a new version of Acrobat Reader DC with the correct update mode.
2. Install (or re-install) the Adobe Update Service (AdobeARMservice).
3. Update the required Windows Registry settings.
4. Ensure GPO settings do not block the updater.

Step 1 – Install Acrobat Reader DC with Silent Update Mode Enabled

When installing Acrobat Reader DC, you must explicitly enable UPDATE_MODE=3 (silent automatic updates) and ensure that the Adobe ARM service is not disabled.

Example command line:

.\AcroRdrDCx642500120982_MUI.exe ... EULA_ACCEPT=YES UPDATE_MODE=3

(Other standard silent install switches may be used depending on your deployment tool.)

⚠️ Important
Do not use the property:

DISABLE_ARM_SERVICE_INSTALL=1

If this property was used previously, the Adobe Update Service will not be installed and silent updates will not work.

Step 2 – Install the Adobe Update Service (AdobeARMservice)

If the Adobe Update Service is missing, you can install it manually by running:

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

After execution, verify that the Windows service AdobeARMservice exists and is set to Automatic.

Note: Even on 64-bit systems, Adobe Acrobat Reader DC update components (ARM) are 32-bit and therefore use Program Files (x86) and WOW6432Node registry paths.

Step 3 – Configure Registry Settings for Silent Updates

Use the following PowerShell commands to configure the required registry keys.

Note: All commands and registry changes must be executed with administrative privileges.

Adobe ARM Configuration

Set-ItemProperty -Path "HKLM:\SOFTWARE\Wow6432Node\Adobe\Adobe ARM\1.0\ARM" -Name "iDisablePromptForUpgrade" -Value 1 -Type DWord

Set-ItemProperty -Path "HKLM:\SOFTWARE\Wow6432Node\Adobe\Adobe ARM\1.0\ARM" -Name "iCheck" -Value 3 -Type DWord

Set-ItemProperty -Path "HKLM:\SOFTWARE\Wow6432Node\Adobe\Adobe ARM\1.0\ARM" -Name "iCheckReader" -Value 3 -Type DWord

Explanation:

• iCheck = 3 → Enables automatic silent updates
• iCheckReader = 3 → Applies the same behavior to Reader
• iDisablePromptForUpgrade = 1 → Prevents user prompts

GPO / FeatureLockDown Setting

If updates were previously disabled via GPO, ensure the updater is explicitly enabled:

Set-ItemProperty -Path "HKLM:\SOFTWARE\Policies\Adobe\Adobe Acrobat\DC\FeatureLockDown" -Name "bUpdater" -Value 1 -Type DWord

Note: Depending on your environment, the policy path may be applied under Adobe Acrobat Reader\DC instead of Adobe Acrobat\DC.

Legacy ARM Configuration (Optional but Recommended)

Some environments still rely on legacy ARM keys:

Set-ItemProperty -Path "HKLM:\SOFTWARE\WOW6432Node\Adobe\Adobe ARM\Legacy\Acrobat\{AC76BA86-1033-FF00-7760-BC15014EA700}" -Name "Check" -Value 24 -Type DWord

Set-ItemProperty -Path "HKLM:\SOFTWARE\WOW6432Node\Adobe\Adobe ARM\Legacy\Acrobat\{AC76BA86-1033-FF00-7760-BC15014EA700}" -Name "Mode" -Value 3 -Type DWord

Step 4 – Troubleshooting and Verification

If silent automatic updates still do not work as expected, use the following checks to identify the issue.

1. Verify Adobe ARM Installation

Verify that Adobe ARM (Adobe Update Manager) is installed both on disk and registered in Windows.

1.1 Check ARM installation folder

Test-Path "C:\Program Files (x86)\Common Files\Adobe\ARM\1.0"

Expected result:

• True → Adobe ARM files are present
• False → Adobe ARM is missing or was not installed

1.2 Verify Adobe ARM Registry Installation

Adobe ARM registers itself in the following registry location:

Test-Path "HKLM:\SOFTWARE\WOW6432Node\Adobe\Adobe ARM\1.0"

You can also list the ARM configuration keys:

Get-ItemProperty "HKLM:\SOFTWARE\WOW6432Node\Adobe\Adobe ARM\1.0\ARM" | Format-List *

Expected results:

• Registry path exists
• ARM-related values such as iCheck, iCheckReader, and update settings are present

If this registry path is missing, Adobe ARM is not properly installed or was removed by policy or cleanup scripts.

1.3 Verify Adobe ARM Installation via Uninstall Registry

Adobe ARM is registered as a Windows component and can be verified through the Uninstall registry keys.

Use the following PowerShell command:

Get-ChildItem "HKLM:\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Uninstall" |
Get-ItemProperty |
Where-Object { $_.DisplayName -match "Adobe" } |
Select-Object DisplayName, DisplayVersion, InstallLocation

Expected results:

• An entry related to Adobe ARM / Adobe Acrobat Reader DC is present
• InstallLocation points to:

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

• A valid DisplayVersion is displayed

If no Adobe ARM–related entry appears:

• Adobe ARM is not installed, or
• It was removed by a previous installation option or a GPO / cleanup script

In this case, reinstall Acrobat Reader DC without using DISABLE_ARM_SERVICE_INSTALL, or manually trigger ARM installation using:

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

2. Verify the Adobe Update Service (AdobeARMservice)

Confirm that the AdobeARMservice is installed and running.

Get-CimInstance Win32_Service -Filter "Name='AdobeARMservice'" | Format-List *

Verify:

• State = Running
• StartMode = Auto

If the service is missing, install it manually:

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

3. Verify the Scheduled Task: Adobe Acrobat Update Task

Get-ScheduledTask -TaskName "Adobe Acrobat Update Task" | Format-List *
Get-ScheduledTaskInfo -TaskName "Adobe Acrobat Update Task" | Format-List *

Ensure:

• Task exists and is Enabled
• LastTaskResult = 0x0

4. Check Ongoing Downloads via BITS

Get-BitsTransfer -AllUsers |
Where-Object DisplayName -match "Acrobat" |
Format-List DisplayName, TransferType, JobState, BytesTransferred, BytesTotal,
@{Name='Percent';Expression={
  if ($_.BytesTotal -gt 0) {
    "{0:N1}%" -f (($_.BytesTransferred / $_.BytesTotal) * 100)
  } else {
    "N/A"
  }
}}, CreationTime, ModificationTime, TransferCompletionTime

5. Additional Checks

• Ensure BITS service is running:

Get-Service BITS

• Verify registry values are not reverted by Group Policy.

Summary

If silent automatic updates do not work:

1. Verify Adobe ARM files and registry entries.
2. Confirm AdobeARMservice is installed and running.
3. Validate the Adobe Acrobat Update Task.
4. Check update activity via BITS.

This structured verification usually reveals whether the issue is related to installation, service registration, scheduled tasks, or policy enforcement.

Conclusion

By reinstalling Acrobat Reader DC with UPDATE_MODE=3, restoring the Adobe Update Service, and correcting registry/GPO settings, you can successfully re-enable silent automatic updates, even if they were previously disabled by policy or installation options.