Subscribe to AfterDawn's weekly newsletter.
Help with smitfraudfix log please...
#26
12 Oct 2006 @ 0:29
Niobis
Visit user's personal pageSend private message to this user
Senior Member
SmitfraudFix is not trying to install MSGuard! It is only checking for it.
I suppose you're clean, but aren't you still having problems?
I suppose you're clean, but aren't you still having problems?
Don't be fooled any longer.
http://www.youtube.com/watch?v=BUtbGYgsIu4&feature=related
http://www.youtube.com/watch?v=BUtbGYgsIu4&feature=related
AfterDawn
Advertisement
#27
12 Oct 2006 @ 4:57
then why did i get ZoneAlarm saying that smitfraud wanted to install a new driver or service when i ran a scan with smitfraud??
that's no coincidence,right?
No problems anymore though...
that's no coincidence,right?
No problems anymore though...
#28
12 Oct 2006 @ 13:03
Smitfraud is spyware, SmitfraudFix(what you're using) is a program to fix desktop hijack malware. It needs to install the following to be used: SrchSTS.exe, swreg.exe, swsc.exe and process.exe. It is not trying to install MSGuard, it is only checking for it.
Anyway, great to hear your not having problems any more. Anything else comes up let me know.
Good luck!
Anyway, great to hear your not having problems any more. Anything else comes up let me know.
Good luck!
Don't be fooled any longer.
http://www.youtube.com/watch?v=BUtbGYgsIu4&feature=related
http://www.youtube.com/watch?v=BUtbGYgsIu4&feature=related
#29
12 Oct 2006 @ 23:57
thanks,i still think it's strange that when i installed smitfraudfix,that's when ZoneAlarm popped up with the message saying that smitfraudfix wanted to install msguard...
#30
26 Jan 2007 @ 22:34
Thank you Niobis.
I found this thread about AVG Anti-Rootkit Beta through a posting by jsin22 at [url=http://www.windowsbbs.com/showthread.php?t=58739][/url].
I was at wits-end, but this solved a BSOD problem that could have been mistaken for a DRAM issue (i.e. "Stop 8E" on some installs). There are many quotes like the following on the Web, "STOP 0x0000008e is definitely a ram error." WRONG! After swapping RAM modules and slots and the BSOD not being random enough I kept digging until I found this.
As I wrote AVG, "Effin Awesome! Give me AVG beta over MS GM any day."
BACKGROUND
I was fixing a beleaguered Presario 2204US for a friend. To give you an idea it had 200,000 "*.t" files on it, 75% fragmentation, and 28GB of 40GB used. Now it is running smoothly with only 7GB, but moving around at first was like walking through a house full of 100,000 empty beer cans.
Zone Alarm blue-screened on install, Kaspersky didn't so I used it. When I finally got to upgrading it to XP SP2 it would blue screen on most updates, ESPECIALLY IE7 VIA WEB OR STANDALONE INSTALL. The system would then BSOD shortly after normal boot up, but would only BSOD during an install in Safe Mode.
After many dead ends, I found this thread and with nothing left to lose I eagerly ran AVG Anti-Rootkit Beta. Worked like a charm. lcx32.sys was the culprit.
Thanks Again.
I found this thread about AVG Anti-Rootkit Beta through a posting by jsin22 at [url=http://www.windowsbbs.com/showthread.php?t=58739][/url].
I was at wits-end, but this solved a BSOD problem that could have been mistaken for a DRAM issue (i.e. "Stop 8E" on some installs). There are many quotes like the following on the Web, "STOP 0x0000008e is definitely a ram error." WRONG! After swapping RAM modules and slots and the BSOD not being random enough I kept digging until I found this.
As I wrote AVG, "Effin Awesome! Give me AVG beta over MS GM any day."
BACKGROUND
I was fixing a beleaguered Presario 2204US for a friend. To give you an idea it had 200,000 "*.t" files on it, 75% fragmentation, and 28GB of 40GB used. Now it is running smoothly with only 7GB, but moving around at first was like walking through a house full of 100,000 empty beer cans.
Zone Alarm blue-screened on install, Kaspersky didn't so I used it. When I finally got to upgrading it to XP SP2 it would blue screen on most updates, ESPECIALLY IE7 VIA WEB OR STANDALONE INSTALL. The system would then BSOD shortly after normal boot up, but would only BSOD during an install in Safe Mode.
After many dead ends, I found this thread and with nothing left to lose I eagerly ran AVG Anti-Rootkit Beta. Worked like a charm. lcx32.sys was the culprit.
Thanks Again.
This discussion thread has been automatically closed, as it hasn't received any new posts during the last 180 days. This means that you can't post replies or new questions to this discussion thread.
If you have something to add to this topic, use this page to post your question or comments to a new discussion thread.
If you have something to add to this topic, use this page to post your question or comments to a new discussion thread.
