Adobe Acrobat Reader 24.005.20307 Install Issue

[msysadmin]

The latest update for Adobe Reader DC was released yesterday. This morning, our technicians started encountering issues while imaging new workstations, specifically during the "Install Application" step, which attempts to install version 24.005.20307. To resolve the problem, I modified the step to install the previous version (24.004.20272), which allowed them to get back on track. Is anyone else experiencing this issue?

Code Select Expand

MSI (s) (9C:78) [15:06:23:705]: Original patch ==> C:\Program Files\Common Files\Adobe\Acrobat\Setup\{AC76BA86-1033-1033-7760-BC15014EA700}\AcroRdrDCx64Upd2400520307.msp
MSI (s) (9C:78) [15:06:23:705]: Patch we're running from ==> C:\WINDOWS\Installer\6723.msp
MSI (s) (9C:78) [15:06:23:705]: Note: 1: 2203 2: C:\WINDOWS\Installer\6723.msp 3: -2147286960
DEBUG: Error 2203:  Database: C:\WINDOWS\Installer\6723.msp. Cannot open database file. System error -2147286960
1: 2203 2: C:\WINDOWS\Installer\6723.msp 3: -2147286960
MSI (s) (9C:78) [15:06:23:708]: Note: 1: 1708
MSI (s) (9C:78) [15:06:23:708]: Product: Adobe Acrobat DC (64-bit) -- Installation failed.
MSI (s) (9C:78) [15:06:23:709]: Windows Installer installed the product. Product Name: Adobe Acrobat DC (64-bit). Product Version: 21.001.20135. Product Language: 1033. Manufacturer: Adobe. Installation success or error status: 1636.
MSI (s) (9C:78) [15:06:23:711]: Attempting to delete file C:\WINDOWS\Installer\6723.msp
MSI (s) (9C:78) [15:06:23:713]: MainEngineThread is returning 1636



[Michael (Patch My PC)]

Hey msysadmin,

I haven't seen any other reports of this.

This is only happening during OSD? Does the installation work from an already built machine?

I'll give the OSD a try in my lab.

[msysadmin]

Hi Michael, I encountered a different MSI error when a production client attempted to install or update to the latest version from Software Center.

Code Select Expand

Property(S): CURRENTDIRECTORY = C:\Program Files\Common Files\Adobe\Acrobat\Setup\{AC76BA86-1033-1033-7760-BC15014EA700}
Property(S): UPDATE_MODE = 0
Property(S): PackagecodeChanging = 1
Property(S): ProductState = -1
MSI (s) (BC:E0) [16:40:40:221]: Product: Adobe Acrobat (64-bit) - Update 'Adobe Acrobat Reader (24.005.20307)' could not be installed. Error code 1603. Additional information is available in the log file C:\windows\ccm\logs\PatchMyPCInstallLogs\test-prod-AcroRdrDCx642400520307_en_US.exe.log.
MSI (s) (BC:E0) [16:40:40:221]: Windows Installer installed an update. Product Name: Adobe Acrobat (64-bit). Product Version: 24.005.20307. Product Language: 1033. Manufacturer: Adobe. Update Name: Adobe Acrobat Reader (24.005.20307). Installation success or error status: 1603.
MSI (s) (BC:E0) [16:40:40:222]: Note: 1: 1708
MSI (s) (BC:E0) [16:40:40:222]: Product: Adobe Acrobat (64-bit) -- Installation operation failed.
MSI (s) (BC:E0) [16:40:40:222]: Windows Installer installed the product. Product Name: Adobe Acrobat (64-bit). Product Version: 24.005.20307. Product Language: 1033. Manufacturer: Adobe. Installation success or error status: 1603.
MSI (s) (BC:E0) [16:40:40:251]: Attempting to delete file C:\WINDOWS\Installer\21d14.msp
MSI (s) (BC:E0) [16:40:40:292]: Deferring clean up of packages/files, if any exist
MSI (s) (BC:E0) [16:40:40:292]: Attempting to delete file C:\WINDOWS\Installer\21d14.msp
MSI (s) (BC:E0) [16:40:40:292]: Unable to delete the file outside of the engine. LastError = 2
MSI (s) (BC:E0) [16:40:40:292]: MainEngineThread is returning 1603

I was only able to install the program successfully after manually uninstalling the previous version.

[Michael (Patch My PC)]

I got the same error during OSD installing on a Win11 24H2. Testing with a 23H2 machine incase that makes a difference.

I do a fresh install of the app on a machine. Testing an upgrade right now.

[Michael (Patch My PC)]

Hey msysadmin,

I got a suggestion from our App Team that worked in my Lab.

With the 'Deployment Type' settings of the App, on the 'Programs' tab, enable the option:

'Run installation and uninstall program as 32-bit process on 64-bit clients'

[nawo69]

Hi

Im seeing similar issue on machines yet if i login to one and goto Software Center and click retry it installs fine.

Do I need to enable 'Run installation and uninstall program as 32-bit process on 64-bit clients' or is this a another issue?

Deployment failed,Action failed,0x664 (1636)
This update package could not be opened. Contact the application vendor to verify that this is a valid Windows Installer update package.

We had just deployed the previous version on Friday and that version had installed fine without this error

[msysadmin]

Hey msysadmin,

I got a suggestion from our App Team that worked in my Lab.

With the 'Deployment Type' settings of the App, on the 'Programs' tab, enable the option:

'Run installation and uninstall program as 32-bit process on 64-bit clients'

I tested this solution this morning, and it seems to have resolved the issue during OSD.

[nawo69]

Yeah thanks, I changed it earlier too and it seems to be fixing it

[Michael (Patch My PC)]

Glad that is working for you both.

Not sure why this fixes it, best guess is Adobe changed something within the installer regarding Environment Variables that aren't resolving correctly during OSD for some reason.

[iamr00t]

I have been seeing the same issue with this new version. I just got the rest of it dialed in correctly to deploy as an upgradable app, then this happens. So, is the change to the Deployment Type Progam going to stick with the latest app version, or will we need to go in each time the product updates and change this?

[Michael (Patch My PC)]

I have been seeing the same issue with this new version. I just got the rest of it dialed in correctly to deploy as an upgradable app, then this happens. So, is the change to the Deployment Type Progam going to stick with the latest app version, or will we need to go in each time the product updates and change this?

Looks like the setting does not carry over to the new version as the newest version that was just published got the same problem.

[msysadmin]

I can confirm that this issue has reappeared with the latest version (24.005.20320) during OSD.

[hidadsoup]

Same problem here. The publisher doesn't have an option to toggle that setting on, so the application reverts back when the catalog is updated with a new version. Given the impact of this problem, how difficult would it be to either 1. have the publisher automatically configure that setting or 2. provide us the option to toggle the setting on in the publisher?

[Andrew Jimenez (Patch My PC)]

We are planning on adding this option to the Publisher, and tracking if this setting needs to be set as well. I don't have a timeline for adding that feature yet, however.

[cyoung]

+1 for having the box ticked by default to run as a 32-bit process if Adobe continues releasing versions like this.  It would help us a lot.  Thank you.