Exit
  • Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
  • 한국 커뮤니티
0

Photoshop Elements Creative Cloud Package Install

New Here ,
Apr 27, 2017 Apr 27, 2017

We had previously created an install package for Photoshop Elements 14 using the creative cloud packager to install PSE on Windows 7 machines without having to log in with a cloud account. It worked great. Now we're looking to move to windows 10 and the installer isn't working. It gets to the point early on in the install process where it shows "Gathering information". the progress bar cycles through once, then starts up again and gets about half way through and rolls back without any further messaging.

The only error code I've been able to track down is an error 1603 in the event viewer, but that doesn't give me much to go on. Any thoughts as to what may be causing this behavior?



677
Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines

correct answers 1 Correct answer

Adobe Employee , May 01, 2017 May 01, 2017

please retry installation of package by double clicking setup.exe created in parallel to .msi file.

if you still face the issue, please send me logs (zip file) using logcollector tool mentioned below to email [email address removed as per forum guidelines]

Log Collector Tool

 

Thanks,

akshita

 

Translate
Adobe Employee ,
Apr 27, 2017 Apr 27, 2017

Hi,

Please find the solution to this error at following link:

Error 1603: A fatal error occurred during Adobe Creative Suite installation

Hope this would solve your problem.

Thanks,

Arshla

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Apr 28, 2017 Apr 28, 2017

So I followed those suggestions and none of them worked.  It did direct me to the PDApp log, which gave me more information than I had before. I found 3 Error listings in the log and one Fatal listing.

The first two errors were as follows:

[ERROR] |  | ASU | DeploymentManager | DeploymentManager |  |  | 4988 | Failed to get value for conflicting processes...

[ERROR] |  | ASU | DeploymentManager | DeploymentManager |  |  | 4988 | Failed to retrieve the conflict process info.

The Fatal listing was:

[FATAL] |  | ASU | DeploymentManager | DeploymentManager |  |  | 4988 | The Bootstrapper Process return code is (-1).Stopping the installation process.

This was followed by:

[ERROR] |  | ASU | DeploymentManager | DeploymentManager |  |  | 4988 | Failed to get/verify the UpdaterCore inventory base path (C:\Program Files (x86)\Common Files\Adobe\AAMUpdaterInventory\1.0\)

And then

[WARN] |  | ASU | DeploymentManager | DeploymentManager |  |  | 4988 | sendAnalytics : Unable to find deviceId.

I found that the return code -1 means to launch in admin mode, but I was run the msi as "Run as Administrator" and was logged in as a local admin.

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Apr 28, 2017 Apr 28, 2017

I forgot to mention, this did not help me resolve the issue and the issue remains.

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Adobe Employee ,
May 01, 2017 May 01, 2017

please retry installation of package by double clicking setup.exe created in parallel to .msi file.

if you still face the issue, please send me logs (zip file) using logcollector tool mentioned below to email [email address removed as per forum guidelines]

Log Collector Tool

 

Thanks,

akshita

 

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
May 01, 2017 May 01, 2017

Looks like that worked! For some reason that wasn't working previously but it is now. Thank you very much.

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Adobe Employee ,
May 02, 2017 May 02, 2017
LATEST

glad to see the issue resolved , please close it by marking resolved .

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines