SuperAntiSpyware Ver 5 Problems

  • Thread starter Thread starter Buffalo
  • Start date Start date
B

Buffalo

Anyone else here use SAS and have problems with the new ver 5 of SAS on
their Win2000ProSP4 system?
I undated it one day (to version 5) and some quick 'entry point error'
message flash on the screen but it kept going.
I then did a defs file update (actually 2 in a row) and did a quick scan
(much faster than Ver 4) and it didn't find anything.
The next day I again updated the defs and clicked on a full scan and
immediately an error message came up saying something about SAS having an
error and that a report would be sent to SAS. I agreed and then SAS quit and
a message came up saying that it would restart SAS. Well, over 5 minutes
later my PC was super slow. Basically I coundn't get anything to work in
under a minute, not even opening a text file.
I waited a little longer and then tried to open the Task Manager (took over
2 minutes) and finally shut down my PC using Shut Down in the Task Manager.
Upon rebooting, Windows would only get to the 'applying your personal
settings' box and then reboot.
Same thing in Safe Mode.
I tried 'Last Known Config' with no good results.
I finally tried a Repair Install using the Win2000Pro CD and it worked.
Then a zillion updates later and reinstalling and uninstalling various
drivers, I was almost back to normal.
Anyone else have this problem with the new SAS ver 5?
After all this, I finally uninstalled SAS using their uninstall utility and
reinstalled the program. I received another problem notice but the install
proceded.
It was "The Procedure entry point WTSGetActiveConsoleSessionId could not be
located in the dynamic link library KERNEL32.dll".
I have since updated the defs and have the latest version and it seems to be
running OK.
Thanks,
Buffalo
 
Buffalo said:
Anyone else here use SAS and have problems with the new ver 5 of SAS
on their Win2000ProSP4 system?
I undated it one day (to version 5) and some quick 'entry point error'
message flash on the screen but it kept going.
I then did a defs file update (actually 2 in a row) and did a quick
scan (much faster than Ver 4) and it didn't find anything.
The next day I again updated the defs and clicked on a full scan and
immediately an error message came up saying something about SAS
having an error and that a report would be sent to SAS. I agreed and
then SAS quit and a message came up saying that it would restart SAS.
Well, over 5 minutes later my PC was super slow. Basically I coundn't
get anything to work in under a minute, not even opening a text file.
I waited a little longer and then tried to open the Task Manager
(took over 2 minutes) and finally shut down my PC using Shut Down in
the Task Manager. Upon rebooting, Windows would only get to the
'applying your personal settings' box and then reboot.
Same thing in Safe Mode.
I tried 'Last Known Config' with no good results.
I finally tried a Repair Install using the Win2000Pro CD and it
worked. Then a zillion updates later and reinstalling and
uninstalling various drivers, I was almost back to normal.
Anyone else have this problem with the new SAS ver 5?
After all this, I finally uninstalled SAS using their uninstall
utility and reinstalled the program. I received another problem
notice but the install proceded.
It was "The Procedure entry point WTSGetActiveConsoleSessionId could
not be located in the dynamic link library KERNEL32.dll".
I have since updated the defs and have the latest version and it
seems to be running OK.
Thanks,
Buffalo
Click to expand...

I don't use SAS, but had a similar problem with another Resident
anti-malware program. The system required a reboot after installation,
and didn't boot up normally even after several retries. Finally I
logged-into Safe mode, and disabled the Service of the problematic app.
(Control Panel/Administrative Tools/Services/Right-click the app's
name/Properties: Set to Manual or Disabled instead of Automatic) so it
wouldn't load at Startup, and later uninstalled it in Normal mode.

You could have considered this while in Normal or Safe Mode (when
things are reasonably good!), than reinstalling the whole OS itself
through Repair install which takes back the OS to its virgin state, and
needs patching from the scratch. Through the Task Manager, you could
have terminated the particular process first to make the system a bit
more stable.

It is also a good idea to Backup at least the 'System State' part
regularly before installing new programs through the Windows Backup
utility, to restore under such situations. Besides, the "Last known
Good Cofig" restoration _as I know_ applies to Hardware Profile only,
unlike the System Restore under ME or XP onwards that restores all
System related.

As per the 'Procedure entry point' error, looks like the app. or the
update is for WinXP onwards and not Win2K compatible. Some programs
won't install if not compatible, and a few others don't even mention
under System requirements, get installed and later refuse to run with
such messages.
 
Mohan said:
I don't use SAS, but had a similar problem with another Resident
anti-malware program. The system required a reboot after installation,
and didn't boot up normally even after several retries. Finally I
logged-into Safe mode, and disabled the Service of the problematic
app. (Control Panel/Administrative Tools/Services/Right-click the
app's name/Properties: Set to Manual or Disabled instead of
Automatic) so it wouldn't load at Startup, and later uninstalled it
in Normal mode.

You could have considered this while in Normal or Safe Mode (when
things are reasonably good!), than reinstalling the whole OS itself
through Repair install which takes back the OS to its virgin state,
and needs patching from the scratch. Through the Task Manager, you
could have terminated the particular process first to make the system
a bit more stable.

It is also a good idea to Backup at least the 'System State' part
regularly before installing new programs through the Windows Backup
utility, to restore under such situations. Besides, the "Last known
Good Cofig" restoration _as I know_ applies to Hardware Profile only,
unlike the System Restore under ME or XP onwards that restores all
System related.

As per the 'Procedure entry point' error, looks like the app. or the
update is for WinXP onwards and not Win2K compatible. Some programs
won't install if not compatible, and a few others don't even mention
under System requirements, get installed and later refuse to run with
such messages.
Click to expand...

SAS did do a minor update which fixed the 'Entry Point' problem on
Win2000ProSP4 systems

Thanks for your info, but I could not boot up in Normal Mode or Safe Mode.
I also went into Task Manager (while the PC was almost frozen) which took
over two minutes just to appear on the monitor. I could not find a Running
Task in Applications and so I finally used the Shut Down tab on Task
Manager. I guess I could have waited another 20 min, but I didn't and I just
figured a reboot would fix the problem. When SAS is doing a scan or trying
to dl a definition update, the PC is basically useless for any other task
(at least the older version was). Once after waiting for SAS(previous
version) to dl a def update for over twenty minutes, (could not stop the
process from within SAS), I did manage to use Task Manager to stop it.

I had to try the Repair method as a last resort.

I will start backing up everything now on an external USB HDD. I may even
buy another internal HDD and use that also for a backup, as it is much
quicker than a USB external HDD, but not as safe.
Buffalo
 
Back
Top