cover manage boot elements on macos
4–6 minutes

Mac Lento allaAvvio? How to Manage Login Elements

If yourMac takes too much time to start, one of the main causes could be the excessive presence ofstart and login elements. On ignition of the computer, in fact, macOS automatically loads several programs, add-ons and background processes. Although most of these are useful, they often accumulate software that we ignore. Optimizing these processes is the first step tospeed up Mac startupand improve overall performance.

What are the Starting and Login Elements on Mac?

Thestart and login elementsare specific system applications or services programmed to activate themselves as soon as you access macOS. Some are indispensable for the proper functioning of the operating system, but others are unnecessary, consume precious RAM andslow down your Macin boot phase. We discover together how to locate, manage them and, if necessary, remove them safely.

How to Manage Login Elements

macOS 13 (Ventura) or later:

  • GoSystem Settings, click on the itemGeneraland selectLogin elements. On this screen you will find two separate sections: one dedicated to apps that automatically open to access and another for software authorized to run background processes even when they are not actively in use.
    System Settings for managing login elements on macOS Ventura

macOS 12 (Monterey) or previous versions:

  • Open the doorSystem Preferences, selectUsers and Groupsand move to the cardLogin elements. You will be shown the list of programs, files and folders that start automatically. Remember that each user account on your Mac has its own custom list.
    Panel Users and Groups in System Preferences to deactivate apps on macOS Monterey

Usually, these elements are automatically integrated after installing a new application (which should always require permission). Forremove a login element, just select it from the list and click on the button with the minus sign (-). On the contrary, to add one manually, use the button with the sign plus (+).

Cleaning of the StartupItems Folder

In less recent editions of macOS, the operating system relied on two specific folders to govern startup:
/Library/StartupItems
/System/Library/StartupItems
Today Apple has deprecated the use of these directories, but some more dated applications may continue to exploit them, weighing the system.

It is good standard to inspect the route/System/Library/StartupItemsto discover any unused elements. If inside individuals folders or files belonging to software you do not recognize or have already uninstalled, simply move them to the Recycle Bin. This will prevent their useless loading during ignition of the Mac.

Launchers and Agents (Launch Daemons and Agents)

Starting with the release of macOS 10.4 Tiger, Apple introduced a much more efficient framework calledlaunchd. This component manages process startup through file extension. p(Property List), which indicates to macOS what processes to start and to what exact conditions (e.g. boot system or at certain times of the day).

The filespcan be located in very precise routes:

Untouchable system folders (/System/Library/LaunchDaemonsand/System/Library/LaunchAgents): host the vital native processes for macOS. They must never be altered, as their modification could compromise the stability and proper functioning of the operating system.

  • User and third-party folders (~/Library/LaunchDaemonsand~/Library/LaunchAgents): include processes related to third-party software installed by the user. These can be disabled or removed with due care if you feel that they are no longer necessary.

Attention:act on system directories only if you have a thorough knowledge of what you are doing. Accidental deletion of critical files can cause severe malfunctions.

How to Manage Starting Processes from Terminal

More experienced users who want a granular and advanced control over startup processes can use the applicationTerminal. Type the commandlaunchctl list, you will be able to view the entire list of processes currently running. To forcefully stop a specific process, you use the commandlaunchctl unloadfollowed by the absolute path of the file. p.

Here is a handy command example to download (stop) an agent in the background:

launchctl unload ~/Library/LaunchAgents/com.apple.FolderActions.enabled.plist

In case of second thoughts, just replaceunloadingwithloadto restore functionality and recharge the process.

Other Hidden Processes that Slow Start

If you can’t locate a “mysterious” process among the classic login elements, in launch folders or in StartupItems, the cause may reside in one of these two factors:

  • Kernel extensions (kext):located in the path/System/Library/Extensions, these extensions are loaded during the very first boot phase to provide low-level hardware and functionality (e.g. third-party drivers). To uninstall them safely, it is always preferable to use the official uninstaller provided by the software manufacturer.
  • Cron Job:although it has been largely supplanted bylaunchdin modern macOS releases, the classic UNIX “Cron” planning system could still host old residual scripts configured to automatically turn on Mac.

Frequently Asked Questions (FAQ) on Starting Elements

Is it dangerous to disable boot elements on your Mac?

Disable apps from the “ Login Options” section in System Settings is a completely secure operation. This step simply prevents automatic opening of the user interface when switching on. It is necessary, however, to provide maximum caution when deciding to delete files. pin foldersLaunchDaemonsor touch Kernel Extensions, procedures indicated only for experienced users.

How do I understand which apps consume more resources at startup?

The best method is to use native applicationActivity Monitoring(found in the Applications > Utility folder). By checking the “CPU” and “Memory” panels in the first minutes after igniting your Mac, you can immediately isolate the heaviest processes that absorb most of your system’s resources.

If I move an app to the Recycle Bin, is the login element removed automatically?

Not always. Moving an application to the Recycle Bin is often not enough to delete its background support files. This can generate the so-called “orphan trials”, i.e. elements that try to start by no longer finding the program of origin, unnecessarily slowing the Mac. To avoid this problem, delete the login element manually using the (-) button before you delete the app, or use specialized uninstall software.

EnglishenEnglishEnglish