Windows 11 search not working is particularly disruptive because search is woven into so much of how the operating system works — finding files, launching apps, accessing Settings. When it breaks, you notice immediately. You’ll find the complete rundown in our Complete Guide to Fixing Windows, Browser, and Software Errors.
The most important thing to understand first: not all search failures are the same problem. The search box might accept text but return nothing. It might not respond to clicks at all. It might work for apps but not for files. Each of these is a different failure with a different fix.
If the search box doesn’t respond to clicking: The SearchApp.exe process has hung. Task Manager → find “Search” → End task → it restarts automatically. Test immediately.
If search accepts typing but returns no results: The index is corrupted or incomplete. Fix 2 (rebuild the index) is the correct fix.
If apps appear in search but files don’t: The file indexing scope is too narrow. Fix 4 covers this.
If everything worked and then stopped after a Windows Update: Check Fix 5 — this is a specific regression pattern with its own fix path.
Fix 1: Restart the Search Process
This takes 30 seconds and fixes the “search box does nothing when I click it” problem specifically. Ctrl + Shift + Esc → Task Manager → Processes tab → find “Search” or “Windows Search” → right-click → End task. Windows restarts SearchApp.exe automatically. Click the search box to test.
If it keeps hanging: check whether CTF Loader (ctfmon.exe) is running. This handles text input services that the search bar depends on. Task Manager → look for ctfmon.exe. If it’s absent: Win + R → ctfmon.exe → Enter. The search bar typically accepts input immediately after ctfmon.exe starts.
Fix 2: Rebuild the Search Index
The search index is a database Windows maintains so searches return results instantly rather than scanning the disk in real time. When this index becomes corrupted — which happens after crashed updates, unexpected shutdowns, and sometimes for no obvious reason — searches either return nothing or return wildly incorrect results.
Rebuilding it from scratch is the definitive fix for “search accepts input but returns no results.” Search for “Indexing Options” in Start → Advanced → Rebuild → OK → confirm. The dialog shows the document count rising as it indexes. During the rebuild (which takes 30 minutes to a few hours depending on file count), search results will be partial or empty — this is expected. Full search functionality returns when the count stabilises.
After rebuilding, also check what’s being indexed: Indexing Options → Modify → confirm the folders you need to search are included. By default, Libraries (Documents, Music, Pictures, Videos) and user profile folders are indexed, but if files are stored outside these locations they won’t appear in search results.
Fix 3: Windows Search Service
The Windows Search service (WSearch) must be running and configured to start automatically. When it’s stopped or set to Disabled — which some system optimisation tools do — search returns no results or the search bar doesn’t open at all.
Win + R → services.msc → find “Windows Search” → right-click → Properties. Startup type must be “Automatic (Delayed Start)” and Status should be “Running.” If it’s set to Disabled or Manual, change the Startup type → Apply → then right-click → Start. After starting the service, rebuild the index (Fix 2) because a stopped service means the index wasn’t being maintained.
Fix 4: Expand the Indexed Locations
If searching for files returns nothing even when you know the files exist: the files are stored somewhere that isn’t in the search index scope. Search only returns results for indexed locations by default.
Indexing Options → Modify → look at the “Indexed Locations” list. If the folders containing your files aren’t there, click “Show all locations” → navigate to and check the folders you want indexed. Large network drives and external drives are typically not indexed by default. After adding locations, wait for the indexer to process them — the item count in Indexing Options shows progress.
Alternatively: switching from Classic search mode to Enhanced mode indexes the entire machine. Search for “Searching Windows” in Settings → Find My Files → change from “Classic” to “Enhanced.” Enhanced mode indexes all fixed drives, making all local files searchable at the cost of slightly longer initial indexing time and a marginally larger index database.
Fix 5: After a Windows Update Broke Search
Windows Updates sometimes introduce search regressions — particularly major feature updates. If search worked and then broke immediately after an update, a few targeted fixes often resolve update-induced search failures before resorting to update rollback.
Run the PowerShell re-registration for search components:
Get-AppxPackage -AllUsers Microsoft.Windows.Search | Reset-AppxPackageOpen PowerShell as administrator and run this. It resets the search app package registration to its correct state, which update-related damage often corrupts. After running it, sign out and back in to your Windows account, then test search.
If that doesn’t resolve it: Settings → Windows Update → Update history → check the date of the update → search the KB number online to see whether Microsoft has documented a search regression and a specific fix. Microsoft typically patches major regressions in the next cumulative update, which usually arrives within two to four weeks of the problematic release.
Fix 6: SFC for System File Corruption
Corrupted Windows system files cause search failures when the affected files are ones the search service depends on. SFC repairs these:
sfc /scannowRun from administrator Command Prompt. If it reports “found corrupt files and repaired them” — system file corruption was involved in the search failure. Restart after completion and test search. Also run DISM beforehand for thoroughness:
DISM /Online /Cleanup-Image /RestoreHealthCortana vs Windows Search
Windows 11 significantly reduced Cortana’s role — the Windows 11 taskbar search box is now purely Windows Search, not Cortana. If someone told you to restart Cortana to fix search: that advice applied to Windows 10. On Windows 11, the component to restart is SearchApp.exe or SearchHost.exe, not Cortana. Disabling Cortana (which some older guides recommend) has no effect on Windows 11 taskbar search functionality.
Search in Specific Apps
When Windows-wide search works but search within a specific application doesn’t (Outlook email search, File Explorer search, SharePoint search in Teams), the problem is that application’s search implementation rather than Windows Search. Outlook maintains its own search index for email; File Explorer uses Windows Search for files but has its own quirks for network locations. These specific in-application search failures need app-specific troubleshooting rather than the Windows Search fixes above.
For Outlook search specifically: File → Options → Search → Indexing Options → Advanced → Rebuild (rebuilds Outlook’s portion of the Windows search index). For File Explorer search not finding files on network drives: network locations are typically not indexed — searching with “This PC” scope rather than a specific network folder may return results, or you can add the network location to the Windows search index if it’s frequently accessed.
Firewall Blocking the Search Service
Windows Defender Firewall occasionally blocks the Windows Search service’s network access — which affects search’s ability to display online results (Bing integration) and to index cloud-hosted content. The symptom: search returns local file and app results but no online suggestions and no content from cloud-synced folders.
Check: search for “Allow an app through Windows Firewall” → Change settings → look for “Windows Search” → confirm both Private and Public are checked. If Windows Search isn’t in the list, adding it (Allow another app → browse to SearchUI.exe in system applications folder) restores its network access.
Our guide on Windows 11 taskbar not working covers the Explorer and shell process issues that accompany search failures when both stop working together — the Explorer restart from that guide sometimes resolves search problems simultaneously. For the Windows Update regression path, our Windows Update troubleshooting guide covers the update rollback process if the search regression persists across multiple update cycles. Microsoft’s Windows 11 search documentation covers the Group Policy settings that affect search behaviour in managed corporate environments, including the settings that restrict Bing integration or limit search scope.
Search Not Finding Apps
Windows search failing to find installed applications — where typing “Chrome” or “Word” returns nothing — is a specific failure involving the Start menu app registration rather than the file indexing system. Apps are indexed separately from files, through the application registration database rather than the NTFS indexing service.
Fix: run the PowerShell re-registration for Start menu apps (which also fixes app search):
Get-AppxPackage -AllUsers | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)AppxManifest.xml" -ErrorAction SilentlyContinue}This re-registers all installed apps with Windows. It takes a minute to run and requires a restart after completion. After the restart, Start menu and search app results should restore. Note that this command generates errors for some packages (shown in the PowerShell window) — these are normal and can be ignored as long as the command completes.
Search History and Suggestions
Windows search maintains a history of recent searches and shows suggestions based on previous searches as you type. When this history becomes corrupted, search may show no suggestions, show suggestions from years ago, or show suggestions that don’t match anything you’ve recently searched for.
Clear search history: Settings → Privacy and security → Search permissions → clear Search history. This wipes the stored search history and forces the suggestion system to rebuild from scratch. If search suggestions were the specific problem (appearing but being wrong), this is the targeted fix. Note that clearing search history also removes your recent search suggestions from the taskbar, which may take a few days to repopulate with useful suggestions as you use search normally.
Enterprise and Domain-Joined Search Behaviour
On machines joined to a corporate domain or managed via Microsoft Intune or Group Policy, Windows search behaviour can be significantly restricted by IT policy. Common enterprise search configurations: Bing results disabled from taskbar search (policies restrict web search in the taskbar), specific file locations excluded from indexing for data security reasons, or search confined to local machine only rather than SharePoint and OneDrive results.
Check active policies: run gpedit.msc → navigate to Computer Configuration → Administrative Templates → Windows Components → Search → look for any enabled policies. Or in Command Prompt: gpresult /h C:gpresult.html → open the HTML report → search for “Search” in the Applied Policies section. If enterprise policies are restricting search in ways that affect your work, contacting IT is the appropriate path — these policies are set for organisational security reasons and require admin access to modify.
Search Working After Manual Restart But Breaking Again
If Fix 1 (restarting the Search process) resolves the issue temporarily but search breaks again after every restart or after a few hours of use, a background service or application is interfering with SearchApp.exe’s continued operation.
Check Task Scheduler for tasks that might be stopping or modifying the search service: search “Task Scheduler” in Start → Task Scheduler Library → look for tasks related to “Search,” “Index,” or “Cortana” with frequent triggers. Some third-party system optimisation tools schedule tasks that disable Windows Search service to “speed up” the system — these scheduled disablements explain why search breaks repeatedly after being manually fixed.
Also check antivirus software for any “process protection” rules that block SearchApp.exe from running. Some endpoint protection products block processes on their suspicious applications list, and older or misconfigured security products occasionally flag Windows Search components. Adding SearchApp.exe and SearchHost.exe to the antivirus exclusions (specifically process execution exclusions, not just file scan exclusions) allows them to run without interference. Related: Windows 11 Pen Not Working.
Quick Search Tips for When It’s Working
A few Windows 11 search behaviours that aren’t failures but look like them:
- Searching by file content vs filename: Windows Search by default searches filenames and common metadata. Searching inside document content requires the document types to have their content indexed — Office documents are indexed by content, but PDFs need the Windows PDF filter to be installed for content indexing. If you search for text you know is inside a file and it doesn’t appear, check whether that file type has content indexing enabled: Indexing Options → Advanced → File Types tab → find the file extension → check whether “Index Properties and File Contents” is selected.
- Natural language queries: Windows search supports natural language, but results vary significantly. Searching “files modified this week” works better as a filter (search → right-click in File Explorer → filter by date modified) than as a natural language taskbar query.
- Network location search: Files on network drives, SharePoint, or mapped drives aren’t indexed by default and won’t appear in taskbar search results. Use File Explorer and navigate to the network location → use its search bar (which searches in real time without indexing) rather than expecting taskbar search to find network files.
