If an app keeps launching after login even though you removed it from Login Items, the app may be starting through a different mechanism. Modern macOS separates visible “Open at Login” items from background activity, while older and more technical software can also install LaunchAgents, LaunchDaemons, helper tools, menu-bar components or system extensions.
Removing one entry therefore does not always remove every component that can start automatically. The right fix is to identify which mechanism is launching the process before deleting files.
Start in System Settings, not in the Library folders
Open System Settings → General → Login Items & Extensions. Apple’s current interface groups startup behavior into sections such as items that open at login and apps that are allowed to run in the background.
If the unwanted app appears under Open at Login, remove it there. If it appears under background activity, switch off the permission and then test after logging out and back in.
Why can an item return after you remove it?
There are several common reasons:
- the app re-adds its helper when you launch it;
- a preference such as “Launch at login” remains enabled inside the app;
- an updater or menu-bar helper is registered separately from the main app;
- a LaunchAgent loads independently of the visible Login Items list;
- the app uses a privileged helper or system extension;
- device-management software enforces the background item on a managed Mac.
For this reason, check the app’s own settings before trying to remove support files manually.
Open at Login and background activity are different
An Open at Login app normally creates a visible user-facing launch after sign-in. Background items can start processes without opening the full application window. They may provide syncing, software updates, cloud drives, clipboard features, VPN components or device communication.
Turning off a background item can therefore disable part of an app even though the main application still opens normally.
What is a LaunchAgent?
macOS uses launchd to start and supervise many processes. A LaunchAgent is typically associated with a logged-in user and can start a background program when that user logs in or when specified conditions are met.
Common locations include:
~/Library/LaunchAgents— agents for the current user;/Library/LaunchAgents— agents available system-wide to user sessions;/Library/LaunchDaemons— system-level daemons that can run without a user logged in.
The presence of a file in these folders does not automatically mean malware. Legitimate applications frequently use them.
Do not delete every plist that has an unfamiliar name
A launch plist usually contains a label and a path to the executable it starts. Before removing anything, inspect the file name and its program path. Search for the owning application and check whether the software provides its own uninstaller.
Security tools, VPN clients, audio drivers, backup software and hardware utilities can depend on several components at once. Deleting one plist can leave the software in a broken half-installed state.
Use the application’s uninstaller when one exists
Dragging an app to the Trash removes its application bundle, but it may not remove privileged helpers or system extensions installed elsewhere. Applications that install deeper system components often include an uninstaller or documented removal procedure.
Use that procedure first. It has the best chance of removing the launch registration and the executable together.
How to find the process that is actually returning
- Restart or log out and back in.
- Open Activity Monitor and identify the unexpected process.
- Note its exact process name.
- Check Login Items & Extensions.
- Check the parent application’s settings.
- If necessary, inspect the LaunchAgents and LaunchDaemons folders for a matching label or program path.
- Remove or uninstall only after you know what owns it.
The process is gone, but macOS still shows a background item
Sometimes the visible entry can remain after an application update or imperfect uninstall. Restart first, then make sure the original app is genuinely removed. If the item belongs to software you still use, reinstalling the current version and then uninstalling it correctly can be cleaner than manually deleting scattered components.
What about notifications saying an item was added in the background?
Recent versions of macOS surface background-task activity more clearly than older releases. These notifications are useful because they show that installing or updating software changed what can run automatically. If the notification names an app you recognize, review its background permission. If you do not recognize it, investigate before approving or deleting anything.
Managed Macs are different
On a work or school Mac, login and background items may be controlled by device-management profiles. Apple’s deployment documentation includes controls for managed login items and background tasks. If an item reappears after every restart and the Mac is managed, local deletion may be intentionally overridden by policy.
When startup troubleshooting is the goal
If the Mac is slow or unstable after login, temporarily removing non-essential login items can help isolate the cause. Test a small group at a time rather than deleting support files. When the problem disappears, re-enable items selectively until the responsible component is identified.
A useful rule for cleanup
Disable first, observe second, uninstall third, manually delete launch files only when you know exactly what they belong to. That approach is slower than deleting everything with “launch” in its name, but it avoids breaking software that relies on legitimate background services.
Apple documentation
- Apple Mac User Guide — Login Items & Extensions settings
- Apple Platform Deployment — Manage login items and background tasks
- Apple Mac User Guide — troubleshooting login items