Skip to main content
Participant
October 14, 2026
Question

Acrobat updater appears to leave Windows Installer busy — configuration error 1602 and AdobeARM error 120100

Hello,

I need help diagnosing an apparently unfinished Acrobat update on Windows.

I am trying to install another application, VirtualBox, but my installation procedure stopped after detecting an apparently active Windows Installer transaction. I would like to establish whether Acrobat is still updating, waiting for user interaction, or encountering a recovery problem.

A read-only diagnostic collected on 13 October 2026 showed:

  • Installed product: Adobe Acrobat (64-bit).

  • Registered version: 26.002.21931.

  • Windows Installer service: Running, with CanStop=False.

  • Both AdobeARM.exe and msiexec.exe processes were present.

  • The MSI InProgress registry key was absent.

Windows Application events recorded this sequence:

  1. An Acrobat transaction started at approximately 16:49:26.

  2. At 16:49:43, Acrobat reported “Configuration failed”, with reconfiguration status 1602, followed by a transaction-end event.

  3. At 16:49:51, another transaction for the same Acrobat product started, with AdobeARM.exe as the client.

The AdobeARM logs also contain:

  • “Another instance of ARM is already running.”

  • “Setting Error Condition: 120100”

  • An InstallProductMsp entry for:
    AcroRdrDCx64Upd2600221931_incr.msp

  • Arguments: ARM_EXECUTION=YES REBOOT=ReallySuppress

The collected excerpt does not show the completion of that second installation attempt. Some ARM helper entries report ERROR_SUCCESS, but I cannot determine whether those refer to the helper or the actual Acrobat update.

The diagnostic itself did not stop processes, change services or registry settings, or launch another installer.

Could someone advise:

  1. Which log or event would reliably confirm whether the second Acrobat transaction has completed?

  2. How can I check for a hidden update, repair, or rollback prompt?

  3. What is the Adobe-supported recovery procedure if this update is stalled, without damaging Acrobat or Windows Installer?

I do not have access to paid support. I can provide relevant, redacted log excerpts if needed.

Thank you.

    2 replies

    Participant
    October 16, 2026

    Thank you so much!

    Translate
    Participating Frequently
    October 14, 2026

    Please collect all Updater log files based on the instructions below, zip all logs, upload zip file somewhere and provide the link, and I will try to check. Also, enable verbose MSI logging (google for instructions) in case MSI verbose log file will be needed for investigation.

    Enable ARM verbose logging - add iLogLevel DWORD registry value in the path below and set it to 1

    HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Adobe\Adobe ARM\1.0\ARM

    Delete any registered errors and last check for updates- delete registry values below in 

    HKEY_CURRENT_USER\Software\Adobe\Adobe ARM\1.0\ARM

    tLastT_Acrobat and\or tLastT_Reader

    [tLastError_Acrobat] (any value that has error in the name)

    Make sure AdobeARM.exe process is not running

    Make sure Acrobat\Reader is not in use

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

    Wait approximately 20 minutes (should be enough if update is available and got installed)

    Collect and provide all ARM logs files that are available (not all files exist all the time)-

    From User Temp folder:

    AdobeARM.log

    AdobeARM_Backup.log

    AdobeARM_NotLocked.log

    AdobeARM_UCB.log

    From Windows Temp folder:

    AdobeARM.log

    AdobeARMHelper.log

    Translate