And as I mentioned, I can recreate this over and over on my test system. Spot checking some systems from other clients and it's not limited to just this single client. Using a PowerShell script to remove the scheduled task in the meantime. Adobe Acrobat Reader DC software is the free, trusted standard for viewing, printing, signing, and annotating PDFs. I had removed Acrobat DC and reinstalled Reader DC on several systems yesterday only to find they had all "upgraded" to Acrobat in the early morning hours when the scheduled task executed. APSB22-16 lists the versions of Adobe Acrobat (Reader) DC affected by the planned release. The description can be found at APSB22-16. The Adobe Reader DC offline installer for Windows and macOS is out there as follows: Down load -> Download Adobe Acrobat Reader DC Edition 2022.001.20169 The Adobe Acrobat Reader DC update for Home windows and macOS is now obtainable: Obtain -> Obtain Adobe Acrobat DC Version 2022.001. Checking for updates within Reader correctly reports the latest version is installed and doesn't cause Reader to be removed and replaced by Acrobat. GermanAdobe is releasing a security update for Adobe Acrobat (Reader) DC to version 22.001.20117 (Windows) and 22.001.20112 (Mac) on April 12, 2022. I've been able to recreate it on a test system by simply installing Reader (32-bit), checking Reader is functional and reports the correct version installed and then opening the task manager and kicking off the scheduled Adobe update task. Found in the event log where Reader had performed an update and then later where AcroPro.msi had began an installation. Has anyone noticed Reader being "updated" to Acrobat during the scheduled update task? I had a client contact me yesterday regarding Reader not working after being updated to the latest version 2022.001.20085 and found the systems now had Acrobat DC (64-bit) installed instead of the 32-bit Reader.
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |