Windows 11 Search Not Working? Here's How to Fix It

Windows Search breaking is one of those problems that feels disproportionately annoying, because so much of how you actually use Windows depends on it. You hit the Start button, type the name of an app or a file, and expect results instantly. When that stops working, everything from opening Settings to finding a document you saved five minutes ago suddenly takes twice as long. This guide walks through why it breaks, what's actually happening behind the scenes, and every fix worth trying, in the order that's most likely to solve your specific problem fastest.

What's Actually Running When You Search

Windows Search isn't one single program. It's a stack of several components working together, and knowing what each one does makes the troubleshooting steps below make a lot more sense.

The visible search box and results panel are handled by a process called SearchHost.exe. This is the part you actually see and interact with. Underneath that sits the Windows Search service, which manages a separate background process, SearchIndexer.exe, responsible for scanning your files and building a searchable catalog of everything on your drive, called the index. On top of both of those, Windows also registers a set of AppX packages tied to the search shell, and in more recent builds, layers in web-based results through Bing and a component called Search Highlights, which pulls in live content and depends on the Edge WebView2 runtime working correctly. That's four distinct layers: the UI host, the indexing service, the registered app packages, and the web content layer. A failure in any one of them can look identical from the outside, which is exactly why "my search bar doesn't work" can have such wildly different actual causes from one PC to the next.

The Three Ways Search Usually Breaks

Before jumping into fixes, it helps to identify which specific symptom you're dealing with, since that narrows down which layer is actually failing.

• The search box opens but the panel is empty or blank. This usually points to the UI rendering layer or a conflict with Search Highlights and WebView2, not the indexer itself.
• The search box doesn't respond to typing at all, or the icon does nothing when clicked. This typically means SearchHost.exe has crashed or hung, and needs to be manually restarted.
• Search opens and accepts input, but returns no results, or misses files you know exist. This is almost always an indexing problem, not a UI problem, and needs a different fix entirely.

Keep your specific symptom in mind as you work through the sections below, since it tells you where to start rather than working through every step in order regardless of relevance.

Quick Fix 1: Restart SearchHost.exe

This is the fastest fix, and it resolves a genuinely large share of cases, particularly the "box opens but doesn't respond" symptom. Open Task Manager with Ctrl+Shift+Esc, click the Details tab, find SearchHost.exe in the list, right-click it, and select End task. Confirm if prompted. You don't need to relaunch anything afterward. Windows automatically restarts the search host the next time you click the search icon or press the Windows key. If SearchHost.exe isn't listed at all, or the search icon has vanished entirely, that's a different problem, and you should skip ahead to the section on rebuilding the search shell itself.

Quick Fix 2: Restart File Explorer

Windows Search is more tightly coupled to the shell than most people realize, and a hung or corrupted Explorer process can drag the search UI down with it. In Task Manager, find Windows Explorer in the Processes tab, right-click it, and select Restart. Your taskbar and desktop icons will briefly disappear and reload. This clears a surprising number of transient UI faults, including cases where the search panel appears but won't accept any text input.

Quick Fix 3: Confirm Search Is Actually Enabled

Before assuming something's broken, rule out the simplest possible explanation: the search box itself might just be hidden by a setting. Go to Settings, then Personalization, then Taskbar, and check that Search is switched on under Taskbar items. It sounds too obvious to matter, but a Windows update occasionally resets this setting, and it's a five-second check that saves you from troubleshooting a problem that isn't actually there.

Run the Built-In Search and Indexing Troubleshooter

Windows ships with a dedicated automated tool built specifically to detect and fix common search and indexing problems, and it's worth running before moving into anything more advanced. Go to Settings, then Privacy and Security, then Troubleshoot, then Other troubleshooters, and run the one labeled Search and Indexing. Alternatively, open the Run dialog with Windows key plus R, type msdt.exe -id SearchDiagnostic, and press Enter to launch it directly. Let it scan and apply whatever fixes it identifies, then test your search again before moving further down this list.

Fix 4: Rebuild the Search Index

If search returns incomplete results, or misses files you know exist on your drive, the index itself is the problem, not the interface sitting on top of it. A corrupted or incomplete index needs to be rebuilt from scratch. Open Control Panel, go to Indexing Options, click Advanced, and select Rebuild under the Troubleshooting section. Be aware that this can take a genuinely long time, potentially several hours on a drive with a lot of files, and your search results will be incomplete the entire time it's running. Start this when you don't urgently need working search, ideally overnight, and let it finish completely rather than interrupting it partway through.

Fix 5: Check What's Actually Being Indexed

Sometimes search "not working" really means search is working correctly, but it's simply not looking where you expect it to. Windows doesn't index your entire drive by default, only specific locations. Still inside Indexing Options, review the list of included locations. If a folder you regularly search isn't listed, click Modify and add it manually. This is also worth checking if search feels sluggish or high on resource usage rather than broken outright: excluding drives you rarely search, like backup volumes or archive folders, reduces the indexer's workload without disabling search entirely.

Fix 6: Run SFC and DISM to Rule Out System Corruption

If search is failing across the entire system, not just for one app or one type of file, underlying corruption in core Windows files is a genuine possibility, and it's worth ruling out with Microsoft's own repair tools. Open an elevated Command Prompt (right-click Start, choose Terminal (Admin), or search for Command Prompt and run it as administrator), and run these three commands in order: DISM /Online /Cleanup-Image /ScanHealth
DISM /Online /Cleanup-Image /RestoreHealth
sfc /scannow Let each command run to completion before starting the next one, and don't close the window while sfc /scannow is verifying, since interrupting it partway through can leave your system in a worse state than before you started. Restart your PC once both commands finish, and test search again.

Fix 7: Reset Windows Search With PowerShell

Microsoft publishes an official PowerShell script specifically built to reset Windows Search back to its default state, and it's a genuinely reliable fix for cases where the search UI has become corrupted in a way basic restarts can't clear. First, open an elevated PowerShell window and check your current script execution policy by running Get-ExecutionPolicy. If it doesn't return Unrestricted, note the current value so you can restore it later, then run: Set-ExecutionPolicy -Scope CurrentUser -ExecutionPolicy Unrestricted Confirm the warning prompt with Y. From there, download Microsoft's official ResetWindowsSearchBox.ps1 script from the Microsoft Download Center, right-click the downloaded file, and select Run with PowerShell. Once it completes, restart your computer, and if you changed your execution policy earlier, set it back to its original value using the same Set-ExecutionPolicy command with the value you recorded.

Fix 8: Re-Register the Search App Package

Sometimes the search shell's own app registration becomes corrupted independently of everything else, which produces a specific symptom: SearchHost.exe launches and the window frame appears, but the content inside never actually renders. Open an elevated PowerShell window and run: Get-AppxPackage Microsoft.Windows.Search -AllUsers | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml"} Since the Start menu shell hosts the entry point to search, it's worth refreshing that registration at the same time: Get-AppxPackage Microsoft.Windows.StartMenuExperienceHost -AllUsers | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml"} Once both commands finish, go back to Task Manager, end the SearchHost.exe task, and test search again.

Fix 9: Clear Corrupted Search Data

Windows stores search-related data locally in your user profile, and if that folder itself becomes corrupted, no amount of resetting the shell or rebuilding the index will fully fix things, since the corrupted data just gets loaded right back in. First, stop the Windows Search service. Open services.msc from the Run dialog, find Windows Search in the list, right-click it, and select Stop. Then navigate to: %USERPROFILE%\AppData\Local\Packages\MicrosoftWindows.Client.CBS_cw5n1h2txyewy Rename this folder rather than deleting it outright, in case you need to restore it. Restart the Windows Search service, then sign out and back in, or restart your PC entirely. Windows will regenerate a fresh copy of this folder automatically.

Fix 10: Test With a New User Account

This step matters because it tells you whether the problem is specific to your user profile or affects the entire system, and that distinction changes what you should try next. Create a new local administrator account through Settings, then Accounts, then Other users. Sign into that new account and test search. If it works fine there, the problem is isolated to your original profile, and migrating your files to a fresh profile is often faster than continuing to chase the corruption inside the old one. If search is still broken on the new account too, the issue is system-wide, and you're likely dealing with a genuine software fault or a problematic Windows update, not anything specific to your personal profile.

When a Windows Update Is the Actual Cause

Sometimes none of the above is really your fault at all. Windows updates have occasionally shipped with regressions that break search specifically, leaving the box opening but empty, or unresponsive to typed input, across a wide range of otherwise healthy systems. If your search problems started immediately after installing a specific update, check Settings, then Windows Update, then Update History, to confirm the timing. If a recent update is the likely trigger, you can uninstall it by going to Windows Update, then Update History, then Uninstall updates, selecting the specific update, and removing it. This is a legitimate, if temporary, fix while waiting for Microsoft to ship a proper patch, and it's worth checking the Feedback Hub, under the Desktop Environment and Search categories, to see whether others are reporting the exact same regression tied to the same update.

Advanced Cause: Search Highlights and WebView2 Conflicts

If your search panel opens, shows the correct window frame, but the content area never actually paints anything, and you're on a recent or Insider build specifically, the cause is often a conflict between the Search Shell and the Microsoft Edge WebView2 runtime, which powers Search Highlights and Bing-integrated content inside the search panel. You can test this theory directly by disabling web-based search results. Go to Settings, then Privacy and Security, then Search Permissions, and turn off options related to Search Highlights and cloud content. If search starts rendering correctly with those disabled, you've confirmed the web content layer, not your local indexer, was the actual point of failure.

Frequently Asked Questions

Is it safe to end the SearchHost.exe process?

Yes. Ending SearchHost.exe simply closes the search interface temporarily. Windows automatically restarts it the next time you open search, and this action doesn't affect your files or your index.

How long does rebuilding the search index take?

It depends heavily on how much data is on your drive, but it can take anywhere from a couple of hours up to a full day on a drive with a large number of files. Start it when you don't need working search immediately, ideally overnight.

Why did search stop working right after a Windows update?

Certain updates have shipped with genuine regressions affecting the search shell specifically. Check your update history for the exact timing, and consider uninstalling the specific update if the timing lines up closely.

Does disabling Windows Search improve system performance?

It can reduce background CPU and memory usage on older or resource-constrained hardware, but it comes at the cost of losing local file search entirely. A better middle ground is narrowing what gets indexed, through Indexing Options, rather than disabling the service outright.

What if none of these fixes work?

At that point, an in-place repair install, or using Reset This PC with the Keep My Files option, is the most reliable remaining option. Back up anything important first regardless, since a repair install occasionally requires reinstalling some applications afterward.

The Bottom Line

Windows Search failures almost always trace back to one of four layers: the visible search host, the background indexing service, the registered app packages, or the newer web content layer tied to Search Highlights. Work through the fixes above roughly in order, starting with the quick restarts and moving toward the index rebuild, PowerShell reset, and system file repair only if the simpler steps don't resolve it. Matching your specific symptom, whether that's a blank panel, an unresponsive box, or missing results, to the right section above will get you to the actual fix far faster than trying every step in sequence regardless of relevance.

Also read: WhatsApp Verification Code Not Received? Here's What to Do