I have to ask for verbose logging from Updater. Please find below instructions- To 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 Next- Make sure Adobe Reader is not running Rename existing AdobeARM.log file in the User Temp folder. Delete  tLastT_Reader Registry value in HKEY_CURRENT_USER\SOFTWARE\Adobe\Adobe ARM\1.0\ARM delete any tLastT_Error (could be slightly different name) Registry value in HKEY_CURRENT_USER\SOFTWARE\Adobe\Adobe ARM\1.0\ARM Launch AdobeARM.exe from C:\Program Files (x86)\Common Files\Adobe\ARM\1.0 In a few minutes collect and send me latest AdobeARM.log file from User Temp folder ... View more

iLogLevel loks fine. I can't explain missing Adobe key in HKCU registry, it looks strange. Did you try to launch AdobeARM.exe? Make sure AdobeARM.exe is not running, try to launch it and check for AdobeARM.log again. If log is not there, try system wide search. ... View more

Manual mode is when you select "Check for updates" from application Help menu. If you see popup "Update is available" in auto mode, most likely Updater cannot access Acrobat Update Service. One way to find out is to provide Updater verbose log file. To 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 Delete  tLastT_Reader Registry value in 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 until you see popup Collect and send me in the private message AdobeARM.log file from current User Temp folder. ... View more

Can you please specify what is the exact issue you are running into? In manual mode Updater will trigger UAC. In auto mode Updater should not. ... View more

Please ignore error code 259, it simply shows that no more products have been found registered with Updater. ... View more

I can take a look at a new verbose log if it is available (please try to provide it in the private message), but it looks like the issue on your system cannot be resolved over posts in this forum. A few other points- Error 111500 indicates failure well before Copy File operation, that is why you might not seeing C:\ProgramData\Adobe\.. folder being created Windows Installer Service (MSI) has nothing to do with the issue If you have any antivirus running or backup software, can you disable it temporarily while manually checking for updates?   ... View more

Hi, The issue is in Copy File operation, which in your log file referenced by the line below- [2023-07-25 22:24:39:0452] Copy Manifest C:\Users\ADMIN_ACCOUNT_NAME\AppData\Local\Adobe\ARM\Acrobat_23.003.20244\AcrobatDCx64Manifest3.msi Unfortunately the log line is cut short; it should say something like [2023-07-25 22:24:39:0452] Copy Manifest C:\Users\ADMIN_ACCOUNT_NAME\AppData\Local\Adobe\ARM\Acrobat_23.003.20244\AcrobatDCx64Manifest3.msi failed [error code] In the normal case TransferProductManifest  would show something like [2023-07-28 23:05:29:0590] TransferProductManifest... [2023-07-28 23:05:29:0592] Transfered: C:\ProgramData\Adobe\ARM\Acrobat_23.003.20244\AcrobatDCx64Manifest3.msi I would bet on incorrect permissions on C:\ProgramData\Adobe\ARM\Acrobat_23.003.20244 folder, but it could be something else. The best course of action for you is to uninstall Reader 64 bit and install again from Adobe.com. You can also try to delete C:\ProgramData\Adobe\ARM folder before reinstalling Reader 64 bit. If you still face the same issue, please provide me with verbose log again in the private message. ... View more

Please check this topic for instructions and provide verbose Updater log file in the private message. Acrobat Pro DC not auto-updating - Adobe Support Community - 13960091   I can't speak for CC updates. Acrobat Updater should be able to update Admin and Standard Users by default. If you customize Updater settings, including anything related to Acrobat Update Service, you might break the functionality. It is not uncommon for enterprises to make changes on the system to disable services or disable Updater setting for a number of business reasons in which case it is Admin responsibility to manage updates without built in Updater.   ... View more

The first line in the log does not show what triggered MSI, it just shows that msiexec.exe process was launched by Windows Installer Service ��===Verboseloggingstarted:25/07/20235:57:42Buildtype:SHIPUNICODE5.00.10011.00Callingprocess:C:\WINDOWS\SysWOW64\msiexec.exe=== I would check Windows event log at the time you see this UI again. Please google for instructions. ... View more

Acrobat has it's own Updater, different from CC. For auto-update mode it uses Acrobat Update Service for elevation and installs updates in Local System context. No need for Admin credentials. In manual mode (Check for updates menu) Updater will use different process, which will require Admin credentials in UAC prompt for Standard users. Just don't cutomize anything related to updates in Acrobat installation and you are all set. ... View more

Acrobat Updater can elevate itself for update installation for Admin and Standard users.   ... View more

Something triggers patch installation on your system, but this is not Updater. There is no reason for changes in Task or Service, or chaniging automatic update preferences; they have nothing to do with the issue. You'd have to investigate differently. One option is to enable MSI verbose logging (google if you don't know how) and check latest MSIxxxx.log file in the User Temp folder right when you see the dialog. At the very beginning of the log you might find what process triggered MSI transaction.   ... View more

By default Acrobat can update itself running in Admin or Standard user context. Did you experienced any issues? ... View more

It might be due to bUpdater registry value set to 0 in HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Policies\Adobe\Adobe Acrobat\DC\FeatureLockDown Is this PC a part of organization? If yes, consult with system admin ... View more

By default Acrobat Pro is set to auto update including for Standard users. Do not customize any update related features for deployment and you are all set. Just one note - if you use Admin Install Point for deployment, do not apply any patch to it. ... View more

goldenmom5 Please check my reply in Reader forum, where you posted your question originally- Update Failed Error 111100 - Adobe Support Community - 13916169 ... View more

Error 111100 means - "Updater could not initialize a product for update" Most likely when your Windows System was upgraded, Reader registration with the System got broken. The easiest fix is to uninstall Reader and reinstall latest version from Adobe.com ... View more

It is safe to delete all these files and subfolders under ..\ARM folder in your image. Uninstalling Reader will not remove them; they are downloaded by Updater and Windows Installer Service is not aware of these files. The main question remains why they are not removed by Updater. Unless you changed default full auto Updater mode, it is possible that something prevents Updater to proceed with installation after files are downloaded. If you do not have highly customized Reader installation, delete all the files (under ARM folder), uninstall Reader and install latest from Adobe.com ... View more

Removed ... View more

Try to run Repair Installation from Help menu on the system where you changed Mode value to 3 manually. If after repair Mode value is still 3, you should be fine just to update the value on all systems. If the value is changed back to 0, you have a few choices- 1. Uninstall Acrobat and install without this customization. 2. Push Mode value every few days to all systems. You should not "force a newer version on top as a new installation". The only way to overwrite installed Acrobat is to create new version using AIP (Admin Install Point), update it with a newest patch and deploy, If you do that, you will not be able to simply update this deployed version with next patch(s); you will have to create new AIP each time new patch is released and deploy it on top of existing Acrobat. Those are MSI basics, not Adobe specific. ... View more

No problem. The registry you provided shows that auto update is not enabled for Acrobat. Here is what Acrobat sections looks like: [HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Adobe\Adobe ARM\Legacy\Acrobat\{AC76BA86-1033-FF00-7760-BC15014EA700}] "Check"=dword:00000048 "Mode"=dword:00000000 "TrackName"="DC" "ManifestURL_3"="https://armmf.adobe.com/arm-manifests/win/AcrobatDCx64Manifest3.msi"   As you can see Mode value is set to 0 instead of 3 I can't tell you how it happenned, most likely someone or something changed this value before deployment or post deployment. You can probably find a way to update this value using appropriate tools on all systems you want. However, if you deployed Acrobat from customised installer, where Mode value has been changed, most likely it will be reset to customised value 0 because any time MSI transaction is executed (during Update for example) original transform created by custimization gets applied. ... View more

Thank you. Mode value looks correct. I have to ask - is this registry export from the same system from where you provided log file initially? The reason I am asking is that you provided verbose log, which is not default. To enable verbose logging you'd have to set iLogLevel registry value. However, in the registry you provided iLogLevel is not set correctly, it shows as "Set iLogLevel"=dword:00000001 This makes me think that log and registry are from different systems. Can you please double check this?  Also, after setting iLogLevel correctly on this system perform a few steps: 1. delete tLastT_Acrobat registry value from HKEY_CURRENT_USER\SOFTWARE\Adobe\Adobe ARM\1.0\ARM 2. launch AdobeARM.exe from C:\Program Files (x86)\Common Files\Adobe\ARM\1.0 3. Wait a few minutes, collect and send me AdobeARM.log file from User Temp folder You can send it to me in the private message; the thread is becoming unreadable. ... View more

Please export registry below and send me reg file in the private message. You might need to change file extension. HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Adobe\Adobe ARM ... View more

Registry path depends on a product. In your case it is- HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Adobe\Adobe ARM\Legacy\Acrobat\{AC76BA86-1033-FF00-7760-BC15014EA700} Registry value is Mode. Please make sure it is set to 3 If it is not set to 3, you will need to find out how it happenned; by default Acrobat installer sets it to 3 ... View more

This line in the log shows why [2023-04-27 08:14:52:0831] Automatic updates preference is off, code: 120200   ... View more

Santosh, I sent you instructions in reply to your private message. ... View more

Peter, latest updates were initially released to approximately 35% of the available users and currently enabled for all 100% of the available users, but check for updates is on 3 days interval. Wait a few days and you should see all systems updated. ... View more

One way to find out why some of the products are not updated is to provide Updater verbose log file. To 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 Repeat "delete the tLastT_Reader Registry value in HKCU and start the task manually" on the system where Reader is not updated. Collect and send me in the private message AdobeARM.log file from current User Temp folder. ... View more

I am not aware of any online documentation for these specific properties. Also, I double checked - looks like DISABLE_FIU_CHECK has been first introduced in 2015 with Adobe Reader DC base version 15.007.20033 ... View more