When you find Windows Search not working, the safe first fix is to install pending updates, restart the search process or the PC, and confirm the missing item sits in an indexed location. Before that, note whether the search interface will not open, accepts no input, or returns incomplete results, and compare Start search with File Explorer search. Rebuilding the index is a later step, not the first response to every search symptom.

Key Takeaways

Separate an unresponsive search interface from missing or slow results.

Verify the file exists, the query is suitable, and the folder is included before changing the index.

Check indexing status, power, storage, and sustained system load.

Restart the affected search process or Windows before rebuilding anything.

Do not disable Windows Search or delete index databases and registry keys as a generic fix.

The device and app troubleshooting guide can help when Start, Settings, File Explorer, and unrelated apps are all behaving abnormally.

Is Windows Search not working at all, or only missing results?

Use one known file and one installed app as controlled tests. Record the exact file name, folder, extension, and whether File Explorer can open it directly. Search for the app by its visible name and search for the file first by exact name, then by a distinctive partial name.

Symptom	Likely layer
Search does not open	Shell, Search process, session, update, or policy
Search opens but typing does nothing	Focus, input method, shell, or session
Apps appear but files do not	Search scope, index coverage, file location, or permissions
One file is missing	Name, location, attribute, extension, permission, or incomplete indexing
Results appear slowly	Index still building, large scope, low power, or resource pressure
File Explorer and Start disagree	Different scope, query rules, or index use

Do not use an Outlook message or a cloud-only placeholder as the first test. Outlook has its own data and integration layers, while a cloud placeholder may not be available locally. A small local text file in Documents gives a clearer baseline.

Also compare a newly created test file with an older missing file. If the new file appears but one old file does not, the issue is narrower than a broken search service. Check the old file's actual path, access permissions, and whether it was moved or renamed.

Windows search bar not responding? What to check

Open Start with the keyboard and try typing. Then open File Explorer and use its search box. If only one interface is frozen, avoid changing the entire index. Close the affected window or sign out of the affected session only after saving other work.

Microsoft's Windows Search troubleshooting guidance lists lighter steps first: restarting the Windows Font Cache Service, installing updates, running the Search and Indexing troubleshooter where available, and ending the SearchHost.exe (Windows 11) or SearchUI.exe (Windows 10) process. Reset scripts and folder regeneration come later.［2］ Preserve the exact symptom and any error text because an organization policy or a damaged user profile needs a different response from an incomplete index.

Save open work.
Check for a pending supported Windows update and complete any required restart.
Reopen Start and File Explorer separately.
If Search alone remains stuck, restart the documented Search process or restart Windows once.
Test the same app and local file again.

Avoid copying commands from old forum posts that unregister shell packages, delete registry branches, or remove Search data. Those operations can widen a local interface problem and make rollback harder. On a work or school PC, stop if policy blocks the setting or the organization manages search behavior.

Is Windows indexing the location you expect?

Windows indexing maintains a catalog so common searches can return results quickly. Microsoft explains that Classic mode indexes standard user locations, while Enhanced mode covers the whole PC and can use more resources.［1］ Before changing modes, check whether the missing folder is currently included or excluded.

Open the Windows search settings and inspect indexing status. If indexing is still in progress, connect the computer to power, keep it awake for a reasonable observation period, and avoid repeatedly rebuilding. Record whether the pending-item count is falling. A large first-time index after setup, update, or moving many files is not the same as a stopped index.

Check these scope questions:

Is the file inside a local folder that the selected mode indexes?
Is the folder excluded for privacy or performance reasons?
Is the item on a removable, network, encrypted, or cloud-only location?
Does the current account have permission to read the folder?
Does the file name or extension match the query you are using?

If the folder is intentionally excluded, adding it changes both privacy exposure and resource use. Do not index a confidential shared folder just to test one file. Use File Explorer to navigate directly and decide whether the folder should be searchable under the device's policy.

How do you turn Windows Search indexing back on?

If you or a cleanup tool turned the Windows Search service off, indexing will not resume by itself. Open the Services console by entering services.msc in the taskbar search box; if that box is broken, use the Run dialog (Windows key + R) instead.

In Services, open Windows Search.
Set Startup type back to Automatic (Delayed Start), the Windows default.
Select Start, then OK.
Open the Windows search settings under Privacy & security (on Windows 10, Settings > Search > Searching Windows) and confirm Find my files uses Classic or Enhanced and your folders are not excluded.

Expect incomplete results while the indexer catches up. If the startup type is locked, or the service stops again right after starting, record the error and give it to IT; on a work or school PC, a disabled service may be a deliberate policy.

Is Windows search indexing incomplete, busy, or short of resources?

Search can be correct but temporarily slow while Windows processes many changes. Observe indexing status and Task Manager rather than assuming every disk spike is corruption. Low battery, sleep, storage pressure, antivirus scanning, cloud synchronization, and a large file migration can all delay useful results.

Create one local test file in an indexed folder and wait for it to appear. If it appears while older content remains missing, narrow the problem to those locations or file types. If the indexing count never changes across a reasonable powered-on interval, record the status and restart once before considering a rebuild.

If disk usage remains near saturation across ordinary tasks, use the Windows 100% disk-usage guide. Do not disable Windows Search merely to make a Task Manager number fall; that removes functionality without proving the original cause.

For a new computer that is still installing updates, synchronizing files, and building its first index, follow the new Windows 11 PC checklist. Let those setup activities settle before treating slower first results as a persistent fault.

When should you rebuild the Windows Search index?

Rebuild only after the interface works, the expected location is included, the query and permissions are correct, indexing is not merely progressing, and a restart did not restore results. A rebuild discards the current catalog and creates it again; results can be incomplete until that process finishes.

Before rebuilding, note the current search mode and exclusions. Connect to power, save work, and choose a time when temporary incomplete results are acceptable. Start one rebuild, then observe status rather than initiating another one.

On a managed PC, or when the index repeatedly fails after a rebuild, give IT the Windows version, indexing status, affected locations, event time, and the controlled test result. Do not manually delete the search database or change registry settings unless the responsible administrator follows a documented recovery plan.

What does Windows Search not cover?

Start search, File Explorer, Outlook, a browser, and an individual application can use different search systems. Success in one does not prove another system is indexed. Keep the article's conclusion limited to Windows shell and file search.

A missing web result, a cloud service outage, a file that was never synchronized, or an application with its own database needs that service's troubleshooting path. If Windows itself is slow to start rather than search being incomplete, use the Windows slow-startup guide.

Summary

Classify interface failure, missing results, and slow indexing separately.
Test a known local file and app before changing scope.
Verify included folders, exclusions, permissions, power, and indexing progress.
Restart the affected layer before rebuilding.
Keep destructive database, registry, and service changes out of generic troubleshooting.

FAQ

Why does Windows Search open but show no files?

The file location may not be indexed, the folder may be excluded, the item may be cloud-only, or the account may lack access. Confirm the exact path and indexing scope first.

Why can File Explorer find a file that Start cannot?

The two interfaces can search different scopes and apply different query behavior. Compare the exact folder, query, and whether that location participates in the Windows index.

Should I switch from Classic to Enhanced indexing?

Only if you need broad whole-PC search and accept the additional indexing work. First confirm the missing folder is outside the current scope; changing modes is not a universal repair.

How long should indexing take?

There is no useful universal duration because file count, storage speed, power state, and recent changes differ. Watch whether the pending count falls while the PC is powered and awake.

Should I disable Windows Search when disk usage is high?

No. Diagnose sustained disk activity and indexing status first. Disabling the service removes search capability and does not prove why the disk was busy.

Will rebuilding the index delete my documents?

A normal index rebuild recreates the search catalog, not the documents. Search results can remain incomplete during the rebuild, so note your settings and allow the process to finish.

Why is one old file missing while new files appear?

The old file may have moved, changed name, lost readable permissions, used an unindexed location, or remained as an unavailable cloud placeholder. Inspect that item rather than rebuilding everything immediately.

When should a work PC go to IT?

Escalate when policy blocks required settings, Search repeatedly fails after supported steps, multiple user profiles are affected, or advanced service and event diagnostics are needed.

Sources

Microsoft Support — Search indexing in Windows — https://support.microsoft.com/en-us/windows/experience/performance-optimization/search-indexing-in-windows
Microsoft Learn — Fix problems in Windows Search — https://learn.microsoft.com/en-us/troubleshoot/windows-client/shell-experience/fix-problems-in-windows-search

Sources checked 4 October 2026.

Windows Search Not Working: What to Check