Skip to content

Windows 11 & Server: Disable Search Indexing (SearchIndexer.exe)

SearchIndexer.exe shows up in Task Manager grinding away at the disk, and on a VM it never seems to stop. Search indexing is a background service that crawls files, e-mail, and app content to make Windows Search fast — useful on a daily driver, but on a headless VM, an RDP jump box, or a lab machine nobody ever searches, it burns CPU cycles, I/O, and disk space for nothing. Microsoft draws the same conclusion: on Windows Server, the service is disabled by default, partly because indexing causes problems on Remote Desktop Session Hosts with multiple simultaneous sessions.

The service behind it is Windows Search, service name WSearch. Disabling it is fully reversible.

Prerequisites

  • Local administrator rights on the machine
  • An elevated PowerShell or Command Prompt (right-click → Run as administrator)

What You Lose Without the Index

Windows Search keeps working without the service — it just gets slow and shallow. Knowing the trade-off up front saves a confused troubleshooting session three months later:

  • File Explorer search falls back to a real-time scan of the folder you are in. Results are complete but take much longer on large directory trees, and file content is no longer searched.
  • Start menu search still finds apps and settings without the indexer.
  • Classic Outlook is the real casualty: Instant Search is built on the Windows Search index. With the service disabled, mailbox search is degraded or returns nothing.

Skip this on machines with classic Outlook

If anyone uses classic Outlook (or heavy File Explorer content search) on the machine, leave the indexer running. This guide is aimed at VMs and servers where nobody searches locally.

Disable the Service (Windows 11)

Disable the startup type first, then stop the service — WSearch is configured to restart itself, so a stopped but still-enabled service comes back on its own.

Option A: PowerShell

Set-Service -Name WSearch -StartupType Disabled
Stop-Service -Name WSearch

Option B: Command Prompt

The space after start= is not a typo — sc.exe requires it; without the space the command fails.

sc.exe config wsearch start= disabled
net stop wsearch

Windows Server

Nothing to do in most cases: since Windows Server 2016, WSearch ships disabled by default. It only runs if someone enabled it manually or installed the Windows Search Service feature (occasionally done on file servers to provide indexed search for network shares). Check the current state:

Get-Service -Name WSearch | Format-List Status, StartType

If it reports anything other than Stopped / Disabled, the commands from the Windows 11 section above apply unchanged.

Optional: Reclaim the Disk Space

The index database lives in C:\ProgramData\Microsoft\Search\Data — Windows.db on Windows 11, Windows.edb on Windows 10/Server (file locations). Depending on how much was indexed, this can be hundreds of MB to several GB. With the service disabled you can delete it safely; Windows rebuilds it from scratch if you ever re-enable the service.

Remove-Item -Path "C:\ProgramData\Microsoft\Search\Data" -Recurse -Force

Verify

Get-Service -Name WSearch | Format-List Status, StartType

Expected output: Status: Stopped and StartType: Disabled. Task Manager should no longer list SearchIndexer.exe, and after the next reboot it must not reappear.

Re-Enable Search Indexing

To restore the default behaviour, re-enable the service with the delayed automatic start Windows uses out of the box:

Set-Service -Name WSearch -StartupType AutomaticDelayedStart
Start-Service -Name WSearch

The index rebuilds in the background; expect elevated disk activity until it finishes.