0X00000071

ERROR_NO_MORE_SEARCH_HANDLES (0x71) Fix in Windows 10/11

This error means the file system has run out of internal search handles. Happens with many open file dialogs or heavy indexing. Restarting the search service usually cleans it up.

When This Error Shows Up

You're working in Windows 10 or 11, maybe running a script that scans folders, or you have multiple file explorer windows open with search bars active. Then you get hit with ERROR_NO_MORE_SEARCH_HANDLES (0x00000071). It doesn't happen often, but when it does, it stops file operations cold. I've seen it most often on machines with heavy antivirus scans running alongside file indexing.

What's Actually Happening Here

Windows tracks file searches using internal objects called search handles. These are different from regular file handles. They're used by the NTFS file system to remember where you are in a folder listing or a search result. The system has a hard limit — usually around 16,384 handles — and once you hit that, you get error 0x71. The trigger is almost always a program that opens searches and doesn't close them properly. Common culprits: buggy backup software, old antivirus, or a stuck Windows Search service.

The Fix — Step by Step

  1. Restart Windows Search Service

    Open Services (services.msc). Find Windows Search. Right-click and choose Restart. If it's stopped, start it. Wait 10 seconds — this releases all stale search handles.

  2. Clear Search History Cache

    Open File Explorer. Go to C:\Users\YourUsername\AppData\Local\Microsoft\Windows\Search. Delete everything inside. Don't delete the folder itself. This forces Windows to rebuild the search index from scratch — no stale handles.

  3. Reboot and Test

    A full reboot flushes all handles. If the error is gone, you're done. If it comes back quickly, something is leaking handles.

  4. Check for Handle-Leaking Software

    Run handle.exe from Sysinternals (or use Process Explorer). Filter by Search or File handle types. Look for programs with thousands of handles. Common offenders: Google Drive Backup, Dropbox, or old Norton Antivirus. Close or update that program.

  5. Registry Tweak (Only If Still Broken)

    If you've rebooted and checked software but the error keeps happening, you can raise the handle limit. This is not a normal fix — only do it if you're sure you need it.

    reg add "HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Executive" /v "AdditionalDelayedWorkerThreads" /t REG_DWORD /d 4 /f

    This adds more threads for handle cleanup. Then reboot.

If It Still Fails

Check the Windows System Event Log. Look for Event ID 322 or 3225 from the NTFS source. That tells you which drive is running out of handles. If it's a network drive, fix the connection. If it's a local disk, run chkdsk /f on that drive — corruption can cause handles to never close.

Finally, if nothing works, disable Windows Search entirely. Go to services.msc, stop Windows Search, set startup type to Disabled. Your file searches will be slower, but you won't see error 0x71 again.

Related Errors in Windows Errors
0XC00D2715 Fix NS_E_DRM_SECURE_STORE_UNLOCK_ERROR 0XC00D2715 0XC00D003D Fix NS_E_INVALID_ARCHIVE (0XC00D003D) Archive Error 0XC00000E0 STATUS_DOMAIN_EXISTS (0XC00000E0) – Domain Already Exists Fix 0X00000524 Windows ERROR_USER_EXISTS (0X00000524) Fix – Account Already Exists

Was this solution helpful?

EP
Erropedia Team
Tech Support Editors
The Erropedia editorial team researches and documents real-world tech errors from across Windows, Linux, macOS, networking, databases, cloud platforms, and more. Every solution is reviewed for accuracy and updated as software and systems evolve.