Windows Search Service Terminated


  1. Posts : 19
    Windows 10 Home
       #1

    Windows Search Service Terminated


    Basic problem is slow start-up and very slow opening files and programs. Here is history of the computer...
    1. Original OS was Windows 7
    2. Windows 7 upgraded to Windows 10, all worked OK
    3. Windows 10 updated with Anniversary Update, problem began

    I first looked in the System Log Event Viewer and found dozens of red errors titled as "The Windows Search Service terminated with the following service-specific error: %%2388525884" The error test and the error code is the same for dozens of times, and seems to grow with more use of the computer. Here is what I have tried so far...
    1. Ran SFC SCANNOW, no help
    2. Ran CHKDSK, no help
    3. Tried a Repair of Windows 10, would not repair, except for clean install
      Googled the error and found nothing of help

    I am at a loss as to what to try next, and really don't want to have to do a clean install, so any advice is appreciated.
      My Computer


  2. Posts : 19
    Windows 10 Home
    Thread Starter
       #2

    Curious why no replies....has no one else seen this issue?
      My Computer


  3. Posts : 19
    Windows 10 x64 Professional
       #3

    You're only giving us a small piece of the event log error. Adding things like the Event ID and any description of what the error is would be helpful.

    I haven't been getting that particular error. Instead I'm getting these every so often (if I leave the Windows Search Service on):

    Event 3104:
    Enumerating user sessions to generate filter pools failed.Details:
    (HRESULT : 0x80040210) (0x80040210)

    It's annoying enough that I've just disabled the Windows Search service for now until they fix it. I know it's not only me, a lot of others are reporting that error since the Anniversary update.
      My Computer

  4. topgundcp's Avatar
    Posts : 2,782
    Linux Mint 20.1 Win10Prox64
       #4

    To be honest, Windows search is one of the first service I disable after every Windows Install and use a third party search engine instead.
    Having said that, since you upgraded from 7 -> 10 - > 10 AU. The Windows Search database might be corrupted. Look under: C:\ProgramData\Microsoft\Search\Data\Applications\Windows. The database file is Windows.edb. With Windows Search service disabled, delete this file, re-enable Windows Search service and let Windows rebuild the database.
      My Computer


  5. Posts : 19
    Windows 10 Home
    Thread Starter
       #5

    Qwinn said:
    You're only giving us a small piece of the event log error. Adding things like the Event ID and any description of what the error is would be helpful.

    I haven't been getting that particular error. Instead I'm getting these every so often (if I leave the Windows Search Service on):

    Event 3104:
    Enumerating user sessions to generate filter pools failed.Details:
    (HRESULT : 0x80040210) (0x80040210)

    It's annoying enough that I've just disabled the Windows Search service for now until they fix it. I know it's not only me, a lot of others are reporting that error since the Anniversary update.
    Qwinn.....Sorry if I wasn't giving enough info...thought the error code would be sufficient. the event ID is 10016 which appears to be a common one and not much help defining my situation. I will look for more info. Tha nks for the reply.
      My Computer


  6. Posts : 19
    Windows 10 Home
    Thread Starter
       #6

    topgundcp said:
    To be honest, Windows search is one of the first service I disable after every Windows Install and use a third party search engine instead.
    Having said that, since you upgraded from 7 -> 10 - > 10 AU. The Windows Search database might be corrupted. Look under: C:\ProgramData\Microsoft\Search\Data\Applications\Windows. The database file is Windows.edb. With Windows Search service disabled, delete this file, re-enable Windows Search service and let Windows rebuild the database.
    Topgundcp....thanks so much for the suggestion...I will give it a try as soon as I can (it's another PC) and report back.
      My Computer


  7. Posts : 19
    Windows 10 x64 Professional
       #7

    10016 is a permissions error that is actually quite fixable. Can you post the entire event log error when you get back to that PC?
      My Computer


  8. Posts : 19
    Windows 10 Home
    Thread Starter
       #8

    Qwinn said:
    10016 is a permissions error that is actually quite fixable. Can you post the entire event log error when you get back to that PC?
    Sorry, my confusion, the 10016 error is a Dcom error I am also having. The Windows Search errors are 7024 and 7034. The content is below...
    Log Name: System
    Source: Service Control Manager
    Date: 8/17/2016 11:20:28 PM
    Event ID: 7024
    Task Category: None
    Level: Error
    Keywords: Classic
    User: N/A
    Computer: DESKTOP-QREDL07
    Description:
    The Windows Search service terminated with the following service-specific error:
    %%2388525584
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
    <System>
    <Provider Name="Service Control Manager" Guid="{555908d1-a6d7-4695-8e1e-26931d2012f4}" EventSourceName="Service Control Manager" />
    <EventID Qualifiers="49152">7024</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8080000000000000</Keywords>
    <TimeCreated SystemTime="2016-08-18T03:20:28.836353100Z" />
    <EventRecordID>1988</EventRecordID>
    <Correlation />
    <Execution ProcessID="944" ThreadID="2116" />
    <Channel>System</Channel>
    <Computer>DESKTOP-QREDL07</Computer>
    <Security />
    </System>
    <EventData>
    <Data Name="param1">Windows Search</Data>
    <Data Name="param2">%%2388525584</Data>
    <Binary>57005300650061007200630068000000</Binary>
    </EventData>
    </Event>


    Log Name: System
    Source: Service Control Manager
    Date: 8/17/2016 11:20:28 PM
    Event ID: 7034
    Task Category: None
    Level: Error
    Keywords: Classic
    User: N/A
    Computer: DESKTOP-QREDL07
    Description:
    The Windows Search service terminated unexpectedly. It has done this 105 time(s).
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
    <System>
    <Provider Name="Service Control Manager" Guid="{555908d1-a6d7-4695-8e1e-26931d2012f4}" EventSourceName="Service Control Manager" />
    <EventID Qualifiers="49152">7034</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8080000000000000</Keywords>
    <TimeCreated SystemTime="2016-08-18T03:20:28.836353100Z" />
    <EventRecordID>1989</EventRecordID>
    <Correlation />
    <Execution ProcessID="944" ThreadID="3036" />
    <Channel>System</Channel>
    <Computer>DESKTOP-QREDL07</Computer>
    <Security />
    </System>
    <EventData>
    <Data Name="param1">Windows Search</Data>
    <Data Name="param2">105</Data>
    <Binary>57005300650061007200630068000000</Binary>
    </EventData>
    </Event>
      My Computer


  9. Posts : 19
    Windows 10 Home
    Thread Starter
       #9

    topgundcp said:
    To be honest, Windows search is one of the first service I disable after every Windows Install and use a third party search engine instead.
    Having said that, since you upgraded from 7 -> 10 - > 10 AU. The Windows Search database might be corrupted. Look under: C:\ProgramData\Microsoft\Search\Data\Applications\Windows. The database file is Windows.edb. With Windows Search service disabled, delete this file, re-enable Windows Search service and let Windows rebuild the database.
    topgundcp....thank you so much! This appears to have fixed my Windows Search error, and now my folders also open very quickly again. wow! Such an easy fix after hours of searching....sure seems MS would be on to this. Thanks again!
      My Computer


  10. Posts : 249
    Windows 10 Home x64
       #10

    Qwinn said:
    You're only giving us a small piece of the event log error. Adding things like the Event ID and any description of what the error is would be helpful.

    I haven't been getting that particular error. Instead I'm getting these every so often (if I leave the Windows Search Service on):

    Event 3104:
    Enumerating user sessions to generate filter pools failed.Details:
    (HRESULT : 0x80040210) (0x80040210)

    It's annoying enough that I've just disabled the Windows Search service for now until they fix it. I know it's not only me, a lot of others are reporting that error since the Anniversary update.
    You got that right. This error is a headache for a lot of people and no one has a solution, just work arounds.
      My Computer


 

  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 08:23.
Find Us




Windows 10 Forums