Was having trouble with Windows Update not working. After much discussion with an agent on Microsoft's community forum, the agent said I had malware and that I should just do a clean install of Windows. I don't want to do a reinstall for a variety of reasons but I will do it as a last resort. I thought I would ask you all if you thought I had malware and whether I can remove it before I hauled off and did the clean install.
I list the details below. Anyone have any thoughts? Thanks!
----- Details -----
- Windows XP Media Center Edition Version 2002 SP3
- McAfee Security Center v11.0, has VirusScan v15.0, DAT 6549.0000, Engine v5400.1158 (I have autoupdate turned on and working)
- Ran a full scan in safe mode with networking. No problems reported. All zeros in the report.
- Ran Stinger in safe mode with networking. Sensitivity level "Very High" with "Report only." Here is the report:
McAfee(r) Labs Stinger(tm) Version 10.2.0.408 built on Dec 2 2011
Copyright (c) 2011 McAfee, Inc. All Rights Reserved.
Virus data file v1000.0000 created on Dec 2 2011.
Ready to scan for 3515 viruses, trojans and variants.
Scan initiated on Sun Dec 04 17:26:15 2011
Rootkit scan result : Not Scanned
Master Boot Record(s):....1
Possibly Infected: ............0
Number of clean files: 18534
Mmmm... I see the line that says "Rootkit scan result : Not Scanned." Do I need to do something to get Stinger to give a rootkit scan result? Does this mean Stinger did not scan for rootkits?
- Stinger also created a file called vscan.bof. Do you want me to attach that file in another post?
- Ran GetSusp in safe mode with networking. GetSusp created a log called GetSusp.xml. Do you want me to attach that file in another post?
- Previously, I posted to Malwarebytes forum. Their agent went through a lot of details and decided I did not have malware. But, the Microsoft agent still thought I had undetected malware even though VirusScan said "no" and the Malwarebytes agent said "no." The Malwarebytes thread is at:
Note that on the Malwarebytes discussion I mentioned a network problem. That problem is resolved now so you probably can ignore that part.