Multiple MSAS icons in Notification Area /100% CPU at times

  • Thread starter Thread starter PeteC
  • Start date Start date
P

PeteC

Most times when I boot up I see 2 or 3 MSAS icons in the
Notification area. Running the mouse over these closes all
but one. Any idea what's going on here?

Still have problems with grasDtServe.exe grabbing 100% of
CPU despite applying the patch suggested elsewhere here
re. VB 6. Any further solutions?

TIA
 
See in GENERAL forun, Subject: Multiple SpyWare icons
on task bar From: "Noel" Sent: 9/15/2005 7:55:27 AM
 
Do you use TightVNC or RealVNC or any other VNC application to remote
control your computer? Also, is this a Tablet PC? This seems to affect most
if not all Tablet
users.

Under Taskmanager, the Microsoft AntiSpyware Processes are represented by,:
gcasDTServ.exe and gcasServ.exe, if those are running, Real time protection
is enabled.

You can also try doing a repair:
Go to Add or Remove Programs in Control Panel. Click Microsoft AntiSpyware
and click Change. Click Next, and then click Update. Also, check back on it
in beta 2.
--
Andre
Extended64 | http://www.extended64.com
Blog | http://www.extended64.com/blogs/andre
http://spaces.msn.com/members/adacosta
FAQ for MS AntiSpy http://www.geocities.com/marfer_mvp/FAQ_MSantispy.htm
 
No VNC apps and this is a desktop running AMD Athlon 64
and XP Pro SP2.

I will try a reinstall later (can't repair - I got that
fed up with MSAS stalling the m/c that I uninstalled MSAS
in favour of a trial of Counter Spy).
 
This can be caused by a software conflict. One known cause is a keyboard or
mouse with a fingerprint scanner. The driver for the fingerprint scanner
has such a conflict.

--
 
Interesting. I have the same problem described by PeteC (multiple, usually
two, MSAS icons). I also have Microsoft Fingerprint Reader installed. Any
possible solutions available? The extra icons appear to be harmless, not
causing any problems with either MSAS or FP Reader, but seems to be a bug.
 
That's definitely a known cause, and the developers are aware of it. I
don't have a workaround except to expect this not to happen with beta2.

--
 
Back
Top