Skip to main content
mark_stephens
Participant
October 22, 2014
Question

Installation Issues Adobe CC Enterprise Package - Explorer.Exe Not restarting and VCredist_x86.exe install behaviour

  • October 22, 2014
  • 10 replies
  • 5154 views

Lengthy email correspondence with Adobe support on this issue with Explorer.Exe closing and not relaunching.

Package Details

I have created a new streamlined package with applications that the business really need.

Current version of Adobe Cloud Packager V1.7.0.4.3

Adobe Acrobat XI Pro

Adobe Illustrator CC

Adobe InDesign CC

Adobe Photoshop CC

Self Updates disabled.  Self installation left enabled.

Packaged using a Adobe CC for Teams License.

Microsoft Visual C++ 2010  x86 Redistributable Setup within the CC Package - Has anyone else noticed that vcredist_x86.exe seems to take ages to install / not install. 

On my LAB build I have tested this behavior with this preinstalled or removed and the behavior is identical.

After 5 mins when the installation of CC seems frozen  (this is a 30 sec install usually) this install disappears and explorer.exe closes.  The installation complete however Explorer.exe never restarts.

Can anyone shed any light on this.  Help assist.  Dealing with Adobe technical support is like pulling your own wisdom teeth out. 🙂

    This topic has been closed for replies.

    10 replies

    puneeta23771395
    Participating Frequently
    February 12, 2019

    Hi Everyone,

    This issue has been taken care in the latest release of Creative cloud Desktop application version 4.8.0.421 with Core Sync build 4.2.0.25. Please use following article to get information about installing latest version of Creative cloud desktop application.

    How to download Creative Cloud desktop app

    Participant
    March 1, 2018

    In my case this turned out to be an MSI error:

    MSI (c) (C4:34) [16:52:15:390]: RESTART MANAGER: Failed while restarting applications. Error: 352

    Adding this to the msiexec command fixed the issues:

    MSIRESTARTMANAGERCONTROL=Disable

    Note: you may still need to restart the explorer process if the Creative Cloud App requires it (not certain this is required)...At least you can control this and have some idea of potential return codes.

    MTGCH
    Participating Frequently
    January 7, 2015

    Hey,

    Another victim of Adobe's Cloud Packager. Waiting for their Support since quite a while, with no sign of any relief. Tried the help of the Dell Packaging Factory, but they couldn't figure it out, too. Have a look at Creative Cloud package is crashing Windows Explorer during install process if interested.

    Cheers,

    MTGCH

    Participant
    November 19, 2014

    As a workaround until this is sorted by Adobe, you could always start explorer at the end of the installation script if it's not running.  Definitely not a fix, but at least there's a usable PC after the install routine completes.

    I have the same exact issue in Windows 7 64bit after creating a package via Creative Cloud Packager a couple days ago.  This is my crappy duct tape fix for now.  This does not occur in Windows 8.1.

    Chris

    Participant
    November 19, 2014

    I'm actually using the Powershell Application Deployment Toolkit as a wrapper for the install at the moment. Allows me more control over the shortcuts and a few cleanup activities.

    There is a function in the toolkit for 'Refresh-Desktop' which basically refreshes Explorer.exe.

    I've tested this morning and it works fine. Deploying with SCCM now.

    Explorer.exe still restarts but at least it reliably comes back!

    Participating Frequently
    November 19, 2014

    We too have issues with the Creative Cloud Packager, here's hoping Adobe do some with the $$$ we're giving them and fix the damn issue. I've never had so many issues deploying software. Adobe get your act together.

    Ben

    Participant
    November 19, 2014

    Also another teams customer here with exact same issue for any package created from the CC suite - explorer.exe doesn't start back up again effectively immobilising the PC.

    Participant
    November 6, 2014

    I found that running the online install CreativeCloudSet-up works fine. During the installation the desktop icons disappear but after a couple of seconds it comes back. However I cannot use this option as I will deploy using SCCM.

    When using a package created with Creative Cloud Packager it kills explorer.exe and does not start it up again. If I create a package and DO NOT ENABLE Creative Cloud Desktop Application during the package creation it works fine.

    Is there an offline version of Creative Cloud Desktop Application install THAT WORKS as that could be a possible solution for me.

    TIA

    Participating Frequently
    November 6, 2014

    You can download the Creative Cloud Desktop app to your PC and run it locally if you want.

    It works reasonably well but it takes AGES (mainly because of the many huge downloads that it does) and it keeps complaining that you don't have an internet connection - even though you do.

    If you persevere you will get there.

    This whole deployment/management suite needs a complete overhaul, it's just not good enough.

    I haven't even tried to deploy the MSI's from PackageCreator via SCCM, though that is certainly on my to-do list.


    Participant
    November 17, 2014

    Just wanted to chime in that I'm experiencing the exact same issues.

    From another thread a technician posted that it's because of the 'cloud services integration with explorer' that they restart Explorer.exe.  What a crock.

    Windows Installer has had restart logic built into it for years, restart logic that is completely controllable and compatible with any of the major deployment systems enterprise would be using.

    Why in the hell would you restart Explorer.exe? It just makes absolutely no sense.

    Participating Frequently
    November 5, 2014

    I have the same problem.

    Enviro is Windows7 x64 clean(ish) build (it has Office 2013 but not much else).

    I built a package using Adobe Package manager, to install most of CC.

    It runs OK, kills Exporer.exe, then seems to stop.

    I get Error 10007 in the Event Log, from "Restart Manager", saying "Application or service 'Windows Explorer' could not be restarted."

    Then nothing happens, the progress bar freezes and Explorer never restarts.

    Remote tasklist shows that the relevant msiexec process is still running, with low and slowly increasing memory usage.

    I will leave this machine for a couple of hours to see if anything changes; I believe from earlier tests that the CC install is actually done, if I force-reboot now it will all work.

    Not a satisfactory situation though.

    mark_stephens
    Participant
    November 5, 2014

    I am out of the office until 10/11/2014.

    I am now out of the office on Annual Leave. I will be collecting my email

    over the holiday, but will only be responding to urgent PROJECT related

    emails ONLY. If urgent, during my absence you should contact FGW-IT on

    01793 515293. Or the IT Support Manager Steve.Ord@firstgroup.com

    Note: This is an automated response to your message "[Enterprise

    Deployment for Creative Cloud, Creative Suite] Installation Issues Adobe CC

    Enterprise Package - Explorer.Exe Not restarting and VCredist_x86.exe

    install behaviour" sent on 05/11/2014 10:54:10.

    This is the only notification you will receive while this person is away.

    This message is confidential. It may not be disclosed to, or used by, anyone other than the addressee. If you receive this message in error, please advise us immediately.

    Internet email is not necessarily secure. First does not accept responsibility for changes to any email which occur after the email has been sent. Attachments to this email could contain software viruses which could damage your system. First have checked the attachments for viruses before sending, but you should virus-check them before opening.

    For more information on our range of services or to book your tickets online, please visit:- http://www.firstgroup.com

    Participant
    November 4, 2014

    I am experiencing the exact same issue. Windows 7 SP1 64-bit clean machine with vcredist_x86.exe pre-installed. Used Creative Cloud Packager to create a package for Adobe Acrobat Pro XI. Used the following command to install

    START /WAIT .\Exceptions\ExceptionDeployer --workflow=install --mode=pre --installLanguage=en_US

    START /WAIT .\Build\AdobeAcrobatPro_XI.msi /QN

    The installation kills explorer.exe

    Did anyone else find a solution to this problem?

    John T Smith
    Community Expert
    Community Expert
    October 22, 2014
    mark_stephens
    Participant
    October 23, 2014

    Thanks John.  If have spent over 50 hours now Dev time working with the Adobe Creative Cloud Product.  I have read all forum threads and have had escalation to the Adobe Creative Cloud Production team.  There has been this issue with the Enterprise Deployment since late last year and they have still not resolved the issue.

    I still have issues in the lab with clean Windows 7 builds, local admin account UAC disabled.  No firewall, No antivirus.

    This is clearly an issue with the installation logic and needs addressing.  I should be charging Adobe for my time.  I am having to counter this issue when scripting my ACC deployment within our enterprise to a lrage targetted audience.

    In 10 years as a packaging and deployment engineer I have never known anything like this from a corporate product. 

    ADOBE WHY ARE YOU NOT TESTING YOUR ENTERPRISE PRODUCTS !!!!

    Brackee
    Participant
    October 24, 2014

    I have seemed to have the same problem, I am deploying for a CC Team, and have noticed that this happens when Photoshop is installing.
    I have created a SCCM package containing the Photoshop by itself and with other software, both of these packages stops the Explorer.exe without restarting it. Packages without Photoshop does not stop/restart explorer.exe and works as intended.

    Mark have you tried creating a package only containing Photoshop to see if it have the same problem?