SearchHost.exe, the process behind the Start menu search bar in Windows 11, can spike CPU usage to 100 percent across eight cores, freezing your system for minutes. This occurs when the search indexer attempts to rebuild its database from scratch or processes a corrupt index file. In this article, you will learn the root cause of this behavior and how to resolve it permanently.
Key Takeaways: Fixing SearchHost High CPU on Windows 11
- Settings > Privacy & security > Search permissions > Search indexing: Disable cloud search indexing for OneDrive and other online sources to reduce index size.
- Services app > Windows Search > Stop, then Delete the index database: Forces a clean rebuild of the search index, eliminating corrupt data.
- Registry Editor: HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Windows Search > DisableSearch (DWORD 1): Completely disables the search indexer if the issue persists.
Why SearchHost.exe Uses 100 Percent CPU on Windows 11
SearchHost.exe is the process that runs the Start menu search box. It relies on the Windows Search Indexer, a separate service called SearchIndexer.exe, to catalog files, emails, and app data. When the indexer encounters a corrupt index database, it enters a loop where it repeatedly tries to read, repair, and re-index the same data. This loop consumes all available CPU cores on your system.
The index database is stored in C:\ProgramData\Microsoft\Search\Data\Applications\Windows. If this file becomes damaged due to a sudden power loss, a failed update, or a disk error, the indexer cannot complete its work. It then retries the operation indefinitely, causing the CPU spike.
Another common trigger is a very large index set. By default, Windows 11 indexes all user folders, including OneDrive, Outlook mail, and network shares. On systems with hundreds of thousands of files, the initial indexing pass can saturate eight or more cores for several minutes.
Steps to Stop SearchHost High CPU Usage
The fix involves stopping the search service, deleting the corrupt index database, and rebuilding it cleanly. Follow these steps in order.
Step 1: Stop the Windows Search Service
- Open the Services console
Press Win + R, typeservices.msc, and press Enter. - Locate Windows Search
Scroll down to Windows Search. Right-click and select Stop. The service status changes to Stopped. - Keep the Services window open
Do not close it yet. You will restart the service later.
Step 2: Delete the Corrupt Index Database
- Open File Explorer
Press Win + E. - Navigate to the index folder
Paste this path into the address bar:C:\ProgramData\Microsoft\Search\Data\Applications\Windows. Press Enter. - Delete the Windows.edb file
Select the file named Windows.edb. Press Shift + Delete to permanently remove it. Confirm the deletion if prompted.
Step 3: Restart the Search Service
- Return to the Services console
Switch back to the Services window you opened earlier. - Start Windows Search
Right-click Windows Search and select Start. The service status changes to Running. - Allow indexing to complete
The indexer will rebuild the database from scratch. This process can take 10 to 30 minutes depending on your file count. During this time, CPU usage may be high but should drop to normal after the rebuild finishes.
Step 4: Verify the Fix
- Open Task Manager
Press Ctrl + Shift + Escape. - Check SearchHost.exe CPU usage
Find SearchHost in the Processes tab. Its CPU column should show less than 5 percent after the index rebuild completes. - Test search
Click the Start button and type a file name. The search results should appear instantly without system lag.
If SearchHost Still Uses 100 Percent CPU After Rebuilding the Index
Windows 11 search indexer keeps restarting every few seconds
If the indexer repeatedly stops and starts, a third-party antivirus or a corrupt system file may be interfering. Run the System File Checker to repair Windows files. Open Command Prompt as administrator and run sfc /scannow. After completion, restart your PC and check the CPU usage again.
SearchHost.exe shows high CPU after every Windows update
Some cumulative updates reset the search index or add new indexing locations. After a major update, the indexer may re-index all files. This is expected behavior and usually resolves within one hour. If the high CPU persists for more than two hours, repeat the index deletion steps above.
CPU usage spikes only when typing in the Start menu search box
This indicates that the indexer is actively searching a very large index. To reduce the index size, limit the locations Windows Search indexes. Go to Settings > Privacy & security > Searching Windows. Under Find My Files, select Classic instead of Enhanced. Classic mode indexes only your Libraries and Desktop, which significantly reduces the index size.
SearchHost.exe vs SearchIndexer.exe: CPU Usage Differences
| Item | SearchHost.exe | SearchIndexer.exe |
|---|---|---|
| Description | UI process for the Start menu search bar | Background service that builds and maintains the search index |
| Normal CPU usage | 0 to 2 percent when idle | 0 to 5 percent during idle, up to 30 percent during indexing |
| High CPU trigger | Corrupt index or very large index set | Corrupt index, disk errors, or post-update re-indexing |
| How to stop it | End task in Task Manager (temporarily) | Stop Windows Search service in Services console |
| Permanent fix | Rebuild the index or reduce index scope | Delete Windows.edb and restart the service |
Conclusion
You now know that SearchHost.exe spikes to 100 percent CPU on eight cores due to a corrupt search index database or an excessively large index set. The reliable fix is to stop the Windows Search service, delete the Windows.edb file, and let the index rebuild from scratch. To prevent recurrence, limit indexing to Classic mode in Settings > Privacy & security > Searching Windows. For advanced control, you can use Group Policy to disable indexing on specific drives entirely.