[HOW TO] Get back your Windows XP Bootloader


Recommended Posts

fixmbr does not trash your partitions. It just returns the Microsoft boot loader to the Master Boot Record. Microsoft cannot (will not?) see the Linux partitions, but they exist and can be used or removed, at the user's discretion.

You can re-install GRUB (or LILO) to re-allow mutli-boot, or you can set up your NT boot loader to do the same thing.

  • 4 weeks later...
  • 3 months later...

very very thanks to you........................................

there is lot of formulas to remove linux and bring back the xp boot loader but easiest way is posted in first post of this thread and that way is also secure.......

thanks

  • 3 weeks later...
  • 3 months later...
Hmm, that must be if you've installed Linux in a VERY specific way, because now I can't boot into either OS. Wonderful.
No. It is very general, as it restores the Microsoft MBR to the hard drive.

Chances are that some other action has corrupted your partitions if this doesn't work.

Well, here is a method that will work, if you can boot Linux (installed or LiveCD, it doesn't matter).

The "code" part of the MBR is the first 446 bytes of the hard drive. If you can get that as a file, then you use the command (as root):

dd if=mbr.bin of=/dev/hda bs=446 count=1

Now, all we need is some nice soul with XP and a LiveCD to grab the 446 bytes from his XP box and post it here, so others can use it to write to their MBR.

That eliminates any problems with booting the XP CD and getting to recovery console, or booting from a floppy from bootdisk.com.

  • 1 month later...

well I have tried the fixmbr in the windows recovery console, but wasn't sure if I had screwed up beacuse after typing that in, installation then rebooted right into the windows xp install. Now even if i try to stop it midway, the installation pop up again even if I reboot. Basically, my concern is if my files will still be avaible to me besides the fact that the windows installation is installnig windows xp again

Yes (if I understand you correctly).

Your Linux partition(s) will be there, untouched. The fixmbr just reset the Windows bootloader to its Microsoft-default settings. You can do a grub-install to get the ability to use GRUB to boot back into Linux.

Use a LiveCD to browse around and verify your data is untouched for yourself. :)

  • 1 month later...

It is fdisk /mbr (no space in the "/mbr" part), or fixmbr. That might be part of the problem.

That fixes the MBR. If for some (non-Linux) reason, your boot.ini file is in need of repair (Linux doesn't touch NTFS, so it could not have modified it*), you can do a fixboot, and I believe that it will fix the boot.ini and NTLDR for you.

* Technically Linux can write to your NTFS partition, but it would take several deliberate actions on your part.

Honestly, I don't know.

Conventional wisdom has been when I started using Linux that it was experimental and not recommended.

I don't know how much native NTFS has improved since then. Also, CaptiveNTFS made its debut a few years ago, and that uses Windows' own NTFS.SYS file to 'understand' the NTFS filesystem. I have heard it works, but is a bit more sluggish.

You will always be safe writing to a Linux native filesystem, or FAT, so that is what I would probably recommend.

well what basicaly happens with me is i did sepll it right, i typed "fdisk /mbr" and it said "are you sure you want to write a new mbr?" and i hit enter, than it just says it again and again, so i couldnt figure out how to restart my pc from there so i hat to hit th power and it was still GRUB.

well what basicaly happens with me is i did sepll it right, i typed "fdisk /mbr" and it said "are you sure you want to write a new mbr?" and i hit enter, than it just says it again and again, so i couldnt figure out how to restart my pc from there so i hat to hit th power and it was still GRUB.

You are not supposed to keep hitting enter, you press "y" and then hit enter.

well, it doesnt say what to do, and it only lets me type one letter

So you have to type a "Y" or a "N" and then <Enter>.... yes? I've done this multiple times and it works ok for me (no looping back).

Barney

**Edit... the guy above me beat me to this! :pinch:

If for some reason you find the need to get back to your Windows XP bootloader instead of the one installed by your Linux distro, simply follow these instructions:

1. Boot up with your Windows XP disc.

2. Select the option Recovery Console.

3. At the prompt, type "fdisk /mbr" (without the quotes of course)

4. Restart your computer.

Edited with correct info from the following posts...

What do you do if your Windows XP CD resides on a HD, for example on a Dell, and the HD you are wanting to recover is on a separate HD. How do you recover it then? Is there a Boot CD that can be downloaded and used?

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Everyone else has said it. I'm gonna say it - you don't know what you're talking about. I do. I have two laptops. One work, one personal. I have access to two more laptops - both personal. At home I manually update my personal laptop when I see on Neowin that there is an update - I carry on and only apply the updates when I am ready. My work one only updates when my workplace decides to send it - I carry on and only apply the updates (when they actually arrive, which is usually days after the release) when I switch off the laptop at the end of the day as usual. The two other personal laptops only get updated when I get to it which is rarely - the people who own them carry on using them until I get to it and update them. All of the browsers on all laptops are configured to restore the tabs when launched. Google and Microsoft have changed from 6 weeks to 4, and it looks like it's going to move to 2. None of these changes affect how any of these browsers on the laptops are used. Not one jot. My advice to you is stop panicking whenever you see an update. Just carry on with what you're doing. This even benefits you in a way - from your comment you sound like you don't like the changes or the frivolous new features - great - then carry on as before!
    • AMAZON needs to take total accountability for this.
    • Server Summit had a heap of announcements, ADCS changes are baller.
    • Nice, hope they *finally* fixed the issue with the NTFS driver where the system would completely brick during large file copies using the built in driver. It's been broken for years requiring me to use the older, slower, NTFS-3G FUSE driver.
    • Windows 11 KB5094126 BSODing, freezing, forcing BitLocker lockout, breaks OneDrive, and more by Sayan Sen Microsoft released Windows 11 KB5094126 and KB5093998 last week as the latest Patch Tuesday updates. Following that the company also published the accompanying dynamic updates under KB5094149, KB5095971, and KB5094156. While Microsoft has so far not acknowledged any major problems with the release, some users online are running into problems. These range from OneDrive and Dropbox access issues, BitLocker recovery lockouts, to blue screens and BSODs. The most common one seems to be happening with HP systems wherein affected users say they hit 0xc0430001 BSOD (blue screen of death) error code after the KB5094126 update. We wonder if this could be related to the recent bug we covered on HP devices wherein the ongoing Secure Boot certificate updates are leading to similar issues. While we are not certain, users affected by this issue likely need to ensure that the boot.stl file is included on the installation media (such as a USB installer or ISO), if the above-mentioned dynamic updates are deployed. If this file is missing, computers may fail to boot from the installation media and could display the error 0xc0430001. This STL file is used by Secure Boot to verify that the boot files are trusted, so it must match the same Windows version and system architecture. To ensure the file is included, Microsoft recommends using the Update WinPE script, which automatically updates the image and handles the required files. Alternatively, you can manually copy the boot.stl file from the Windows\Boot\EFI folder on a Windows device and place it in the matching folder on your installation media before deploying the updated image. Aside from blue screening some users also note their systems have been freezing following the update. This could be happening to Lenovo PCs specifically. In the case of the OneDrive and Dropbox access issues, a user figured out that there could be a conflict with UAC. He explained: "Okay, so I did some digging, and in our environment KB5094126 breaks OneDrive and Dropbox in Explorer. I went through all our GPOs and found out that the combination of disabling UAC and having my user being a local admin breaks OneDrive in Explorer. ... If I enable UAC again, then it works, even with KB5094126 still installed." Hopefully, Microsoft will look into these issues. Source: Microsoft forum (link1, link2, link3, link4), Reddit (link1, link2, link3, link4)
  • Recent Achievements

    • Week One Done
      Jeroen Wilms earned a badge
      Week One Done
    • Week One Done
      rolfus earned a badge
      Week One Done
    • One Month Later
      Leroy Jethro Gibbs earned a badge
      One Month Later
    • Conversation Starter
      flexorcist earned a badge
      Conversation Starter
    • One Month Later
      AndreaB earned a badge
      One Month Later
  • Popular Contributors

    1. 1
      +primortal
      508
    2. 2
      +Edouard
      197
    3. 3
      PsYcHoKiLLa
      138
    4. 4
      ATLien_0
      90
    5. 5
      Steven P.
      80
  • Tell a friend

    Love Neowin? Tell a friend!