The image now installed is 13.0.1  That is the image that was created when AAMEE created the install package.  This is the umage that was installed after the conflict.  I do not know what version was installed at the time of the crash since once the conflict started any attempt to open Photoshop (or Illustrator for the systems that had that crash) results in the "fight" starting again with no chance to actually get Photoshop to open enought to even get its version number.

I will run a scan on all the systems I have with CS6 Master installed to try to get the versions installed and see if any correlation can be made as to which version is installed before a crash.  I do know that some systems have been updated, using AAM without problems ocurring during the update and one system actually did go into "fight" mode when Photoshop tried to open after AAM had already started an update.  That update was started manually.  I am not sure why POhotoshop started to try to open at that time.  It will take a while to do the scan to get the currently installed versions.

AAM version installed on the system I checked is 6.2.112.0  This was after the Photoshop reinstall on the system that crashed.

Just for info.  One of the systems that crashed was on 13.0.4  It did change its crash mode while I was watching it.  Previously a crashing system would fight the fight for  a minute or more till I forced a shut down.  Now the crashing 13.0.4 system fights the fight for about a half minute or maybe a bit less then both PS and AAM give up an do not open but at least the rest of the programs (other than Adobe which I did not try) will function.    This fight will continue even after a shut down and cold start.

Thank you for the video.  It is exactly what has been reported by me and some others in the Illustrator forum also.  To me a "crash" is when a program fails to open properly and requires a forced power off to recover the computer.  I will add that the same problem as shown will appear again as soon as Photoshop (or Illustrator if that is the broken program) is reopened.  The problem will remain until PS (or AI) is uninstalled and reinstalled.  The version I have for the installer is the older 13.1 but that had worked for several weeks and this problem just started recently and I had not installed (at least knowingly) any changed software be it PS, AI or AAM. prior to that time.  I did have some systems at the latest update and at least one of those failed also.

I have tried creating an Update package from AAMEE but the package that is created does not install using Apple Remote Desktop nor does it install if the created package is copied to the desktop of the system I am trying to update.

It is looking to me like the problem is located in the Adobe Application Manager since that app is common to both Photoshop and Illustrator.  I have tried using the AAM that installs as part of the Master Suite and the first thing it does is update itself.  My guess is that this "update" that AAM self-installs is broken and is causing the problem.  That is only my guess based on my observations.  Perhaps someone can come up with a way to prove or disprove my guess.

My next project for tomorrow will be to try to create a brand new installer with all updates since trying to individually use the Update button in the actual Photoshop  does work but I'll be damned if I am going to visit two hundred seperate machines to have to install the update on each and every system as a stand alone update, especially since I have already had at least one system that I know was on the latest update but still failed in exactly the way your video shows.

A follow up will be to try to remove the AAM and reinstall a new version from the Adobe web site just to see if that helps, hurts or has no discernable effect.

Could you please give detailed directions as to which logs would be needed and exact directions as to where the needed logs are located in the Apple 10.8 system.  Thank you.

HELLOOOOOO  ADOBE, WHERE ARE YOU?

Since I am now up to 19 (and coutning) systems that have developed this problem. and the problem is also appearing when InDesign is opening, some acknowledgment from the AAM team at Adobe would be useful.

Chris Cox, if this is out of your realm, can you please put us in touch with the AAM team or at least point to where the forum is for AAM???