Skip to main content
Participant
March 29, 2014
Answered

Setup was unable to initialize, please download the Adobe Support Advisor to detect the problem

  • March 29, 2014
  • 2 replies
  • 1706 views

Setup was unable to initialize, please download the AdobeSupport Advisor to detect the problem

:

What should I do?


This topic has been closed for replies.
Correct answer johnrakker

I had the exact same problem (Dutch version)

I searched wide and low.

I have applied expletives.

My neighbor knows much about computers and English. It took him hours, he found:

Remove Install and OOSE directories from c:\program files (x86)\common files\adobe

the installer log is found in the %temp% location (pdapp.log) and gave little info.

Info I found at

Installer failed to initialize. {CS6}  Thanks to Johan Smohan!

My neighbor has this to say for the developers at Adobe: when you make debugging logs and something isn't found, you shall explain why and what (difference between access rights and not existing!). You Always do this, bunch of lazy.

More importantly, the folks up in management who want to keep the GUI simple: if something fails you may as well say what it was. I end up at your site anyway. Imagine killing a product (as indicated in the OP) for a brandnew downloaded version. How could you?

It is clear that windows doesn't allow you to remove/access a directory in common files if it gets the wrong rights setting. If so, you do not leave the poor user (who paid good money) in such dire straits. Very much not so good.Sorry.

Now: please add the 'verify the common files directory' to your installation steps help stuff, okay?

2 replies

johnrakker
johnrakkerCorrect answer
Participant
March 16, 2016

I had the exact same problem (Dutch version)

I searched wide and low.

I have applied expletives.

My neighbor knows much about computers and English. It took him hours, he found:

Remove Install and OOSE directories from c:\program files (x86)\common files\adobe

the installer log is found in the %temp% location (pdapp.log) and gave little info.

Info I found at

Installer failed to initialize. {CS6}  Thanks to Johan Smohan!

My neighbor has this to say for the developers at Adobe: when you make debugging logs and something isn't found, you shall explain why and what (difference between access rights and not existing!). You Always do this, bunch of lazy.

More importantly, the folks up in management who want to keep the GUI simple: if something fails you may as well say what it was. I end up at your site anyway. Imagine killing a product (as indicated in the OP) for a brandnew downloaded version. How could you?

It is clear that windows doesn't allow you to remove/access a directory in common files if it gets the wrong rights setting. If so, you do not leave the poor user (who paid good money) in such dire straits. Very much not so good.Sorry.

Now: please add the 'verify the common files directory' to your installation steps help stuff, okay?

kglad
Community Expert
Community Expert
March 29, 2014

check your install logs, http://helpx.adobe.com/x-productkb/global/installation-launch-log-errors-creative.html

if you need more help than that, what os, what adobe program, what are you clicking to start 'setup'?

Participant
March 26, 2020

THATS WHERE THE WHOLE PROBLEM STARTED ME BEING INVALID AND 1 EYE SIGHTED AND LIVE SINCE YEAR IN WESTERN CAPE AREA ALONE