Jump to content

JohnBurns

Members
  • Content Count

    22
  • Joined

  • Last visited

Everything posted by JohnBurns

  1. Thanks - used Chrome - no problem. Appreciate your response and efforts.
  2. Still getting this as of TODAY (10/02) Is there a fix still in the works?
  3. JohnBurns

    Definition Updates

    I agree, however it is unusual to go 2 days without an update. Maybe a server problem?
  4. JohnBurns

    Update for SuperAntiSpyware Alternate Start Tool

    Thanks for reply - my SAS Alternate Start Tool looks identical to yours. I have contacted SuMo for more information....appreciate your response. Update 05/30 No longer a problem - SuMo has corrected it - thanks for your input.
  5. My updater app (SuMo) indicates an update is available for SAS Alternate Start Tool - version 1.0.0.26, but I can't seem to find it - and SAS Automatic Update does not install it. Please advise if this is an error by my updater app, or if there is in fact an update which I can manually update. Thanks.
  6. JohnBurns

    Updates Failed

    This morning I can't update definitions - either manually or automatically - is there a problem on the server? Never mind - updates have now processed - problem resolved.
  7. JohnBurns

    SuperAntiSpyware 5.1.0.1002

    Thanks!
  8. JohnBurns

    SuperAntiSpyware 5.1.0.1002

    Can anyone tell me what Version 5.1.0.1002 is? It is currently on many download sites but the latest version at SAS is 5.0.0.1150, which is what I presently have installed. Just curious....
  9. Thanks for your help. I downloaded the pre-release (with no problem) and the event errors appear to have stopped. I appreciate your effort and patience with me. It's all a constant learning process for me. Thanks again!
  10. I did not intend to imply that the event viewer errors caused the problems. In my case it was the conflict between PerfectDisk and SuperAntiSpyware at boot time which caused the problems. Once I stopped SAS drivers from conflicting with PD by installing PD's Blocked List Registry "fix", that problem ceased. It was THEN that the event viewer errors started showing - which was a result of my action of blocking SAS Drivers with the "fix" I am pleased that a 64bit SAS is soon being released. In the interim, I don't mind "living" with the multiple event viewer errors.................sorry I added to the heated discussion in this thread. We just need to exercise some patience and try to understand things happen in spite of everyone's good efforts and intentions. Thanks for the information provided.
  11. This thread seems to be going nowhere - and I wish it could. I also am having problems with SuperAntiSpyware on my Windows 7 Home Premium 64bit OS. Part of my problem is with SuperAntiSpyware and PerfectDisk boot defrag, I know. I had to apply a patch from PD to block the drivers of SAS at boot in order to perform a boot defrag. See: http://www.perfectdisk.com/support/kb/823 This has solved BSOD's however the event viewer still shows Critical events os SASENUM, SASDIFSV.SYS, SASDIFSV and SASKUTIL at boot. Apparently the blocked list from PD is blocking these drivers at boot in order to perform boot-time defrag. I don't know if this even relates to the problem in this thread, however, I would like to know if there is a way to stop the event viewer from continuing to show repeated errors in my event viewer log. I hope this might help some for the previous posts - and help me find a solution to the problem I am experiencing. BTW, I am not a troll............lol! Thanks
  12. JohnBurns

    PCPBIOS.EXE: Rogue.Agent/Gen-Nullo[EXE]

    Thanks, Robin - just updated to Core 4374, Trace 2214, restored file, and ran scan...........everything is ok again. Appreciate all the help in here.
  13. JohnBurns

    PCPBIOS.EXE: Rogue.Agent/Gen-Nullo[EXE]

    Thanks for posting, weighty44 - at least I know I'm not the only instance of this problem......
  14. JohnBurns

    PCPBIOS.EXE: Rogue.Agent/Gen-Nullo[EXE]

    Thanks, Robin..............appreciate your post, HOWEVER, I updated SuperAntispyware after reading your post (to Core 4373, Trace 2214) - restored the file, and ran SuperAntispyware scan again - and there it is.......back again, just like before. Glad you got your pc's cleared, but I'm afraid mine is still in "limbo".
  15. JohnBurns

    PCPBIOS.EXE: Rogue.Agent/Gen-Nullo[EXE]

    Even it this is a "false positive", can someone tell me if it's ok to remove it? If, in fact, it is related to PC Pitstop utility, which i haven't used in a couple years, it would seem that it isn't needed. In searching the Net for an answer, it appears as though this is left-over crap from the PC Pitstop tests which I ran at one time in the past. SuperAntiSpyware hasn't flagged it before, however, even if it isn't spyware, I'd like to remove it unless it causes problems by removing it. So far, putting it in Quarantine has not presented any problems. Appreciate any input in this regard, also. Thanks.
  16. JohnBurns

    PCPBIOS.EXE: Rogue.Agent/Gen-Nullo[EXE]

    New update issued tonight continues to find spyware, C:\Windows\System32\PCPBios.EXE. False positive report submitted. Please advise whether this needs to be removed - or if it is a false positive. MSE and MalwareBytes do not indicate any spyware on the pc , but SuperAntiSpyware continues to flag it. Thanks. I have this item quarantined and no apparent bad results...... also found some crap left behind by PcPitstop, which I have deleted, so this was a good warning flag to clean out the pc. In the meantime, I guess leaving pcpbios.exe quarantined is a good plan until I figure this all out.
  17. JohnBurns

    PCPBIOS.EXE: Rogue.Agent/Gen-Nullo[EXE]

    I also have this (PCPBIOS.EXE: rogue.Agent/Gen-Nullo [EXE] in quarantine - found it last night. Not sure if it's a false positive or not. Would someone please advise if it should be deleted? I think it may be an old entry from PC Pitstop site...but not sure. It's been on this pc since March, 2007 and never been identified as a problem......
  18. The latest definitions downloaded found two instances of spyware on both my home pc's. This is for a reminder program which has been installed several years and never had any indication of spyware before. No changes have been made to the application, so I believe it to be a false positive. The specific name of the application is: Mult-iReminders . Copy of scan log is attached. SUPERAntiSpyware Scan Log http://www.superantispyware.com Generated 10/07/2009 at 08:09 AM Application Version : 4.29.1002 Core Rules Database Version : 4150 Trace Rules Database Version: 2079 Scan type : Quick Scan Total Scan Time : 00:15:26 Memory items scanned : 586 Memory threats detected : 0 Registry items scanned : 723 Registry threats detected : 0 File items scanned : 10241 File threats detected : 2 Trojan.Agent/Gen-Clicker C:\PROGRAM FILES\MULTI REMINDERS\UNINST.EXE C:\DOCUMENTS AND SETTINGS\JOHN R BURNS\START MENU\PROGRAMS\MULTI REMINDERS\UNINSTALL.LNK
  19. JohnBurns

    False Positive - Reminder Application

    Problem solved with latest updates - items no longer appear as spyware.
  20. JohnBurns

    Possible False Positive

    Thanks for your response - I just ran a new scan of my pc with Core 3082 update and there is NOTHING to report. Evidently 3081 and my pc didn't get along well together. Thanks again.
  21. JohnBurns

    Possible False Positive

    A little background first - I had a problem yesterday with Lavasoft Adaware - their incorrect definitions gave false positives on Win32.Trojan.Downloader. However, they corrected that and today I downloaded new definintions and ran LavasoftAdaware again, with no spyware found. Subsequently, I ran SuperAntiSpyware and it found 6000+ traces of Trojan.Downloader.Comcast-Variant, before crashing without completing scan. Being somewhat surprised, I went to SafeMode and ran ewido, which found nothing (as Lavasoft Adaware had done). Subsequently, I have run Spybot S&D, Windows Defender, AVG AntiVirus, all which have found nothing on my pc. Then I tried SuperAntiSpyware again and it started zooming in on Trojan.Downloader.Comcast-Variant again. This time I stopped it since it crashed before after about 30+ minutes of scanning. Is there a problem with the latest definitions that anyone knows about? I find it strange that it is finding trojan when none of the other programs do. Appreciate any help. Thanks.
  22. JohnBurns

    Possible False Positive

    I just checked and it showed version 3081. I had downloaded updates twice before today. Just now I tried again and it changed to 3082. Will try that thatnks for your response. Just curious - was there a problem with 3081?
×