Jump to content


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.

Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.


Boo/sinowal.f Boot Sector Virus

  • Please log in to reply
1 reply to this topic

#1 steve.marks59


  • Members
  • 11 posts
  • Local time:11:23 AM

Posted 12 July 2010 - 03:39 AM

This was in an Avira scan:

"Master boot sector HD2
[DETECTION] Contains code of the BOO/Sinowal.F boot sector virus
[NOTE] The boot sector was not written!"

The HD2 referred to here is an external HD in an enclosure connected by a USB cable.
I don't boot using this drive.

I have tried to clean this using various tools but it remains.

My questions are:

1. Can this infection hurt me even though I don't boot this drive?

2. How can I fix the MBR on that drive? I have 3 partitions on that drive and don't want to lose access
to my files on them. It is a 250GB drive and my other drive is only 40GB.

3. The CD drive is missing from my laptop so I can only boot from my internal HD or the floppy
drive. My BIOS does not support USB booting.


BC AdBot (Login to Remove)


#2 steve.marks59

  • Topic Starter

  • Members
  • 11 posts
  • Local time:11:23 AM

Posted 20 July 2010 - 02:22 AM

Problem Solved!

This is what worked for me:
I downloaded Bootkit Remover version .

Here is the download link: http://www.esagelab.com/files/bootkit_remover.rar

I followed the included instructions.


The tool should be run from a command line with Administrator privileges.

1. To verify purity of all system drives' MBRs:

> remover.exe

Scanning should be completed in a couple of milliseconds. In the output
you will receive one of the three verdicts for each drive:

OK (DOS/Win32 Boot code found)
- MBR boot code is clean.

Unknown boot code
- MBR boot code is modified. This practically corresponds to either
an active bootkit infection, or a custom boot manager installed (such
as GRUB).

Controlled by rootkit!
- a bootkit with self-hiding capabilities is detected.

2. To restore the original boot code:

> remover.exe fix <device>

... where <device> is the target physical drive name (ex. \\.\PhysicalDrive0).

This tool restored my boot code. My partitions on the drive remained intact and I was able to access them
without any problems. The Drive Letters were changed. I used Disk Management to change them back .
I was very pleased with this tool.

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users