windows defender

  • Thread starter Thread starter Petey
  • Start date Start date
P

Petey

Anyone else find Windows Defender makes their cpu sluggish? If I want to
open a browser, or any program in less than 40 seconds, I hafta stop windows
defender in msconfig. I've got 128mb or sdram, a 1.1gig p4 processor, 30gig
hd (40%free space). Any input???
 
it used to run well (until sp1 and sp2 and all the "updates" which happen to
all be 11.01mb or 11.02mb -according to add/remove prgrms stats). Why are
all these updates approx. same size? Is this just MS sniffing around my
hard drive? I've known people who are running bare bones xp (i.e. NO
updates or sp's whatsoever).

I might attempt a clean install and run with no updates - Good idea?
Bad idea?
 
Petey said:
Anyone else find Windows Defender makes their cpu sluggish? If I
want to open a browser, or any program in less than 40 seconds, I
hafta stop windows defender in msconfig. I've got 128mb or sdram, a
1.1gig p4 processor, 30gig hd (40%free space). Any input???



Your problem is not Windows Defender. If you have only 128MB of RAM, you
have a computer that is by nature an etxremely sluggish one. *Anything* you
run on it will make it worse.

How much RAM you need is *not* a one-size-fits-all situation. You get good
performance if the amount of RAM you have keeps you from using the page
file, and that depends on what apps you run. Most people running a typical
range of business applications find that somewhere around 256-384MB works
well, others need 512MB. Almost anyone will see poor performance with less
than 256MB. Some people, particularly those doing things like editing large
photographic images, can see a performance boost by adding even more than
512MB--sometimes much more.
 
I would guess that having the extra strain of Defender put your PC over the
limit. Stopping Defender fress enough ressources to make a differerence.
The best thing would be to add more memory.
 
Bad Idea............unless you never ever access the net.The updates
installed more net security
peter
 
I have the same problem - 1.6 GHz P4M and 1GB memory.

It seems to me the problem with defender is that the scans are CPU hogs -
especially when scanning compressed files - and run at normal priority. You
can see this clearly on the Task Manager Process tab while experiencing a
slowdown.

Everyone running this product at MS must have dual core CPUs?
 
Back
Top