Windows Search Indexing Stuck Not Responding – Fix

Corrupt Index Database – The Real Culprit

Nine times out of ten, when Windows Search indexing gets stuck or stops responding, it's because the index database itself is corrupt. You'll see SearchIndexer.exe eating up CPU or memory, or the search box just shows "Working on it..." forever. I've seen this on Windows 10 20H2 and Windows 11 22H2 mostly, but it can happen anywhere.

Here's the fix — rebuild the index. Don't bother with the Windows Search troubleshooter, it rarely fixes this.

1. Open Control Panel (hit Win+R, type control, press Enter).
2. Go to Indexing Options (view by Large icons makes it easier to find).
3. Click Advanced at the bottom (you need admin rights).
4. Under the Index Settings tab, in the Troubleshooting section, click Rebuild.
5. Confirm the warning — it'll take a while depending on how much data you have. Expect 30 minutes to a few hours.

This nukes the old index and rebuilds from scratch. I've fixed hundreds of machines this way. If the rebuild itself hangs, move to the next fix.

Stuck File or Corrupt File in Indexed Location

Sometimes a single file — usually a corrupt PST email file, a broken Outlook archive, or a dead-zone PDF — causes the whole indexing service to lock up. You'll notice the indexer's memory usage spikes when it hits that file, then stays high. The fix is to exclude the offending folder temporarily, rebuild, then add it back.

1. Open Indexing Options again.
2. Click Modify and uncheck Outlook or any custom location you suspect (like your Document folder if you have a specific problem file).
3. Click OK, then do the rebuild from step 1.
4. After rebuild completes, re-check those locations. If the indexer hangs again, you know that folder has a bad file. You'll need to find and delete or repair that file manually.

Outlook PST files are the main offender here — especially if you have a 50GB archive. I've also seen corrupt .docx files from Office 2016. Check the Windows Search log in Event Viewer under Applications and Services Logs > Microsoft > Windows > Search for error details. Look for Event ID 3100 or 3200 — those point to a specific corrupt file.

Permission Issues on Indexed Folders

Another common cause: the search indexer service (running as LocalSystem) can't access a folder due to messed-up permissions. This usually happens after a user profile migration or a folder redirection change. The indexer gets stuck trying to enumerate files it can't read. The symptom is slow indexing that never finishes, not a total freeze.

To fix this:

1. Open an elevated Command Prompt (right-click Start, choose Command Prompt (Admin) or Terminal Admin).
2. Run icacls "C:\Users" /grant "NT AUTHORITY\SYSTEM":(OI)(CI)F /T (adjust the path if your user folder is on a different drive). Be careful — this gives SYSTEM full control on the entire Users folder. Only do this if you're sure that's the problem.
3. Then stop and restart the search service: net stop wsearch and net start wsearch.
4. Manually rebuild the index again (see step 1).

If you don't want to mess with permissions broadly, narrow it down: check the folder C:\ProgramData\Microsoft\Search\Data\Applications\Windows — the indexer writes its database there. If the SYSTEM account doesn't have full control on that folder, nothing works. Right-click it, Properties > Security, and verify SYSTEM has Full control.

Quick-Reference Summary Table

That's it. Start with the rebuild. If it doesn't work, hunt down the bad file. Permissions are the last thing I check unless the user just restored a profile. Don't waste time with SFC or DISM — those rarely fix a stuck indexer. Good luck.