Jump to content

nighthawkext

Team SUPERAntiSpyware
  • Content Count

    219
  • Joined

  • Last visited

Everything posted by nighthawkext

  1. It's possible that our realtime detected these items in memory and shut them down. The reason the scanner may not find them is that the rule many be an in-memory only detection rule. Do these items show in your quarantine under real-time?
  2. Kalzon, It appears that there is a problem on your machine with the settings being saved. I sent you an PM to see if you would like to work to resolve this issue. It would be very helpful to us if we could work with someone who can reproduce this problem. Let me know if you would like to pursue this further. Thanks Don Fowler SUPERAntiSpyware Developer
  3. The only way SAS would detect and remove those files without your input would be if you had real time running in the pro version and ran eicar or trojansim. My guess is that, if they are still on your machine, that they are corrupted somehow. Thanks Don
  4. What version of SAS are you running? Do you see any feedback when the automatic update is running? Does the update happen quickly, indicating a failure?
  5. We changed the rules that detect EICAR and TROJAN SIMULAR from notify to remove. Is it possible that you removed those from your machine on a previous scan? Version 5 will be compatible with all of the same OS and service packs as Version 4.
  6. I am a software engineer working on SUPERAntiSpyware. I would like to find a resolution to your problem. Are you running as an administrator when this occurs? At what point, during the running of SAS, does this occur? Immediately on startup, after a scan, during the clean/remove stage? Do you have realtime enabled? Thanks Don
  7. I would verify that the file \windows\system32\regsvr32.exe exists.
  8. If you can see the drive that you installed windows on then copy the file \boot.ini.sab over your current \boot.ini
  9. Have you rebooted since you installed SAB? If not, please do so and let us know if you are still having the problem. Thanks Don
  10. The log information that you've listed is completely safe and is not an indication of any real problem. This issue has been addressed and the change will be available in the next release. SUPERAntiSpyware Support Team
  11. When you ran SAS, did you scan your system or just run it and shut it down? SUPERAntiSpyware Support Team
  12. What version of windows are you running? We don't support 64 bit repairs on this release. Thanks SUPERAntiSpyware Support Team
  13. Sheila, SUPERAntiSpyware Pro supports right-click scanning of folders and files. Thanks SUPERAntiSpyware Support Team
  14. The product does not currently support that feature. It is on our list of possible features. Thank you for your suggestions. SUPERAntiSpyware Support Team
  15. Jack, We understand your frustration but ranting is inapproprate and will not get your problem solved any sooner. Your name does not show up in our support system. Please use the following link to open a support request and we will work to solve your issue. https://www.superantispyware.com/csrcreateticket.html SUPERAntiSpyware Support Team
  16. That is not normal. Let me know how long the scan took total, or if it even finished and we can work with you to fix the problem Thanks Customer Support Team
  17. Ali, it sounds like you have two copies of superantispyware in your run keys in the registry. I would uninstall SAS and search your registry for any references to SUPERAntiSpyware.exe and remove them. Short Circuit, your symptoms match the Norton problem symptoms. Follow the instructions you were given for rolling back your NIS2009 suite. SUPERAntiSpyware Support Team
  18. There is another problem that matches your symptoms. It is caused by a Norton Internet Security 2009 update that occurred around the 19th of August. Symantec has pulled the update until they can figure out their issues. Norton is causing problems for a lot of applications out there right now and one of the problems we have experienced is that it causes SAS to use large amounts of system time and fail to completely start up. The only solution that we're aware of at the moment is to uninstall NIS2009 and re-install it without the update. Hope this helps. Don
  19. I was able to reproduce the problem as well as receiving minidumps from another user on this forum. After extensive debugging, I found that ThreatFire was crashing the system. The evidence that it was threatfire was complete and conclusive. Don
  20. There is a known problem with a recent Norton Internet Security update. Symantec has pulled the update until they figure out what the problem is. Are you running this program?
  21. It's not necessary to install for each hard drive. Installing the software once will protect your entire computer.
  22. Yes, that configuration will work well for you. SUPERAntiSpyware Support Team
  23. We have found PCTool ThreatFire to cause this scenario. Simply disabling ThreatFire does not make the program go away. I would recommend removing ThreatFire until they release a path that resolves the issue. SUPERAntiSpyware Support Team
  24. Open a suport request so we can help you https://www.superantispyware.com/precreateticket.html SUPERAntiSpyware Support Team
  25. Please open a support ticket and we will attempt to help you. https://www.superantispyware.com/precreateticket.html SUPERAntiSpyware Support Team
×
×
  • Create New...