Windows 10: Win10 search: “These results may be incomplete”, won't find files

I wasn't suggesting rebuilding the index just for the sake of it.. but that an interruption to Windows search service reproduces your error message. Only if there were no interruption to the service would rebuilding be necessary to restore search properly. The signficant thing there was the effect of one interruption.

However your problem could well be sthg else.

 

Oh, sorry, I misunderstood.

I just did this: Windows 10 Event 10016 Fix: The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.I a – Quarter Five – Thoughts and Solutions for every CLSID and AppID yielding an error in the Event Viewer and owned by the TrustedInstaller. It still doesn't work.

Windows 10 is crap.

 

As I've not seen a report quite like yours, I would say your experience of this is comparatively unusual; to conclude the OS is rubbish is premature. But because MS allows much of its OS to be overwritten by users and programs, it's open to all manner of things.

However, it has very definite weaknesses- I avoid Win 10's start menu, Cortana, and universal apps.
========================

Unfortunately you can't run search in Safe Mode. As you say you do see search results immediately after logging in, this suggests an effect of sthg you've installed. Have you done a clean boot using msconfig?

Beyond that, I suggest you either
a. uninstall programs progressively and retry search each time
or
b. reinstall Win 10, check search is working.
- Create a disk image so you can readily restore that state.
- install programs one by one, check search, update your disk image until you find what's corrupting search.

That's the simplistic logical do-able approach.

Otherwise it's a matter of trying to analyse what's happening. If some program or service running is corrupting search in some fashion after logging on, it won't be fixable after the event.

Someone else may be able to suggest a better way forward.

The routine use of disk imaging is something we very strongly recommend in any case- can be a great timesaver.

 

Thanks, I'll see what can I do...
Which of the options do you mean, selective or diagnostic?

 

You could try a diagnostic startup, but I'm guessing Windows search might not be started. And it seems starting after logging in might require rebuilding the index based on my comment above.. (I just don't know at that level of detail).

So try selective startup first, make sure Windows search is running and see what happens.

The idea is to get back as far as possible from where you are to having nothing you've installed running.
If you want to go that far, try Sysinternals Autoruns (free, from MS) - can be very handy. Run as admin.