Jump to content

siliconman01

Members
  • Content Count

    1052
  • Joined

  • Last visited

Everything posted by siliconman01

  1. Please post back here a SAS scan log that shows the infected files. Also ensure that you are running SAS V4.49.1000 which is the latest version. Then boot into SAFE MODE and run complete scan with SAS. Let it quarantine what it finds. What Windows operating system are you running (with Service Pack number) and is it 32-bit or is it 64-bit?
  2. There is no official published target date for the final release of V5.0. It has not yet entered the Pre-Release testing phase, but I suspect that it will in the very near future. The final release date depends on what is discovered during the pre-release testing by various SAS users doing the testing. Keep in mind that there are thousands and thousands of hardware/software configurations that worldwide users have; therefore, some totally unanticipated bugs may crop up during the pre-release testing that will slow down the final release. I suspect that the final release will come out 2-3 months after pre-release testing starts...maybe earlier, maybe later. There is no official mailing list that you can be added to for alerting you that V5 is released. The best thing to do is just keep on eye on the www.superantispyware.com home page which shows the current public release version of SAS.
  3. First of all, you should update to the latest version of SAS which is V4.49.1000. You can do this by: 1. Right click on the SAS icon in the Notification Tray and select "Check for Updates" 2. When the blue/white popup appears next to the task bar, select the option to download/update the new version and let it do so. Note: The "Check for Updates" on the main GUI of SAS only checks for new definitions, not for program updates. It is best to use the right click option of the icon as described above so that you maintain the latest version of SAS. Concerning your right click scan question: 1. SAS does not unzip .ZIP or .RAR or .Cab files at the present time. So if you are trying to scan one of these types of files, it will only show 1 or 2 files. 2. Right click scanning does use the options that you have selected under Preferences>Scanning Control. So if you have "Scan only known files types (.exe, .com, .dll, etc.), right click scanning will skip "unknown" types of files. Also if you have the first two "Ignore" options selected, it will ignore those files as well.
  4. The System Volume Information directory is your system restore points and is a Microsoft protected directory that I doubt that SAS can delete/quarantine files from...even though it says it does. The only safe way to clean out the System Volume Information directory is to turn off System Restore for that disk (the G:\ disk in this case), reboot your system, and then turn System Restore back on for that disk. The same applies if the this had been on the C:\ drive. http://windows.microsoft.com/en-US/windows-vista/Turn-System-Restore-on-or-off http://www.howtogeek.com/howto/windows-vista/disable-system-restore-in-windows-vista/ http://us.norton.com/support/kb/web_view.jsp?wv_type=public_web&docurl=20080421114858EN&ln=en_US
  5. Try Malwarebytes Anti-Malware free from http://www.malwarebytes.org/
  6. What Windows operating system (with Service Pack number) are you running? Is your Windows OS 64-bit or is it 32-bit? Are you running V4.49.1000 of SAS free?
  7. Try this: 1. Open SAS GUI and go to Preferences>Scanning Control. 2. Uncheck the following items and then run a Complete Scan while in SAFE MODE. - Use Kernel Direct File Access (recommended) - Use Kernel Direct Registry Access (recommended) - Use Direct Disk Access (recommended) That will probably stop the scan lockup.
  8. The number of files in memory is highly dependent on what windows you have open at the time a memory scan is done. For example, if you have 3-4 browser windows open, there will be more files in memory at the time of the memory scan. And if you are in SAFE MODE, the number of items loaded in memory is substantially less because SAFE MODE only starts critical drivers and files to permit you do basic things via SAFE MODE. So in answer to your question, I would say that you are not experiencing any problems...based on the information supplied in your post. I suspect that if you have all windows/GUIs closed when booted into normal mode and then scan memory with SAS being the only GUI open that you will see between 700-750 items scanned.
  9. - The portable version runs on Windows XP, Vista, Windows 7 (32-bit and 64-bit). - It requires a Windows environment to run. - It requires ~ 15 mbyte of USB space. https://www.superantispyware.com/portablescanner.html?tag=SAS_PORTABLEFOLDER
  10. Will it start up if you disable real-time protection in SAS? Or if you temporarily disable the real-time protection of any other security programs that you have....such as your anti-virus security program?
  11. See the link below on how to submit a suspected False Positive. https://www.superantispyware.com/supportfaqdisplay.html?faq=28
  12. Does the SAS icon show up if you LOGOFF your account and log back in? Is SuperAntiSpyware.exe in memory...which it should be.
  13. The public pre-release testing is supposed to start this week. The final public release depends on what issues are found during the pre-release testing.
  14. You cannot start an update via the Task Scheduler (SSUpdate.exe). The update is controlled internally via communications between SuperAntiSpyware.exe and SSUpdate.exe. This is changed in the upcoming new V5.0 which uses Task Scheduler for both updates and scheduled scans.
  15. SAS V4.49.1000 is available for upgrading your V4.48.1000 One thing you can do to correct the initial problem is: 1. Using Windows Explorer, navigate to the SuperAntispyware folder at C:\Program Files\Superantispyware and open the folder. 2. Right click on the file SuperAntiSpyware.exe and select Properties from the menu. 3. When the Properties window opens, select the Compatibility tab. 4. Under Privilege Level, check mark "Run this program as an administrator". 5. Click on Apply and OK 6. Shut down and then restart SuperAntiSpyware That should resolve your problem for the future.
  16. For Windows 7 users who have upgraded to Service Pack 1: The link below provides the procedure for cleaning up backup files that are created during the SP1 installation. This cleanup procedure makes SP1 permanent and that means SP1 cannot be removed. So be sure that you want SP1 to be permanent. The cleanup will regain 1-4 gigabytes of disk space depending on your Win 7 system. Run a disk DEFRAG after the cleanup to improve system performance. The deletion of tens of thousands of the backup files will definitely speed up an SAS scan http://www.ghacks.net/2011/02/23/remove-windows-7-sp1-backups-to-free-up-disk-space/
  17. Please submit a support request ticket so that the SAS gurus can identity what the kernel mode scanner to fail on your system.
  18. Go to Preferences>Scanning Control tab and uncheck: - Use Kernel Direct File Access (recommended) - Use Kernel Direct Registry Access (recommended) - Use Direct Disk Access (recommended) Now try to perform a Complete Scan and see if the problem is resolved. Is your Intel CPU the new I7 Sandy Bridge technology? At any rate, please submit a Customer Support Request so that the SAS gurus can work with you to resolve this system specific issue. https://www.superantispyware.com/precreateticket.html
  19. https://www.superantispyware.com/prerelease.html
  20. But it did block trojansimulator.exe from running which is exactly what SAS real-time is designed for. Check the Quarantine folder of SAS and see if TrojanSimulator.exe is there.
  21. What was the warning that SAS issued when you executed TrojanSimulator.exe? It should have wanted to quarantine it. It would be best to put TrojanSimulator.zip on a flash drive or DVD so that none of the scanning programs will unzip it and flag TrojanSimulator when you scan. It is definitely benign and is only for testing. Take a look in MSConfig at your startup programs and make sure that Trojansimulator.exe or Tsserv.exe are not started up when you startup your computer. If they are, remove them from your startup program list. Please read the instructions for TrojanSimulator uninstall. http://www.misec.net/trojansimulator
  22. Keep in mind that SAS PRO does not scan web pages and the various links that load when you open a web page. You can use TrojanSimulator to see real-time block a "malicious" file from running in your computer. TrojanSimulator is a benign file that simulates a malicious file. 1. Turn off your anti-virus scanner so that it does not detect the benign TrojanSimulator.exe file before SAS PRO does. 2. Go to the link below and download the TrojanSimulate.zip file. Save it on your desktop. http://www.misec.net/products/TrojanSimulator.zip 3. Unzip the file. SAS PRO should/may trigger when you unzip the file and attempt to quarantine file trojansimulator.exe. Let SAS quarantine it if it does trigger. 4. If you do not get an SAS trigger, execute file trojansimulator.exe. That should definitely cause it to trigger. 5. Once you have completed the test, remove the .ZIP file and the unzipped folder from your system and reactivate your anti-virus scanner. You can read about TrojanSimulator at the link below. http://www.misec.net/trojansimulator
  23. It is typical for the biggie security vendors to say not to run any other security program in real-time along side theirs. Users by the millions do it with no problems all over the world...not two anti-virus or firewall programs together, however. SAS is not an anti-virus program.
  24. Submit a Customer Support Request and the Gurus will straighten it for you. https://www.superantispyware.com/precreateticket.html
  25. I think that you have a series of False Positives. I recommend that you create a Customer Support Ticket and let the SAS gurus diagnose this. All the registry detections (Oreans32) look like False Positives. The only files that are possibly not False Positives are: Below is the CSR link. https://www.superantispyware.com/precreateticket.html You could also run the detected files through VirusTotal and see what other scanners say about them. http://www.virustotal.com/
×
×
  • Create New...