How to Fix Windows Search Not Working in Windows 11

Introduction

Windows Search is one of those features you never think about until it stops working. When you press the Windows key and type an app name, a document, or a setting and nothing appears—or the search box just spins forever—your entire workflow grinds to a halt. This problem is surprisingly common in Windows 11, and it can affect home users, office desktops, and managed enterprise fleets alike. This guide covers How to Fix Windows Search Not Working in Windows 11 in practical, step-by-step detail, walking you through diagnosis, repair, and prevention. Whether you are a beginner who just wants the Start menu search back or an IT administrator responsible for hundreds of machines, the procedures below apply to both environments.

The root cause of a broken Windows Search is rarely a single thing. It can be a corrupted search index, a disabled Windows service, a failed cumulative update, a misconfigured Group Policy, or a damaged user profile. Because Windows Search relies on the SearchHost.exe process, the Windows Search service (WSearch), the search index database, and the Cortana/Search UI components working together, fixing it usually means checking each layer in turn. The good news is that most failures can be resolved within 15 to 45 minutes without reinstalling Windows.

It is important to note that fixing Windows Search is not the same as installing Linux software. There is no package manager, no command-line package repository, and no dependency tree to resolve. The “installation steps” in this article refer to installing, repairing, or re-registering the Windows Search components and, where relevant, deploying the fix across multiple machines using scripts or management tools. If you came here expecting apt, dnf, or pacman, you are in the wrong place—but the troubleshooting discipline is similar.

One more key fact to keep in mind: always verify software compatibility with your hardware architecture (ARM64 vs x86). A fix script or a third-party search utility built for x64 will not run correctly on an ARM64 device such as a Surface Pro X, and vice versa. Checking architecture before you deploy anything saves you from wasting time on fixes that were never going to apply.

Prerequisites

Before you touch anything, confirm that you meet the following baseline requirements. Skipping this section is the most common reason people waste an hour and still have a broken search box.

• Windows 11 build: Windows 11 21H2, 22H2, 23H2, or 24H2. Search behavior and the location of settings differ slightly between builds, so know yours. Run winver from the Run dialog to check.
• Administrator rights: Restarting services, rebuilding the index, and running DISM or SFC all require an elevated Command Prompt or PowerShell session. Beginners should right-click and choose “Run as administrator.”
• Architecture awareness: Determine whether your device is x64, ARM64, or (rarely) x86. Open Settings > System > About and read the “System type” line. This matters because some repair utilities, PowerShell modules, and third-party search replacements ship separate ARM64 and x64 builds.
• Up-to-date OS: Keeping your operating system updated before installation prevents dependency conflicts. A missing servicing stack update or a half-installed cumulative update is a classic cause of SearchHost.exe crashes.
• Local admin account: If the search failure is profile-specific, you will need a second account to test with. Know the credentials before you start.
• Backup (recommended): Create a restore point or ensure you have a recent system image. IT admins should confirm that the device is backed up through their standard tooling.
• Network access (for admins): If you plan to push fixes via Intune, Group Policy, or a PowerShell remoting session, verify connectivity and that the relevant ports and endpoints are reachable.

No prior Linux experience is required, and none of the fixes below assume familiarity with Bash, systemd, or package management. Everything here is native Windows tooling.

Preparation

Preparation is where you separate a clean fix from a messy one. Work through these items in order.

• Document the symptom: Does search fail only in the Start menu, only in File Explorer, or everywhere? Does the search box show “Working on it” indefinitely, return zero results, or crash to desktop? The symptom narrows the cause.
• Check recent changes: Look at Windows Update history, recently installed drivers, and any new endpoint security or third-party search tools. A fix that starts right after an update points to that update.
• Test a second user profile: Create or log into a different local account and try search there. If it works, the problem is profile-scoped; if not, it is system-wide.
• Disable third-party search modifiers: Tools such as Everything, Listary, or vendor search bars can conflict with Windows Search. Temporarily disable them rather than uninstalling outright.
• Open an elevated terminal: Launch Windows Terminal or Command Prompt as administrator. Keep it open for the duration.
• Note your architecture again: If you downloaded a repair script or a replacement search index tool, confirm it matches ARM64 or x86/x64 before running it.
• Schedule downtime: Rebuilding the index can pin CPU and disk for a while. Do this when the machine is not needed for time-sensitive work, or warn users in advance.

Installation Steps

Step 1: Review prerequisites and compatibility

Re-confirm the items from the Prerequisites and Preparation sections. Specifically, verify your Windows 11 build, your architecture (ARM64 vs x86), and that your OS is fully patched. Run winver and check Settings > Windows Update for pending updates. If an update is pending, install it and reboot before continuing—many search failures resolve at this point alone. For administrators, verify that the fix method you plan to use (script, Intune policy, or manual steps) is compatible with the target architecture and OS build.

Step 2: Prepare the environment

Open an elevated Command Prompt or PowerShell window. Create a restore point so you can roll back if needed:

• Press Windows key + R, type sysdm.cpl, and press Enter.
• Go to the System Protection tab and click Create.
• Name the restore point “Before Search Fix” and confirm.

Next, check the status of the key services. In the elevated terminal, run services.msc and locate Windows Search (WSearch) and Windows Push Notifications User Service. Note whether they are Running, Stopped, or Disabled. Also confirm that SearchIndexer.exe and SearchHost.exe appear in Task Manager. If a third-party search tool is installed, disable it now.

Step 3: Configure core settings

Before running repairs, correct the settings that commonly break search:

• Enable the Windows Search service: Set WSearch to Automatic and start it if it is stopped or disabled.
• Check index locations: Go to Settings > Privacy & security > Searching Windows. Ensure “Find my files” is set to Classic or Enhanced as appropriate, and confirm that the folders you care about are included in the index.
• Review Group Policy (admins): In gpedit.msc, navigate to Computer Configuration > Administrative Templates > Windows Components > Search. Make sure “Allow Cortana” and “Allow search and Cortana to use location” are not set in a way that disables search entirely. If the machine is domain-joined, check the equivalent Intune or GPO settings centrally.
• Verify indexing is not paused: In Indexing Options (control /name Microsoft.IndexingOptions), confirm indexing is enabled and not paused.
• Check regional and language settings: A mismatch between display language and search language can cause empty results. Confirm your language pack matches what you expect.

Step 4: Run the main installation procedure

This is the core repair sequence. Work through it from the least to the most invasive. Stop as soon as search works.

• Restart the search processes: In Task Manager, end SearchHost.exe and SearchIndexer.exe. They restart automatically. Test search.
• Run the Search and Indexing troubleshooter: Go to Settings > System > Troubleshoot > Other troubleshooters and run “Search and Indexing.”
• Rebuild the search index: Open Indexing Options > Advanced > Rebuild. Confirm, then let it complete. This can take 15–60 minutes depending on data volume.
• Run system file repairs: In the elevated terminal, run DISM /Online /Cleanup-Image /RestoreHealth, then sfc /scannow. Reboot when finished.
• Re-register the search app: In an elevated PowerShell window, run Get-AppxPackage -AllUsers Microsoft.Windows.Search | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml"}.
• Reset the search component (aggressive): If the above fails, run Get-AppxPackage Microsoft.Windows.Search | Reset-AppxPackage or reinstall the package via the Microsoft Store.
• Replace the profile (last resort): If search works in a new profile but not the current one, migrate the user to a fresh profile.

Step 5: Verify the installation

Verification is not optional—test search in multiple places to be sure the fix is real and not a temporary cache effect:

• Press the Windows key and type an app name such as “Notepad.” Confirm it appears.
• Open File Explorer and search for a known file in a known folder.
• Search Settings, for example type “display” and check that matching settings appear.
• Open Task Manager and confirm SearchHost.exe and SearchIndexer.exe are running with reasonable memory use.
• Reboot the machine and repeat the tests to confirm the fix survives a restart.

For administrators, run these checks on a sample of machines and confirm via your management console that the fix persisted.

Step 6: Configure post-install options

With search working, apply the finishing touches so the problem does not return:

• Set index locations deliberately: Exclude noisy folders (build artifacts, temp directories) to keep the index lean and fast.
• Re-enable third-party tools one at a time: If you disabled Everything or Listary, turn them back on individually and retest, so you know which one caused the conflict, if any.
• Apply policies (admins): If you want to prevent recurrence across a fleet, deploy a GPO or Intune configuration profile that keeps the Windows Search service set to Automatic and prohibits disabling it.
• Document the fix: Record which step resolved the issue and on which build and architecture. This becomes your runbook for next time.
• Schedule maintenance: Ensure Windows Update, index optimization, and disk cleanup are scheduled so the index stays healthy.

Post-Installation

Once the fix is applied, a few habits keep Windows Search reliable. Keep your system updated, because Microsoft regularly ships.