1: No. System Restore only backs up stuff within the OS, and the MBR is something different
2: The MBR stands for Master Boot Record, so it's not an index of everything on the drive. It's a special section of the drive where the OS bootloader is stored, or at least something pointing to where the bootloader is stored goes. Basically it's a defined area of the drive that the BIOS will look at when trying to find an OS to boot after POST
3: fixmbr SHOULD overwrite the MBR with a clean one, but at the same time, if you haven't removed the source of the infection first, it'll likely just come back
4: The recovery console is only on the Windows CD/DVD
5: Disk 0 is almost always the boot drive. Technically all it really means is that it's the first physical drive found, but unless you set up a dual boot or did something similarly unusual, Disk 0 is pretty much always going to be the boot drive
Also, I noticed that you seem to be under the mistaken impression that merely having an AV program installed absolves you of any responsibility for the security of your system. Nothing could be further from the truth. AV programs are supplementary at best. They will not catch everything because they are reactionary by their very nature. A threat has to be identified, then analyzed, a counter measure has to be devised, tested, all of which can take a few days to weeks. Then it has packaged into an updated definitions file for distribution, which could add a few more days to the whole process before that updated definitions file gets to your particular system. So there could well be a 2-3 week window, commonly referred to as a 0-day threat, where an AV program will have no idea about some threat you may have downloaded. Which is why YOU need to take primary responsibility for your system's security. All the security programs in the world still won't stop you from doing something stupid and infecting your system.
Looks like I've got a master boot record virus. I want to know what my options are.
GMER included this worrisome report in a very long and complex report:
---- Disk sectors - GMER 1.0.15 ----
Disk \Device\Harddisk2\DR5 sector 00: rootkit-like behavior
McAfee Stinger says:
2 master boot records, possibly infected 0
3 boot sectors possibly infected 0
(Six or seven different antivirus programs and scans have failed to identify any specific rootkit virus.)
Gmer's mbr log reports:
Stealth MBR rootkit/Mebroot/Sinowal/TDL4 detector 0.4.2 by Gmer, http://www.gmer.net
Windows 5.1.2600 Disk: HP______ rev.1.00 -> Harddisk2\DR5 -> \Device\0000007e
device: opened successfully
user: error reading MBR
kernel: MBR read successfully
user != kernel MBR !!!
Avast's aswMBR reports:
wMBR version 0.9.9.1297 Copyright(c) 2011 AVAST Software
Run date: 2012-01-16 00:09:40
00:09:40.750 OS Version: Windows 5.1.2600 Service Pack 3
00:09:40.750 Number of processors: 4 586 0x2A07
00:09:40.750 ComputerName: DORA UserName:
00:09:40.968 Initialize success
00:09:41.046 AVAST engine defs: 12011501
00:09:57.203 Disk 0 \Device\Harddisk0\DR0 -> \Device\Ide\IdeDeviceP0T0L0-3
00:09:57.203 Disk 0 Vendor: WDC_WD3200AAKS-00V1A0 05.01D05 Size: 305245MB BusType: 3
00:09:57.203 Device \Driver\usbstor -> DriverStartIo USBSTOR.SYS b83d1f26
00:09:57.218 Disk 2 MBR read successfully
00:09:57.218 Disk 2 MBR scan
00:09:57.218 Disk 2 Windows XP default MBR code
00:09:57.218 Disk 2 MBR hidden
00:09:57.218 Disk 2 Partition 1 80 (A) 07 HPFS/NTFS NTFS 39997 MB offset 63
00:09:57.218 Disk 2 Partition - 00 0F Extended LBA 265237 MB offset 81915435
00:09:57.234 Disk 2 Partition 2 00 07 HPFS/NTFS NTFS 265237 MB offset 81915498
00:09:57.250 Disk 2 scanning E:\WINDOWS\system32\drivers
00:10:04.781 Service scanning
00:10:05.156 Service WRkrn E:\WINDOWS\System32\drivers\WRkrn.sys **LOCKED** 32
00:10:05.656 Modules scanning
00:10:12.500 Disk 2 trace - called modules:
00:10:12.500 ntkrnlpa.exe CLASSPNP.SYS disk.sys hal.dll
00:10:12.515 1 nt!IofCallDriver -> \Device\Harddisk2\DR5[0x8939b2d8]
00:10:12.828 AVAST engine scan E:\WINDOWS
00:10:18.312 AVAST engine scan E:\WINDOWS\system32
00:11:34.109 AVAST engine scan E:\WINDOWS\system32\drivers
00:11:45.734 AVAST engine scan E:\Documents and Settings\Dora Smith
00:14:02.875 AVAST engine scan E:\Documents and Settings\All Users
00:14:50.578 Scan finished successfully
00:17:47.453 Disk 2 MBR has been saved successfully to "E:\MBR.dat"
00:17:47.468 The log file has been saved successfully to "E:\aswMBR.txt"
I didn't continue with the files that were called by the master boot record.
The "Service WRkrn E:\Windows\System32\drivers\WRkrn.sys ***LOCKED** 32 line is in yellow. Do I need to do something special about that?
Avast aswMBR has an option to "FixMBR" - I guess by putting standard code. Alternatively apparently one can do the same thing from within AVAST (I currently have AVAST paid version installed after Vipre didn't do anything to protect or fix my computer.)
MBRCheck from geekstogo.com found
298 GB Physical Drive 0 Windows XP MBR code detected (in green)
SHAI (long string)
74 GB Physical Drive 1 Re: Unknown MBR code
Found nonstandard or infected MBR (restore MBR of a physical disk w standard boot code).
Choose physical disk to fix, usualy 0, choose code for system (ie XP), confirm change.
Alternatively one can boot into the Repair Console and type fixmbr, which, I guess, creates a NEW master boot record with standard code - which might still work.
1. I don't suppose that there's any chance that using system restore from early enough would restore the master boot virus? I believe it backs up everything, but I'm not sure what "everything" includes.
2. One part that puzzles me is that sometimes the replaced code/ file works and sometimes it doesn't. If the master boot record is an index of everything on the drive, then how would substituted standard code still allow the machine to function?
3. If I run fixmbr in the recovery console to fix it, should I also run fixboot, or not?
4. If I have the recovery console installed on my computer, do I need the Windows CD?
5. The other part I'm having trouble with is whether to replace the code in "Disk 0" or "Disk 2". I seem to have two conflicting versions of which "disk" has the corrupted code. And if I did fix "disk 0" what should I do with the mbr in "disk 2"?