Vista - Problem with search indexer and windows live mail suddenly?

Hey gang,

I have been running Vista 64 bit Ultimate, and it has run very well for me
since installing in late Feb. It is updated with SP1, and I have all updates
current.

Today, I noticed all of a sudden my cpu useage was running around 25-30%,
constantly pretty much all day. This is very unsual for me, I have not seen
it behave this way before, I checked under the performance monitor in task
manager, and it appears to be the search indexer that is using up the cpu
cycles. I have not seen it behave this way before.

Then, I tried to open Windows Live Mail, and it would not open - it just
hangs at the opening screen, with the spinning circle that never changes, I
have to close the program in task manager to get it to close.

Any ideas on where I might begin would be greatly appreciated. I have not
installed any new software or hardware of late, and this just began today.


Thanks,



--
Don

"Don" <d.burnette@xxxxxx> wrote in message
news:OB7eflUOJHA.3732@xxxxxxAn update:

First, I tried system restore to a restore point from yesterday morning, my
computer was fine all day yesterday.
Did not work, cpu still hovering around 25-30% constantly, with windows
search being the culprit in the resource monitor. Windows Live Mail would
still not open either.

I then went into services.msc, and disabled the windows search indexer. CPU
is behaving normal now, and Windows Live Mail came right up for me.

Anyone else ever run into this suddenly? For some reason sometime this
morning, the search indexer started running, constantly, and ran all day
long keeping my cpu around 25-30% useage, and Windows Live Mail would not
open, only get to the opening screen and the spinning circle, I would have
to close it from within task manager.
Now that I have disabled the Windows Search Indexer in services, all seems
to be well.

Anyone else ?


Thanks,


--
Don

On Tue, 28 Oct 2008 18:25:27 -0500, "Don"
<burnettedclothes@xxxxxx> wrote:
Vista search is a colossal waste and design mistake. Why do you need
to run a program full time to index your hard drive when you spend
about .00001% of your computer life searching for files... and likely
less than half of that searching for actual content of files (file
names and directories hardly need indexing) ?

A search index makes sense for a distributed files such as the
Internet. It might make sense for business networks with lots of
shared drives (running on the server and accessible to clients). It
makes no sense at all as a local application searching the C: drive.

Not to mention, the Vista search tool sports one of the poorest
interface designs ever.

Keep the indexer off. Down load "Agent Ransack". Use that instead. My
only complaint with Ransack is that you have to manually type in the
drive letter for network drives to browse them. Aside from that, it
meets most all search needs.

Get ird of Windows Indexer and get this free program:

http://www.voidtools.com/

It is truly amazing, and this guy should be bought out to replace the
nonsense currently parading as indexing in Windows.

"Telstar" <none@xxxxxx> wrote in message
news:ekxWztYOJHA.3968@xxxxxxPS

FYI

The program does not index the content of files, only file and folder names
and extensions.

Disabling the Indexer in Windows will stop the Instant Search in Office 2007
Outlook. Go to Tools, Instant Search, Advanced Search to bring up the
previous XP search....

"+Bob+" <nomailplease@xxxxxx> wrote in message
news:sa9fg45glsu12caatl1i06a9qulurign8v@xxxxxxThanks Bob, I will do that.
I had disabled disk indexing on my partitions, but apparently had not
disabled the search indexing. Curious that it had not posed a problem for
me until yesterday, having run Vista for several months.




--
Don

On Wed, 29 Oct 2008 04:57:35 -0500, "Don"
<burnettedclothes@xxxxxx> wrote:
I made the mistake of assuming that shutting off indexing on all
drives would stop it from running. Silly me. I found it running like
yours one day. LOL. A program doing massive disk access to index...
absolutely nothing!

Shutting down the service as you did stops it. I renamed the .exe for
good measure :-)