Excessive Security Events.

[fwall4]

Hi: Ever since I installed the new Widows Search program (vs. 4.0) I notice
in the Event Viewer under "Security", numerous (up to 250) Event 528
(Logon/Logoff) and Event 576 (Privelege use). These events are always shown
in the same order.... 528 and 576 and no other events are listed. This does
not happen if I snooze indexing for 1 day. Furthermore, the program is
constantly indexing and this slows my machine considerably. Why is this
happening? Does Microsoft plan to have an update to fix this nuisance. The
time I save on a faster search is more than doubly lost and slow PC
performance. Other than removing the program what solution is there?
In advance thanks for your response, Fred

 

[Twayne]

Hi: Ever since I installed the new Widows Search program (vs. 4.0) I
notice in the Event Viewer under "Security", numerous (up to 250)
Event 528 (Logon/Logoff) and Event 576 (Privelege use). These events
are always shown in the same order.... 528 and 576 and no other
events are listed. This does not happen if I snooze indexing for 1
day. Furthermore, the program is constantly indexing and this slows
my machine considerably. Why is this happening? Does Microsoft plan
to have an update to fix this nuisance. The time I save on a faster
search is more than doubly lost and slow PC performance. Other than
removing the program what solution is there?
In advance thanks for your response, Fred

Well, it won't really make any difference, but go ahead and turn off
indexing. See Help and Support for how-to. It's highly doubtful this
is a bug or that MS plans on making any changes to it since it's about
to go obsoleted.
If your machine is experincing slowdowns, I would look to the last
thing you installed to begin with. Try removing it temporarily and see
if the slowness goes away. It may or may not, but it's one thing to
try. Unless you've picked up malware somehow recently (which is likely)
it's probably something you recently installed causing the slowdowns.

 

[fwall4]

Hi Twayne: Thanks for your fast reply. I have made sure that Windows Search
4.0i s the culprit since my PC works fine with W.S. disabled. However, when I
disable the stupid thing I get a DCOM red X in the event viewer. At any rate,
I just live with it and snooze it until I feel indexing is in order (which is
hardly ever). The program hasn't been out long enough to go obsolete... But
then again, with MS one never knows. Thanks again, Fred

 

[Twayne]

Hi Twayne: Thanks for your fast reply. I have made sure that Windows
Search
4.0i s the culprit since my PC works fine with W.S. disabled.
However, when I disable the stupid thing I get a DCOM red X in the
event viewer. At any rate, I just live with it and snooze it until I
feel indexing is in order (which is hardly ever). The program hasn't
been out long enough to go obsolete... But then again, with MS one
never knows. Thanks again, Fred

I can't speak to the DCOM error but you might want to toy with the idea
of just leaving indexing off and see if/how much it actually bothers
you. I have it on because I frequently do long searches and like the
way programs start up faster, but if those are minor details to you, who
cares? Just a thought; I know some people who leave it off and some,
though I've never experienced it, who swear it slows down their general
operations.
If I'm not misaken, and here I only know what I've read, doesn't WS
do its own indexing of some sort? Over and above XP's indexing? If so,
perhaps there's a sort of "training period" you just have to let it go
through to get real benefit from it without impacting system
performance.
Just sort of thinking out loud; hope I'm not making mountains<g>.

Luck,

Twayne

 

[fwall4]

Hi (again) Twayne: Thanks for the reply. I have concluded that since I don't
used W.S. that often I just leave it in a snooze mode and maybe once a week
let it do its indexing. I reallly appreciate you taking the time to address
this matter and giving it your thoughts. Thanks again, Fred