How to Fix Windows 11 Search Bar Not Working & SearchIndexer.exe High CPU Usage (2026 Guide)

When Windows 11 Search Freezes: Symptoms and Mechanics

The search bar is the central navigation hub of Windows 11. Whether you are launching an application, locating a spreadsheet buried across subdirectories, or adjusting a system setting, pressing the Windows key and typing is the fastest path through the operating system. However, when the search subsystem breaks down, users typically experience two distinct, equally frustrating failure modes:

1. Unresponsive Search Interface: Clicking the taskbar magnifying glass or pressing Win + S produces no response, leaves a blank gray window, or freezes the Start Menu indefinitely.
2. SearchIndexer.exe Resource Hogging: The background indexing daemon (SearchIndexer.exe) consumes 40% to 100% of your CPU capacity and constantly thrashes your NVMe SSD, spinning laptop cooling fans to maximum RPM even when the computer is completely idle.

Both problems trace back to the identical architectural bottleneck: the Windows Extensible Storage Engine (ESE) database located in C:\ProgramData\Microsoft\Search\Data\Applications\Windows\Windows.edb. When this database suffers corruption due to an unexpected reboot or an indexing loop across thousands of temporary developer files, the entire search pipeline locks up.

Method 1: Force Terminate the Frozen SearchHost.exe Process

In Windows 11, the search user interface is rendered by a dedicated background package named SearchHost.exe (part of the Microsoft Windows Search application). When the interface becomes unresponsive, killing this process forces Windows to spawn a fresh, responsive instance:

1. Press Ctrl + Shift + Esc to launch Task Manager.
2. Switch to the Details tab.
3. Scroll down alphabetically to locate SearchHost.exe.
4. Right-click SearchHost.exe and select End process tree.

Alternatively, you can terminate it instantly from an elevated Command Prompt or PowerShell terminal:

The moment you click the taskbar search bar or press Win + S, Windows will automatically restart SearchHost.exe with a clear memory buffer, restoring immediate responsiveness.

Method 2: Launch the Hidden Search & Indexing Diagnostic Utility

Windows includes a dedicated, scriptable troubleshooting package designed to repair search service permissions, fix broken registry keys, and restart the background indexing service:

1. Press Win + R to open the Run dialog.
2. Type or paste the following diagnostic command and press Enter:

3. In the wizard that appears, click Advanced and check Apply repairs automatically, then click Next.
4. Check the boxes corresponding to your exact symptoms, such as "Files, folders, apps, or settings don't appear in results" or "Search or indexing is slowing down the computer".
5. Click Next to allow the tool to repair permissions on C:\ProgramData\Microsoft\Search and restart the WSearch daemon.

Method 3: Rebuild the Entire Search Index Catalog

If your search bar functions but fails to find files, or if SearchIndexer.exe continuously maxes out your processor and storage bandwidth, the search database (Windows.edb) is corrupted. Rebuilding the database purges the corrupt file and builds a clean index from scratch:

1. Press Win + R, type control.exe srchadmin.msc, and press Enter to launch Indexing Options.
2. In the Indexing Options window, click Advanced (requires administrator authorization).
3. Under the Index Settings tab, locate the Troubleshooting section.
4. Click the Rebuild button.
5. A confirmation prompt will warn that rebuilding the index may take several hours to complete. Click OK.

Windows will delete the corrupted database and rescan your configured locations in the background. While the rescan runs, searches may be incomplete, but CPU usage will normalize once the index completes.

Method 4: Re-register the Windows Search AppX Package

If the search bar remains completely non-interactive or clicking the magnifying glass produces zero visual output, the underlying Universal Windows Platform (UWP) package has suffered file registration corruption. Re-register it via PowerShell:

1. Right-click the Start Menu and select Terminal (Admin).
2. Ensure you are in a PowerShell console, then paste and execute the following command:

Press Enter. PowerShell will re-register the search package manifests across all local user accounts in five to ten seconds. Once complete, restart your machine.

Method 5: Exclude Heavy Developer Folders to Stop High CPU Loops

One of the most widespread causes of SearchIndexer.exe pinning CPU cores at 100% capacity is allowing the indexing engine to crawl deep programming repositories. A single modern web or Python project can contain hundreds of thousands of files inside node_modules, .git, or venv directories. Because these files update dynamically, SearchIndexer enters an unending loop of indexing, invalidation, and re-indexing:

1. Open Indexing Options (control.exe srchadmin.msc).
2. Click Modify at the bottom left.
3. Click Show all locations.
4. Expand your user folder and uncheck directories containing source code repositories, large asset caches, or virtual machine images.
5. Click OK and Close.

Restricting search indexing strictly to your primary documents, desktop, and Start Menu cuts background CPU utilization to 0% and guarantees instant, responsive search queries across Windows 11.