Version 2021.005.20058. Adobe Acrobat Reader DC software is the free global standard for reliably viewing, printing, and commenting on PDF documents. And now, it's connected to the Adobe Document Cloud − making it easier than ever to work across computers and mobile devices. It's the only PDF viewer that can open and interact with all types. Adobe Acrobat Reader DC (Continuous Track) update - All languages 19.008.20081 (APSB18-40) TU-072: Critical: 23: Adobe Acrobat Reader DC (Continuous Track) update - All languages 19.010.20064 (APSB18-41) TU-072: Critical: 24: Adobe Acrobat Reader DC (Continuous Track) update - All languages 19.010.20069 (APSB19-02)(CVE-2018-19725) TU-072. Update or Complete Download. Reader DC and Acrobat DC were updated to version 21.005.20060. U pdates should become available via the internal updater or checks can be manually activated by choosing Help/Check for Updates.

Acrobat

[German]German blog reader Martin E. alerted me last night to a problem with yesterday’s Adobe Reader/Acrobat DC security update. There are massive installation problems on Windows with the Adobe Reader /Acrobat DC security update dated February 9, 2021 (the setup ends with Error 1722). It probably affects systems when no user is logged in to the system, as I saw during a quick research. Root cause is a new UWP app from Adobe, but there is a workaround.

Advertising

Yesterday I had reported about Adobe’s security update for Reader/Acrobat DC in the German blog post Adobe Reader/Acrobat: Wichtiges Sicherheitsupdate verfügbar (9.2.2021). Adobe has published a Security Bulletin APSB21-09 with details. Since I don’t use the products, I wasn’t able to test anything.

Users reports install error 1722

German blog reader Martin E. contacted me yesterday by mail, reporting serious install issues with that update (thanks for that). He wrote:

We downloaded here (Continous Track).

And here is the “MUI” MSP:

This “crashed” in our SYSTEM without a logged in user.

In other words, Martin got an installation error on his systems when installing the window update for Adobe Reader, which ends in a crash. The problem only occurs when no user is logged in. Martin wrote in another mail that he searched the internet for:

RdrServicesUpdater.exe, command: 21.001.20135 20.013.20074.0

Advertising
Acrobat

but then came across the forum posts linked here in the article.

German blog reader Thomas directed me within this comment to a discussion within German forum administrator.de. The update fails during installation with an error 1722:

Product: Adobe Acrobat Reader DC MUI — Error 1722.There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor. Action InstallWebResources, location: C:Program Files (x86)AdobeAcrobat Reader DCReaderAcroCEFRdrServicesUpdater.exe, command: 21.001.20135 20.013.20074.0
Product: Adobe Acrobat Reader DC MUI — Configuration failed.

The user tried to uninstall the previous version and then reinstall the package, but ends up with a DLL error:

C:Program Files (x86)AdobeAcrobat Reader DCEslAiodLite.dll

because the module is not found. Meanwhile, in the Adobe Community, there is this thread where more users confirm the bug. Blog reader Thomas E. emailed me this morning and referred to the post Error 1722 after installing Adobe Reader DC Update… – Adobe Support Community – 11821190, where somebody wrote:

Error 1722 after installing Adobe Reader DC Update 21.001.20135

Trying to distribute the Adobe Reader DC Update 21.001.20135 to a larger group of machines,

Adobe Acrobat Reader Dc Update Failed

by means of SCCM (but also manually donwloaded and installed)

I receive the following error message:

“Product: Adobe Acrobat Reader DC MUI — Error 1722.There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor. Action InstallWebResources, location: C:Program Files (x86)AdobeAcrobat Reader DCReaderAcroCEFRdrServicesUpdater.exe, command: 21.001.20135 20.013.20074.0”

These problems are also confirmed by third parties there. One user writes that the installer of the Adobe Acrobat Reader 2020 MUI update works for him. In a post, another user confirms that it affects both Acrobat Reader and Acrobat DC Pro on Windows.

Adobe Acrobat Reader Dc Update

Confirmed that this issue is not limited to Reader and occurs on Acrobat DC Pro using this new update.
Tested on:
– Windows 10 1909 and 20H2 Enterprise, both existing and clean installs of the operating system
– Visual C++ 2013 versions 12.0.30501, 12.0.40060, and 12.0.40664, including no version of Visual C++ 2013 previously installed
– Existing and clean installs of Acrobat DC Pro
– Utilizing SYSTEM or administrator accounts

Adobe Acrobat Reader Dc Update For Mac Free

As others have mentioned, machines with at least one interactive logon will install the update successfully either the first or second installation attempt.

The help posted by Adobe in the forums for error 1722 is not very helpful, as users write. There seems to be only one workaround to circumvent the problem: Make sure that a user is logged in to the client when the update is rolled out (e.g. via WSUS or SCCM).

There is a root cause and a workaround: omit UWP app

Martin E. has send me a 3rd mail outlining the root case and a workaround, a user has postet within this Adobe forum thread:

After an analysis of the error message, update install log and msi/mst, the following command line worked for us (workaround): msiexec / p “AcroRdrDCUpd2100120135_MUI.msp” INSTALLUWPAPP=NO / qb-!

Adobe Acrobat Reader Dc Update

This will not install the UWP App Adobe Acrobat Notification Client where the error seems to occur.

More information about the UWP App Adobe Acrobat Notification Client can be found here:

Not sure, but it looks like that an internet connection is needed for this part to install. In our environment only ‘normal’ users have an internet connection, and installation of the update is not done via a normal user account but via the System account (SCCM).

So the new Adobe Acrobat Notification Client, shipped als a UWP app is the root cause for the error. Use the install command:

msiexec / p “AcroRdrDCUpd2100120135_MUI.msp” INSTALLUWPAPP=NO / qb-! DISABLE_NOTIFICATIONS=1

to exclude the UWP app Adobe Acrobat Notification Client from installation should avoid the error 1722.

Cookies helps to fund this blog: Cookie settings
Advertising

Although web browsers like Chrome, Firefox and Edge have an integrated PDF reader, probably one of the first applications one wants to have after unboxing a Windows device and its initial usage is a dedicated PDF reader. Within the Liquit Setup Store we provide different PDF readers. Out of these Adobe Acrobat Reader DC, Foxit Reader, PDF-XChange Editor and SumatraPDF are the most popular ones. For this blog I’ve picked the most popular one: Adobe Acrobat Reader DC.

As an organization when you want to deploy Acrobat Reader DC using Liquit Workspace, please be advised to read this Adobe FAQ first. Let’s pick two topics from the ‘Enterprise deployment’ section and discuss these along the way:
– What’s the difference between Continuous and Classic tracks?
– What is the Acrobat Reader DC MUI version?
First let’s see what the Setup Store contains when we search for ‘reader dc’:

That lists nine setups and updates. The reason why you only see ‘Dutch’, ‘French’ and ‘English’ versions for ‘Reader DC’ in this list is because my Liquit Setup Store connector is configured to only show the setups for these languages when multiple language versions are available in the store:

So if you’re from Finland, check the ‘Finish’ checkbox, uncheck ‘Dutch’ and ‘French’ and then the Finnish version for Adobe Acrobat Reader DC will show up in the list too. Setups for languages which have been deselected will not show anymore.

If you want to use the ‘Classic Track’ for Adobe Acrobat Reader DC, be aware that that track is only available when you opt for the MUI version.

Adobe Acrobat Reader MUI is Adobe’s Multilingual User Interface version of Reader, which lets you roll out Acrobat Reader using a single installation. Local users can then select a user interface language, let Adobe Reader handle this automatically based on your Windows locale or it can be set by group policies. This setup is labeled as ‘Reader DC (MUI)’ in the Setup Store.

Let’s create a managed package for the English version of Adobe Acrobat Reader DC in Liquit Workspace using the Setup Store connector:

  • Click Manage, Connector, then select the Setup Store connector
  • Click Resources and search for ‘reader dc’
  • Select ‘Reader DC (English)‘
  • Click ‘Create Package’
  • In the Details screen opt for ‘Adobe Reader DC (English)’ for the package name, click ‘Next’
  • In the Customize screen click the ‘Configure’ option.
    This will show what we call a ‘Configuration Wizard’. For MSI setups we provided these wizards in Liquit Release & Patch, both when using the Setup Store connector and Liquit Setup Commander.
    With this wizard you can configure Acrobat Reader using enterprise best practice settings. We already preconfigured this wizard using settings which are typical for enterprise deployment.
    Click ‘Next‘ after you’re done with the configuration.
  • In the Entitlements screen add the users you want to assign this package to, click ‘Next‘
  • In the Summary screen uncheck the ‘Modify package after creation’
  • Click ‘Finish’

Now you’re ready to deploy Acrobat Reader DC.
Updating Acrobat Reader DC needs an additional managed package though. Because Adobe uses what are called ‘MSP’-files (Microsoft Windows Installer Patch files) to update Adobe Reader DC installations. That’s why MSP’s are flagged as ‘Update’ in the Type column:

Creating a managed package for the corresponding update:

Acrobat
  • When you want to update Acrobat Reader DC MUI with continuous track updates you need the ‘Reader DC update – Multilingual (MUI) installer‘ update
  • When you want to update Acrobat Reader Reader DC MUI with classic track updates you need the ‘Reader DC Classic Track update – Multilingual (MUI)‘ update.
  • When you want to update Acrobat Reader Reader DC with continuous track updates you need the ‘Reader DC update – All languages‘ update which is what I’m going to use for my second managed package.

Using the Setup Store connector:

  • Click Manage, Connector, then select the Setup Store connector
  • Click Resources and search for ‘reader dc’
  • Select ‘ Reader DC update – All languages‘
  • Click ‘Create Package’
  • In the Details screen opt for ‘Adobe Reader DC update – All languages’ for the package name, click ‘Next’
  • In the Customize screen the ‘Configure’ option is greyed out, because there’s nothing to configure when we’re dealing with a MSP file.
  • In the Entitlements screen add the users you want to assign this package to, click ‘Next‘
  • In the Summary screen uncheck the ‘Modify package after creation’ checkbox
  • Click ‘Finish’

Adobe Acrobat Reader Dc Update Download

There are a few things can you do additionally with these packages. Since you probably want to deploy Adobe Acrobat Reader DC on every device, you can set the publish option within the entitlement to ‘Forced’. In my example this means this package will be installed in the Workspace of ‘Everyone’:

Adobe Acrobat Reader Dc Update For Mac

The other option you can do within the ‘Adobe Reader DC update – All languages’ package is to insert an additional action set ‘Prerequisites’. This action set has one ‘Install package’ action which checks for the installation of ‘Adobe Reader DC (English)’.

Adobe Acrobat Reader Dc Updater

That creates a dependency on ‘Adobe Reader DC update – All languages’ for the ‘Adobe Reader DC (English)’ package:

⇐ ⇐ Adobe Acrobat Reader Dc Update
⇒ ⇒ Bellsouth 1008 Walkie Talkies Manual