Skip to main content
ricoBennysSpecialSauce
December 3, 2025
Answered

How do we Run / Trigger Adobe Acrobat Updates for PC's using Ansible?

  • December 3, 2025
  • 1 reply
  • 356 views

We installed acrobat 2025 using chocolaty and building our transform's file etc to remove not allowed features etc. We are wondering is there a command we can run to trigger patches/updates from ansible as we would like to do this on a monthly basis with our other patching. The machines are locked down so users cant do this themselves. We tried the following from admin cmd and powrershell 

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

 

and are getting failures but updates work if we run upgrade from the gui then sign in with admin account. 

 

 

Any help would be greatly appreciated!

 

 

Error log is 

[2025-12-03 11:43:34:0030] Adobe ARM 1.824.460.1110 logging started.
[2025-12-03 11:43:34:0030] Command Line: /ArmCleanup
[2025-12-03 11:43:34:0030] CleanupEx...
[2025-12-03 11:43:34:0030] Notify...
[2025-12-03 11:43:34:0030] WriteFile succeeded in Notify
[2025-12-03 11:43:34:0030] no folders to cleanup
[2025-12-03 11:43:34:0030] ARM returns ERROR_SUCCESS
[2025-12-03 11:43:34:0030] Adobe ARM 1.824.460.1110 logging finished.

 

 

Succesful gui log is 

[2025-12-03 11:22:37:0139] Adobe ARM 1.824.460.1110 logging started.
[2025-12-03 11:22:37:0139] Command Line: /PRODUCT:Acrobat /VERSION:25.0 /MODE:3
[2025-12-03 11:22:37:0175] ProductCode: {AC76BA86-1033-FFFF-7760-BC15014EA700}
[2025-12-03 11:22:37:0175] ProductName: Adobe Acrobat (64-bit)
[2025-12-03 11:22:37:0175] ProductVersion: 25.001.20756
[2025-12-03 11:22:37:0175] ProductUACPatching: enabled
[2025-12-03 11:22:37:0212] Using CommandLine preference AUTO_ALL
[2025-12-03 11:22:37:0216] Registered Error not expired
[2025-12-03 11:22:37:0216] Last installation error not expired, code: 120300
[2025-12-03 11:22:37:0217] Using registered preference AUTO_ALL
[2025-12-03 11:22:37:0218] Last check for updates not expired, code: 120300
[2025-12-03 11:22:37:0443] ARM returns ERROR_SUCCESS
[2025-12-03 11:22:37:0443] Adobe ARM 1.824.460.1110 logging finished.

Correct answer Anshul_Nautiyal

Hi @ericr5924979,

Thanks for reaching out. As checked I am able to see you have an active Teams license associated with the Adobe ID you used to post this query. I understand you're trying to trigger Adobe Acrobat 2025 updates via Ansible, and the AdobeARM.exe /update command is failing while updates succeed only through the GUI with an admin login. Please confirm if this is the issue you need assistance with.

The command:

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


only triggers the cleanup routine, not the actual patching process. That’s why the log shows /ArmCleanup and no update action.

The successful GUI log shows the parameters:

/PRODUCT:Acrobat /VERSION:25.0 /MODE:3


This indicates that AdobeARM.exe handles updates differently in an interactive session. However, AdobeARM.exe is not a supported method for automating updates in enterprise or managed environments, especially where Acrobat has been deployed via MSI or with transforms.

 

For enterprise deployments, Adobe officially recommends using supported update workflows such as:

Remote Update Manager (RUM) — a command-line tool that allows admins to remotely trigger and install updates for Adobe applications without needing to log in to each client machine. You can refer to the official documentation here:
https://adobe.ly/3Y2H1Z4

 

MSP patch deployment via your management tool  (SCCM, Intune, etc.), which is the standard enterprise update method.

 

Using one of these supported enterprise update mechanisms will ensure reliable monthly patching without requiring GUI access or manual elevation.

Hope this helps. Let us know if you need further assistance.

 

Regards,
^AN

1 reply

Anshul_NautiyalCommunity ManagerCorrect answer
Community Manager
December 3, 2025

Hi @ericr5924979,

Thanks for reaching out. As checked I am able to see you have an active Teams license associated with the Adobe ID you used to post this query. I understand you're trying to trigger Adobe Acrobat 2025 updates via Ansible, and the AdobeARM.exe /update command is failing while updates succeed only through the GUI with an admin login. Please confirm if this is the issue you need assistance with.

The command:

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


only triggers the cleanup routine, not the actual patching process. That’s why the log shows /ArmCleanup and no update action.

The successful GUI log shows the parameters:

/PRODUCT:Acrobat /VERSION:25.0 /MODE:3


This indicates that AdobeARM.exe handles updates differently in an interactive session. However, AdobeARM.exe is not a supported method for automating updates in enterprise or managed environments, especially where Acrobat has been deployed via MSI or with transforms.

 

For enterprise deployments, Adobe officially recommends using supported update workflows such as:

Remote Update Manager (RUM) — a command-line tool that allows admins to remotely trigger and install updates for Adobe applications without needing to log in to each client machine. You can refer to the official documentation here:
https://adobe.ly/3Y2H1Z4

 

MSP patch deployment via your management tool  (SCCM, Intune, etc.), which is the standard enterprise update method.

 

Using one of these supported enterprise update mechanisms will ensure reliable monthly patching without requiring GUI access or manual elevation.

Hope this helps. Let us know if you need further assistance.

 

Regards,
^AN

ricoBennysSpecialSauce
December 3, 2025

This is exactly what we needed thank you! 

Community Manager
December 3, 2025

Glad it helped. Let us know if you need further assistance in the future.

 

Regards,

^AN