Issues with the latest Update to SAS

[Peter Foldes]

July 30 2002 Update

Note that not everyone will encounter the issues listed in the link supplied

http://forums.superantispyware.com/...ge-detected/page__st__20__p__22470#entry22470

 

[FromTheRafters]

July 30 2002 Update

Note that not everyone will encounter the issues listed in the link
supplied

http://forums.superantispyware.com/...ge-detected/page__st__20__p__22470#entry22470

Looks like a more recent development than 2002. )

 

[FredW]

July 30 2002 Update

Note that not everyone will encounter the issues listed in the link supplied

http://forums.superantispyware.com/...ge-detected/page__st__20__p__22470#entry22470

Answer of SAS:
"We fully test our updates as we have always done - we have not been
able to reproduce this, nor did we see any issue prior to release -
there were no code changes to the core product, only the updater - so
this may be related to specific system configurations. Can you provide
your specifics of the systems you had problems with? "

I downloaded and installed version 4.56.1000 Free.
http://www.superantispyware.com/download.html
(bottom choice)
During install I take care to "untick" everything relating to a toolbar
from bottom to top (3 squares).

I updated and performed a complete scan yesterday (Sunday).
I had no problems.

 

[FromTheRafters]

Answer of SAS:
"We fully test our updates as we have always done - we have not been
able to reproduce this, nor did we see any issue prior to release -
there were no code changes to the core product, only the updater - so
this may be related to specific system configurations. Can you provide
your specifics of the systems you had problems with? "

I downloaded and installed version 4.56.1000 Free.
http://www.superantispyware.com/download.html
(bottom choice)
During install I take care to "untick" everything relating to a toolbar
from bottom to top (3 squares).

I updated and performed a complete scan yesterday (Sunday).
I had no problems.

I understand the purported issue to be with the active protection(s) of
the paid for version.

Anyway, they seem to indicate that it is not a widespread issue and may
even be specific to this one case.

 

[Rich Webb]

I understand the purported issue to be with the active protection(s) of
the paid for version.

Anyway, they seem to indicate that it is not a widespread issue and may
even be specific to this one case.

About half? one quarter? the time that I shutdown Windows (WinXP/SP3+) I
do get the "application won't shutdown: kill/cancel" box for SAS (paid
version). I just hit the Cancel button (NOT the kill process button) and
the shutdown then proceeds normally.

No big drama. I assume it's some side effect of how Windows sequences
its shutdown and how, or how long, it waits for processes to answer.
Very occasionally the Waiting for Shutdown box goes away by itself. At
most a very minor inconvenience (and intermittent, so probably hard to
reliably duplicate).

 

[FromTheRafters]

About half? one quarter? the time that I shutdown Windows (WinXP/SP3+) I
do get the "application won't shutdown: kill/cancel" box for SAS (paid
version). I just hit the Cancel button (NOT the kill process button) and
the shutdown then proceeds normally.

No big drama. I assume it's some side effect of how Windows sequences
its shutdown and how, or how long, it waits for processes to answer.
Very occasionally the Waiting for Shutdown box goes away by itself. At
most a very minor inconvenience (and intermittent, so probably hard to
reliably duplicate).

Hopefully, if it's something that the SAS folks can fix for you, their
support channel will eventually work for you. IMO the 'value' of a paid
version is in the support.

 

[Peter Foldes]

Issue resolved

From Nick (Developer):
Posted Today, 04:56 PM
We have located and resolved the problem. This ONLY happens on 64 bit
systems, and with users running an older SASCORE64.EXE. This is one of
those issues that is hard to find in standard "testing". We are updating
the 4.56 package now (testing, then releasing) so that the issue won't
happen. We apologize for the inconvenience and I will update this thread
when the new 4.56 is ready. We appreciate everyone alerting us!

Thanks to jen for the above

 

[FromTheRafters]

Issue resolved

From Nick (Developer):
Posted Today, 04:56 PM
We have located and resolved the problem. This ONLY happens on 64 bit
systems, and with users running an older SASCORE64.EXE. This is one of
those issues that is hard to find in standard "testing". We are updating
the 4.56 package now (testing, then releasing) so that the issue won't
happen. We apologize for the inconvenience and I will update this thread
when the new 4.56 is ready. We appreciate everyone alerting us!

Thanks to jen for the above

Nick has always been straightforward and helpful. I'm not surprised at
all that he came through.