You currently have javascript disabled. Several functions may not work. Please re-enable javascript to access full functionality.

Register a free account to unlock additional features at BleepingComputer.com

Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.

Help!

I contracted this Winspyware protector thing and it keeep telling me that i got so much viruses in my computer, both in registry and memory. I cant find the WinSpyware in the control panel. What should i do, by deleting WinSpyware, will the virus shown by it gone too?

Advice please, i wish to get rid of Winspyware as well as the virus shown by it.

Hope to get some free advice as i am not very rich to have money buy those programes.

This is usually the result of using specialized malware removal tools. You have brokr the path for the program to open with. Windows wants to open it and can not...hence the message.

To resolve this, download Autoruns, http://www.microsoft.com/technet/sysintern...s/Autoruns.mspxsearch for the related entry and then delete it.Create a new folder on your hard drive called AutoRuns (C:\AutoRuns) and extract (unzip) the file there. (click HERE if you're not sure how to do this.)Open the folder and double-click on autoruns.exe to launch it.Please be patient as it scans and populates the entries.When done scanning, it will say Ready at the bottom.Scroll through the list and look for a startup entry related to the file(s) in the error message.Right-click on the entry and choose delete.Reboot your computer and see if the startup error returns.

run the atf cleaner, clean all and immediately run MBAM and post a new log, make sure you update MBAM