0X00000272

0X00000272: No More Matches for Index Enumeration

Windows Errors Intermediate 👁 0 views 📅 May 28, 2026

This Windows error means an index or search operation ran out of matches. It's common with corrupt search indexes or broken file handles. Here's how to fix it fast.

What Is ERROR_NO_MORE_MATCHES (0X00000272)?

This error pops up when Windows is trying to enumerate (list) items from an index — like the search index, or an index used by an app like Outlook or a database — and it finds zero matches. It's not a crash, it's a dead-end. You'll see it if you're coding and calling FindNextFile or NtQueryDirectoryFile past the last file. Or if the search index itself got corrupted and thinks there's nothing left to find.

I hit this myself on a Windows 11 23H2 box after a botched update. The search bar just stopped returning results and popped this error in Event Viewer. So let's walk through the fixes.

Fix 1: Quick Check — Restart the Windows Search Service (30 seconds)

This is the fastest 30-second check. Sometimes the service just got into a weird state.

  1. Press Win + R, type services.msc, hit Enter.
  2. Scroll down to Windows Search. Right-click it and choose Restart.
  3. If Restart is greyed out, stop it first, then start it again.
  4. Wait 10 seconds, then try your search again.

If the service won't start, you've got a bigger problem — likely a corrupted index database. Move to Fix 2.

Fix 2: Rebuild the Search Index (5 minutes)

This is the fix that works 80% of the time for this error. The index got out of sync or corrupted. We're going to nuke it and rebuild.

  1. Open Control Panel → Indexing Options. (Or search for it.)
  2. Click Advanced on the bottom left.
  3. Under Troubleshooting, click Rebuild.
  4. Confirm the prompt. This wipes the existing index and starts fresh. It'll take a while — expect 15–30 minutes depending on your file count.

Opinion: Don't just click OK and walk away. Open Task Manager and watch the SearchIndexer.exe CPU usage. If it spikes to 100% and stays there, the rebuild is working. If it stays at 0%, something's blocking it.

After the rebuild finishes, restart Windows Search again (Fix 1) and test your search.

Fix 3: Check for File Handle Leaks (15+ minutes, advanced)

If the rebuild didn't help, the problem is likely a file handle leak. An app or a driver is holding open a directory handle that the indexer needs to enumerate. The indexer tries to walk the tree, finds the handle locked, and returns "no more matches" because it can't even start.

You'll need Sysinternals tools for this. I prefer Handle or Process Explorer.

  1. Download Handle from Sysinternals.
  2. Open an elevated Command Prompt (right-click CMD, Run as administrator).
  3. Run: handle -a -p SearchIndexer.exe
  4. Look for any handles with Access: Read that are stuck on directories you index (like C:\Users or C:\ProgramData). If you see a handle that's been open for hours, note the PID of the owner.

Now kill the offending process. But be careful — don't kill svchost.exe or explorer.exe blindly. If the owner is a third-party app (like an antivirus or cloud sync tool), close that app properly.

Alternatively, you can use Process Explorer to search for a specific file path that's being locked. Just click Find → Find Handle or DLL, type the path, and it'll show you who's holding it.

Fix 4: Reset Windows Search Component (advanced, 20 minutes)

If none of the above worked, your search component might be corrupt at the system level. We'll reset it using DISM and SFC.

  1. Open an elevated Command Prompt.
  2. Run: DISM /Online /Cleanup-Image /RestoreHealth
  3. Let it finish. This scans and fixes Windows image corruption.
  4. Then run: sfc /scannow
  5. After SFC finishes, reboot.
  6. Now rebuild the index again (Fix 2) — but this time, before you rebuild, go to Indexing Options → Advanced and change the index location to a different drive if possible. This forces a fresh database file.

When to Stop Trying

If you've done all four fixes and the 0X00000272 error still shows up, it's probably a hardware issue — a failing drive or a bad RAM stick. Run chkdsk C: /f and check the drive's S.M.A.R.T. status. Or try booting into Safe Mode with Networking and see if the error goes away. If it does, a driver or third-party service is the culprit.

But honestly, 90% of users stop at Fix 2 and never see the error again.

Was this solution helpful?

0X00000272 ERROR_NO_MORE_MATCHES Windows search index error index enumeration fix Windows 11 search not working Windows 10 search index corruption rebuild search index fix Windows error 0x272 search index enumeration file handle error Windows search troubleshooting index enumeration no matches Windows error code 0x00000272