Skip to main content
A
Anonymous
August 21, 2018
Answered

Failed install w/ CCP

  • August 21, 2018
  • 2 replies
  • 530 views

Can't believe we are back to this. Dealing with the installation of Adobe products has proven to be one of the most annoying part of using the software. It's great after the install.

Deployment package created using CCP. Testing sees most of the products installed just to have the entire package un-installed.

Would it be to much to simply roll back then skip ONLY the failing app instead of removing the ENTIRE suite?!?!?!?

We have run the clean tool and it still fails to complete.

That being said... the clean tool simply doesn't seem to do what is use to do. Lingering files, folders, etc would be deleted on running it... that is not happening now. We found files and folders left by the uninstall process that were ignored by the tool.

Here is the log for anyone that can point out whats wrong this time: https://jpst.it/1mvRf

    This topic has been closed for replies.
    Correct answer Albrecht Volk

    Your installation appears to be failing because system requirements were not met (see Creative Cloud download and install errors ). What is your operating system and which apps have been included in your package?

    2 replies

    A
    Adobe Employee
    Albrecht VolkCorrect answer
    Adobe Employee
    August 22, 2018

    Your installation appears to be failing because system requirements were not met (see Creative Cloud download and install errors ). What is your operating system and which apps have been included in your package?

    A
    Anonymous
    August 28, 2018

    Albrecht Volk​Albrecht Volk

    Thank you for the quick response. We resolved this ourselves.

    We did review the logs again. Again we saw the same thing you did BUT the VM this was tested on more than met the requirements for the install to complete without fail. The requirements for each application were verified before the initial post and after your response.

    We did nothing more than find every file and registry entry related to Adobe and removed them. We already had a list from previous experiences, but that was not sufficient in this case.

    We could have simply provided a fresh image and loaded CC first, BUT this headache has allow me to create a "total clean when Adobe installs get demonic" SOP.

    The team that works on the uninstall process and the clean tool need to be far more thorough in their cleaning.

    Adobe customers should not have to scour the the OS & registry while cross referencing IDs to clean up something that should be done automatically.

    I would hate to see what a typical end-user goes through when installs throw fits.

    D
    daniels38881609
    New Participant
    August 21, 2018

    AGREED

    We dread each and every request for an additional deployment of the Creative Cloud Suite. 50% of the time we'll get the installation to complete without rolling back. We've spent hours upon hours cleaning systems with the AdobeCreativeCloudCleanerTool as well as deep dives into the local registry and file system.  The log files the installer produces are usually unhelpful and never lead to a root cause we can fix. We usually end up deploying a clean/freshly-imaged computer to the end-user and then attempt the install. Even that is only 80% effective.

    FYI: Adobe, your software really really sucks in the realm of enterprise deployment. I mean, IT REALLY SUCKS...

    -25 year IT Professional

      Terms & ConditionsAccessibility statement
      Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices