This is a read-only archive of malwareremoval.com. No new posts or registrations. Privacy Page
Malware Removal Forums

Please help! 80000000.@ and 800000cb.@ errors

1 min read

✨ The volunteers who helped with this thread aren't active anymore, but you can still get a personalized answer — click Ask AI below.

This thread's last reply is from August 15, 2012, 7:41 PM UTC. Software, malware, and removal-tool advice below may be out of date — treat specific steps and download links with caution.

blondespot11
August 15, 2012, 12:17 PM UTC
So I let my Dad use my computer and next thing you know I have a virus. I was able to get free avast installed and I am able to use my computer again but avast keeps giving me pop ups over and over that it has deleted the trojan 80000000.@ or 800000cb.@.
Avast says it is located in C:\Windows\Installer\{0f3f7e79-ffc3-1731-0fc8-4386b2e85c5d}\U

I have attached DDS.txt and Attach.txt. I have ordered Malwarebytes hoping that will help. Please let me know what I need to do. Thanks so much.

Attachments:

deltalima Admin/Teacher
August 15, 2012, 7:41 PM UTC
Posting Logs as Attachments

May I draw your attention to the topic: ALL USERS OF THIS FORUM MUST READ THIS FIRST, which you should have read before posting for help.

The instructions for running DDS found HERE, state how we need you to post the logs, so we can help you.

The section here explains why you should not post attachments unless the helper assisting you requests that you do so.

If you still require assistance, please start a new topic and copy and paste your DDS logs (DDS.txt and Attach.txt) and wait for a new helper. Thank you for your understanding.


This topic is now closed.

✨ Ask AI about this thread

No ads, no affiliate links — generated on request from this thread's own archived content, not written by forum staff. Never run a scan/removal tool as a self-service step if the original thread describes it being done under a helper's direct supervision, and don't include your name, email, or other personal details in a follow-up question. See our privacy page for details on how this works.