Jump to content

nighthawkext

Team SUPERAntiSpyware
  • Content count

    213
  • Joined

  • Last visited

About nighthawkext

  • Rank
    Site Admin
  • Birthday 07/28/69

Profile Information

  • Gender
    Male
  • Interests
    SUPERANTISPYWARE
  1. I cannot reproduce this issue. Is this still occurring?
  2. A Product Update is Available > ∞

    Please download and install the latest version of SAS from our website. We have made numerous fixes to update system. After installing the new version, if you still have update issues - please let us know.
  3. what happened to SAS?

    I'm sorry that you're under the impression that SAS is useless. As stated earlier, no software catches everything. We are updating our definition set daily to detect current malware infections. We know that SAS currently detects ~3,000,000 malware infections a months. That doesn't include tracking cookies. What I'm wondering is what type of infections is ESET detecting and why are you getting infected on such a regular basis. Thanks Don
  4. Cookies

    Cookies cannot be quarantined and restored with SAS, so they were removed from quarantine. It has always been necessary for the browser to be closed when removing cookies from chrome and firefox. SAS now has the option to close the browser for you.
  5. SAS 6.0.1164 still no support for Cyberfox

    Some of the information for quick scans comes from the current definition file. Do you have the latest version of definitions?
  6. mdsllc, I apologize it took so long for an answer. I check this forum multiple times a day and never saw the question or any of the updates until today. I will look into how that could happen.
  7. SAS Pro version CHM Help file woefully outdated

    We haven't distributed a CHM help file with SAS in a long time. There is no current CHM help file. My guess is that you have an old version of SAS that has been updated.
  8. SAS 6.0.1164 still no support for Cyberfox

    Maximus, there is definitely support for CyberFox. I told you that personally. If it's not working for you, we can figure that out. You are familiar enough with SAS to know that we always do a download release for a few days before enabling the update servers. We never have a change log until we enable the update servers. It's too confusing for the millions of users we have.
  9. Detected Threats Not Being Removed

    It seems that some piece of software has created those multiple levels of application data. Probably a bug. Many programs will crash when they encounter a path this long. I would look into how this happened and try to remedy the situation.
  10. SUGGESTED FEATURE-- PROGRESS BAR

    We have been discussing this feature for years. The main issue is that the product would have to know how many files are on the drive before scanning. To achieve this, you have to spend resources prior to scanning to enumerate them. There are other options that aren't as accurate and we're still examining them.
  11. Detection Problem. ALL Malware

    Lagarvp, Each type of malware has to be detected in a unique way. Many many pieces of the files in a strain of malware change constantly.. it's all easy to edit and change.
  12. browsefox

    Maximus, We appreciate your help on the forums. I would like to clarify that it's erroneous to say SAS is only good for removing tracking cookies. As I've stated before, the product removes over 3,000,000 malware infections a month. Those people who thank us for helping them when no other software could would probably disagree with your sentiment.
  13. Please add support for Cyberfox

    The next release of SAS will have support for CyberFox cookie cleaning
  14. Please add support for Cyberfox

    We'll look into it. Thanks Maximus
  15. Malware.Trace ?

    The (x86) at the start of the registry path indicates that it is under an x86 registry path. Try looking in HKEY_USERS\S-1-5-21-1025616775-32965946-2427245248-1008-{ED1FC765-E35E-4C3D-BF15-2C2B11260CE4}-0\SOFTWARE\Wow6432Node\MICROSOFT\WINDOWS NT\CURRENTVERSION\WINLOGON#SHELL
×