Click to See Complete Forum and Search --> : What To do About MBR Virus
Orangeman
October 26th, 2003, 09:31 PM
Hey Gang,
I just ran the AVG quick test and found the attached screenshot record of a mbr virus.
If I click KEEP I still get the warning AND if I click CONFIRM CHANGES I still get the warning.
Assuming that I have a virus that my AVG AV won't get rid of, how do I replace and/or fix the MBR?http://www.members.aol.com/jpb701/mbr
Thanks,
Orangeman :confused:
DocPC
October 26th, 2003, 11:15 PM
Hey Gang,
I just ran the AVG quick test and found the attached screenshot record of a mbr virus.
If I click KEEP I still get the warning AND if I click CONFIRM CHANGES I still get the warning.
Assuming that I have a virus that my AVG AV won't get rid of, how do I replace and/or fix the MBR? http://www.members.aol.com/jpb701/mbr
Thanks,
Orangeman :confused:
Sorry man, I don't click NUTTIN' that ends in AOL.com.......
:sad:
Orangeman
October 26th, 2003, 11:24 PM
Sorry man, I don't click NUTTIN' that ends in AOL.com.......
:sad: ....nuttin' except bother to bother me... :redeyes:
silencio
October 27th, 2003, 01:50 AM
fdisk /mbr I've never seen it blow away a system but it could happen though.
Orangeman
October 27th, 2003, 04:00 AM
I just heard from AVG. They said it was a cosmetic 'bug' in their system, not a virus. If it were, it would have listed the type.
:rolleyes:
It is probably some software I installed that is causing the glitch. :(
TripleRLtd
October 28th, 2003, 11:17 AM
It is probably some software I installed that is causing the glitch. images/smilies/frown.gif No need daffy/orangeman:
AVG already said it was THEIR software:
I just heard from AVG. They said it was a cosmetic 'bug' in their system, not a virus. If it were, it would have listed the type.
:rolleyes:
bcyee
October 28th, 2003, 12:22 PM
Regardless of source of the change to the master boot record, silencio has the best solution. Boot to a known unaffected boot disk with the fdisk program on it and issue the command fdisk /mbr and it will rewrite the system with a fresh MBR. This is unless you are running some sort of boot manager in your MBR and don't want it corrupted.