Skip to main content
Brackee
Brackee
Participant
October 16, 2014
Question

Problem: Adobe CC deployment of Photoshop kills Explorer.exe

  • October 16, 2014
  • 2 replies
  • 1407 views

Hello,

I have created several deployment packages lately via the Creative cloud packager. They are deployed via SCCM and when both InDesign and Illustrator have been working fine while Photoshop kills the Explorer.exe under the deployment.

The explorer.exe does not come back automatically and have to be started via task manager.

I also created a package that includes several programs, among them Photoshop and the same happens with it.

Note: Photoshop do complete the installation and are working correctly.

Is there anyone that have encountered this problem before, and do anyone have a solution for it?

This topic has been closed for replies.

2 replies

cmendesvdl
cmendesvdl
Participating Frequently
January 2, 2018

this is just unbelievable... how can this still not be fixed!?

A
Anonymous
October 24, 2014

Brackee wrote:


Is there anyone that have encountered this problem before, and do anyone have a solution for it?

Oh so it is not just me then.  I have this issue and other than doing what you do and starting explorer.exe back up no solution.  As you say the install completes fine and as I build Adobe into our image it is not really a big issue to do this once every six months.

    Brackee
    BrackeeAuthor
    Participant
    October 24, 2014

    This wouldn't be a big problem if it was I that did the installation as I know how to start explorer.exe in that situation, but that does not all our users know, and if I where to allow deployment of this via SCCM we would encounter this.

    A
    Anonymous
    October 24, 2014

    We don't use SCCM but use MDT instead so how I would approach this is make bat file run after the deployment that would start explorer.exe back up.  I would chain dependencies together so that the bat file relied on the post-install being installed and the post-install relies on the install and so on but at the end of the day you are right, this should be fixed by Adobe themselves.

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