CleanMyMac not working on Mac: what to check

When a resident Mac utility stops behaving, the first instinct is usually to reinstall it. For this category of app that instinct is close to useless, because the settings that most often cause the failure live in macOS rather than in the application bundle. Delete the app, install it again, and the same permissions are still switched off in the same place. The symptom returns within a minute.

What actually resolves these cases is an order of inspection. Background permission first, then the toggle inside the app, then the login items index that macOS maintains, then Full Disk Access. Four places, checked top to bottom. Most problems stop at one of the first two, and the ones that do not are usually a specific, documented condition rather than a mystery.

Three failures, one complaint

"Not working" covers at least three separate conditions, and they have different causes. Establishing which one applies takes ten seconds and saves the rest of the session.

• The app launches, but no icon appears in the menu bar at all.
• The icon appears, opens, and shows empty placeholders that never fill in.
• Scans run but return very little, or operations stop and keep asking for permission.

The first is a background component that is not running. The second is a component that is running but is not being fed readings by the monitor behind it. The third is a permissions issue with what the app is allowed to read. MacPaw treats the first two as separate articles in its knowledge base, which is a good indication that they have separate fixes.

Understanding why requires one structural fact. CleanMyMac is not a single process. It ships several background items: the Menu that appears in the menu bar, a Health Monitor that supplies its readings and watches for malware, an Agent that performs operations needing root privileges, and an Updater for the app itself. Each is permitted separately by macOS. One of them being blocked produces a specific symptom rather than a general failure, which is exactly why the symptom is worth naming before touching anything.

Layer one: the permission that sits above the toggle

Start in System Settings, not in the application. Open System Settings, go to General, then Login Items & Extensions, and look at the list of items allowed to run in the background. CleanMyMac's components should be listed and enabled there.

This layer outranks the app's own settings. MacPaw states directly that when the background item is not allowed, the Menu will not open and switching it on or off inside CleanMyMac Settings has no effect. That single sentence explains a large share of the reports in this category: someone flips a switch in the app, nothing happens, and they conclude the app is broken when the system was overriding it the whole time.

Two situations knock these permissions out on a working machine. The first is a macOS major upgrade. The second is a large app update, which can register new components that arrive in a not-yet-approved state. If the failure appeared right after either event, this list is almost certainly the answer. Apple's documentation on login items covers the same settings pane from the system side.

Layer two: the switch inside the app

If the background permission is on and the icon is still missing, open CleanMyMac, go to Settings, select the Menu tab, and check whether the Menu is enabled. That is a single checkbox, and it is off more often than people expect.

It gets switched off deliberately at some point and then forgotten. It also fails to carry across in some migration scenarios, so a Mac restored from another machine or set up with a fresh user account can end up with the component allowed at the system level and disabled at the app level. Toggling it off, waiting a few seconds, and toggling it back on is worth trying before anything more involved, because it forces the component to start rather than merely permitting it to.

Between these two layers, the majority of cases resolve. Going deeper before checking both is how a fifteen minute problem becomes an afternoon.

Layer three: rebuild the login items index

If the icon is still absent, or if it appears but its contents never load, macOS may be holding stale information about the app's login items. MacPaw describes this as the system occasionally forgetting the login items of recently updated apps, or launching outdated versions of them, and notes that the behaviour is not specific to their software. Any app that updates frequently and installs background components can hit it.

The documented fix has two steps, in order.

Step one is to update macOS. Open System Settings, go to General, then Software Update, install anything pending, and let the Mac restart. This resolves a portion of cases on its own, and it is the low risk option, so it goes first.

Step two applies only if the problem survives the update. It involves deleting the files that store login item settings so that the system rebuilds its index. In Finder, choose Go, then Go to Folder, and enter /private/var/db/com.apple.xpc.launchd/. Inside are property list files whose names include user ID numbers such as 501. Removing them and restarting the Mac forces macOS to regenerate the index from scratch.

Two cautions before doing that. These files hold login item settings rather than app data, so nothing you created is at risk, but they are shared: login items belonging to other apps are rebuilt too, and a few of those apps may ask for approval again after the restart. And this is a system directory, so it belongs in the category of changes made with a current backup in place. MacPaw also publishes a Terminal equivalent for anyone who prefers it, but the Finder route is easier to reverse if you land in the wrong folder.

Full Disk Access decides what a scan can see

A different symptom, with a different cause: scans complete but return implausibly small results, or whole categories come back empty.

CleanMyMac requires Full Disk Access to reach the protected areas macOS walls off, and MacPaw states that without it the app cannot scan all areas of the Mac for junk files or for malware. That reframes the symptom usefully. A near-empty result is not the app reporting that nothing is there. It is the app reporting that nothing is there within the part of the disk it was allowed to look at.

To grant it, open System Settings, go to Privacy & Security, then Full Disk Access, and enable the relevant entries. On macOS Ventura and later this is a single CleanMyMac entry. On Big Sur 11.4 and Monterey, MacPaw's instructions list three separate items to enable: CleanMyMac, CleanMyMac Health Monitor, and CleanMyMac Menu. Enabling one of three and seeing no change is a common outcome of not noticing that split.

If the entries are not in the list at all, run a scan once first. MacPaw notes that the components register themselves with macOS during a Smart Care scan, so the list can genuinely be empty before the app has ever run a scan. Apple's own page on Privacy & Security settings describes the same pane.

Two things that look like faults and are not

Before concluding something is broken, rule out two conditions where the software is behaving exactly as designed.

The first is edition differences. CleanMyMac is sold through the MacPaw Store, through Setapp, and through the App Store, and MacPaw publishes a matrix showing that the App Store edition omits a substantial list of features because of App Store review rules. Missing there are system cache and system log cleanup, language files, universal binaries, iOS device backups, several maintenance tasks including flushing the DNS cache and reindexing Spotlight, and the Protection monitor inside the Menu. Same name, same version number, different capabilities. A feature you read about and cannot find may never have shipped in the copy you installed.

There is a version dimension to this as well. MacPaw lists the current release as 5.5.7, dated 22 July 2026, with macOS 11 or later required and a minimum display size of 1200 by 800 pixels. A Mac running an older system than that is outside the supported range, which is a different situation from a fault and will not be resolved by any of the steps above. Checking the version and the system requirements takes a moment and occasionally ends the investigation immediately.

The second is antivirus interaction. MacPaw documents that third-party antivirus software can conflict with CleanMyMac. When two products scan the same files simultaneously, the visible result is a scan that stalls, takes far longer than usual, or fails to delete something. Pausing one of them temporarily and retrying is a fast way to confirm or eliminate that as the cause.

Hidden is not the same as stopped

There is one diagnostic trap specific to a busy menu bar. On a Mac running a tool that hides menu bar icons, "the icon is gone" and "the component stopped" look identical, and they are not.

The check takes a second: expand the menu bar and look at the collapsed section. If the icon is sitting there, the background component is running normally and the whole problem is a display setting. If it is genuinely absent, go back to layer one.

Worth knowing too: an app that installs more than one menu bar component can end up with one visible and one hidden, depending on how the organizer sorted them when they first appeared. That produces a confusing middle state where part of the app looks alive and part looks dead. Any tool in this space handles that sorting slightly differently, and the compare page sets out how the main options treat newly added items and per-app grouping.

Collecting evidence when none of that works

MacPaw ships a Support Tool that gathers logs, app preferences, and system data into a report for their support team. It exists because these problems are frequently environment-specific and hard to reproduce on request.

There is a practical timing point here. Changing settings repeatedly in an attempt to self-fix can make the fault stop reproducing without explaining it, at which point there is nothing useful to send. If two or three of the steps above have not worked, generating the report before continuing to experiment is the better sequence.

For reducing the odds of a repeat, the useful lever is the number of resident apps requiring background permission. Every macOS upgrade is an opportunity for those approvals to reset, and a machine with more than ten such apps turns every incident into a long process of elimination. Fewer permitted components means faster diagnosis, which is a maintenance argument rather than an aesthetic one.

What to change first

Work the four layers in order before reinstalling anything: background permission, in-app toggle, login items index, Full Disk Access. If a menu bar organizer is installed, expand the bar first so that a hidden icon is not mistaken for a stopped process, since the two need completely different fixes. The features page explains where hiding stops and stopping begins, pricing and Koffret cover the practical details if you decide to manage the row rather than prune it, and FAQ collects the setup questions that come up most.