Search anomaly in Windows 10
 

One of the very few things I don't like about W10 from a usability perspective:

1. Press the Windows key
2. Type xxx (where xxx.yyy is a file I wish to open)
3. No results found despite the default being to show all results
4. Click the Documents icon at the top of the search results pane to restrict results to documents only
5. Observe that file xxx.yyy is now listed
6. Hover over the Documents icon and observe the balloon message "Remove documents filter to find all results"
7. Click the Documents icon
8. Observe no results found once more

Que?

This doesn't seem right but is consistent across all five W10 computers in my household. A proven method to fix this annoyance would be appreocated if it exists.

TVM,
XV

XV
There are a couple of ideas here.

I use Effective File Search - works every time.............

Thank you, noughtsnones, a nice try to help but I have unfortunately already spent multiple hours troubleshooting including to try the options listed at that link.

HH - I would just like W10 search to work properly. :)

For Info
 

Desktop PC with updated W10

I have the Cortana search box visible on the task bar. Typing part or all of the file name seems to work fine, so it’s not a problem common to all installations.

Maybe a problem due to another item of software installed on all 5 computers?

An unrelated issue following last week’s W10 upgrade

The google search page crashes in Chrome. Internet Explorer and Edge.
Fixed it by going to the ‘Advanced Settings’ in Edge - de-select and re-select ‘Get Cortana to assist me in Microsoft Edge’. :confused:

A nice idea thanks QA1 but a quick check on three W10 computers in a store today revealed the same behaviour.

Try UltraSearch, does the job thoroughly and easily.

Thanks, flywatcher but as written in reply to Heathrow Harry I want to get W10 search to work properly. I already have a search tool and inference from what I have found on the web is that it is not a crock of brown smelly stuff and should ordinarily be working correctly - So solution not workaround. :ok: