![]() There's a workaround for this issue that i found on the fly. ![]() Basically it puts a white or black rectangular horizontal line about 1 - 2" thick across the whole screen on top (sometimes at the bottom) covering the tool bar and making it inaccessible. It happens in file explore, web broswer and adobe from what i noticed. I work for a firm that uses lenovo laptops and this happens to a lot of users. Deleting or renaming tLastT_Acrobat will force the updater to actually install the current version on it's next run.I believe this might have something to do with Lenovo, or integrated graphics with multi monitors. This timestamp is recorded under the registry key HKEY_CURRENT_USER\SOFTWARE\Adobe\Adobe ARM\1.0\ARM in tLastT_Acrobat. Updates have been found and successfully installed.No updates are found in the manifest for system’s current product configuration.The current version would be 23.006.20320 (which contains an important 0-day RCE bugfix).īy default, the Updater performs an update check every 3 days and records the year and day of the last successful check in two cases: The update process stops after Last check for updates not expired is determined, despite version 23.003.20284 being out of date. Last check for updates not expired, code: 120300 In my case it contained the following information about the last update run: Adobe ARM 1.824.460.1052 logging started. C:\Users\.\AppData\Local\Temp\AdobeARM.log) The updater's log file is located at %temp%\AdobeARM.log (e.g. How to troublshoot and force an early update Therefore the update should be installed after waiting for a few days. The auto updater immediately stops if not at least 3 days have passed since the last "full" updater run. This guide for the Acrobat-Reader Updater was a helpful resource for this. I think I've figured out what's going on. I was also wondering, why the auto updater did not update me to the latest version, while a manual update check would. I'll entertain and seek to prove that theory. Perhaps AdobeARM.exe needs local admin to perform its update task. Has anyone here ever encountered this phenomenon, and what did you do to solve it?Īfterthought: As I write this, it occurs that perhaps the problem is the scheduled task running under the user's context (INTERACTIVE) - About 90% of users don't have local admin rights. They think we should be trying harder to find the reason why 90% just don't update - I can find no evidence of literature for such, nothing to point me in a valid direction. Very little work, but some parties still complain it's not fully zero-touch, and the app has its own zero-touch auto-updater. I get around this by using PDQ Deploy to push out the new version - Which requires me to download the new version and release the deployment. Most of what's true for one machine is the same as the next. Really? We have SOEs applied and a high level of software and hardware standardisation. People have told me "we must have something on our network" blocking it. I could accept this better if 10% of my machines didn't work. In this scenario, they definitely have the old version, and I know there's a new version - All the task does is run AdobeARM.exe, which it does successfully, and yet. If I remote onto a machine with a previous version and an update has just released, I can manually run the task, and it works exactly as expected - Within minutes, the new version is evident upon running Reader.įor the other 90% (rough figures), this inexplicably does nothing. It runs the task under the user's context (INTERACTIVE), and executes "C:\Program Files (x86)\Common Files\Adobe\ARM\1.0\AdobeARM.exe" at user logon, and at 11am each day.įor 10% of my machines, this works just fine. It does this by creating a Windows scheduled task upon installation, called "Adobe Acrobat Update Task". 1000 computer network are not automatically updating Acrobat Reader (free).ĪFAIK, Adobe Reader automatically downloads and installs updates in a truly seamless manner - In theory, a zero-touch approach for administrators.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |