Skip to main content
GARY5E45
Participant
September 4, 2026
Question

Remote Update Manager Failing

  • September 4, 2026
  • 3 replies
  • 38 views

Starting a week or so ago, all of our corporate machines have started to report errors when attempting to update Adobe through RUM.   

After digging through logs, all of our machines are reporting the following:

[2026-09-04 09:05:01:0217] Adobe ARM 1.824.460.1149 logging started.
[2026-09-04 09:05:01:0217] Command Line: /RUM /ProxyUserName:"" /ProxyPassword:"" /PRODUCT:Acrobat /VERSION:26.0
[2026-09-04 09:05:01:0222] ProductCode: {AC76BA86-1033-FFFF-7760-BC15014EA700}
[2026-09-04 09:05:01:0222] ProductName: Adobe Acrobat (64-bit)
[2026-09-04 09:05:01:0222] ProductVersion: 26.001.21789
[2026-09-04 09:05:01:0222] ProductUACPatching: enabled
[2026-09-04 09:05:01:0251] Failed to get Value for StringID: IDS_ACTION_CONNECTING
[2026-09-04 09:05:01:0251] DownloadFileAndWait isComplete returns error
[2026-09-04 09:05:01:0251]  Error Code: -2145386493
[2026-09-04 09:05:01:0257] BITS AddFileSet failed with error:
[2026-09-04 09:05:01:0257]  Error Code: -2147023651
[2026-09-04 09:05:01:0257] downLoadFileSet() failed
[2026-09-04 09:05:01:0257]  Error Code: -2147023651
[2026-09-04 09:05:01:0259] BITs failed, download manifest Job is not in Transferred state
[2026-09-04 09:05:01:0259] ** Setting Error Condition: 140300
[2026-09-04 09:05:01:0259] Failed to get Value for StringID: IDS_TITLE_NOT_UPDATED
[2026-09-04 09:05:01:0259] Failed to get Value for StringID: IDS_ERROR_DOWNLOAD_DESCRIPTION
[2026-09-04 09:05:01:0259] Failed to get Value for StringID: IDS_ERROR_DIALOG_DETAIL
[2026-09-04 09:05:01:0259] Failed to get Value for StringID: IDS_TITLE_CHECKING
[2026-09-04 09:05:01:0415] Failed to get Value for StringID: IDS_BAL_DOWNLOADPROGRESS
[2026-09-04 09:05:01:0562] MDOV1615
[2026-09-04 09:05:01:0563] New file object: AcrobatDCx64Upd2600221869_incr.msp
[2026-09-04 09:05:01:0563] MVF259
[2026-09-04 09:05:01:0570] Failed to get Value for StringID: IDS_TOOLTIP_DOWNLOADING
[2026-09-04 09:05:02:0699] InstallProductMsp...
[2026-09-04 09:05:02:0699]    file - C:\ProgramData\Adobe\ARM\Acrobat_26.001.21789\AcrobatDCx64Upd2600221869_incr.msp
[2026-09-04 09:05:02:0699]    args - ARM_EXECUTION=YES REBOOT=ReallySuppress
[2026-09-04 09:05:38:0464] Entered INSTALLMESSAGE_ERROR
[2026-09-04 09:05:38:0465] MSI Record [0]: Error [1].The file '[2]' cannot be installed because the file cannot be found in cabinet file '[3]'. This could indicate a network error, an error reading from the CD-ROM, or a problem with this package.
[2026-09-04 09:05:38:0465] MSI Record [1]: 1334
[2026-09-04 09:05:38:0465] Reporting actual error: 1334
[2026-09-04 09:05:38:0465] MSI Record [2]: pdfport.dll3
[2026-09-04 09:05:38:0465] MSI Record [3]: Languages.cab
[2026-09-04 09:05:38:0465] Error 1334.The file 'pdfport.dll3' cannot be installed because the file cannot be found in cabinet file 'Languages.cab'. This could indicate a network error, an error reading from the CD-ROM, or a problem with this package.
[2026-09-04 09:05:38:0465]  Error Code: 13
[2026-09-04 09:05:38:0465] ** Setting Error Condition: 150000
[2026-09-04 09:05:38:0465] Failed to get Value for StringID: IDS_TITLE_NOT_UPDATED
[2026-09-04 09:05:42:0780] Installation returned error code: 1603
[2026-09-04 09:05:42:0780] Last MSI action name: Rollback
[2026-09-04 09:05:42:0780] Error Code: 1603
[2026-09-04 09:05:42:0782] *** Product after installation ***
[2026-09-04 09:05:42:0784] ProductCode: {AC76BA86-1033-FFFF-7760-BC15014EA700}
[2026-09-04 09:05:42:0784] ProductName: Adobe Acrobat (64-bit)
[2026-09-04 09:05:42:0784] ProductVersion: 26.001.21789
[2026-09-04 09:05:42:0784] ProductUACPatching: enabled
[2026-09-04 09:05:43:0001] Adobe ARM 1.824.460.1149 logging finished.

All are reporting the same error that “pdfport.dll3” cannot be found in cabinet file “Languages.cab”.

Anyone else receiving the same error?   

Thanks!

    3 replies

    Community Manager
    AnkitVermaCommunity Manager
    Community Manager
    September 4, 2026

    Hi ​@GARY5E45,

    Thanks for reaching out, and for posting the full ARM log. We know how disruptive it is when updates start failing across every machine at once, especially on something as routine as RUM.

    Reading through the log, the download stage is where things first break: the BITS transfer doesn't complete (the manifest job never reaches the Transferred state, error 140300), and the 1334 rollback happens on the install attempt that follows. So the starting point is the failed download rather than the install itself.

    A few things would help us narrow this down:

    1. Are your clients pulling updates directly from Adobe, or through an AUSST internal update server?
    2. If you're on AUSST, does the failure still happen when a single test machine is pointed straight at Adobe (by temporarily removing the overrides file)?
    3. Did anything change on the network around when this started, a week ago, such as a proxy, firewall, or SSL inspection rule? BITS transfers to Adobe run over the endpoints listed here, so it's worth confirming these are reachable and not being intercepted: https://helpx.adobe.com/enterprise/kb/network-endpoints.html
    4. Which RUM version are you running (Admin Console > Packages > Tools), and is it consistent across the fleet?

    Please share what you find and we'll take it from there.

    Thanks,
    ^AV

    GARY5E45Author
    Participant
    September 4, 2026

    Thank you for the response.  Here are the answers to your questions:

    1. Pulling directly from Adobe
    2. N/A
    3. Nothing changed and we are 100% work from home, so we have variety of connections that it is failing on (fiber, cable, DSL).    I’ll review your KB article to see if I can find anything relevant there.
    4. It is consistent across the fleet.
    Community Manager
    AnkitVermaCommunity Manager
    Community Manager
    September 4, 2026

    Hi ​@GARY5E45,

    Thanks, that helps. With AUSST out of the picture and the same failure showing up across fiber, cable, and DSL, this doesn't look like a network issue on any one connection. What every machine has in common is the build (26.001.21789) and the same 1334 on the same file in the same patch.

    Could you try installing the 26.002.21869 update manually on one affected machine, outside of RUM? You can grab it from the release notes: https://adobe.ly/4iNqy6w. If it still rolls back with the same 1334, we know RUM isn't the factor and we'll dig into the patch and the local install state. If it goes through cleanly, then it's something in how RUM is pulling the file, and we'll look there.

    Before you run it, clear the old cache at C:\ProgramData\Adobe\ARM\Acrobat_26.001.21789\ so it's not reusing a partial file. And since the file it's choking on lives in Languages .cab let me know if your machines are all one language or a mix.

    Let us know how the manual install goes.

    Thanks,
    ^AV

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