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

Page 2 of 2 FirstFirst 12

  1. Posts : 14
    10x64
    Thread Starter
       #11

    Many things to reply to. Yes, I use Everything most of the time. Yet content search is vital for me and I use it often too. Settings search works, and rather fast (not instantaneous). And I'm trying to keep untrustworthy thirdparty software to a minimum.

    Privacy settings: I've set to share everyting with M$FT and didn't change a thing since first boot. And I haven't used any "tweaking" program that might've changed anyting (other than maybe HP preinstalled software, but that's bare too).

    Indexing with a modern SSD is unnoticeable. Yet it brings big productivity gains when it works.

    -2017_02_01_12_31_193.png

    -2017_02_01_12_30_382.png



    -2017_02_01_12_29_001.png

    Everything I might search for is under \Users
      My Computer


  2. Posts : 43,296
    Win 10 Pro (22H2) (2nd PC is 22H2)
       #12

    That all looks ok. Have you tried a clean boot? you mentioned search seemed to work ok initially after logging in.

    Check if the Windows search service is running. (E.g. Windows key + R, services.msc). (But it does appear to start again automatically if stopped- see below for significance)

    ** Look what I get if I
    a. Stop Windows search service
    b. Try to find something I didn't try to find before I disabled the search
    -untitled.png
    N.B. finding sthg successfully, then disabling the search, then finding the same thing succeeds, so don't do that.

    I also found that having disabled windows search, even restarting it and restarting left me with the same problem. So now I'm rebuilding the index.

    That could be a good clue.
      My Computers


  3. Posts : 14
    10x64
    Thread Starter
       #13

    dalchina said:
    That all looks ok. Have you tried a clean boot? you mentioned search seemed to work ok initially after logging in.

    Check if the Windows search service is running. (E.g. Windows key + R, services.msc). (But it does appear to start again automatically if stopped- see below for significance)

    ** Look what I get if I
    a. Stop Windows search service
    b. Try to find something I didn't try to find before I disabled the search
    -untitled.png
    N.B. finding sthg successfully, then disabling the search, then finding the same thing succeeds, so don't do that.

    I also found that having disabled windows search, even restarting it and restarting left me with the same problem. So now I'm rebuilding the index.

    That could be a good clue.
    I don't think that rebuilding the index once more will help. After all, for a brief few seconds after start I see the results, so the index is ok.

    The service is up and running. Restarting it brings back the results for a few seconds (<5s).

    I've disabled every startup item and the problem persists, so it's Windows.

    I do get three of the following errors in the Event log.


    The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) 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.


    A quick search for the first GUID on Google points to it being Cortana (and thus search) related, but I haven't had yet the time to investigate it fully. Just wanted to let you know.

    Thanks!
      My Computer


  4. Posts : 43,296
    Win 10 Pro (22H2) (2nd PC is 22H2)
       #14

    I don't think that rebuilding the index once more will help. After all, for a brief few seconds after start I see the results, so the index is ok.
    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.
      My Computers


  5. Posts : 14
    10x64
    Thread Starter
       #15

    dalchina said:
    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.
      My Computer


  6. Posts : 43,296
    Win 10 Pro (22H2) (2nd PC is 22H2)
       #16

    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.
      My Computers


  7. Posts : 14
    10x64
    Thread Starter
       #17

    dalchina said:
    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?
    -2017_02_02_15_28_201.png
      My Computer


  8. Posts : 43,296
    Win 10 Pro (22H2) (2nd PC is 22H2)
       #18

    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.
      My Computers


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 02:29.
Find Us




Windows 10 Forums