Windows 10 search has its own personality compared to Windows 11: it runs through SearchUI.exe, historically tangled up with Cortana, and it leans on Bing for web results in a way that can hang the entire results pane when the network hiccups. When it breaks, you get the familiar symptoms — type in the taskbar box and nothing happens, results never appear, or the search window opens blank.
The architecture matters for the fix: on Windows 10 you’re restarting SearchUI (not SearchHost), re-registering the Cortana package (not the Windows 11 search package), and dealing with Bing integration as a potential culprit. The steps below are built for exactly this setup.
Why this happens
- SearchUI.exe crashes: The search/Cortana UI process dies and doesn’t recover cleanly, leaving the taskbar search box dead.
- Corrupt search index: The index database gets damaged, so file and app searches return nothing or outdated results.
- Windows Search service disabled: Debloat scripts and “privacy” tools disable the indexing service, killing search.
- Bing integration hanging: The web-results pane waits on a network response that never comes, freezing the whole search UI.
- Cortana package corruption: SearchUI lives inside the Cortana app package; if its registration breaks, search breaks with it.
- Corrupt system files: Update or disk damage to search components.
- Profile-specific corruption: Search works in a new account but not yours — the per-user search database is damaged.
How to fix it
Work through these in order — the process restart and troubleshooter resolve most cases.
Fix 1: Restart the SearchUI process
The Windows 10 equivalent of the quick fix.
- Press Ctrl + Shift + Esc to open Task Manager.
- On the Processes tab, find Search (listed as Search/Cortana) — or go to Details and find
SearchUI.exe. - Right-click and choose End task. Windows restarts it automatically.
- Click the taskbar search box and test. If it was just a crashed process, you’re done in under a minute.
Fix 2: Run the Search and Indexing troubleshooter
Built-in diagnosis before manual surgery.
- Open Settings > Update & Security > Troubleshoot > Additional troubleshooters.
- Select Search and Indexing and click Run the troubleshooter.
- Tick the symptoms that match and apply its fixes.
- Microsoft documents further search repairs at Microsoft’s Windows support hub .
Fix 3: Verify the Windows Search service
Optimizer tools disable this constantly.
- Press Win + R, type
services.msc, press Enter. - Find Windows Search — set Startup type to Automatic (Delayed Start) and make sure it’s Running.
- If you recently ran a debloating or “privacy” script, review everything it changed — they often disable several services search depends on.
Fix 4: Rebuild the search index
For missing results, stale results, or new files never appearing.
- Open Control Panel > Indexing Options > Advanced > Rebuild.
- Let it run — it takes 30 minutes to several hours. Search will be incomplete meanwhile; that’s normal.
- When Indexing Options reports “Indexing complete,” test thoroughly: apps, settings, and files.
Fix 5: Disable Bing web results (if search hangs)
When the results pane freezes, Bing is often the anchor.
- Press Win + R, type
regedit, press Enter. - Navigate to
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Search. - Create a DWORD (32-bit) value named
BingSearchEnabledset to0. Also setCortanaConsentto0if present. - Restart
SearchUI.exevia Task Manager (Fix 1) and test. Local search becomes noticeably faster, and network hangs stop freezing results. - Only use this after confirming the basics work — it’s an optimization, not a repair for a dead SearchUI.
Fix 6: Re-register the Cortana/Search package
For a search box that won’t open or crashes instantly.
- Open PowerShell as administrator (Win + X > Windows PowerShell (Admin)).
- Run:
Get-AppXPackage -Name Microsoft.Windows.Cortana | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml"} - Ignore errors about already-registered components.
- Restart and test. This repairs the package registration updates sometimes damage.
Fix 7: Repair system files and install the latest cumulative update
Deeper corruption in search components — plus the updates that fix them.
- In an elevated PowerShell, run
sfc /scannow. - Then
DISM /Online /Cleanup-Image /RestoreHealth. - Restart.
- Then open Settings > Update & Security > Windows Update and install everything offered, including optional updates. Microsoft ships search fixes in cumulative updates — several notorious search breakages were fixed this way, and staying current is genuine prevention.
- After updating, re-run the troubleshooter (Fix 2) once, since updates sometimes reset the configurations it repairs.
- If the Start menu is misbehaving too, the Start menu fix guide covers the shared shell infrastructure.
Fix 8: Reset the per-user search data or try a new profile
Final isolation: profile vs. system.
- Stop the Windows Search service, then delete the contents of
C:\ProgramData\Microsoft\Search\Data\Applications\Windows. - Restart the service and let the index rebuild from scratch.
- If that fails, create a new local account (Settings > Accounts > Family & other users > Add someone else to this PC) and test search there.
- Working in the new account means your old profile’s search data is unrecoverable — migrate your files over.
Closing
Windows 10 search failures come down to its three moving parts: the SearchUI process, the index, and the Windows Search service — with Bing integration as the bonus troublemaker. Restart the process, verify the service, rebuild the index, and only then reach for package re-registration and profile surgery. Match the fix to the symptom and the taskbar search box goes back to being the fastest way to launch anything on your PC. On a Windows 11 machine the architecture differs (SearchHost instead of SearchUI), so use the Windows 11 search fix guide there instead of these steps.
And keep Windows Update current afterward. A surprising number of “search suddenly broke” cases are fixed by the very next cumulative update, because Microsoft keeps patching this subsystem. The troubleshooter plus an updated system resolves nearly everything this component can throw at you.
