C
Cliff
should this log get this big? mine is currently 199mb !!!
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
S
Segovia
Cliff said:should this log get this big? mine is currently 199mb !!!
Hmm. Mine is only 1 KB, but I have heard of people having ones as large as
you describe. I think one guy said his was 29 gigs?! Shouldn't it be
automatically truncated to a certain limit?
J
Jacques
Mine was too big to be read so I'd just a look for the head. Said "can't
read memory... (Ithink it's happening during another apply "not
responding").
read memory... (Ithink it's happening during another apply "not
responding").
A
Andre Da Costa
Yes, it tends to get big, you can delete and it will restore itself.
B
Bill Sanderson
I've had one machine out of about 3 dozen on which this log grew
uncontrollably. It did this only occasionally--I discovered the problem,
deleted the file, uninstalled the beta. Then I reinstalled the beta, and it
ran for weeks without the problem coming back. However, after some weeks it
did come back, so I've removed the beta from that machine until we get
another build.
uncontrollably. It did this only occasionally--I discovered the problem,
deleted the file, uninstalled the beta. Then I reinstalled the beta, and it
ran for weeks without the problem coming back. However, after some weeks it
did come back, so I've removed the beta from that machine until we get
another build.
C
chris
yes error.log is known to get bigger, still waiting for
microsoft explanation on the microsoft antispyware site
i think this error.log have something to do with
microsoft antispyare perfomance and stability with the
realtime protection not doing its job.
microsoft explanation on the microsoft antispyware site
i think this error.log have something to do with
microsoft antispyare perfomance and stability with the
realtime protection not doing its job.