HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\AntivirusPro_2010 HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ESENT\Process\ HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Ext\Settings\ HKEY_CURRENT_USER\Software\Microsoft\Internet Explorer\SearchScopes HKEY_CURRENT_USER\Software\Microsoft\Internet Explorer\SQM\PIDs HKEY_CURRENT_USER\Software\Microsoft\Internet Explorer\Recovery HKEY_CURRENT_USER\Software\Microsoft\Internet Explorer\LowRegistry\Extensions HKEY_CURRENT_USER\Software\Microsoft\Internet Explorer\LinksBar\ItemCache Best policy is avoid malware installs by using a Windows account with normal user rights in stead of full admin rights even Antivirus Pro 2013 cannot beat that policy.ĪntivirusPro_2010.exe yxine.exe Uninstall.exe mifiryvele.exe Combine avast with other free anti malware programs like MBAM and SAS, and then when a rootkit is involved the anti-malware may cleanse it only with a result that the malware restarts after a reboot. There is no resident solution that gets them all and sometimes one's luck is in and one gets a zero-day version. Where you probably will have a similar issue in the future, because of the everchanging malware landscape out there. i am in the process of removing avast from all of my machines and going with something else. if this malware has been in the wild for over a year it is shocking that avast could not detect it. the only question that i have is why avast choked? why didn't it stop it in the first place. the machine has been reloaded so the suggestions though appreciated are pointless. also tried manual removal of the the antivirus pro 2010 by removing registry keys, unregistering dlls, and deleting files all to no avail. i tried all the above in diagnostic startup, selective startup with everything off, in safe mode, etc. a google search showed me others with this same problem and no solutions. was then able to apply the registry patch that corrected the policy which kept me from being able to run any application, and so was then able to install mwb, but mwb would be shut down after 3 seconds of scanning. I was able to apply the registry patch to gain access to the task manager and stop the Antivirus Pro 2010 process, and also stop the svhaste (not svhost) process. Thanks for the reply, but as i said i followed the instructions on bleeping computer (and others) to no avail. What the heck Avast? I used to think you had a good product! I have never seen a virus/malware/whatever as aggressive as this and despite it supposedly being a well known one why didn't Avast catch it? On top of the hours wasted trying to repair the problem hours were spent reloading the system from scratch. I followed the instructions on bleeping computer to the letter, multiple times, and thought those instruction seemed like they were promising (allowing me to gain access to the task manager again) it ultimately was a complete waste of time. Starting in safe mode I was able to uninstall, reboot, and reinstall avast which schedualed a boot scan that did not detect anything. The Task manager was disabled and system policies were applied that kept Avast from running. The culprit was something called Antivirus Pro 2010 as well as another similar sounding product. About a week ago, while running the current and fully up to date Avast Home on my fully updated Windows XP Pro machine, I visited a computer parts web site and contracted malware that Avast neither detected or could repair.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |