I just update the antispyware recently and i have notice that eventhough i
deselect active protection, update etc, the program still startup with
Windows. I like to have full control on what's starting up with my computer
and decide whenever i need spam scanning or not. There is no need to have
that running all the time. A simple scan regularely is sufficient for me.

Please remove that startup if we do not want it active all the time.

I think that beta2 will make this choice easier. In the meantime, removing
the RUN registry entry is the quickest way to fix this.

--

"armagedon" <(E-Mail Removed)> wrote in message
news:435518C6-5165-4E34-8561-(E-Mail Removed)...
>I just update the antispyware recently and i have notice that eventhough i
> deselect active protection, update etc, the program still startup with
> Windows. I like to have full control on what's starting up with my
> computer
> and decide whenever i need spam scanning or not. There is no need to have
> that running all the time. A simple scan regularely is sufficient for me.
>
> Please remove that startup if we do not want it active all the time.

"Bill Sanderson" wrote:

> I think that beta2 will make this choice easier. In the meantime, removing
> the RUN registry entry is the quickest way to fix this.
>
> --
>
> "armagedon" <(E-Mail Removed)> wrote in message
> news:435518C6-5165-4E34-8561-(E-Mail Removed)...
> >I just update the antispyware recently and i have notice that eventhough i
> > deselect active protection, update etc, the program still startup with
> > Windows. I like to have full control on what's starting up with my
> > computer
> > and decide whenever i need spam scanning or not. There is no need to have
> > that running all the time. A simple scan regularely is sufficient for me.
> >
> > Please remove that startup if we do not want it active all the time.
>
>
>
Bill,

curiously there is no entry in the run/registry. Even Autoruns from
SysInternals can't dig it out. It's buried somewhere else.

"armagedon" <(E-Mail Removed)> wrote in message
news:2C5F9D53-05C6-4A43-AB45-(E-Mail Removed)...
>
>
> "Bill Sanderson" wrote:
>
>> I think that beta2 will make this choice easier. In the meantime,
>> removing
>> the RUN registry entry is the quickest way to fix this.

>>
> Bill,
>
> curiously there is no entry in the run/registry. Even Autoruns from
> SysInternals can't dig it out. It's buried somewhere else.

Well - here's the official story:

Use the "workaround" paragraph in this KB article:

http://support.microsoft.com/kb/892375

I see the startup at:

HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Run gcasserv

"Bill Sanderson" wrote:

> "armagedon" <(E-Mail Removed)> wrote in message
> news:2C5F9D53-05C6-4A43-AB45-(E-Mail Removed)...
> >
> >
> > "Bill Sanderson" wrote:
> >
> >> I think that beta2 will make this choice easier. In the meantime,
> >> removing
> >> the RUN registry entry is the quickest way to fix this.
>
> >>
> > Bill,
> >
> > curiously there is no entry in the run/registry. Even Autoruns from
> > SysInternals can't dig it out. It's buried somewhere else.
>
> Well - here's the official story:
>
> Use the "workaround" paragraph in this KB article:
>
> http://support.microsoft.com/kb/892375
>
> I see the startup at:
>
> HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Run gcasserv
>
>
>
Ho my mistake, i used Sysinternal/Autoruns and i had desable MS signed
entries check.

Yes it's there. Thanks !