Skip to main content
L
luigib69639999
Participant
May 29, 2016
Question

Failed Agents on Mac

  • May 29, 2016
  • 2 replies
  • 15102 views

I ran EtreCheck on my MacBook Pro running the latest version of El Capitan. Three Adobe processes showed as "failed."

I searched the Mac for these processes using Spotlight. No luck.

I have uninstalled Adobe Creative Cloud in order to fix these issues. No luck.

I then ran Adobe Creative Cloud Cleaner Tool and fixed one issue.

The following two processes still show as "failed" in EtreCheck:

Launch Agent

com.adobe.ARM.202f4087f2bbde52e3ac2df389f53a4f123223c9cc56a8fd83a6f7ae.plist

User Launch Agent

com.adobe.ARMDCHelper.cc24aef4a1b90ed56a725c38014c95072f92651fb65e1bf9c8e43c37a23d420d.plist

Can anybody say why these agents are failing, and how I can get rid of them? Thanks in advance.

      This topic has been closed for replies.

      2 replies

      D
      DavidB3
      Participating Frequently
      August 8, 2016

      I have the same problem with one of the processes the OP cited:

      User Launch Agent

      com.adobe.ARMDCHelper.cc24aef4a1b90ed56a725c38014c95072f92651fb65e1bf9c8e43c37a23d420d.plist

      Can anyone answer the original question?

      Thank you,

      David

      Jeffrey_A_Wright
      Jeffrey_A_Wright
      Legend
      August 15, 2016

      David are you running this EtreCheck utility referred to by the original poster?  Do you see any errors when not utilizing a third-party diagnostic utility?

      patrickm66434646
      patrickm66434646
      Participant
      June 23, 2016

      Reported Bug 3162265 was reported and could be in reference to issue at hand....

      Flash Player's new auto-update mechanism installs a LaunchDaemon in /System. /System is normally reserved for Core OS LaunchDaemons/LaunchAgents that are managed by Apple. This goes against conventions for the system. Systems administrators who support OS X look in the user and /Library folders to get a sense of what daemons may be loaded on a system, and generally don't expect to find anything in /System except what ships with the OS......          Any third-party LaunchDaemons/LaunchDaemons that are to be used system-wide should reside in /Library, not /System/Library. Changing the LaunchDaemon location to /Library wouldn't impact the functionality in any way, it would simply bring the Flash Player install into compliance with the conventions of the OS. Given that other Adobe products install update mechanisms in /Library, it would only make sense for Flash to also use this location.

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