# SearchProtocolHost.exe

Windows Process: Microsoft Corporation

Also called searchprotocolhost, search protocol host

Windows, System Component

Windows Search protocol handler host. It loads ISearchProtocol handlers to crawl URIs. SearchIndexer.exe writes the catalog. SearchFilterHost.exe loads IFilters.

## What you need to know

Protocol host crawls. It does not write the catalog and does not load IFilters.

SearchProtocolHost.exe is the Windows Search protocol handler host. It opens file, MAPI, and other URI protocols so the indexer can see items. SearchIndexer.exe writes the catalog. SearchFilterHost.exe isolates IFilters. SearchApp.exe is UI.

- **Safe?**: Yes, with Windows Search

  **Does it write the index?**: No. SearchIndexer does

  **Does it load IFilters?**: No. SearchFilterHost does

Feex says

If I see SearchProtocolHost busy after I added a folder, I check Indexing Options first. I rebuild the catalog last, and I do not blame SearchFilterHost for a crawl.

## What is SearchProtocolHost.exe?

SearchProtocolHost.exe is the protocol handler host. It loads ISearchProtocol implementations to crawl URIs. It does not write the catalog. SearchIndexer.exe does that. It does not load IFilters. SearchFilterHost.exe does that.

## What does it do?

It enumerates items through protocol handlers (file system, Outlook, custom handlers). Parsed text still goes through the filter host. The catalog write is the indexer.

## Why is it running?

WSearch is crawling a location you included, a new PST, or a URI a protocol handler owns. Disk here is the crawl, not SearchApp drawing suggestions.

## Why are there multiple copies?

More than one protocol host can crawl different URIs at once. None of those copies write the catalog. SearchIndexer.exe does that.

## Is it safe?

Usually safe

System32 SearchProtocolHost.exe is the crawl host. A copy in a "speed up search" zip is not. This file still does not write the catalog and still does not load IFilters.

A legitimate copy normally runs from:

`C:\Windows\System32\SearchProtocolHost.exe`

- Expected publisher: Microsoft Corporation
- Catalog writer: SearchIndexer.exe
- IFilter host: SearchFilterHost.exe

## Can I end it?

The crawl pauses

Ending SearchProtocolHost.exe stops that protocol crawl until the indexer starts another host. It does not wipe the catalog. It does not unload IFilters in SearchFilterHost.

## Can I remove it?

No

Do not delete SearchProtocolHost.exe. Remove a location in Indexing Options if you want less crawling. Disable WSearch only if you accept unindexed search.

## Should it start with Windows?

WSearch starts protocol hosts on demand. This is not a Startup Apps row next to SearchApp.

## Normal resource behavior

These are contextual labels, not universal averages.

- **CPU**: Rises while a protocol handler enumerates a large URI space

  **Memory**: Moderate during a deep crawl

  **Disk**: Reads from the crawled location. Catalog writes are the indexer

  **Network**: UNC or other remote protocol handlers

## File information

| Executable name        | SearchProtocolHost.exe                     |
| ---------------------- | ------------------------------------------ |
| Common legitimate path | C:\Windows\System32\SearchProtocolHost.exe |
| Publisher              | Microsoft Corporation                      |
| Signature expectation  | Signed by Microsoft Windows                |

## Common problems

### High disk blamed on SearchFilterHost

Filter CPU is content parsing. Protocol-host disk is walking folders and mail stores. Split those in Resource Monitor.

### Outlook crawl never ends

A MAPI protocol handler can keep this host busy. Reduce Outlook indexing in Indexing Options before you rebuild.

## Troubleshooting

Diagnose before you change anything destructive.

### Trim Indexing Options locations first

Drop the huge folder or the stale UNC. That stops the protocol host without touching IFilters.

### Rebuild the index last

A rebuild restarts crawls and filters. Use it after you fix locations or a broken protocol handler, not as click one.

## Technical details

Technical details

| Image name | SearchProtocolHost.exe     |
| ---------- | -------------------------- |
| Role       | ISearchProtocol crawl host |

## Related

These entities connect to this article. Type is shown on every link.

[SearchIndexer.exe: Windows Process](https://feex.it/wiki/process/searchindexer.exe)[SearchFilterHost.exe: Windows Process](https://feex.it/wiki/process/searchfilterhost.exe)[Windows Search: Windows Service](https://feex.it/wiki/service/windows-search)

## Sources and verification

Reviewed by Feex editorial. Last verified August 2026 Status: Feex Reviewed. [How we research](https://feex.it/wiki/research).

- [Microsoft Learn: protocol handlers ](https://learn.microsoft.com/windows/win32/search/-search-3x-wds-extendingindexing-developing-protocol-handlers)· ISearchProtocol hosts crawl URIs
- [Microsoft Support: search indexing ](https://support.microsoft.com/windows/search-indexing-in-windows)· Locations and rebuild belong to the indexer
- [Foxhole process map ](https://foxhole.feex.it/)· First-party samples on Windows PCs. Not a lab benchmark.

## Was this article useful?

A yes or no is enough. Pick a reason if you want, or add a short note.

Quick facts

The short identity of this page. Specs, sources, and the full story stay in the article.

- **Type**: Windows Process

  **Publisher**: Microsoft Corporation

  **Executable**: SearchProtocolHost.exe

  **Typical path**: C:\Windows\System32\SearchProtocolHost.exe

  **Mapped by Feex**: Seen on Windows PCs in Foxhole

  **Related process**: [SearchIndexer.exe](https://feex.it/wiki/process/searchindexer.exe)

Feex Reviewed: Last verified August 2026

---

Source: [Canonical Feex Wiki page](https://feex.it/wiki/process/searchprotocolhost.exe/)

[Developer guide](https://feex.it/wiki/developers/) | [API policy](https://feex.it/developers/api-policy/) | [Agent guidance](https://feex.it/wiki/llms.txt)