I see a lot of windows indexer terminated unexpectedly in the event logs. It's a bit annoying. Since our firm already uses a DMS we do not use windows indexer and I would like to disable it. I can see it under services.msc wsearch. How do I disable using GPO.
Everyday, my Reliability Monitor on Windows 7 x64 reports at least one SearchIndexer.exe crash. Here is the log.
What can I do to stop it?
user477799
1 Answer
In the dump, I can see this call t
query!CSdidLookupTable::LookupSDIDOrAdd+0x152
, so there is an issue looking for permissions.I can see this string floating around
C:ProgramDataMicrosoftSearchDataApplicationsWindowsProjectsSystemIndexSecStoreCiST0000.001
. So make sure that SYSTEM has access to it. I can also see that a 3rd party dll called
guard64.dll
is involved. and this belongs to COMODO:
remove it and look if this fixes the crashes.
magicandre1981magicandre1981
Relevant Specs:
- Windows 7 Professional 64-bit SP1
- Outlook 2010 Version 14.0.7116.5000 (32-bit)
Original Symptom:In outlook, I attempted to search for an email but nothing ever returned and the indicator kept going like it was searching.
Attempted Resolutions: I investigated the search options and with some research noticed the Windows Service 'Windows Search' (SearchIndexer.exe) was not running.
I attempted to start it but I receive this error message: 'Windows could not start the Windows Search service on Local Computer. Error 1067: The process terminated unexpectedly.'
The Event Viewer gives this error entry:
The regular windows search (from start menu) works fine, and if I reboot the machine the service starts up OK but as soon as it kicks off when I let the machine idle for long enough it crashes (same Event Viewer entry).
We also tried the Microsoft Utility to no avail. Has anyone seen this issue before?
Josh JayJosh Jay
migrated from serverfault.comJun 4 '14 at 5:36
This question came from our site for system and network administrators.