How the indexer works and when it becomes the problem
Windows Search is served by the WSearch service, whose visible face is SearchIndexer.exe. It crawls the locations you allowed — by default your document libraries and e-mail — and writes a database of names, content and metadata under %PROGRAMDATA%\Microsoft\Search\Data, commonly 1–10 GB on busy machines. Searching feels instant precisely because results come from this database instead of a live disk scan.
The indexer earns its CPU cycles honestly on a healthy system: a short spike after login, then silence. Problems start when the index is rebuilding, when Enhanced mode has it crawling an entire drive, or when the database is corrupted and the service loops. Then SearchIndexer.exe sits at a steady 10–30% CPU for hours, fans spin up, and laptops lose battery — that is the moment disabling is worth considering.
- SearchIndexer.exe holds a steady CPU share or pins the disk at 100% for hours
- The machine is an always-on low-power PC where even modest background load matters
- You never search inside files — only by name, and only occasionally
- The PC is a gaming or production box and you want zero background churn during sessions
- Enhanced indexing on a huge drive makes the indexer run hot day after day
Disabling the Windows Search service
Press Win+R, type services.msc and press Enter. Find Windows Search in the list, double-click it, press Stop and wait until the disk activity settles. Set Startup type to Disabled and click OK — indexing is now off for good. If you only want a break, choose Manual instead: the service then stays quiet until something explicitly calls it.
The command-line route is an elevated prompt with sc stop WSearch followed by sc config WSearch start= disabled — note the space after start=. Power users can also run Stop-Service WSearch and Set-Service WSearch -StartupType Disabled in PowerShell. To undo, set the service back to Automatic (Delayed Start is its default) and Windows resumes indexing where it left off.
What you lose — and lighter alternatives to a full shutdown
Be clear about the trade before flipping the switch. Start menu search still finds apps and settings, and File Explorer search still works — but it now scans folders live, returning results in seconds instead of instantly, and content search inside documents and e-mail bodies is gone. Outlook is hit hardest: its search rides entirely on the Windows index and will return nothing until the service returns.
Often you do not need the nuclear option. Switching Enhanced mode back to Classic in Settings → Privacy & security → Searching Windows cuts the crawl to your document folders. The Modify button in Control Panel → Indexing Options lets you drop heavy folders — games, video projects, virtual machine disks — from the index. And if the index is simply broken, rebuilding it from Indexing Options → Advanced usually fixes the runaway CPU without giving up instant search at all.
Questions and Answers
Will disabling Windows Search break the Start menu?
No. The Start menu keeps finding apps and settings; only file search degrades to slower live scanning, and content search inside files disappears.
How do I turn off search indexing temporarily?
In services.msc, stop the Windows Search service but leave Startup type as Manual or Automatic — the indexer then stays off until you reboot or start it again. Indexing Options also has a Pause button for short breaks.
Why is SearchIndexer.exe using so much CPU?
Usually an index rebuild in progress, Enhanced mode crawling a whole drive, or a corrupted index looping the service. Pause indexing, narrow the scope, or rebuild the index before disabling the service outright.
Know what is included before you buy.
The one-time 30-minute trial covers core tools. PRO-labelled features stay locked until a paid license is activated.
Read next
Write to us: [email protected]