Browse documentation

Troubleshooting

The handful of things that actually go wrong, and what each one means.

A scan returns nothing

Almost always Full Disk Access. If the module reads system-managed locations and the permission is missing or stale, it will find nothing and say so. Re-add the permission as described in the permissions guide.

If the permission is definitely in place, the result may simply be correct — a Mac that was cleaned recently genuinely has little to remove.

Some items could not be deleted

The summary lists which ones and why. The usual cause is a file that is open in a running application, or a stale permission after the app was replaced with a new build.

Quit the application that owns the file, or re-grant Full Disk Access, then run the module again. Items that failed are left exactly as they were.

A scan is taking a long time

Modules that walk your whole home folder — Large & Old Files, Duplicates, Similar Images — are bounded by disk speed and by how many files you have. Progress shows a live count and an estimate.

Disk Recovery is the slowest by nature: it reads the entire surface of a volume once. Every scan can be cancelled, and cancelling keeps whatever was already found.

I removed something I needed

Open the Trash and drag it back. Everything iSweepy removes goes there by default, and it stays until you empty the Trash yourself.

If the Trash has already been emptied, Disk Recovery can carve the file back as long as the space has not been reused. Stop writing to that disk first — every new file reduces the chance.

The app looks like it is in the wrong language

iSweepy follows your system language when it is one of the languages the app ships fully translated. Anything else falls back to English rather than showing a half-translated interface.

You can override the choice in Settings → General → Language. macOS resolves an app's language at launch, so the change takes effect after a restart — the app offers to restart itself.