
Please contact the ITS Service Desk should you continue to experience problems with the software.
If the above steps do not work, please remove and reinstall the Adobe Acrobat Pro application from your computer. Attempt to open the Adobe Pro Application and wait for the installer to complete. Contact your support personnel or package vendor. It is OK to allow this change to be made. A program run as part of the setup did not finish as expected. Note: You may receive a prompt asking for permission to make this change. Go to the following location: C:\Program Files (x86)\Common Files\Adobe. Upon launching the program the installer may come up and present the above error message, and then crash the program. It is possible that the installation of the Adobe software or an update of the Adobe software did not complete fully or successfully. Adobe Acrobat Reader DC Update 21.001.20135 Failing to update Adobe Acrobat Reader DC Update 21.001.20135 Failing to update. I've set the detection method to look for the latest version number, but I don't think this is a detection based problem, Intune tends to be very clear when that's the case.When I try and open Adobe Acrobat I get an error message that states the following:Įrror 28000: Installation of Acrobat Licensing Module has failed. I'm not really sure where to go with this one. That error code keeps bringing me back to articles around Windows Update failures, so not really much help. Enterprise organizations will user either the Classic or Continuous track. Most end users will install the Continuous track provided from the Reader Download Center. The problem is, Intune is reporting that the install failed with a "Fatal error during installation (0x80070643)" The Acrobat DC product family introduces two tracks for both Acrobat and Reader which are essentially different products: Classic and Continuous. The installer updates the old version and, at some point during the process, updates itself to the very latest version. The new customised version is actually two major versions out of date (why? because if I use the latest version I can't test the auto-update feature immediately). I packaged the MSI and all the associated files as a Win32 App, set it up in Intune with the transformation files referenced in the installer string and.it works great. I don't believe that current deployment enables auto update. We already have a version of Reader installed from the end of last year.
Locate the option that says Enable Protected Mode at startup and disable it. Then go to Preferences, and select Security (Enhanced).
One of the flags I ticked was to allow the app to update itself. Launch Adobe Acrobat Reader, and click on the Edit menu. So I used the Adobe Customisation tool to create a deployment of Adobe Reader DC (the free one).