[Vista 6000] [Search Indexer] Stoped Working And Was Closed

Question

Hello,

Having major propblems with the Indexer,
Its causing major system performance issues and problems...

I dont know when or how it started, but recently.
The Indexer will crash, and pop up an error box.

This happens when...
Deleting a file.
Opening Outlook. (Office 2007)
Moving Files.

Pracatly anything to do with the Indexer.

While deleting or moving files system performance slows to a trail.
Outlook stops completely.

Opening controll panel, then indexing options...
States that Indexing is not running.

Basicly it wont stop crashing.

Any workaround or fix?

Windows Vista Business x86 6.0 Build 6000
Intel Pentium 4 x86 Family 15 Model 3stepping 4
1.5 GIG Memory

Product
Microsoft Windows Search Indexer

Problem
Stopped working

Date
04/03/2007 15:23

Status
Not Reported

Problem signature
Problem Event Name: InPageError
Error Status Code: c000009c
Faulting Media Type: 00000003
OS Version: 6.0.6000.2.0.0.256.6
Locale ID: 2057
Additional Information 1: 6f3b
Additional Information 2: 2bd88d149d85c0ab26359bfa0a122304
Additional Information 3: a509
Additional Information 4: 1953256f91532f6ba546df0162013f4b

Files that help describe the problem
Version.txt
AppCompat.txt
memory.hdmp
minidump.mdmp

[AppCompat.txt]
<?xml version="1.0" encoding="UTF-16"?>
<DATABASE>
<EXE NAME="SYSTEM INFO" FILTER="GRABMI_FILTER_SYSTEM">
    <MATCHING_FILE NAME="advapi32.dll" SIZE="770048" CHECKSUM="0xF07A52F9" BIN_FILE_VERSION="6.0.6000.16386" BIN_PRODUCT_VERSION="6.0.6000.16386" PRODUCT_VERSION="6.0.6000.16386" FILE_DESCRIPTION="Advanced Windows 32 Base API" COMPANY_NAME="Microsoft Corporation" PRODUCT_NAME="Microsoft® Windows® Operating System" FILE_VERSION="6.0.6000.16386 (vista_rtm.061101-2205)" ORIGINAL_FILENAME="advapi32.dll.mui" INTERNAL_NAME="advapi32.dll" LEGAL_COPYRIGHT="© Microsoft Corporation. All rights reserved." VERDATEHI="0x0" VERDATELO="0x0" VERFILEOS="0x40004" VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0xC54C5" LINKER_VERSION="0x60000" UPTO_BIN_FILE_VERSION="6.0.6000.16386" UPTO_BIN_PRODUCT_VERSION="6.0.6000.16386" LINK_DATE="11/02/2006 09:39:30" UPTO_LINK_DATE="11/02/2006 09:39:30" EXPORT_NAME="ADVAPI32.dll" VER_LANGUAGE="English (United States) [0x409]" />
    <MATCHING_FILE NAME="gdi32.dll" SIZE="296448" CHECKSUM="0xAD21A1D1" BIN_FILE_VERSION="6.0.6000.16386" BIN_PRODUCT_VERSION="6.0.6000.16386" PRODUCT_VERSION="6.0.6000.16386" FILE_DESCRIPTION="GDI Client DLL" COMPANY_NAME="Microsoft Corporation" PRODUCT_NAME="Microsoft® Windows® Operating System" FILE_VERSION="6.0.6000.16386 (vista_rtm.061101-2205)" ORIGINAL_FILENAME="gdi32" INTERNAL_NAME="gdi32" LEGAL_COPYRIGHT="© Microsoft Corporation. All rights reserved." VERDATEHI="0x0" VERDATELO="0x0" VERFILEOS="0x40004" VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0x514CE" LINKER_VERSION="0x60000" UPTO_BIN_FILE_VERSION="6.0.6000.16386" UPTO_BIN_PRODUCT_VERSION="6.0.6000.16386" LINK_DATE="11/02/2006 09:39:31" UPTO_LINK_DATE="11/02/2006 09:39:31" EXPORT_NAME="GDI32.dll" VER_LANGUAGE="English (United States) [0x409]" />
    <MATCHING_FILE NAME="kernel32.dll" SIZE="874496" CHECKSUM="0x8440BFFC" BIN_FILE_VERSION="6.0.6000.16386" BIN_PRODUCT_VERSION="6.0.6000.16386" PRODUCT_VERSION="6.0.6000.16386" FILE_DESCRIPTION="Windows NT BASE API Client DLL" COMPANY_NAME="Microsoft Corporation" PRODUCT_NAME="Microsoft® Windows® Operating System" FILE_VERSION="6.0.6000.16386 (vista_rtm.061101-2205)" ORIGINAL_FILENAME="kernel32" INTERNAL_NAME="kernel32" LEGAL_COPYRIGHT="© Microsoft Corporation. All rights reserved." VERDATEHI="0x0" VERDATELO="0x0" VERFILEOS="0x40004" VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0xD9614" LINKER_VERSION="0x60000" UPTO_BIN_FILE_VERSION="6.0.6000.16386" UPTO_BIN_PRODUCT_VERSION="6.0.6000.16386" LINK_DATE="11/02/2006 09:42:24" UPTO_LINK_DATE="11/02/2006 09:42:24" EXPORT_NAME="KERNEL32.dll" VER_LANGUAGE="English (United States) [0x409]" />
    <MATCHING_FILE NAME="ntdll.dll" SIZE="1162656" CHECKSUM="0x8FD38B20" BIN_FILE_VERSION="6.0.6000.16386" BIN_PRODUCT_VERSION="6.0.6000.16386" PRODUCT_VERSION="6.0.6000.16386" FILE_DESCRIPTION="NT Layer DLL" COMPANY_NAME="Microsoft Corporation" PRODUCT_NAME="Microsoft® Windows® Operating System" FILE_VERSION="6.0.6000.16386 (vista_rtm.061101-2205)" ORIGINAL_FILENAME="ntdll.dll.mui" INTERNAL_NAME="ntdll.dll" LEGAL_COPYRIGHT="© Microsoft Corporation. All rights reserved." VERDATEHI="0x0" VERDATELO="0x0" VERFILEOS="0x40004" VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0x128171" LINKER_VERSION="0x60000" UPTO_BIN_FILE_VERSION="6.0.6000.16386" UPTO_BIN_PRODUCT_VERSION="6.0.6000.16386" LINK_DATE="11/02/2006 09:43:37" UPTO_LINK_DATE="11/02/2006 09:43:37" EXPORT_NAME="ntdll.dll" VER_LANGUAGE="English (United States) [0x409]" />
    <MATCHING_FILE NAME="ole32.dll" SIZE="1314816" CHECKSUM="0xEFDF1843" BIN_FILE_VERSION="6.0.6000.16386" BIN_PRODUCT_VERSION="6.0.6000.16386" PRODUCT_VERSION="6.0.6000.16386" FILE_DESCRIPTION="Microsoft OLE for Windows" COMPANY_NAME="Microsoft Corporation" PRODUCT_NAME="Microsoft® Windows® Operating System" FILE_VERSION="6.0.6000.16386 (vista_rtm.061101-2205)" ORIGINAL_FILENAME="OLE32.DLL.MUI" INTERNAL_NAME="OLE32.DLL" LEGAL_COPYRIGHT="© Microsoft Corporation. All rights reserved." VERDATEHI="0x0" VERDATELO="0x0" VERFILEOS="0x40004" VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0x14E4A9" LINKER_VERSION="0x60000" UPTO_BIN_FILE_VERSION="6.0.6000.16386" UPTO_BIN_PRODUCT_VERSION="6.0.6000.16386" LINK_DATE="11/02/2006 09:42:42" UPTO_LINK_DATE="11/02/2006 09:42:42" EXPORT_NAME="ole32.dll" VER_LANGUAGE="English (United States) [0x409]" />
    <MATCHING_FILE NAME="oleaut32.dll" SIZE="558080" CHECKSUM="0x24E63A53" BIN_FILE_VERSION="6.0.6000.16386" BIN_PRODUCT_VERSION="6.0.6000.16386" PRODUCT_VERSION="6.0.6000.16386" COMPANY_NAME="Microsoft Corporation" FILE_VERSION="6.0.6000.16386" INTERNAL_NAME="OLEAUT32.DLL" LEGAL_COPYRIGHT="© Microsoft Corporation. All rights reserved." VERDATEHI="0x0" VERDATELO="0x0" VERFILEOS="0x40004" VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0x94097" LINKER_VERSION="0x60000" UPTO_BIN_FILE_VERSION="6.0.6000.16386" UPTO_BIN_PRODUCT_VERSION="6.0.6000.16386" LINK_DATE="11/02/2006 09:42:45" UPTO_LINK_DATE="11/02/2006 09:42:45" EXPORT_NAME="OLEAUT32.dll" VER_LANGUAGE="English (United States) [0x409]" />
    <MATCHING_FILE NAME="shell32.dll" SIZE="11314688" CHECKSUM="0xE0871A1E" BIN_FILE_VERSION="6.0.6000.16386" BIN_PRODUCT_VERSION="6.0.6000.16386" PRODUCT_VERSION="6.0.6000.16386" FILE_DESCRIPTION="Windows Shell Common Dll" COMPANY_NAME="Microsoft Corporation" PRODUCT_NAME="Microsoft® Windows® Operating System" FILE_VERSION="6.0.6000.16386 (vista_rtm.061101-2205)" ORIGINAL_FILENAME="SHELL32.DLL.MUI" INTERNAL_NAME="SHELL32" LEGAL_COPYRIGHT="© Microsoft Corporation. All rights reserved." VERDATEHI="0x0" VERDATELO="0x0" VERFILEOS="0x40004" VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0xAD8CDD" LINKER_VERSION="0x430020" UPTO_BIN_FILE_VERSION="6.0.6000.16386" UPTO_BIN_PRODUCT_VERSION="6.0.6000.16386" LINK_DATE="11/02/2006 09:43:16" UPTO_LINK_DATE="11/02/2006 09:43:16" EXPORT_NAME="SHELL32.dll" VER_LANGUAGE="English (United States) [0x409]" />
    <MATCHING_FILE NAME="user32.dll" SIZE="633856" CHECKSUM="0xFA697C" BIN_FILE_VERSION="6.0.6000.16386" BIN_PRODUCT_VERSION="6.0.6000.16386" PRODUCT_VERSION="6.0.6000.16386" FILE_DESCRIPTION="Multi-User Windows USER API Client DLL" COMPANY_NAME="Microsoft Corporation" PRODUCT_NAME="Microsoft® Windows® Operating System" FILE_VERSION="6.0.6000.16386 (vista_rtm.061101-2205)" ORIGINAL_FILENAME="user32" INTERNAL_NAME="user32" LEGAL_COPYRIGHT="© Microsoft Corporation. All rights reserved." VERDATEHI="0x0" VERDATELO="0x0" VERFILEOS="0x40004" VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0x9F083" LINKER_VERSION="0x60000" UPTO_BIN_FILE_VERSION="6.0.6000.16386" UPTO_BIN_PRODUCT_VERSION="6.0.6000.16386" LINK_DATE="11/02/2006 09:44:00" UPTO_LINK_DATE="11/02/2006 09:44:00" EXPORT_NAME="USER32.dll" VER_LANGUAGE="English (United States) [0x409]" />
    <MATCHING_FILE NAME="wininet.dll" SIZE="822272" CHECKSUM="0x7AC6E1FB" BIN_FILE_VERSION="7.0.6000.16386" BIN_PRODUCT_VERSION="7.0.6000.16386" PRODUCT_VERSION="7.00.6000.16386" FILE_DESCRIPTION="Internet Extensions for Win32" COMPANY_NAME="Microsoft Corporation" PRODUCT_NAME="Windows® Internet Explorer" FILE_VERSION="7.00.6000.16386 (vista_rtm.061101-2205)" ORIGINAL_FILENAME="wininet.dll.mui" INTERNAL_NAME="wininet.dll" LEGAL_COPYRIGHT="© Microsoft Corporation. All rights reserved." VERDATEHI="0x0" VERDATELO="0x0" VERFILEOS="0x40004" VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0xD0C56" LINKER_VERSION="0x60000" UPTO_BIN_FILE_VERSION="7.0.6000.16386" UPTO_BIN_PRODUCT_VERSION="7.0.6000.16386" LINK_DATE="11/02/2006 09:44:57" UPTO_LINK_DATE="11/02/2006 09:44:57" EXPORT_NAME="WININET.dll" VER_LANGUAGE="English (United States) [0x409]" />
    <MATCHING_FILE NAME="WINSOCK.DLL" SIZE="2864" CHECKSUM="0x73AE8088" BIN_FILE_VERSION="3.10.0.103" BIN_PRODUCT_VERSION="3.10.0.103" PRODUCT_VERSION="3.10" FILE_DESCRIPTION="Windows Socket 16-Bit DLL" COMPANY_NAME="Microsoft Corporation" PRODUCT_NAME="Microsoft® Windows(TM) Operating System" FILE_VERSION="3.10" ORIGINAL_FILENAME="WINSOCK.DLL" INTERNAL_NAME="WINSOCK" LEGAL_COPYRIGHT="Copyright © Microsoft Corp. 1981-1996" VERDATEHI="0x0" VERDATELO="0x0" VERFILEOS="0x10001" VERFILETYPE="0x2" MODULE_TYPE="WIN16" 16BIT_DESCRIPTION="BSD Socket API for Windows" 16BIT_MODULE_NAME="WINSOCK" UPTO_BIN_FILE_VERSION="3.10.0.103" UPTO_BIN_PRODUCT_VERSION="3.10.0.103" VER_LANGUAGE="English (United States) [0x409]" />
</EXE>
<EXE NAME="msvcrt.dll" FILTER="GRABMI_FILTER_THISFILEONLY">
    <MATCHING_FILE NAME="msvcrt.dll" SIZE="681472" CHECKSUM="0x3FB350C4" BIN_FILE_VERSION="7.0.6000.16386" BIN_PRODUCT_VERSION="6.1.8638.16386" PRODUCT_VERSION="7.0.6000.16386" FILE_DESCRIPTION="Windows NT CRT DLL" COMPANY_NAME="Microsoft Corporation" PRODUCT_NAME="Microsoft® Windows® Operating System" FILE_VERSION="7.0.6000.16386 (vista_rtm.061101-2205)" ORIGINAL_FILENAME="msvcrt.dll" INTERNAL_NAME="msvcrt.dll" LEGAL_COPYRIGHT="© Microsoft Corporation. All rights reserved." VERDATEHI="0x0" VERDATELO="0x0" VERFILEOS="0x40004" VERFILETYPE="0x1" MODULE_TYPE="WIN32" PE_CHECKSUM="0xAB070" LINKER_VERSION="0x60000" UPTO_BIN_FILE_VERSION="7.0.6000.16386" UPTO_BIN_PRODUCT_VERSION="6.1.8638.16386" LINK_DATE="11/02/2006 09:41:53" UPTO_LINK_DATE="11/02/2006 09:41:53" EXPORT_NAME="msvcrt.dll" VER_LANGUAGE="English (United States) [0x409]" />
</EXE>
</DATABASE>

[Version.txt]
Windows NT  Version 6.0 Build: 6000
Product (0x6): Windows Vista (TM) Business
Edition: Business
BuildString: 6000.16386.x86fre.vista_rtm.061101-2205
Flavor: Multiprocessor Free
Architecture: X86
LCID: 1033

 

Thanks.

Answer 1

Try to reset search by going to Indexing Options then to the advanced options. Click on the "Restore Defaults" button and reboot your machine. Let me know if that solves it.

Answer 2

Yes, Thanks, Seems to be resolved.

Seemed like an easy resolution, but when ever i looked at the indexer options, everyhting was always unselectable.
Even the advanced options button,

But,
Looks like it wasnt that time.

All fixed, Thanks.

Answer 3

Hi John,
could you please help me explaining how did you resolve the issue of the unselectable options. I'm having the same problem. The indexing options appear to be unselectable, but still I'm getting the Windows Indexing error.
Thanks for any advice,
Miguel

Answer 4

Hi Miguel

When it next crashs, and you get the error box,
Opening up your controll panel, then close the error boxes and then try opening the Indexing Options.

Try this, im not sure, its just a guess.
Post back if it works or dosnt.

So your basicly opening the indexing options when you have no error boxes.

 

 

John

Answer 5

Miguel, you can set the registry key HKLM/Software/Microsoft/Windows Search/SetupCompletedSuccessfully to zero and reset the machine. This will effectively reset the indexer and achieve the same result.

Answer 6

same subject as above slution given above didnt fix the problem.   I am actually trying to run dvd movie.  It open the title and sudden crash with blue screen saying memory dump crash. Memory has been tested by vista program saying no problem

 

Windows NT  Version 6.0 Build: 6000
Product (0x1): Windows Vista (TM) Ultimate
Edition: Ultimate
BuildString: 6000.16386.x86fre.vista_rtm.061101-2205
Flavor: Multiprocessor Free
Architecture: X86
LCID: 1033

 

roblem signature:
  Problem Event Name: BlueScreen
  OS Version: 6.0.6000.2.0.0.256.1
  Locale ID: 1033

Additional information about the problem:
  BCCode: e3
  BCP1: 87323B80
  BCP2: 8488A020
  BCP3: 8777B1C0
  BCP4: 00000003
  OS Version: 6_0_6000
  Service Pack: 0_0
  Product: 256_1

Files that help describe the problem:
  C:\Windows\Minidump\Mini050507-05.dmp
  C:\Users\shahzad\AppData\Local\Temp\WER-57969-0.sysdata.xml
  C:\Users\shahzad\AppData\Local\Temp\WERBA3.tmp.version.txt

Read our privacy statement:
  http://go.microsoft.com/fwlink/?linkid=50163&clcid=0x0409

Answer 7

Hi. I am having the same problem of winodws showing the error message of " Windows Search Indexer has stopped working". How do I get about changing the registry key? I could not locate it. Thanks.

 

Calvin

Answer 8

I have a new Sony Vaio which is having similar problems with the indexer and error notices regarding data executed prevention and Windows defender. Vista is nothing but a headache so far and I wish I did not have it. My whole system crashed with a blue screen error, the desktop was completely blank and all my files disappeared. The CPU usage soared to 60% with no programs open. Then I got a system 32 error. I restarted in safe mode, which opened to a blank screen. Finally, I did a system restore on restart which temporarily worked but now the messages are popping up again. Microsoft should be ashamed of itself. I would appreciate any input and advice. Thanks.

Answer 9

My indexer will not start I get the following errer windows could not start the windows search service on the local computer  error 1067 the process terminated unexpectedly. and I cant use anything in the stupid computer I just got this dell with vista on it and i am beginning to hate it.  very very frustrated YES need help YES i tried booting in safe mode and the search indexer does not work in safe mode. I cant reinstall the indexer I cant find any other data on how to fix it either. please help...

Answer 10

Same problem here.  It is exasperating, because I get the error window constantly.  Tried the "resetting" indexing, and registry fixes, with no luck.  I just want the indexing to stop altogether; I can't stand anymore these constant errors.

Answer 11

Hi

I have the same problem - but when I go to Indexing Options to restore defaults" button, the item is geyed out and on top it says "Indexing is not running".

Do you have any idea how I can fix this?

Thank you so much

Answer 12

This is driving me beserk.  I am not, repeat NOT a software geek.  Please please can someone post a step by step idiots guide to solving this problem.  I have tried the last 2 sets of directions and have got nowhere, not their fault just mine as I do not wish to mess up my machine.

 

The sooner MS do a "fix" the better

Answer 13

Same problem here. I just got this new computer two weeks ago. I have an external HD with thousands of files and so after starting the indexer, I made sure to include the HD too, to havel "live" access to them.

 

Well, after running the indexer, I noticed that it created a root directory in my external HD for the following registry keys:

 

- FailedMoveNewDataLocation

- DataDirectory

- DefaultApplicationsPath

- TempPath

 

This new directory had the following Windows Search folders:

 

- Search > Data > Temp > usgthrsvc

 

These had very heavy files in them, and I was certain those files were needed for Windows Search. What made me delete them was the fact that these folders and files were created inside a "clone" folder Windows Search had created off another folder I have in my HD and it was just driving me crazy what was the reason for it.

 

So I had two folders with the same name; one with my personal documents and the other with Windows Search files. So I deleted them. Since they did not fit in the Recycle Bin, I did a "hard delete" and the files and directory were gone.

 

However, that was when everything started going crazy: Windows Search now says "Waiting

to receive indexing status"... It's been like that for the past 5 days or so.

 

I have tried every conceivable remedy, from adding and creating back those files into my HD, to setting my registry values in SetupCompletedSuccessfully to zero and nothing.

 

I have even used the "Remove Windows Features" service through Control Panel, which lets you "add" and "remove" Windows Search and nothing happens. I have even called Dell for support and they suggested a System Reinstall... which I don't want to do.

 

I am still playing with the registry to see if it works and nothing. Actually, there is something very wierd with the registry; even if I turn the SetupCompletedSuccessfully to zero and reboot, nothing happens, I try to access the Indexing Options and it says that Indexing is not on, so I go back to the registry and set SetupCompletedSuccessfully to 1 and the indexing goes back to "Waiting to receive indexing status".

 

I go to the Services feature and "restart" Windows Search and nothing... If the value on SetupCompletedSuccessfully is zero, Services will give me this error: "Windows could not start the Windows Search service on Local Computer: Error 3: The system cannot find the path specified"... I set the value of SetupCompletedSuccessfully to 1 and go back to Services, restart, Windows Search restarts but the Indexing Options box keeps on telling me the same thing "Waiting to receive indexing status", with all the buttons grayed-out but the close one.

 

Another weird thing is that even though I have set up the value of SetupCompletedSuccessfully to zero, restarted the computer and even unpluged my external HD, the Windows Search registry values go back to the paths in my external HD.... Even after I keep on deleting those directories from my external HD, Windows Searcg keeps on creating them after I plug my external HD, so at least it shows that my Windows Search is working but stalls.

 

By the way, I can change the falues and directories of some Windows Search registries but not all. Some of them give me this error: "Cannot edit xxxx: Error writing the value's new contents".

 

Is there a solution for this? Anyone?

 

Thanks!

 

MROSARIONYC

Answer 14

1. In this directory "%systemdrive%\ProgramData\Microsoft\Search\Data\Config", you need two files "gathrprm.txt" and "schema.txt"
2. Copy the "gathrprm.txt" file from the windows directory, "C:\Windows\winsxs\x86_windowssearchengine_31bf3856ad364e35_6.0.6000.16386_none_47e1b1bb326f0fb4\gathrprm.txt"
3. Copy the "schema.txt" file from the windows directory, "C:\Windows\winsxs\x86_windowssearchengine_31bf3856ad364e35_6.0.6000.16386_none_47e1b1bb326f0fb4\schema.txt"
4. Reboot

Answer 15

Thanks... but no change.. still "Waiting to receive indexing status..."

 

Answer 16

 

i trully think that it is a problem in the registry.... if thats the case, there is no way to reinstall the registry rite? Other than just re-installing the whole system... rite?

Answer 17

Would Microsoft PLEASE post a simple step-by-step instruction to correct this problem.  I am seriously sick of this error popping up NON-STOP. I can't use Outlook and it's VERY, VERY, VERY frustrating.  I am now regretting purchasing Windows Vista (Business), because I can't even conduct business without this constant annoyance.  The "advanced" option is deselected and I tried some of the other recommendations. None of them worked. I contacted Dell, where I purchased my laptop and they were of no use and they deleted my Outlook and Works which did not solve anything.

MICROSOFT - Please post something and tell us non-IT people how to get to the "Registry" or anything else needed to resolve this. Do we have to start by going to My Computer, Control Panel, What???? All of these computer languages are not helping. One posting listed instructions for copying a bunch of stuff. However, it didn't indicate from WHERE nor did it indicate where it was to be pasted. PLEASE, PLEASE help us before I throw my laptop over a cliff. 

        

Answer 18

I too have a new Dell PC and have been experiencing this error for at least a couple of weeks at first I merrily clicked on the link to search the web for a solution to no avail but it is much more frequent now and whether it is a coincidence I am not sure but I am now experiencing installation upgrade /patch problems.  A safe and solid answer from Microsoft would be great like a solution within an update rather quick! As I have to say I have read through the threads and I am not happy to mess about in the reg key as I am not that proficient and it seems that in some cases it has made it worse?!!!

So Microsoft ; please put us out of our misery, it is wasting hours and hours of precious time and causing much angst.

 

 

Answer 19

Same problem on my hp laptop.  Can't restore defaults because the options button is greyed out. help.

 

Answer 20

Thought I would jump on this pile as well. Problem started a week ago, I think after an automatic update. I have tried several solutions with no success! Outlook becomes basically unusable with this error. Microsoft does need to post a step-by-step fix ASAP!

Answer 21

My question is, is this problem exclusive to Dell laptops only?  I have 2 Dell laptops and 1 Toshiba laptop, all running Vista.  The "Search Indexer" error msg appears on the Dells, and not on the Toshiba.

 

Answer 22

no definitely ran into it on my hp, a file apparently got corrupted when i was trying to install norton; internet security of all things.  I did some poking around and found a solution that worked for me.  I will copy it below, it is from a post on techsupportforums.com:

 

I just want to say, for the sake of anybody who finds this on Google, that I fixed it. The trick is to delete all files related to search indexing, located by default at:

C:\ProgramData\Microsoft\Search\Data\Applications\Windows

and:

C:\ProgramData\Microsoft\Search\Data\Temp

Delete all files and folders in these directories (you might want to make a backup, I did, but it proved unnecessary).

Then, change the service back to starting automatically. You still can't start the service until you reboot, at which time Windows will rebuild the index.

 

This procedure worked for me.  You will need to enable "show hidden files" on your windows explorer toolbar to see the above file locations.  I would follow the recommendation to copy the files to a disk or something just in case, I do not claim to understand how this stuff works.  Good luck all, and thanks for nothing microsoft, you were zero help.

Answer 23

Wondered where the MS guys were?  This is the 3rd or 4th thread on this topic.  I repeat - my prblems started when I loaded Office 2007.  Indexer stopped etc.  Went back to a pre office 2007 restore point (Office 2003).  Did what I was told and indexer seemed to work - boxes accessible etc.  Re-loaded Office 2007 and it all went wrong again.  So still no indexer.  MS don't hide your light under a bushel tell us how to solve it.

Answer 24

Wonders never cease.  Switched on this evening. Thought I had better check Indexing OPtions and lo and behold it all seems to be working.  Magic!   Have no idea what I did but there you go.   Still think there is  glitch in the code somewhere - but that is for the MS geeks to look at.

 

Answer 25

Finally I am able to post to this forum. I had posted my complaint in the past also, and somehow I was blocked: I could not log in to post a reply until now.

 

I was able to fix my problem with WS (well, part of it at least). This is what I did.

 

I followed the instructions posted here on where to look for and copy these files: gathrprm, msscolmn, schema:

 

Go to C:\Windows\winsxs\x86_windowssearchengine_31bf3856ad364e35_6.0.6000.16386_none_47e1b1bb326f0fb4

 

And copy those three files and put them in a secure folder somewhere else in your computer where they are very accesible.

 

Then make sure to go to Services (Start button > Type Services), double click on Windows Search, select Startup Type = Disabled and then hit Stop on Service status. Dont close this window yet, since sometimes the Windows Service starts automatically. If that happens, you wont continue with the next steps and going back to the Services window will allow you to stop the service again, if necessary.

 

Go to data folders created by Windows Search (in your C drive and in the Index Location you chose when you 1st ran WS, and delete all the files inside them, but leave the empty folders (if windows gives you errors when deleting, go back to Services and make sure WS is Stopped, or hard-delete the files with Shift+Delet because they may be too big for your trash can). These should be the data folders and their respective locations (names with * are text files, the rest are folders):

 

C:\Windows\System32\Search
      > Config > *gathrprm, *msscolmn, *schema
      > Data  > Config > *gathrprm, *schema

 

your new Index Location (in my case is an external HD)

 

J:\Articles > Search
    > Config > *gathrprm, *msscolmn, *schema
           > Data
      > Applications > Windows > Config > *gathrprm, *schema
      > Config > *gathrprm, *schema
      > Temp > usgthrsvc

 

Make sure to delete all the "gathrprm, msscolmn, schema" occurences and any other file or folder that are not called: Config, Data, Applications, Windows, Temp and usgthrsvc. Everything else you can delete. If you have many files, these data files may be very very large, just take your time deleting them. Temp is ussually empty, but check it any ways.

 

Then, go to Run > regedit  > and open these folders: HKEY_LOCAL_MACHINE > then SOFTWARE > then Microsoft > Windows Search.

 

On the right, you will get details of the Windows Search Registry. These are the most important places you should look for: from the 13 files in that window, make sure that:

 

(Default)

 

DataDirectory

 

FailedMoveNewDataLocation

 

FailedMoveOldDataLocation

 

and

 

InstallDirectory

 

Match with the information in this folder: Gathering Manager, which is a folder located on the left. 

 

In the registry keys of the Windows Search folder (the 1st one) you can make changes, but not in the keys of the Gathering Manager. Make sure that the info in Gathering Manager matches to the T with the info in Windows Search.

 

Create folders in the data destination folders (mentioned above) if they do not exist, following the break-down from the keys on Gathering Manager, this is pretty much a fixed map, and the info on the Windows Search folder does not match, you will have problems with the software.

 

After you have made your changes and corrections, go back to the Windows Search folder (the 1st one), click on SetupCompletedSuccessfully and make sure it says 0, not one. Also the same for MustRecover & UseLowPriorityConfiguration.

 

Close all the windows and RESTART...

 

After restart, open the Indexing Options menue (Start > type Indexing...). Make sure it says that it is not working or that it has been stopped and that all of the boxes are grayed-out.  If that's the case, then proceed, if not, make sure to go to Services (Start > type Services), look for Windows Search and turn it off like mentioned above: Startup Type = Disabled and then hit Stop on Service status.

 

Open the folder where you saved these files: gathrprm, msscolmn, schema;

 

Now, open the roots of the data locations for WS, like mentioned above, and paste those files back into those empty folders, following the same break-down:

C:\Windows\System32\Search
      > Config > *gathrprm, *msscolmn, *schema
      > Data  > Config > *gathrprm, *schema

 

your new Index Location (in my case is an external HD)

 

J:\Articles > Search
    > Config > *gathrprm, *msscolmn, *schema
           > Data

> Applications > Windows > Config > *gathrprm, *schema
      > Config > *gathrprm, *schema
      > Temp > usgthrsvc

 

Now, with those files back in those folders, go back to Services, select Windows Search, make Startup Type: Automatic and hit Start. Your WS, in theory, should start working perfectly fine.... or at least most of it.

I have done this many times and it works. The key is to match in the info from the WS registry and that those files and folders exist for real in the correct locations. Again, you can't change the info on Gathering Manager but you can in Windows Search.

 

Hope this helps!

 

Miguel

 

Answer 26

Has this worked for anyone?

 

Answer 27

Spoke far too soon.  As was well for a few days - now it has turned off again and I cannot get it started.  Every thing as slow as a tortoise

 

Answer 28

But did it work? If you have many files, you gotta give it time to re-index, it took mine 2 days to index over 230K files in my HD.... however, i have encountered an error (or conflict) in the search of Outlook 2007, which it does not work... if I disable WS, it works, if I turn it on, the search feature in Outlooks stops working and gives me this error: "The messaging interface has returned an unknown error. If the problem persists, please restart Outlook".

I really dont know the reason for this conflict and I have resorted to just forget about the search feature in Outlook and use WS which is working perfectly fine.

When I go to the properties of the Outlook search, and I remove the check marks on the data files to index, then it works ok... but WS removes those files from the Index.... If I add the check marks on Outlook search to index those data files, Outlook search stops working but WS takes over and add those files to the index....

Why does this happen????

Answer 29

Tried a restore to a known good point - that did not work.  Tried copying schema and other files as directed got this mesage in the event viewer:

 

<Provider Name="Microsoft-Windows-Search" Guid="{CA4E628D-8567-4896-AB6B-835B221F373F}" EventSourceName="Windows Search Service" />

  <EventID Qualifiers="49152">1006</EventID>

  <Version>0</Version>

  <Level>2</Level>

  <Task>1</Task>

  <Opcode>0</Opcode>

  <Keywords>0x80000000000000</Keywords>

  <TimeCreated SystemTime="2007-08-09T13:48:04.000Z" />

  <EventRecordID>28565</EventRecordID>

  <Correlation />

  <Execution ProcessID="0" ThreadID="0" />

  <Channel>Application</Channel>

  <Computer>Potterhome</Computer>

  <Security />

  </System>

- <EventData>

  <Data Name="ExtraInfo" />

  <Data Name="Phase">4</Data>

  <Data Name="HR">0x80070020</Data>

  </EventData>

  </Event>

Please can you help me resolve this.  Checked my restore points and noticed that there were a couple of Windows updates after the point at which things seemed to work on 2 Aug 07

Answer 30

I dont know what else to say. I hac activated and deactivated WS may times following my instructions and it works well. You need to go back and thougroughly check the registry, it think that is where the problem lies....

Answer 31

I have tried Eric (MSFT) solution  by reseting the registry key and it went well.

Answer 32

I get the search indexer working - it goes for a couple of daysthen stops again.   The latest event viewer error is:

 

Provider Name="Microsoft-Windows-Search" Guid="{CA4E628D-8567-4896-AB6B-835B221F373F}" EventSourceName="Windows Search Service" />

  <EventID Qualifiers="49152">1006</EventID>

  <Version>0</Version>

  <Level>2</Level>

  <Task>1</Task>

  <Opcode>0</Opcode>

  <Keywords>0x80000000000000</Keywords>

  <TimeCreated SystemTime="2007-08-14T18:31:58.000Z" />

  <EventRecordID>30853</EventRecordID>

  <Correlation />

  <Execution ProcessID="0" ThreadID="0" />

  <Channel>Application</Channel>

  <Computer>Potterhome</Computer>

  <Security />

  </System>

- <EventData>

  <Data Name="ExtraInfo" />

  <Data Name="Phase">4</Data>

  <Data Name="HR">0x80070020</Data>

  </EventData>

  </Event>

 

PS.  Why, oh why when it is working but running slowly do I get a message which says " Slow running due to user activity".   I thought "user activity" what what we bought these machines for.   Of course MS may have better ideas.  Please can MS respond. This is getting beyond a joke

Answer 33

Hi Eric Wolz - MSFT

 

Works perfectly. THANKS ALOT. Saved me from reformatting. Can you imagine? HP told me to reformat. Someone from Microsoft should train those HP Customer Service Agent. I hope the MS guys are taking note on this forum so they can find a way to debug this problem!

 

Anyways, for those who have the same problem as Miguel and cannot reboot Search Indexer here's step by step what to do: (Sorry Eric, some steps are missing in your answer and took me time to get it

 

Go to my computer

Click on the C: Drive or your main drive

Click on Windows

Go to Regetit (Registry Editor) and double click

Vista is asking for permission - Allow

Open Hkey_local_machine

Open software

Open Microsoft

Open Windows Search

on your right there's a window. Look for file Setupcompletedsuccessfully

Right click on the file

Click Modify (A window will open)

Set the value data to zero

Press Ok

 

RESTART your computer

 

PLEASE NOTE: It is possible that during restart, your computer might freeze. But if the llittle yellow or green or red light is on (light near the startup button) or flashing that means your computer is working and don't try to reboot. Give it time to assess the changes. After that you can open the Indexed Options in the control Panel (for Classic View or follow the steps described above to get to Indexed Options) and you will see the Indexer indexing all your files. Better not close the computer and let the indexer index ALL your files 'till the end.

 

For now, it solved alot of problems. Error message does not appear anymore. But for how long? I will keep you posted.

 

Natasha

 

 

 

Answer 34

I read the fix for the search indexer except I can't click on any of the buttons because it says it isn't running. As a matter of fact, that's the problem. It is crashing and then it says to let windows find a solution on-line and then it just keeps crashing. I looked at the error log and it's crashed continuously since I got this machine last month. Any ideas on how to reset the darn thing?

Answer 35

Hi  dogbob,

 

I had the same problem. As posted earlier in this forum, here are the steps to reboot the search indexer. Try this it should work.

 

Re: [Vista 6000] [Search Indexer] Stoped Working And Was Closed

Hi Eric Wolz - MSFT   Works perfectly. THANKS ALOT. Saved me from reformatting. Can you imagine? HP told me to reformat. Someone from Microsoft should train those HP Customer Service Agent. I hope the MS guys are taking note on this forum so they can find a way to debug this problem!   Anyways, for those who have the same problem as Miguel and cannot reboot Search Indexer here's step by step what to do: (Sorry Eric, some steps are missing in your answer and took me time to get it   Go to my computer Click on the C: Drive or your main drive Click on Windows Go to Regetit (Registry Editor) and double click Vista is asking for permission - Allow Open Hkey_local_machine Open software Open Microsoft Open Windows Search on your right there's a window. Look for file Setupcompletedsuccessfully Right click on the file Click Modify (A window will open) Set the value data to zero Press Ok   RESTART your computer   PLEASE NOTE: It is possible that during restart, your computer might freeze. But if the llittle yellow or green or red light is on (light near the startup button) or flashing that means your computer is working and don't try to reboot. Give it time to assess the changes. After that you can open the Indexed Options in the control Panel (for Classic View or follow the steps described above to get to Indexed Options) and you will see the Indexer indexing all your files. Better not close the computer and let the indexer index ALL your files 'till the end.   For now, it solved alot of problems. Error message does not appear anymore. But for how long? I will keep you posted.   Natasha

Answer 36

Thanks Natasha,

 

That was an easy fix, and so far no error messages.  Mine started after I ran Max Registry Cleaner, so it was a self-inflicted wound, as so often happens.  But this seems to have corrected it, and took a minute or two; nice & easy, just the way I like my fixes!

 

Royal3

 

Answer 37

pleinelune, works great so far. Thank you!

 

Answer 38

Yes, there has been known issues with registry cleaners deleting registry keys that we require.

Answer 39

Hi Miguel,

your posting seems to be very helpful - I lost the HDD with my index-directory  - but, could you please post the structure of the index-directory again? It is not quite clear (for me) what directory is a sub-directory...

 

J:\Articles > Search
    > Config > *gathrprm, *msscolmn, *schema
           > Data
      > Applications > Windows > Config > *gathrprm, *schema
      > Config > *gathrprm, *schema
      > Temp > usgthrsvc

 

Thank's a lot!

Michael

 

Answer 40

John Mallah wrote:

Hello, Having major propblems with the Indexer, Its causing major system performance issues and problems... I dont know when or how it started, but recently. The Indexer will crash, and pop up an error box. This happens when... Deleting a file. Opening Outlook. (Office 2007) Moving Files. Pracatly anything to do with the Indexer. While deleting or moving files system performance slows to a trail. Outlook stops completely. Opening controll panel, then indexing options... States that Indexing is not running. Basicly it wont stop crashing. Any workaround or fix? Windows Vista Business x86 6.0 Build 6000 Intel Pentium 4 x86 Family 15 Model 3stepping 4 1.5 GIG Memory Product Microsoft Windows Search Indexer Problem Stopped working Date 04/03/2007 15:23 Status Not Reported Problem signature Problem Event Name: InPageError Error Status Code: c000009c Faulting Media Type: 00000003 OS Version: 6.0.6000.2.0.0.256.6 Locale ID: 2057 Additional Information 1: 6f3b Additional Information 2: 2bd88d149d85c0ab26359bfa0a122304 Additional Information 3: a509 Additional Information 4: 1953256f91532f6ba546df0162013f4b Files that help describe the problem Version.txt AppCompat.txt memory.hdmp minidump.mdmp [AppCompat.txt] <?xml version="1.0" encoding="UTF-16"?> <DATABASE> <EXE NAME="SYSTEM INFO" FILTER="GRABMI_FILTER_SYSTEM">     <MATCHING_FILE NAME="advapi32.dll" SIZE="770048" CHECKSUM="0xF07A52F9" BIN_FILE_VERSION="6.0.6000.16386" BIN_PRODUCT_VERSION="6.0.6000.16386" PRODUCT_VERSION="6.0.6000.16386" FILE_DESCRIPTION="Advanced Windows 32 Base API" COMPANY_NAME="Microsoft Corporation" PRODUCT_NAME="Microsoft® Windows® Operating System" FILE_VERSION="6.0.6000.16386 (vista_rtm.061101-2205)" ORIGINAL_FILENAME="advapi32.dll.mui" INTERNAL_NAME="advapi32.dll" LEGAL_COPYRIGHT="© Microsoft Corporation. All rights reserved." VERDATEHI="0x0" VERDATELO="0x0" VERFILEOS="0x40004" VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0xC54C5" LINKER_VERSION="0x60000" UPTO_BIN_FILE_VERSION="6.0.6000.16386" UPTO_BIN_PRODUCT_VERSION="6.0.6000.16386" LINK_DATE="11/02/2006 09:39:30" UPTO_LINK_DATE="11/02/2006 09:39:30" EXPORT_NAME="ADVAPI32.dll" VER_LANGUAGE="English (United States) [0x409]" />     <MATCHING_FILE NAME="gdi32.dll" SIZE="296448" CHECKSUM="0xAD21A1D1" BIN_FILE_VERSION="6.0.6000.16386" BIN_PRODUCT_VERSION="6.0.6000.16386" PRODUCT_VERSION="6.0.6000.16386" FILE_DESCRIPTION="GDI Client DLL" COMPANY_NAME="Microsoft Corporation" PRODUCT_NAME="Microsoft® Windows® Operating System" FILE_VERSION="6.0.6000.16386 (vista_rtm.061101-2205)" ORIGINAL_FILENAME="gdi32" INTERNAL_NAME="gdi32" LEGAL_COPYRIGHT="© Microsoft Corporation. All rights reserved." VERDATEHI="0x0" VERDATELO="0x0" VERFILEOS="0x40004" VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0x514CE" LINKER_VERSION="0x60000" UPTO_BIN_FILE_VERSION="6.0.6000.16386" UPTO_BIN_PRODUCT_VERSION="6.0.6000.16386" LINK_DATE="11/02/2006 09:39:31" UPTO_LINK_DATE="11/02/2006 09:39:31" EXPORT_NAME="GDI32.dll" VER_LANGUAGE="English (United States) [0x409]" />     <MATCHING_FILE NAME="kernel32.dll" SIZE="874496" CHECKSUM="0x8440BFFC" BIN_FILE_VERSION="6.0.6000.16386" BIN_PRODUCT_VERSION="6.0.6000.16386" PRODUCT_VERSION="6.0.6000.16386" FILE_DESCRIPTION="Windows NT BASE API Client DLL" COMPANY_NAME="Microsoft Corporation" PRODUCT_NAME="Microsoft® Windows® Operating System" FILE_VERSION="6.0.6000.16386 (vista_rtm.061101-2205)" ORIGINAL_FILENAME="kernel32" INTERNAL_NAME="kernel32" LEGAL_COPYRIGHT="© Microsoft Corporation. All rights reserved." VERDATEHI="0x0" VERDATELO="0x0" VERFILEOS="0x40004" VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0xD9614" LINKER_VERSION="0x60000" UPTO_BIN_FILE_VERSION="6.0.6000.16386" UPTO_BIN_PRODUCT_VERSION="6.0.6000.16386" LINK_DATE="11/02/2006 09:42:24" UPTO_LINK_DATE="11/02/2006 09:42:24" EXPORT_NAME="KERNEL32.dll" VER_LANGUAGE="English (United States) [0x409]" />     <MATCHING_FILE NAME="ntdll.dll" SIZE="1162656" CHECKSUM="0x8FD38B20" BIN_FILE_VERSION="6.0.6000.16386" BIN_PRODUCT_VERSION="6.0.6000.16386" PRODUCT_VERSION="6.0.6000.16386" FILE_DESCRIPTION="NT Layer DLL" COMPANY_NAME="Microsoft Corporation" PRODUCT_NAME="Microsoft® Windows® Operating System" FILE_VERSION="6.0.6000.16386 (vista_rtm.061101-2205)" ORIGINAL_FILENAME="ntdll.dll.mui" INTERNAL_NAME="ntdll.dll" LEGAL_COPYRIGHT="© Microsoft Corporation. All rights reserved." VERDATEHI="0x0" VERDATELO="0x0" VERFILEOS="0x40004" VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0x128171" LINKER_VERSION="0x60000" UPTO_BIN_FILE_VERSION="6.0.6000.16386" UPTO_BIN_PRODUCT_VERSION="6.0.6000.16386" LINK_DATE="11/02/2006 09:43:37" UPTO_LINK_DATE="11/02/2006 09:43:37" EXPORT_NAME="ntdll.dll" VER_LANGUAGE="English (United States) [0x409]" />     <MATCHING_FILE NAME="ole32.dll" SIZE="1314816" CHECKSUM="0xEFDF1843" BIN_FILE_VERSION="6.0.6000.16386" BIN_PRODUCT_VERSION="6.0.6000.16386" PRODUCT_VERSION="6.0.6000.16386" FILE_DESCRIPTION="Microsoft OLE for Windows" COMPANY_NAME="Microsoft Corporation" PRODUCT_NAME="Microsoft® Windows® Operating System" FILE_VERSION="6.0.6000.16386 (vista_rtm.061101-2205)" ORIGINAL_FILENAME="OLE32.DLL.MUI" INTERNAL_NAME="OLE32.DLL" LEGAL_COPYRIGHT="© Microsoft Corporation. All rights reserved." VERDATEHI="0x0" VERDATELO="0x0" VERFILEOS="0x40004" VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0x14E4A9" LINKER_VERSION="0x60000" UPTO_BIN_FILE_VERSION="6.0.6000.16386" UPTO_BIN_PRODUCT_VERSION="6.0.6000.16386" LINK_DATE="11/02/2006 09:42:42" UPTO_LINK_DATE="11/02/2006 09:42:42" EXPORT_NAME="ole32.dll" VER_LANGUAGE="English (United States) [0x409]" />     <MATCHING_FILE NAME="oleaut32.dll" SIZE="558080" CHECKSUM="0x24E63A53" BIN_FILE_VERSION="6.0.6000.16386" BIN_PRODUCT_VERSION="6.0.6000.16386" PRODUCT_VERSION="6.0.6000.16386" COMPANY_NAME="Microsoft Corporation" FILE_VERSION="6.0.6000.16386" INTERNAL_NAME="OLEAUT32.DLL" LEGAL_COPYRIGHT="© Microsoft Corporation. All rights reserved." VERDATEHI="0x0" VERDATELO="0x0" VERFILEOS="0x40004" VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0x94097" LINKER_VERSION="0x60000" UPTO_BIN_FILE_VERSION="6.0.6000.16386" UPTO_BIN_PRODUCT_VERSION="6.0.6000.16386" LINK_DATE="11/02/2006 09:42:45" UPTO_LINK_DATE="11/02/2006 09:42:45" EXPORT_NAME="OLEAUT32.dll" VER_LANGUAGE="English (United States) [0x409]" />     <MATCHING_FILE NAME="shell32.dll" SIZE="11314688" CHECKSUM="0xE0871A1E" BIN_FILE_VERSION="6.0.6000.16386" BIN_PRODUCT_VERSION="6.0.6000.16386" PRODUCT_VERSION="6.0.6000.16386" FILE_DESCRIPTION="Windows Shell Common Dll" COMPANY_NAME="Microsoft Corporation" PRODUCT_NAME="Microsoft® Windows® Operating System" FILE_VERSION="6.0.6000.16386 (vista_rtm.061101-2205)" ORIGINAL_FILENAME="SHELL32.DLL.MUI" INTERNAL_NAME="SHELL32" LEGAL_COPYRIGHT="© Microsoft Corporation. All rights reserved." VERDATEHI="0x0" VERDATELO="0x0" VERFILEOS="0x40004" VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0xAD8CDD" LINKER_VERSION="0x430020" UPTO_BIN_FILE_VERSION="6.0.6000.16386" UPTO_BIN_PRODUCT_VERSION="6.0.6000.16386" LINK_DATE="11/02/2006 09:43:16" UPTO_LINK_DATE="11/02/2006 09:43:16" EXPORT_NAME="SHELL32.dll" VER_LANGUAGE="English (United States) [0x409]" />     <MATCHING_FILE NAME="user32.dll" SIZE="633856" CHECKSUM="0xFA697C" BIN_FILE_VERSION="6.0.6000.16386" BIN_PRODUCT_VERSION="6.0.6000.16386" PRODUCT_VERSION="6.0.6000.16386" FILE_DESCRIPTION="Multi-User Windows USER API Client DLL" COMPANY_NAME="Microsoft Corporation" PRODUCT_NAME="Microsoft® Windows® Operating System" FILE_VERSION="6.0.6000.16386 (vista_rtm.061101-2205)" ORIGINAL_FILENAME="user32" INTERNAL_NAME="user32" LEGAL_COPYRIGHT="© Microsoft Corporation. All rights reserved." VERDATEHI="0x0" VERDATELO="0x0" VERFILEOS="0x40004" VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0x9F083" LINKER_VERSION="0x60000" UPTO_BIN_FILE_VERSION="6.0.6000.16386" UPTO_BIN_PRODUCT_VERSION="6.0.6000.16386" LINK_DATE="11/02/2006 09:44:00" UPTO_LINK_DATE="11/02/2006 09:44:00" EXPORT_NAME="USER32.dll" VER_LANGUAGE="English (United States) [0x409]" />     <MATCHING_FILE NAME="wininet.dll" SIZE="822272" CHECKSUM="0x7AC6E1FB" BIN_FILE_VERSION="7.0.6000.16386" BIN_PRODUCT_VERSION="7.0.6000.16386" PRODUCT_VERSION="7.00.6000.16386" FILE_DESCRIPTION="Internet Extensions for Win32" COMPANY_NAME="Microsoft Corporation" PRODUCT_NAME="Windows® Internet Explorer" FILE_VERSION="7.00.6000.16386 (vista_rtm.061101-2205)" ORIGINAL_FILENAME="wininet.dll.mui" INTERNAL_NAME="wininet.dll" LEGAL_COPYRIGHT="© Microsoft Corporation. All rights reserved." VERDATEHI="0x0" VERDATELO="0x0" VERFILEOS="0x40004" VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0xD0C56" LINKER_VERSION="0x60000" UPTO_BIN_FILE_VERSION="7.0.6000.16386" UPTO_BIN_PRODUCT_VERSION="7.0.6000.16386" LINK_DATE="11/02/2006 09:44:57" UPTO_LINK_DATE="11/02/2006 09:44:57" EXPORT_NAME="WININET.dll" VER_LANGUAGE="English (United States) [0x409]" />     <MATCHING_FILE NAME="WINSOCK.DLL" SIZE="2864" CHECKSUM="0x73AE8088" BIN_FILE_VERSION="3.10.0.103" BIN_PRODUCT_VERSION="3.10.0.103" PRODUCT_VERSION="3.10" FILE_DESCRIPTION="Windows Socket 16-Bit DLL" COMPANY_NAME="Microsoft Corporation" PRODUCT_NAME="Microsoft® Windows(TM) Operating System" FILE_VERSION="3.10" ORIGINAL_FILENAME="WINSOCK.DLL" INTERNAL_NAME="WINSOCK" LEGAL_COPYRIGHT="Copyright © Microsoft Corp. 1981-1996" VERDATEHI="0x0" VERDATELO="0x0" VERFILEOS="0x10001" VERFILETYPE="0x2" MODULE_TYPE="WIN16" 16BIT_DESCRIPTION="BSD Socket API for Windows" 16BIT_MODULE_NAME="WINSOCK" UPTO_BIN_FILE_VERSION="3.10.0.103" UPTO_BIN_PRODUCT_VERSION="3.10.0.103" VER_LANGUAGE="English (United States) [0x409]" /> </EXE> <EXE NAME="msvcrt.dll" FILTER="GRABMI_FILTER_THISFILEONLY">     <MATCHING_FILE NAME="msvcrt.dll" SIZE="681472" CHECKSUM="0x3FB350C4" BIN_FILE_VERSION="7.0.6000.16386" BIN_PRODUCT_VERSION="6.1.8638.16386" PRODUCT_VERSION="7.0.6000.16386" FILE_DESCRIPTION="Windows NT CRT DLL" COMPANY_NAME="Microsoft Corporation" PRODUCT_NAME="Microsoft® Windows® Operating System" FILE_VERSION="7.0.6000.16386 (vista_rtm.061101-2205)" ORIGINAL_FILENAME="msvcrt.dll" INTERNAL_NAME="msvcrt.dll" LEGAL_COPYRIGHT="© Microsoft Corporation. All rights reserved." VERDATEHI="0x0" VERDATELO="0x0" VERFILEOS="0x40004" VERFILETYPE="0x1" MODULE_TYPE="WIN32" PE_CHECKSUM="0xAB070" LINKER_VERSION="0x60000" UPTO_BIN_FILE_VERSION="7.0.6000.16386" UPTO_BIN_PRODUCT_VERSION="6.1.8638.16386" LINK_DATE="11/02/2006 09:41:53" UPTO_LINK_DATE="11/02/2006 09:41:53" EXPORT_NAME="msvcrt.dll" VER_LANGUAGE="English (United States) [0x409]" /> </EXE> </DATABASE> [Version.txt] Windows NT  Version 6.0 Build: 6000 Product (0x6): Windows Vista (TM) Business Edition: Business BuildString: 6000.16386.x86fre.vista_rtm.061101-2205 Flavor: Multiprocessor Free Architecture: X86 LCID: 1033   Thanks.

Answer 41

You have an exception status code of c000009c. This translates to STATUS_DEVICE_DATA_ERROR  which means that the OS couldn't page in the memory due to a disk error (maps to Win32 error: ERROR_CRC). This is most likely a hardware failure.

 

Answer 42

Hi Michael. Sorry for the delay. All in red are subdirectories inside Search, which is the main directory of the Indexer in your external HD:

> Config > *gathrprm, *msscolmn, *schema

> Data > Applications > Windows > Config > *gathrprm, *schema

          (Inside Data) Config > *gathrprm, *schema

          (Inside Data) Temp > usgthrsvc

All with * are files inside the directories. 

Hope that helps. Please let me know and I'll post a more detailed explanation.

Miguel

Answer 43

 

Hi Miguel,

thanks for your answer! It works fine now!!

Answer 44

Great!!! 

Answer 45

Hi David, same problem here for over 3-4 weeks now- the "modify" and "advanced" option selections are grey in the indexing options page, therefore unaccessible.  Is there some other way to activate access to them.  Please help me, the problem seems to be getting progressively worse with my system.

 

Thank you.... John Perry

 

Answer 46

I have the same problem. Its been happening for the last couple of weeks.

My machine is an Acer & still don't have a solution.

 

Answer 47

 

If you ask me ... this is a big Windows Vista bug.  The "windows search indexer has stopped working" error keeps coming over and over -- even though I did the proceedures recommended here.

 

It seems Windows Vista does not like external hard drives -- like Western Digital, Seagate, or SimpleTech.  No matter what external hard drive I use, I get the error.

 

Not only are we burdend by the SLOW copy file functions ... now we have this miserable problem to deal with.  Windows explorer needs a rework.

 

 

Answer 48

After having most of the symptoms other users had regarding problems getting the search engine activate here is a quick summary.

 

Make sure you TEMP path is set where you want it to be and working.

Run SFC  /SCANNOW  to ensure relevant Search files are in system areas.

Check registry 'HKLM/Software/Microsoft/Windows Search'

 for the Search Data folder 'DataDirectory' ... probably a sub folder from your Temp Path.

 

e.g.   <TempPath>\Search\Data

 

Copy the directory structure from C:\ProgramData\Microsoft\Search\Data\ to your Search Data area you found in the registry    top level folders are Applications, Config and Temp.

 

Copy the two schema TXT files from "%systemdrive%\ProgramData\Microsoft\Search\Data\Config" to you Search Data folder \ Config

 

Now go back to the registry and set

SetupCompletedSuccessfully to 0

 

Reboot

 

Answer 49

Thanks heaps for the help, saved ripping my remaining hair out....lol it has workd, but like you say, I'll be keeping an eye on it until they come out with a proper patch for it, I dare say that the patch will replicate your procedure.

 

Cheers

 

 

pete (aka Ozsoldier)

 

Answer 50

Found your fix online and it worked like a charm. Thanks.

Answer 51

No, this is not exclusive to Dell, I have an Aspire 5050 and I have had this message for a month, it's pissing me off to be quite frank. I was able to fix it once and now it's started again.

Answer 52

Where do I find Indexing Options?

Answer 53

Hi --

I have exactly the same problem -- Indexer has stopped running. It seems the advice you gave works. However, where do I find "Indexing Options" and "advanced options" so I can restore the defaults.

Thanks,
Gary

Answer 54

Control Panel > Classic View > Indexing Options > Advanced

 

Hope that helps 'gadaha'

 

Cheers

Answer 55

Dear Ozsoldier

The "Advanced" option is greyed out. Now what to do? Windows is struggling to find all my files, literally.

I don't understand how to execute the instructions given by TravelHigh on 1 October this year. Please help. Thanks.

Sincerely, Pranada

Answer 56

Hi Pranada,

  This is what Natasha posted on page 3 of this forum, and it has worked for me, although I have had to repeat it about every third week. but it does work. NOTE, (since doing this a Vista update 3 days ago of about 250Mb could have fixed it??).

 

Go to my computer

Click on the C: Drive or your main drive

Click on Windows

Go to Regetit (Registry Editor) and double click

Vista is asking for permission - Allow

Open Hkey_local_machine

Open software

Open Microsoft

Open Windows Search

on your right there's a window. Look for file Setupcompletedsuccessfully

Right click on the file

Click Modify (A window will open)

Set the value data to zero

Press Ok

 

RESTART your computer

 

PLEASE NOTE: It is possible that during restart, your computer might freeze. But if the llittle yellow or green or red light is on (light near the startup button) or flashing that means your computer is working and don't try to reboot. Give it time to assess the changes. After that you can open the Indexed Options in the control Panel (for Classic View or follow the steps described above to get to Indexed Options) and you will see the Indexer indexing all your files. Better not close the computer and let the indexer index ALL your files 'till the end.

 

For now, it solved alot of problems. Error message does not appear anymore. But for how long? I will keep you posted.

 

Natasha

 

After you have carried out this action you can access the advanced icon.

 

Hope this is helpful.

 

cheers

 

Peter

Answer 57

Hi

I have the same probl. I did the things above but now unter Index Options the is standing "waiting for indexing" (have a german system -> "Auf empfang des indizierungsstatus wird gewartet" )

 

Another Problem is that Outlook2k7 is reporting following error:

 

Protokollname: Application
Quelle: Outlook
Datum: 08.01.2008 09:22:44
Ereignis-ID: 35
Aufgabenkategorie:Keine
Ebene: Fehler
Schlüsselwörter:Klassisch
Benutzer: Nicht zutreffend
Computer: XXXX
Beschreibung:
Fehler beim Bestimmen, ob sich der Speicher im Crawlbereich befindet (Fehler=0x80004005).

 

What can i do?

 

Answer 58

THANK GOD FOR NATASHA!!!!!! OF COURSE MICROSOFT NEVER RESPONDED.  I FOLLOWED YOUR VERY SIMPLE INSTRUCTIONS WHICH WAS NEEDED AND FINALLY NO MORE STUPID MESSAGES AND I CAN FINALLY USE OUTLOOK AND ALL OTHER PROGRAMS AND MOVE ON WITH MY LIFE!!!! I CAN'T THANK YOU ENOUGH.   

 

Answer 59

That doesn't help me..... this problem has been going on for like 8 months and Iam about to throw the computer......when in the control panel and indexing opions, the advanced is not highlighted for me to click on, so now what it is the most annoying thing in the world..........

Answer 60

Miguel, my problem with windows search was just as described in this thread and has been aggravating me for weeks.  I have tried all sorts of suggestions to no avail.  Most recently your method was applied as this looked very promising...but it failed again.  Your suggestions are from August 2007.  Since the windows search 4 has been released and installed and I have Vista Home Premium and SP1, but my problems can be described exactly as this thread describes.  Can you assist me?

 

Answer 61

 What Natasha posted on page 3 of this forum worked for me. I would like to understand why I only started to have this problem in Jan 2009.

Answer 62

maybe you should take a search add-in for outlook...

i hope this solves your problems with the wds

 

lookeen

Answer 63

I am also having this huge issue gettin my indexer to start. Like everyone above my indexing options app in the control panel has all button except advanced grayed out. When you go in the to advanced screen you can do nothing. I have read through these threads and have followed the advice of copying the two file into the correcr config directory and stil the service wont start and no chage with my indexer. I read this thread and have a question about the following directories you recomend I delete:

C:\ProgramData\Microsoft\Search\Data\Applications\Windows

and:

C:\ProgramData\Microsoft\Search\Data\Temp

Each time I delete these folders, right before my eyes the re-created themselves. Any advice would be of great help.

Answer 64

I think these directories are created from WDS. Maybe WDS is continously indexing you computer and the files you delete are from WDS?
I found an article who describes how to get Instant Search working again. Perhaps this will help, if not i hope it does for other people :)

How to fix Outlook 2007 Instant Search from not working