Adobe Reader DC failing to install VIA TS

[JoeG NHS]

Thread necro because this issue cropped back up again today.  Acrobat Reader has been working fine since 2022, but had this same problem again today.  I don't suppose PMPC had any luck with what you were trying or if you would reconsider my idea above of extracting the contents of the Adobe .exe first before packaging the application (which is what we have to do manually for the workaround when this happens).

I can confirm we are also seeing this issue, we are using the 32bit adobe reader within our OSD Task Sequence. When I manually run the installer within the task sequence, it does extract and install fine all within the Task Sequence environment. But fails with error 150201 when trying to do it via the PMPC scriptrunner.

This is on windows 11 23H2 (Nov 2024 Eng Int build)

Failing in OSD TS



Successful install from previous version of adobe last week

[Andrew Jimenez (Patch My PC)]

We've actually found a workaround on this and have been trying to dissect why this specific behavior is occurring over the last week. The workaround is to set the "Run installation and uninstall program as 32-bit processes on 64-bit clients." on the deployment type for Adobe.

What we are planning on doing, since this issue keeps reoccurring, is to add this option into the Publisher directly, and have the Publisher set this flag automatically for applications that run into this issue.

[JoeG NHS]

We've actually found a workaround on this and have been trying to dissect why this specific behavior is occurring over the last week. The workaround is to set the "Run installation and uninstall program as 32-bit processes on 64-bit clients." on the deployment type for Adobe.

What we are planning on doing, since this issue keeps reoccurring, is to add this option into the Publisher directly, and have the Publisher set this flag automatically for applications that run into this issue.

Thank you, yes this would be the ideal resolve as from reading other posts, that option if you set it manually for the Application in SCCM (vs in PMPC Publishing app which you cant do atm), will not persist on the next app version bump, and with Adobe, thats almost every week!

I think we all appriciate that Adobe software is very hard to predict what changes or things break each time a new version is released.

Your addition to the publisher would be very much appreciated, keep up the good work

[will.locke]

We've actually found a workaround on this and have been trying to dissect why this specific behavior is occurring over the last week. The workaround is to set the "Run installation and uninstall program as 32-bit processes on 64-bit clients." on the deployment type for Adobe.

What we are planning on doing, since this issue keeps reoccurring, is to add this option into the Publisher directly, and have the Publisher set this flag automatically for applications that run into this issue.

Setting the indicated setting did fix the issue for us as well.  So a little different than the original thread.  But thank you for the response and the updated for how PMPC will make a more permanent fix.  Appreciate the support.