This is truly bonkers.
Here is what seems to be happening:
- Upon Launching Acrobat, it works for a handful of seconds
- Then one of the following happens:
- Acrobat does some sort of check which then triggers a call to PDApp.exe ("C:\Program Files (x86)\Common Files\Adobe\OOBE\PDApp\core\PDapp.exe") and Acrobat is terminated; OR
- Something else triggers PDApp.exe which forces Acrobat to quit
- The command line parameters/arguments for PDApp.exe: "C:\Program Files (x86)\Common Files\Adobe\OOBE\PDApp\core\PDApp.exe" --appletID=LWA_UI --appletVersion=1.0 --workflow=Provisioning_{AC76BA86-1033-F400-7760-000000000005} --locale=en_US --mtlibXMLFile="C:\Users\myuser~1\AppData\Local\Temp\oobelib_a03376"
Surely with all this information, there must be some sort of audit trail of what's happening; some sort of validation that's failing or not taking place. In my free time (hah!) I'll whip out process explorer & process monitor to see exactly whats happening during that period.
I imaged 4 machines today and accepted the EULA only on one of them. I'll see what they look like on Monday.
Ah yes the old CR bug. Good one! I had no issues opening a PDF called "CRunchy.pdf" on the one machine I accepted the EULA. I tried the same PDF on one of the other machines where I'm still getting the prompt and it opens without issue then terminates.
As for your other questions:
- That may very well be the case. I only found one installer which is a simple batch file that calls Setup.exe followed by msiexec.exe /update AcrobatUpd1010.msp /qb. (that's it literally) Acrobat *IS* in the gold image so it was installed on the reference machine, then sysprepped & captured.
- I have not yet tried running the same setup on a vanilla non-customized machine. I want to get there, but time is not on my side as we're in the midst of a deployment/rollout.