# SearchFilterHost.exe

Windows Process: Microsoft Corporation

Also called searchfilterhost, search filter host, ifilter host

Windows, System Component

Windows Search IFilter host. It loads IFilters in isolation so a bad filter cannot kill the indexer. It is not SearchProtocolHost and not SearchApp.

## What you need to know

IFilter isolation host, not SearchProtocolHost and not SearchApp UI.

SearchFilterHost.exe loads IFilters so Windows Search can read PDF, Office, and other formats. Isolation means a crashing filter dies here instead of taking SearchIndexer.exe with it. SearchProtocolHost.exe crawls. SearchApp.exe is the search UI.

- **Safe?**: Yes. It isolates IFilters

  **Same as SearchProtocolHost?**: No. That one crawls URIs

  **Same as SearchApp?**: No. SearchApp is UI

Feex says

If SearchFilterHost vanishes and search misses PDF text, I look at the PDF IFilter. I do not rebuild because SearchApp looked busy.

## What is SearchFilterHost.exe?

SearchFilterHost.exe is the IFilter isolation host. A crashing PDF or Office filter dies here so SearchIndexer.exe can continue. It is not SearchProtocolHost.exe, which crawls URIs, and it is not SearchApp.exe, which is the search UI.

## What does it do?

It loads IFilter DLLs and returns extracted text. It does not write the catalog and it does not draw Start search.

## Why is it running?

The indexer found a file type that needs a filter. A storm of new Office or PDF files will keep this host busy. A quiet filter host with a loud SearchApp is UI, not parsing.

## Why are there multiple copies?

A second filter host can appear when another IFilter is isolated. That is still not SearchProtocolHost and not SearchApp.

## Is it safe?

Usually safe

System32 SearchFilterHost.exe is the IFilter host. A filter host in Temp is not. Crashes here point at a vendor IFilter, not at SearchApp.

A legitimate copy normally runs from:

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

- IFilter isolation is the point
- Protocol crawl is SearchProtocolHost.exe
- UI is SearchApp.exe or SearchHost.exe

## Can I end it?

Those file types go unparsed

Ending SearchFilterHost.exe drops in-flight filters. The indexer can start another host. SearchApp can still open. The catalog writer is still SearchIndexer.exe.

## Can I remove it?

No

Do not delete SearchFilterHost.exe. Uninstall a bad third-party IFilter if PDF or Office parsing crashes the host. Leave the System32 isolation host in place.

## Should it start with Windows?

WSearch starts filter hosts when a file needs parsing. Not a Startup Apps checkbox.

## Normal resource behavior

These are contextual labels, not universal averages.

- **CPU**: A heavy IFilter on a large PDF or PST attachment

  **Memory**: Follows the filter. Leaks are often the vendor DLL

  **Disk**: Reads file content. Catalog writes stay with the indexer

  **Network**: Only if the file is on a remote path already opened by the crawl

## File information

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

## Common problems

### Repeated filter-host crashes

Event Viewer often names the IFilter DLL. Adobe, a PDF printer, or an old Office filter are usual. SearchApp crashing is a different stack.

### People disable WSearch to stop this host

That also stops SearchProtocolHost and SearchIndexer. Remove the bad filter first.

## Troubleshooting

Diagnose before you change anything destructive.

### Identify the IFilter that crashed

Application log and the modules in this host. Repair or remove that filter. Do not restart SearchProtocolHost to fix a parse crash.

### Do not treat SearchApp CPU as a filter problem

Suggestions and the flyout are UI. Content extraction is this host. Rebuild only after the filter is stable.

## Technical details

Technical details

| Image name | SearchFilterHost.exe   |
| ---------- | ---------------------- |
| Role       | IFilter isolation 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)[SearchProtocolHost.exe: Windows Process](https://feex.it/wiki/process/searchprotocolhost.exe)[SearchApp.exe: Windows Process](https://feex.it/wiki/process/searchapp.exe)

## Sources and verification

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

- [Microsoft Learn: IFilter ](https://learn.microsoft.com/windows/win32/search/-search-ifilter-about)· IFilters extract text for the indexer
- [Microsoft Learn: Windows Search overview ](https://learn.microsoft.com/windows/win32/search/-search-3x-wds-overview)· Indexer, protocols, and filters are separate hosts
- [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**: SearchFilterHost.exe

  **Typical path**: C:\Windows\System32\SearchFilterHost.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/searchfilterhost.exe/)

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