by marzametal » Fri Nov 29, 2013 7:06 am
It happened again. This seems to be a temperamental thing. I suspect it might have something to do with software, more specifically security software... which one gets to load first wins the match sorta thing (who gets their hooks in first). I am not sure if there is a way to manually order the way startup items load, since logically speaking, either a firewall or anti-malware application would need to load before AdMuncher... Thoughts?
This time I didn't reboot into safe mode with networking... I just switched off MalwareBytes AntiMalware protection (both checkboxes) and rebooted normally. The error in AdMuncher had disappeared.
EDIT: a bit about my setup...
Windows 7 Home Premium 64bit SP1
Emsisoft AntiMalware
Emsisoft Online Armor Premium
MalwareBytes Anti-Malware
AdMuncher Pro
In regards to browser, I use Pale Moon 64bit, with NoScript and Ghostery...
EDIT 2: I had this error 4 times in a row, so I disabled MBAM from startup and loaded it instead when Windows had booted up. No error! Will keep you posted if it happens again without MBAM...
EDIT 3: The error happened again, with MBAM not loading at startup. This time I removed AdMuncher from my Firewall/HIPS exclusion list in Emsisoft Online Armor Premium, so the software could recognise AdMuncher and rebooted. Then I went into Online Armor Premium and modified an advanced setting for AdMuncher (both AdMunch.exe and AdMunch64.exe), allowing it to "set global hooks". I also allowed MBAM to reload on startup again. Will keep y'all posted!
EDIT 3.5: Having MBAM and AdMuncher run after Windows loads, as in manual execution. Didn't work. The winsock error was still present.
EDIT 4: It still pops up... this time, I set both AdMunch executable files to "Run as Administrator". I also removed the exclusions for AdMuncher from Emsisoft AntiMalware, since it kept on unticking one of the 3 exclusion options (Behaviour Blocker). Lets see if this works... !!!