Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Exit
LeoUpdaterX
Advocate
LeoUpdaterX
Advocate
Activity
‎Nov 06, 2019
09:59 AM
I would need verbose log file to determine why it is not updated.
The most common reasons are-
1.
bUpdater policy is set to disable updates. If that is the case, "Check for updates" menu item under Help menu is disabled.
2.
You deployed from Admin Install Point where you created new product (v19.012.20034) by applying 034 patch to the base product.
Check this to better understand your case-
https://community.adobe.com/t5/Acrobat/Acrobat-DC-Pro-will-not-update-beyond-15-9-20069-15942/td-p/9660476
... View more
‎Nov 05, 2019
06:58 PM
Updater is set for automatic updates by default and should be able to update Standard users without a request for credentials.
If it does not happen, please provide verbose log file (AdobeARM.log) from Updater session (search forums for iLogLevel registry value for instruction)
Please do not post log file here; send me private message.
Updater will not force close Adobe or reboot the machine. If reboot is required in rare cases, Updater will present a UI and user will need to click "reboot" button.
... View more
‎Nov 01, 2019
02:16 PM
1 Upvote
Duncan,
The log you provided is verbose, but it is not from Updater "RUM" session.
Compare Command line in your first log and the latest log.
Other notes-
1. Please delete the log from this thread (I saved the copy). Would make it easier to follow.
2. The log shows that some products are disabled by the policy and some not. You would need to double check that bUpdater policy is set properly for all products if that is your intention.
3. Delete the following registry before next test - HKEY_CURRENT_USER\Software\Adobe\Adobe ARM\1.0\ARM
You seem to have an issue with decryption. Next time you run Updater, please provide latest log in the private message; do not post here.
4. Delete the following folder before next test - C:\Users\All Users\Adobe\ARM
5. It seems that UAC is off on this system. If this is the case, it is not safe. Unless it is your intention I would advise to keep UAC on.
... View more
‎Oct 31, 2019
11:09 AM
The error from the log is-
[2019-10-31 15:13:38:0042] Missing file on server (HTTP Error 404)
This log is not verbose and does not show URL used by Updater. You can enable verbose logging (search this forum for iLogLevel registry value), run check for updates, find out from updated AdobeARM.log which URL is used and make sure that downloaded file actually exists on the server.
... View more
‎Oct 26, 2019
09:59 PM
There are number of reasons why update is available, but not yet installed automatically.
Check the registry value Mode using the link I provided. If Mode set to 3, it is fully automatic mode.
If you havn't installed update yet, restart PC, wait for approximately 30 minutes (do not launch any applications, especially Acrobat, Outlook, Browsers..) and check for updates again from Acrobat Help menu.
... View more
‎Oct 26, 2019
01:43 PM
Please refer to "Mode" registry value described in this article-
https://www.adobe.com/devnet-docs/acrobatetk/tools/PrefRef/Windows/index.html
Select Updater-Win in the table of contents on the left when you open the link.
... View more
‎Oct 02, 2019
11:39 AM
Would you check this thread below or search forum for similar issue? https://community.adobe.com/t5/Acrobat-Reader/Persistent-AdobeArm-failure-to-update/m-p/3964638#M7180
... View more
‎Sep 20, 2019
01:09 PM
1 Upvote
With new Forum version it is a chellenge to insert ftp link. Thanks for the note. Also, try Help\Check for updates menu again after updates are installed until you get "No updates available" from Updater.
... View more
‎Sep 20, 2019
12:56 PM
1 Upvote
Please install using .msi version of the installer - AcroRdrDC1500720033_en_US.msi from ftp://ftp.adobe.com/pub/adobe/reader/win/AcrobatDC/1500720033/ After installer finishes start Reader, accept EULA, go to Help\Check for updates menu and install latest updates.
... View more
‎Sep 15, 2019
05:19 PM
What exact Acrobat Reader version do you have installed? Which exact OS version? Can you provide an image of the "prompts to download and install the update"? Best if you could enable verbose updater logging and provide verbose log file (full file in the private message). Please search this forum for "iLogLevel" registry value for instructions.
... View more
‎Jul 19, 2019
03:45 PM
Have you seen this thread? Adobe Acrobat 2015 Updater Fails - Error 1309
... View more
‎Jul 19, 2019
09:38 AM
1 Upvote
What is your operating system and Reader version? On Windows, auto update does not start if application is in use.
... View more
‎Jul 15, 2019
02:13 AM
Franck, in your particular case, .msp files you see marked optional are not orphaned in a sense that MSI has their information registered for the product. When cumulative Patches for Acrobat are built, one of the built-in setting tells MSI to mark previous Patches as "obsolete". When latest Patch is installed, Patch Sequencer (part of MSI) enumerates all patches registered for a product, and tries to find and sequence those that should be applied. Obsolete patches are not applied. You have to decide if you want to proceed with solution to remove these "optional" files after testing Repair as I suggested. Again, it is crutial that you do not touch anything other than optional Patches. Uninstall should work fine even without these files. The only required file for uninstall is .msi - actual installer database.
... View more
‎Jul 14, 2019
11:34 PM
2 Upvotes
Download and run AcroSize.exe file from AcroSize.exe - Google Drive Select "Start Acrobat Report" button. Wait a few seconds. You should see Acrobat installation info. In the Description column find "Patch" records. Each Patch record would have Required or Optional value in the last column - Details. Those that are marked Optional can be deleted (again, this is against Windows Installer Service registration and you have to be careful) Start with renaming these "optional" files one by one and after each file I would recommend running Acrobat Repair from Help menu. If repair succeeds after file is renamed, it means that Windows Installer Service does not need this file. If possible, save these files somewhere on external drive just in case something will stop working in the future.
... View more
‎Jul 14, 2019
09:43 PM
2 Upvotes
Downloaded updates are deleted after successful installation. However, Windows Installer Service caches these files in C:\Windows\Installer folder (hidden) for maintenance. It is not recommended to manually remove files or registries managed by Windows Installer Service. If you absolutely can't work without cleanup, let me know and I will provide possible work around.
... View more
‎Jun 25, 2019
12:54 PM
Daf, you will need to provide more details to get meaningful help. For example, exact details on "Previously when trying to run the Adobe update...". Did you try manual update or allowed Updater to update your product? If your policies do not allow access for Local System account, you might not be able to install updates at all. Updater does not install updates; it calls Windows Installer Service (MSI) to do actual installation. MSI would need to have access to many things on the system and it would not be easy task to provide the list of what is required. What about Registries? These also need to be accessed by Updater and MSI.
... View more
‎Jun 24, 2019
11:29 PM
Daf, In automatic mode (default) updates are installed under Local System account, meaning that Standard users should be updated without any need of unlocking anything.
... View more
‎Jun 17, 2019
12:28 PM
You can't install Patch on the system where you installed "updated version", which I assume is MSI slipstreamed with a Patch. Therefore "...or install the updated version and manually patch every release" will not work. You can install base version and either deploy latest Patch yourself or let Updater do the work. You do not need "years worth of cumulative updates"
... View more
‎Jun 17, 2019
11:46 AM
Please check this thread Acrobat DC Pro will not update beyond 15.9.20069.15942
... View more
‎May 14, 2019
02:22 PM
DC Release Notes — Release Notes for Acrobat DC Products
... View more
‎May 09, 2019
04:33 PM
2 Upvotes
Latest version of AUSST 5.0.0.20 should be able to download Manifest3 files
... View more
‎Apr 29, 2019
03:07 PM
Error 1328 has different solution - restart OS and try again, or uninstall existing product and start over. Most likely reason for error 100600 is that you deployed Reader from patched AIP (Admin Install Point) If that is the case, patch cannot be applied. To confirm, please enable Updater verbose logging and provide AdobeARM.log file - send it to me directly (do not post content here) More on this, including enable logging, is here- Automatic update for Acrobat Reader DC does not update
... View more
‎Apr 10, 2019
10:13 PM
Start with this one - System Error Codes - Windows applications | Microsoft Docs There probably a dozen(s) more header files with hundreds if not thousands error codes, plus custom defined error codes, plus 3rd party error codes. Also, the same error code might have different meaning under different conditions. As others already suggested, post your error code here including all related information - steps to get the error, images if any, etc..
... View more
‎Apr 10, 2019
04:04 PM
1 Upvote
Web page likely references older versions. If you have not touched these values in Registry, they should be correct. Please enable logging, delete tLastT_Reader registry value from HKEY_CURRENT_USER\Software\Adobe\Adobe ARM\1.0\ARM, launch AdobeARM.exe from C:\Program Files (x86)\Common Files\Adobe\ARM\1.0 wait a few minutes, provide AdobeARM.log file from User\Temp folder
... View more
‎Apr 10, 2019
10:22 AM
Reason 1 - bUpdater policy is set (this is unlikely; you mentioned that manual check for updates is enabled in the application menu) Reason 2 - Reader was deployed from Admin Install Point patched by old Patch (more on this here - Acrobat DC Pro will not update beyond 15.9.20069.15942 If you enable Updater verbose logging and provide log file, I can help to identify the exact cause. Do not post file here; send it to me directly. Enable Updater verbose logging- Set iLogLevel REG_DWORD value to 1 in the registry below HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Adobe\Adobe ARM\1.0\ARM on 64 bit OS HKEY_LOCAL_MACHINE\SOFTWARE\Adobe\Adobe ARM\1.0\ARM on 32 bit OS Log file called AdobeARM.log and can be found in the User Temp folder.
... View more
‎Mar 18, 2019
10:52 AM
Hi mc900fthanna, Can you please remove log file content from the thread? It is helpful, but I'd prefer to get logs complete in the private message. Posting here makes the thread hard to read. Regarding Sources - you can read more about "Source resiliency" here - Source Resiliency Policy - Windows applications | Microsoft Docs Make sure that the installer files you copied are correct original files, and AcroPro.msi has valid digital signature. Normally Source registration managed by MSI. I cannot officially support adding Source info manually. Registry location in your case will be HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Installer\Products\68AB67CA3301FFFF7706E01180573600\SourceList\Net where 68AB67CA3301FFFF7706E01180573600 is converted ProductCode value {AC76BA86-1033-FFFF-7760-0E1108756300} Regarding Updater- after Source info is set, you can delete tLastError_Acrobat value from HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Adobe\Adobe ARM\1.0\ARM tLastT_Acrobat value from HKEY_CURRENT_USER\Software\Adobe\Adobe ARM\1.0\ARM Launch AdobeARM.exe manually from C:\Program Files (x86)\Common Files\Adobe\ARM\1.0 Wait while all AdobeARM.exe processes finished, which in case of patch installation might take up to 15 minutes (make sure Acrobat is not in use!), and check if product was updated. Send me all logs privately if you still have issues. Good luck
... View more
‎Mar 14, 2019
05:37 PM
A few notes- 1. The only registry value that is set correctly is iLogLevel. The rest can be removed. 2. Can you please remove posted log sample and instead send me full AdobeARM.log files from User\Temp folder and Windows\Temp folder? 3. The Source referenced in the error is what MSI (Microsoft Installer) Engine needs to successfully update. In relation to Acrobat, it is original base installer, namely AcroPro.msi (installer database) and Data1.cab (file archive) If you are able to update from Acrobat menu, but auto update fails running in the System context, this suggest that Source actually exists, but not available to the process running in the System context. Can you check if original Acrobat sources are cached under path that looks like this - C:\Program Files (x86)\Adobe\Acrobat 2017\Setup Files\[GUID] ? Alternatively, you can download AcroSize.exe tool from https://drive.google.com/file/d/1ag0rlOL2mZfQFmLWPpBx-GTSVVfZipaN/view?usp=sharing Run it, select "Start Acrobat" button, wait for several seconds and send me AcroSize.log file from User\Temp folder?
... View more
‎Mar 13, 2019
05:57 PM
You can find answers here - Acrobat DC Pro will not update beyond 15.9.20069.15942 And here - Introduction — DC Deployment Planning and Configuration
... View more
‎Feb 28, 2019
10:56 AM
1 Upvote
Thank you frank, There seems to be temporary issue with Updater manifests. Should be resolved in a day or two. Just a note - Acrobat X and Acrobat XI no longer supported and no more updates are available for these products. If you are on the latest versions, you should see "No updates available" from Updater when issue is resolved.
... View more
‎Feb 28, 2019
12:36 AM
Can you please locate AdobeARM.log file in the current User Temp folder and send it to me in the private message? Please do not post the file content here.
... View more
Copyright © 2025 Adobe. All rights reserved.
AdChoices