When the Windows 11 search box stops working — blank results, the panel won’t open, typing does nothing, or it crashes instantly — it feels like a small problem until you realize how much you depend on it. The good news: Windows Search is a self-contained set of processes and a database, and nearly every failure is one of a handful of repeat causes: a hung SearchHost.exe process, a corrupt search index, broken components after an update, or services that got disabled.
Start with the quick wins. A hung search process restarts in seconds; a corrupt index takes hours to rebuild, so you want to rule out the fast fixes before committing to the slow ones. If search is also eating CPU while broken, our guide on SearchApp high CPU usage covers that variant; for the update-specific angle, see search not working in 24H2 .
Why this happens
- Hung or crashed SearchHost.exe: The search UI process hangs and stops responding to input — the most common cause, and the fastest to fix.
- Corrupt search index: The index database that powers instant results gets damaged, returning nothing or crashing the search panel.
- Broken components after a Windows update: Updates replace search files and reset indexing options; a bad update breaks search outright.
- Disabled Windows Search service: The underlying
WSearchservice gets disabled by “optimization” guides or debloating tools. - Third-party debloaters and “privacy” tools: Scripts that rip out Cortana, Bing integration, or search components break dependencies search needs.
- Corrupt user profile: Search works in a new account but not yours — the profile’s search data is damaged.
- Conflicting shell extensions or Start menu mods: Third-party Start menu replacements and shell tweaks hook into search and break it.
How to fix it
Work through these in order — diagnose first, then act.
Fix 1: Restart the SearchHost.exe process
Thirty seconds, fixes the majority of “search does nothing” cases.
- Press Ctrl + Shift + Esc to open Task Manager.
- Go to the Details tab and find SearchHost.exe.
- Right-click it and choose End task. Windows relaunches it automatically within seconds.
- Press Win + S and test. If search works now, the process had simply hung.
Fix 2: Restart the Windows Search service
The engine behind the UI.
- Press Win + R, type
services.msc, and press Enter. - Find Windows Search in the list. If its status is blank or Stopped, double-click it.
- Set Startup type to Automatic (Delayed Start) and click Start.
- If it was already running, right-click and choose Restart. Test search again — a stale service state clears with a restart.
Fix 3: Run the Search and Indexing troubleshooter
Let Windows diagnose its own search stack.
- Open Settings > System > Troubleshoot > Other troubleshooters.
- Run the Search and Indexing troubleshooter.
- Check the boxes matching your symptom (e.g. “Files don’t appear in search results”) and let it apply fixes.
- Test search. The troubleshooter commonly restarts services and repairs permissions you’d otherwise fix manually.
Fix 4: Rebuild the search index
For corrupt-index symptoms: empty results, missing files, or search that worked yesterday.
- Open Control Panel > Indexing Options (switch to Large icons if you don’t see it).
- Click Advanced, then under Troubleshooting click Rebuild.
- Confirm. The rebuild runs in the background — expect several hours on a full drive, during which results will be incomplete.
- Keep the laptop plugged in and powered on until Indexing Options shows “Indexing complete.” Then test with a filename you know exists.
Fix 5: Toggle search highlights and online integration
Bing integration and highlights are frequent breakage points.
- Open Settings > Privacy & security > Search permissions.
- Under Cloud content search, toggle Microsoft account and Work or School account off, test search, then toggle back on if you want them.
- In Settings > Privacy & security > Search (Windows permissions), toggle Show search highlights off and test.
- If search works with cloud content off, the problem is the online component — leave it off or sign out and back into your Microsoft account to refresh its tokens.
Fix 6: Re-register the search app package
Repairs broken search components after updates.
- Open Terminal (Admin) or PowerShell (Admin).
- Run:
Get-AppXPackage -AllUsers -Name Microsoft.Windows.Search | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml"} - Wait for completion (red “already registered” warnings are normal).
- Restart and test. This restores search files that updates sometimes leave in a broken state.
Fix 7: Test in a new user account
Isolates profile corruption quickly.
- Go to Settings > Accounts > Other users > Add account and create a local account.
- Sign into it and press Win + S. If search works there, your main profile’s search data is corrupt.
- You can try deleting the corrupt search database in the old profile (
%USERPROFILE%\AppData\Local\Packages\Microsoft.Windows.Search_cw5n1h2txyewy), but migrating to the new account is more reliable. - If search fails in the new account too, the problem is system-wide — continue to Fix 8.
Fix 8: Repair system files and check for bad updates
The last-resort software layer.
- Open Terminal (Admin). Run
sfc /scannow, thenDISM /Online /Cleanup-Image /RestoreHealth, and restart. - If search broke right after an update, go to Settings > Windows Update > Update history > Uninstall updates and remove the most recent quality update, then test.
- Check Microsoft’s support site for known search issues with your Windows build before reinstalling the update.
- If you previously ran a debloating script, consider an in-place upgrade repair (Windows 11 ISO > setup > Keep personal files and apps) to restore removed components properly.
Closing
Windows Search failures are annoying but shallow — a hung process, a corrupt index, or a broken component, in that order of likelihood. Work the quick fixes first (process restart, service restart, troubleshooter) before committing to the index rebuild, and resist “fixes” that involve registry hacks from random forums; the supported steps above resolve essentially every search failure without risking the rest of the system.
