[cbailey249]

I've tried that many times now and it just keeps doing the same thing. After it says it's complete it restarts and says it can't startup and I need to run the startup repair or the blue screen comes up.

[Advertisements]

Try this please. You will need a USB drive and a blank CD.

Download GETxPUD.exe to the desktop of your clean computer

• Run GETxPUD.exe
• A new folder will appear on the desktop.
• Open the GETxPUD folder and click on the get&burn.bat
• The program will download xpud_0.9.2.iso, and upon finished will open BurnCDCC ready to burn the image.
• Click on Start and follow the prompts to burn the image to a CD.
• Remove the USB & CD and insert it in the sick computer
• Boot the Sick computer with the CD you just burned
• The computer must be set to boot from the CD
• Gently tap F12 and choose to boot from the CD
• Follow the prompts
• A Welcome to xPUD screen will appear
• Press File
• Expand mnt
• sda1,2...usually corresponds to your HDD
• sdb1 is likely your USB
• Click on the folder that represents your USB drive (sdb1 ?)
• Press Tool at the top
• Choose Open Terminal
• Type the following and press enter:
  
  dd if=/dev/sda of=mbr.bin bs=512 count=1
  
  
• Press Enter
• After it has finished a file will be located on your USB drive named mbr.bin
• Remove the USB drive and insert it back in your working computer and navigate to mbr.bin, zip it up and attach it to your next reply.

This will allow me to have a look at the MasterBootRecord of your drive and see if it is infected.

[CompCav]

Try this please. You will need a USB drive and a blank CD.

Download GETxPUD.exe to the desktop of your clean computer

• Run GETxPUD.exe
• A new folder will appear on the desktop.
• Open the GETxPUD folder and click on the get&burn.bat
• The program will download xpud_0.9.2.iso, and upon finished will open BurnCDCC ready to burn the image.
• Click on Start and follow the prompts to burn the image to a CD.
• Remove the USB & CD and insert it in the sick computer
• Boot the Sick computer with the CD you just burned
• The computer must be set to boot from the CD
• Gently tap F12 and choose to boot from the CD
• Follow the prompts
• A Welcome to xPUD screen will appear
• Press File
• Expand mnt
• sda1,2...usually corresponds to your HDD
• sdb1 is likely your USB
• Click on the folder that represents your USB drive (sdb1 ?)
• Press Tool at the top
• Choose Open Terminal
• Type the following and press enter:
  
  dd if=/dev/sda of=mbr.bin bs=512 count=1
  
  
• Press Enter
• After it has finished a file will be located on your USB drive named mbr.bin
• Remove the USB drive and insert it back in your working computer and navigate to mbr.bin, zip it up and attach it to your next reply.

This will allow me to have a look at the MasterBootRecord of your drive and see if it is infected.

[cbailey249]

Would a blank DVD work just as well?

Edited by cbailey249, 24 May 2012 - 08:17 PM.

[CompCav]

Yes any recordable CD or DVD

CompCav

[cbailey249]

Ok I think that I have "zipped it up." I put the mbr.bin file on my desktop, right clicked on it, chose send to, and then compressed (zipped) folder. But now I can't figure out how to attach anything on here.

[CompCav]

OK click use fullEditor and then below the input box you will see click to attach files.

Click "Click to Attach Files and then browse to the file on your computer.

[cbailey249]

Here it is.

Attached Files

•  mbr.zip   553bytes   437 downloads

[CompCav]

I believe we should replace the master boot record. We have a copy of the original one if we needed, though it isn't working so the only downside to replacing it is that if you wanted to access the recovery console we would have to make it bootable instead.

So if that is acceptable to you I will begin to prepare the fix, just let me know if it is OK.

[cbailey249]

I guess I don't really understand the downside to it. Is that something that could come back to bite me later or what?

[CompCav]

I do not believe so but if everything were working and you actually had a good recovery partition then we would need to go in and make it boot to get to it manually. No other downside.

[cbailey249]

Yeah that sounds fine we can go ahead and do that.

[CompCav]

Enter System Recovery Options.

To enter System Recovery Options from the Advanced Boot Options:

• Restart the computer.
• As soon as the BIOS is loaded begin tapping the F8 key until Advanced Boot Options appears.
• Use the arrow keys to select the Repair your computer menu item.
• Select English as the keyboard language settings, and then click Next.
• Select the operating system you want to repair, and then click Next.
• Select your user account an click Next.

To enter System Recovery Options by using Windows installation disc:

• Insert the installation disc.
• Restart your computer.
• If prompted, press any key to start Windows from the installation disc. If your computer is not configured to start from a CD or DVD, check your BIOS settings.
• Click Repair your computer.
• Select English as the keyboard language settings, and then click Next.
• Select the operating system you want to repair, and then click Next.
• Select your user account and click Next.

On the System Recovery Options menu you will get the following options:
Startup Repair
System Restore
Windows Complete PC Restore
Windows Memory Diagnostic Tool
Command Prompt

• Select Command Prompt
• Type each of the lines below individually and press Enter after each line:

bootrec /FixMbr

bootrec /FixBoot

exit

Then try to reboot back into windows again!

[cbailey249]

Couldn't get this to work either. After restarting it I just got the same results. After selecting English, though, I never had the opportunity to select the operating system to repair. It just took me straight to the user account instead.

[CompCav]

Boot up the same way to the command prompt but instead type:

chkdsk /r

Let it run through all 5 stages and try to boot again.

[cbailey249]

After typing that in it says: The type of the file system is NTFS. Cannot lock current drive. Windows cannot run disk checking on this volume because it is write protected.