Skip to main content
Kamal2568898
Kamal2568898
Participating Frequently
February 19, 2026
Question

RUM Exit Code 2 – AcrobatDC 25.0 Fails to Install via AUSST Override (Works on Some Devices)

  • February 19, 2026
  • 1 reply
  • 0 views

Environment

  • Product: Adobe Acrobat DC (Continuous Track)

  • Version attempting to install: 25.0 (e.g. 2500121208)

  • RUM Version: 3.1.0.3

  • Update method: Remote Update Manager

  • Updates hosted internally via AUSST

  • Override file configured to point to internal AUSST server

Internal update path confirmed working:
https://domain/updates/Acrobat/pub/adobe/acrobat/win/AcrobatDC/2500121208/

 

Issue

On some devices, RUM successfully installs Acrobat 25.x from our AUSST server.
On other devices (same override, same RUM version), the update fails consistently.

RUM output:

RemoteUpdateManager version is : 3.1.0.3Starting the RemoteUpdateManager...**************************************************Following Acrobat/Reader updates are applicable on the system :(AdobeAcrobatDC-25.0)******************************************************************************************************* Installing (AdobeAcrobatDC-25.0) ...*** Failed to install (AdobeAcrobatDC-25.0) ...**************************************************No new applicable Updates. Seems like all products are up-to-date.Following Updates failed to Install :(AdobeAcrobatDC-25.0)**************************************************RemoteUpdateManager exiting with Return Code (2)Adobe RUM finished with exit code 2

Key Points

  • The override XML is identical across all devices.

  • AUSST structure contains the correct 25.x build.

  • Some machines update successfully using the same override.

  • Failing machines consistently return Exit Code 2.

  • Acrobat application is not running during update. Machine was freshly restarted.

  • RUM is executed as SYSTEM & Administrative user.

  • No difference in override XML between working and failing devices.

 

Question

Given that:

  • The override configuration is identical

  • AUSST content is present and working

  • RUM version is consistent

  • Some devices update successfully

What conditions cause RUM Exit Code 2 when the update is detected as applicable but fails during installation?

 

All our machines have Office 365, Microsoft Teams installed. Is this something to do with Office 365?

    1 reply

    A
    Community Manager
    Anshul_NautiyalCommunity Manager
    Community Manager
    February 19, 2026

    Hi ​@Kamal2568898 

    Thank you for reaching out. Based on your query, I understand that on some devices RUM successfully installs Acrobat 25.x from your AUSST server, while on other devices (with the same override and RUM version) the update fails consistently with RemoteUpdateManager exiting with Return Code (2). Please confirm if this is the issue you need assistance with.

    Exit Code 2 indicates that one or more updates could not be installed. In some scenarios, Code 2 may appear alongside “no updates applied” when components are skipped or blocked (for example, AUSST not offering a newer payload yet, FeatureLockDown disabling updates, or the EULA not being accepted). The net effect is that nothing gets installed.

    What to do about the EULA
    If the EULA isn’t accepted, updates may be skipped. There are two options:
    • Manual: Launch Acrobat once and accept the prompt.
    • Enterprise (recommended): Pre-accept via configuration so users never see the prompt by setting the following registry key:
    HKLM\SOFTWARE\Adobe\Adobe Acrobat\EULA\EULAAccepted = 1
    You can review this document for more details: https://www.adobe.com/devnet-docs/acrobatetk/tools/Wizard/properties.html?highlight=eula

    Review your Acrobat FeatureLockDown settings. If you intend to allow RUM updates, the lockdown key preventing updates should be configured appropriately. The key is bUpdater and it should be set to 1 to allow update functionality. You can review this document: https://www.adobe.com/devnet-docs/acrobatetk/tools/PrefRef/Windows/FeatureLockDown.html

    Additionally, verify that the affected machines can reach the internal update server on the required port without redirects or blocks.

    Hope this helps. Please try these steps and let us know if the issue persists.

    Regards,

    ^AN

    Kamal2568898
    Kamal2568898Author
    Participating Frequently
    February 19, 2026

    Doesn’t seem to help still getting the errors.


    REG ADD "HKLM\SOFTWARE\Adobe\Adobe Acrobat\EULA" /v EULAAccepted /t REG_DWORD /d 1 /f

    REG ADD "HKLM\SOFTWARE\Adobe\Adobe Acrobat\FeatureLockDown" /v bUpdater /t REG_DWORD /d 1 /f

     

    RemoteUpdateManager version is : 3.1.0.3
    Starting the RemoteUpdateManager...

    **************************************************
    Following Acrobat/Reader updates are applicable on the system : 
            (AdobeAcrobatDC-25.0)
    **************************************************
    **************************************************
    *** Installing (AdobeAcrobatDC-25.0) ...
    *** Failed to install (AdobeAcrobatDC-25.0) ...
    **************************************************
    No new applicable Updates. Seems like all products are up-to-date.
    Following Updates failed to Install :
            (AdobeAcrobatDC-25.0)
    **************************************************
    RemoteUpdateManager exiting with Return Code (2)
    Adobe RUM finished with exit code 2

    A
    Community Manager
    Anshul_NautiyalCommunity Manager
    Community Manager
    February 19, 2026

    ​@Kamal2568898 Thank you for testing those steps and for sharing the update. Additionally, please confirm whether the Creative Cloud Desktop app is installed on the affected machines.

     

    Could you please share the following logs so I can review them and assist you further?

    Acrobat Updater DC.log
    Windows
    C:\Users<username>\AppData\Local\Temp\Adobe\Acrobat\Acrobat Updater DC.log

    RemoteUpdateManager.log
    Windows
    C:\Users<username>\AppData\Local\Temp\RemoteUpdateManager.log

    Acrobat Update Helper DC.log
    Windows
    C:\Users<username>\AppData\Local\Temp\Adobe\Acrobat\Acrobat Update Helper DC.log

    Additionally, please confirm whether the affected machines can reach the internal update server on the required port without redirects or blocks.

    Once we have these details, we can review further and help identify the cause.

    Regards,
    ^AN

    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices