Very Slow XP with MS AntiSpyware Ver: 1.0.615

  • Thread starter Thread starter J R Birch
  • Start date Start date
J

J R Birch

Since stalling MS antispyware on my laptop and desktop
both systeme have slowed to a snails pace. In fact to the
point where I'm almost unable to work.

Anybody experienced the same problems.?
 
-----Original Message-----
Since stalling MS antispyware on my laptop and desktop
both systeme have slowed to a snails pace. In fact to the
point where I'm almost unable to work.

Anybody experienced the same problems.?
.
No, can`t say I have. Sounds like they may need an
Click to expand...
overhaul and/or memory upgrades - even a defrag and a
registry clean out? You may have too many applications
hogging RAM memory sitting in your system tray and MSAS
has pushed things over the top. For this I use a handy
utility called `Autoruns` to keep things in perspective
and according to `it` MSAS uses 462K. You`d be surprised
at what is loaded at start up that you really don`t need.
Then there`s always MS`s very own MSCONFIG.

Incidentally. I am using a note book with just 256MB and
Windows XP Home SP2.
 
-----Original Message-----
Yes, it is a MSAS process, to fix the CPU 100% issue,
apply this fix:
Update VB v6 service Patch 6 using the following link...
Click to expand...

Do you mean to say MSAS was written with VB6??
 
Yes, there shouldn't be any problem with that.

Didn't mean to imply there was a problem :-)

I just wanted verification so I could mention it the next
time I overhear some C++ bigots moaning about VB not
being a "real" programming language, and no commercial
apps could/shoiuld ever be written with a "toy" langauge
like VB.

Doesn't matter to me one way or the other, as long as the
compiled apps work.

But MS support for VB6 is going out the window soon
(2007, I think?) so that leaves a big question mark as to
what MS plans to do with MSAS. Convert it to Dot Net
soon, I hope.
 
Didn't mean to imply there was a problem :-)

Actually, now that I think about, VB6 *could* be a
problem for MSAS. The VB app will only run with the
credentials of the logged in user account, which is why
MSAS doesn't work very well when running under a Limited
User login.

If it weren't VB6, it could be compiled to run as a
Service with System credentials (like serious AntiVirus
apps do, such as Norton/Syamntec AntiVirus, etc.), thus
alleviating the issues regarding Limited User account
functionality.
 
Back
Top