Spotlight Stuck at 0% After Sonoma? Here's the Real Fix

I know how maddening this is. You update to Sonoma, open Spotlight to find a file you need, and the progress bar sits at 0% like it's mocking you. Search returns nothing. You reboot. Still 0%. You're not alone — this hit thousands of people after the Sonoma rollout, and the usual "just wait, it takes time" advice is useless when nothing's actually moving.

Let's fix it. Work through these three fixes in order. Stop the moment Spotlight starts crawling forward again.

Fix 1: The 30-Second Fix — Kill the Stuck Indexer

Most of the time, the indexer process has simply hung. Something during the Sonoma migration — a permissions flag on your home folder, a corrupted Spotlight plist, a third-party app fighting for disk access — froze the process mid-start. Killing it forces macOS to spawn a fresh one, and it usually just works.

Open Terminal (Spotlight won't help you here — use /Applications/Utilities/Terminal.app in Finder). Run this:

sudo killall -9 mds mdworker mdworker_shared

You'll be asked for your password. Type it — you won't see anything, that's normal — then hit return. Nothing visible happens, and that's exactly what you want. Within about ten seconds, macOS respawns the indexing daemons on its own.

Open System Settings, click Siri & Spotlight, then Spotlight Privacy at the bottom. If you see any drives listed there, the indexer is ignoring them. Remove anything you don't actually want excluded.

Wait two minutes. Then check indexing status:

mdutil -s /

You want to see Indexing enabled. Open Spotlight (Cmd + Space) and check the progress bar. If it's creeping past 0%, you're done. Close Terminal and get on with your day.

If it's still frozen? Move to Fix 2. Don't keep killing the process — you'll just spin your wheels.

Fix 2: The 5-Minute Fix — Rebuild the Index Properly

When a kill doesn't cut it, the index itself is corrupted. The Sonoma updater has a nasty habit of leaving half-written index files behind, and Spotlight can't recover from a torn index on its own. You have to burn it down and let it rebuild.

Before you touch anything, plug in your power adapter if you're on a laptop. A full rebuild on a 500GB drive takes 20–45 minutes, and it'll pause on battery.

In Terminal, run these three commands in order:

sudo mdutil -i off /
sudo mdutil -E /
sudo mdutil -i on /

Here's what each one does. The first turns indexing off for your boot volume. The second erases the existing Spotlight index (that's the -E — think Erase). The third switches indexing back on and kicks off a fresh scan.

You'll see output like Indexing enabled. after the last command. Give it a minute, then check Spotlight again. The progress bar should start moving within 30 seconds. If it does, walk away and let it finish. Don't open Spotlight every 20 seconds to peek — that actually slows the indexer down.

One thing people miss: if you've got an external drive plugged in, Spotlight reindexes that too, and a slow USB 2.0 drive will make the whole thing look frozen. Unplug external drives before you start the rebuild, then plug them back in after.

Still stuck at 0% after five minutes? You've got something deeper going on. Fix 3 is next.

Fix 3: The 15-Minute Fix — Clear the Metadata Cache and Rebuild From Scratch

This is the nuclear option, and honestly, it's what fixes the Sonoma bug for most people who get this far. The metadata cache on your drive — the database that stores all the file attributes Spotlight reads — has gone bad. Killing the indexer doesn't help because the indexer chokes on the corrupted cache every single time it starts.

First, back up. I'm serious. This step involves deleting system-level cache files, and while I've never lost data doing it, you don't want to be the first. Time Machine is fine.

Now, disable indexing entirely:

sudo mdutil -i off -a

The -a flag applies it to all volumes. Now delete the metadata stores. These live in a hidden folder at the root of each volume:

sudo rm -rf /.Spotlight-V100
sudo rm -rf /System/Volumes/Data/.Spotlight-V100

On Sonoma, the real one lives in the second path — the sealed system volume uses a firmlink, so the first command handles the legacy location and the second handles the actual data volume. Run both, ignore any "No such file or directory" errors.

Now fire up a full rebuild across all volumes:

sudo mdutil -E -a
sudo mdutil -i on -a

This is the point of no return. Spotlight will now rebuild every index on every mounted volume. On a 1TB SSD with a lot of small files (think node_modules, Photos libraries, Xcode DerivedData), expect 30–90 minutes. The progress bar in Spotlight shows the boot volume only — external drives and secondary volumes don't show up there.

To watch real progress, use this instead:

sudo fs_usage -w -f filesys mdworker | head -50

If you see lines scrolling by, the indexer is working. If it's silent for more than a minute, something's still wrong — and at that point, you're looking at a corrupted APFS metadata issue that usually means booting into Recovery mode and running First Aid on the volume.

Why This Bug Hits After Sonoma Specifically

Sonoma changed how macOS handles the sealed system volume. During the upgrade, Spotlight's existing index files get migrated to the new volume layout, and if the migration is interrupted — low disk space, a forced reboot, a kernel panic mid-update — the index lands in a half-migrated state that the indexer can't parse. It doesn't error out. It just hangs at 0%, silently, forever. That's why reboots and waiting don't help: there's nothing to wait for. The indexer is stuck in a loop trying to read files it can't interpret.

If you've got a Time Machine backup from before the Sonoma update, and you're comfortable with it, restoring /.Spotlight-V100 from that backup saves you the rebuild. But honestly, the rebuild is cleaner. Just do Fix 3 and make yourself a coffee.

When Nothing Works

If you've done all three fixes and Spotlight is still at 0%, check two things. First, run Disk Utility and check the APFS container for errors. Second, look at Console.app, filter for mdworker, and see what it's choking on. Nine times out of ten it's either a failing SSD (SMART status in Disk Utility will tell you) or a third-party kernel extension — usually an old antivirus or backup tool — that's blocking file access. Uninstall it, restart, and try Fix 3 again.

You'll get there. It's annoying, but it's fixable.