This did the trick. Thank you so much, Tim for finding this fix. Seems to me
MS needs to put a "panic button" or better still have a more graceful
recovery from this problem.
Petter
"Tim Smiley" wrote:
> The following action mentioned in the enclosed thred solved this issue for me:
>
> If you are comfortable modifying the registry you can set the value of the
> key HKEY_LOCAL_MACHINE\Software\Microsoft\Windows
> Search\SetupCompletedSuccessfully to 0 and then reboot. This will delete
> everything the indexer has currently indexed and start again.
>
> http://groups.google.com/group/micro...cdfc94bba8be5f
>
>
> "Petter" wrote:
>
> > Thank you very much, Ronny, but unfortunately the problem is with image 1 on
> > the page you suggested. I get a message saying "Waiting to receive indexing
> > status..." and all buttons but close are greyed out.
> >
> > Clearly Windows is confused and some sort of manual reset + deleting of
> > indexes seems in order, but how do I do that?
> >
> > Petter
> >
> > "Ronnie Vernon MVP" wrote:
> >
> > > Petter
> > >
> > > Go to the following website for a good tutorial on configuring and
> > > rebuilding the Search Index.
> > >
> > > Indexing Options - Vista x64 Forums:
> > > Indexing Options
> > >
> > >
> > > --
> > >
> > > Ronnie Vernon
> > > Microsoft MVP
> > > Windows Shell/User
> > >
> > >
> > > "Petter" <Petter@discussions.microsoft.com> wrote in message
> > > news:5D4F7ACD-A7FB-41FF-A630-8D85F294F4D6@microsoft.com...
> > > > Office2007 and Vista search are not working any more on my machine. The
> > > > indexing service is running, but the control panel search options just
> > > > keep
> > > > telling me it is waiting to receive indexing status, and all buttons are
> > > > greyed out (but cance 
).
> > > >
> > > > Is there a way to perhaps reset the indexing options, delete any indexes
> > > > that may be there and set it all up from scratch without reinstalling
> > > > Vista
> > > > (which otherwise works beautifully by the way).
> > > >
> > > > I suspect a low disk condition may be the cause of this error, but I no
> > > > longer have such a condition on the machine.
> > > >
> > > > Thanks in advance!
> > >