Discussion in 'other anti-malware software' started by SUPERAntiSpy, Apr 15, 2011.
What error are you getting? Can you provide some specific information?
Does the process show *32? If it does, then SAS may be compatible, but not native 64-bit.
SUPERAntiSpyware and all associated components are ALL native 64-bit applications unlike many other products - we have specifically written 64-bit native versions of our software.
Why does it install into Program File (x86) then?
Did you have an old 4.x version installed? It could be a left over folder. Did you install using XP compatability mode? If you are on a 64-bit system it installs 64-bit components - in task manager does the superantispyware.exe process have an *32 next to it?
Version 4.x installs in Program Files, but Triple Helix reports that version 5 installs in Program Files (x86). Why is that so?
Read it again! I just assumed v4 installed in C:\Program Files (x86) but v5 went in C:\Program Files!
Do you have any estimate on when SUPERAntiSpyware 5.0 will be released?
Thanks in Advance.
When we are done with pre-release testing, so far so good! We are finishing up the help file and language translations, etc.
New Build Released
18 min full scan super fast
found two bad boys and killed like the dogs they are!!
thanks Nick, for a great peice of work!!
Thanks for the update...!!! Is this the stable build?
Its still PRE-RELEASE and could not find a change log
The primary change was the "trusted/allowed" items had a small fix that was required.
Allowing items into the trusted list is no longer non-functional.
thank you Nick
Does sas 5 fix exe and other file associations?
Yes, we focus on the ones we see hi-jacked by malware.
Explanation, it is because SUPERAntiSpyware is using its service application, running in the background with administrator rights, for the detection, cleaning, repairing, etc. stuff..
The SUPERAntiSpyware.exe is communicating with this service in all user accounts, so it works across the board
This service is installed by SUPERAntiSpyware and loaded automatically every time the computer is started..
Ok nice, any help needed for language translations?!
So SAS Core Service is still necessary if you use SUPERAntiSpyware on-demand only?
I think yes, you could try to start SAP without the Core Service loaded/started and see what happens.. ;-)
Yes, you should not disable it - it uses little memory and no cpu when idle!
New build released...5.0.1084
Separate names with a comma.