The Search window opens, but neither local apps nor files appear in results. This is a narrower problem than a total system outage. The first useful clue is the contrast between the failed action and a related action that still works. Do not reinstall or reset unrelated components before identifying which boundary is failing.
What the symptom tells you
Search for a built-in app and then a newly created harmless text file; compare Start search with File Explorer search. This comparison matters because an apparently identical error can be caused by a setting, the path used to reach the feature, or a capability the current device does not support.
Record the exact Windows device, signed-in account and relevant local application. Note whether the behavior started after a specific update, connection change or account change. Keep one control case unchanged while you test the affected scenario; that gives you a reliable before-and-after result.
Three likely causes and how to separate them
| Possible cause | Evidence to look for | What it means |
|---|---|---|
| A stuck SearchHost process | Search for a built-in app and then a newly created harmless text file; compare Start search with File Explorer search. | The issue is likely to follow the exact feature state or configuration, rather than every device or document. |
| A paused or unhealthy search index | Repeat the same action with one known-good control while keeping the other conditions constant. | A difference between two accounts, connections or modes identifies the component to inspect next. |
| A profile-specific search setting or policy | Test a fresh Windows profile and inspect Search service/indexer errors before rebuilding the affected index. | This possibility needs more evidence and should not be treated as confirmed after a single failure. |
The rows are diagnostic hypotheses, not a guaranteed diagnosis. For example, a stuck searchhost process can coexist with a second issue, but changing several settings at once makes it impossible to tell which correction helped.
Before making changes
Keep a second administrator or recovery sign-in available before changing OS settings; use built-in Settings and diagnostics first. Avoid wiping the index or removing packages before proving which search component fails.
Fix the problem in a controlled order
- Reproduce the actual failure. The Search window opens, but neither local apps nor files appear in results. Keep the test short and use non-sensitive data wherever practical.
- Check a working baseline. Search for a built-in app and then a newly created harmless text file; compare Start search with File Explorer search. Write down what worked, what did not, and the version or mode in each test.
- Examine the first explanation. A stuck SearchHost process. Look for an obvious setting or hardware state that differs from the control.
- Rule out the second explanation. A paused or unhealthy search index. Change only one reversible setting or comparison variable.
- Apply the targeted fix. Restart Windows Explorer and Search from Task Manager, then retest a built-in app; check Settings > Privacy & security > Searching Windows for indexing status.
- Check the result immediately. A built-in app and the test file appear as selectable results without deleting indexed user data. If it fails, restore the last changed setting before trying a different route.
Solution A: the least disruptive correction
Restart Windows Explorer and Search from Task Manager, then retest a built-in app; check Settings > Privacy & security > Searching Windows for indexing status. Focus on the first setting, route or mode that differs from the control case. If a setting is absent on the current model, OS build or app version, do not invent a hidden menu or assume the user has that feature.
Reproduce the original failure right after applying the correction. A success in an easier, unrelated test is not enough: the same Windows device, signed-in account and relevant local application should now behave as intended. If the result is mixed, keep notes and avoid continuing with broader changes.
Step-by-Step Troubleshooting
Beginner: check the feature without deleting data. Advanced: identify the underlying dependency using controlled evidence.
Identify the symptom
The Search window opens, but neither local apps nor files appear in results. Identify the exact failing action, affected device/app and the time the problem began. Keep a record rather than testing from memory.
Compare with a working case
Search for a built-in app and then a newly created harmless text file; compare Start search with File Explorer search. Use a harmless sample and repeat with the same account, network and settings when possible. Only change one variable.
Make the small correction
Restart Windows Explorer and Search from Task Manager, then retest a built-in app; check Settings > Privacy & security > Searching Windows for indexing status. Pause if the available menu or capabilities differ from the instructions for your product.
Verify without losing data
A built-in app and the test file appear as selectable results without deleting indexed user data. Reopen or reconnect once when relevant. Keep the old setting recorded so it can be restored if the result is worse.
Prove the first failure boundary
Check whether a stuck searchhost process. Compare the outcome with: Search for a built-in app and then a newly created harmless text file; compare Start search with File Explorer search. A failing control means the first hypothesis is not sufficient.
Inspect the secondary dependency
Investigate a paused or unhealthy search index. Record the model, versions and connection or account difference. Preserve the working baseline.
Use deeper diagnostics safely
Test a fresh Windows profile and inspect Search service/indexer errors before rebuilding the affected index. If the third cause — a profile-specific search setting or policy — is involved, prefer official documentation and supported diagnostic utilities.
Recheck and document rollback
A built-in app and the test file appear as selectable results without deleting indexed user data. Avoid wiping the index or removing packages before proving which search component fails. If this verification fails, undo only the latest change and capture a privacy-safe support report.
Solution B: determine which component is responsible
Test a fresh Windows profile and inspect Search service/indexer errors before rebuilding the affected index. Take observations before making further changes. When the test indicates that an administrator policy, carrier service, device firmware, platform restriction or subscription entitlement is responsible, follow that supported path instead of trying to circumvent it.
A useful escalation record contains four facts: the precise symptom, a control result, one targeted action taken, and the outcome. Export relevant event entries and note the Windows build and affected user profile before escalating to Microsoft or the device manufacturer.
Solution Checklist
Verify the repair
Pass condition: A built-in app and the test file appear as selectable results without deleting indexed user data. Repeat the test after one ordinary reopen, reconnection or restart only when the affected feature needs it. Also check that the known-good comparison still works; this helps detect a fix that merely moved the problem elsewhere.
If it still fails
Return to the original baseline and collect evidence for the third possibility: a profile-specific search setting or policy. Test a fresh Windows profile and inspect Search service/indexer errors before rebuilding the affected index. If the supported options are exhausted, stop before destructive resets and contact the appropriate vendor or service provider with redacted observations.
Prevent the same issue from returning
Keep a record of the working Windows device, signed-in account and relevant local application. After a major app, OS, firmware or network change, repeat the same short control test before modifying several options. This makes a recurrence easier to trace and protects settings that were already correct.
FAQ
Why does a similar device or app still work?
The two cases may differ in Windows device, signed-in account and relevant local application. Search for a built-in app and then a newly created harmless text file; compare Start search with File Explorer search. A successful comparison isolates a condition; it does not prove that the failing hardware is defective.
Should I factory reset or reinstall first?
No. Avoid wiping the index or removing packages before proving which search component fails. Try the reversible a stuck searchhost process check and targeted fix before any action that could erase local data or settings.
What information is useful for support?
Include the exact symptom, affected product and current version, the controlled comparison and whether this check passed: A built-in app and the test file appear as selectable results without deleting indexed user data. Exclude passwords, tokens, private messages and full account identifiers.
Official resource
Microsoft Support — Search indexing in Windows — use the vendor instructions that apply to your installed version and device.
Disqus hosts the discussion. Comments load automatically as you approach this section and may use cookies.