[HOW TO] Get back your Windows XP Bootloader


Recommended Posts

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...

For me and some others you might need to type "fdisk /mbr" instead of "fixmbr"

just thought I'd add that before people start saying it doesn't work

585566261[/snapback]

Hahaha, you beat me to it!

Yeah, Fixmbr and Fixboot both don't work. I know, I've tried several times. All they do is jack up the NTLoader.

Edited by Jstphish
is there a way to recover the winlogin.exe

585566297[/snapback]

Of course there is :) Boot into the recovery console and use this command.

expand d:\i386\winlogon.ex_ c:\windows\system32\winlogon.exe

D: = drive Xp cd is in

C: = drive Xp is installed on

Edited by Mr. Dick C. Normous
Jeez, leave it to me to have a typo in my very first HOW TO.  Mark, fix that would ya?

585566188[/snapback]

Not a problem. Done.

You should always be able to go back and edit your first post. All members are able to do this. At least that is how I understand it to work. :unsure:

And, by the way, thanks for the quick write-up! This gets asked an awful lot.

  • 3 weeks later...
Hahaha, you beat me to it!

Yeah, Fixmbr and Fixboot both don't work.  I know, I've tried several times.  All they do is jack up the NTLoader.

585566400[/snapback]

Agreed with that.

It always mess with the NTLoader.....arghhhhhh...gotta hate windows.

  • 5 weeks later...
fdisk /mbr does not work for me. I've even ran a search on my XP box for 'fdisk'...and it's not on here.

Is there a way that actually works? shall I try the 'fixmbr' command and see if that works - because I really don't wanna' mess up my system.

585823046[/snapback]

I have always used fdisk /mbr, but I pretty much stopped using Windows right about the start of the XP days, so I can't say for sure which command is supported in XP. Both are equivalent commands, so they are both safe (and set the MBR back to the MS default)

I have always used fdisk /mbr, but I pretty much stopped using Windows right about the start of the XP days, so I can't say for sure which command is supported in XP.  Both are equivalent commands, so they are both safe (and set the MBR back to the MS default)

585830160[/snapback]

If you have MS Windows 95/98/ME installed, click on Start >> Run. Type in "command", without the quotes, and press Enter. At the command prompt, type in the command "fdisk /mbr" to reinstall the Windows bootloader into the MBR.

If you have MS Windows 2000/XP installed, you will need to have the Windows Installation CD. Insert the Installation CD into your CD-ROM drive and reboot your computer. When Windows Setup loads up, follow the onscreen instructions to open the Recovery Console. At the Recovery Console command prompt, type in the command "fixmbr" to reinstall the Windows bootloader into the MBR.

Slight difference in the OS's.

Ok folks.

Fixmbr and fixboot are not working for me. It says it has revised the boot sector etc, but when I restart the computer it still says the hard drive is not bootable. Tried from the Windows XP CD. The options are limited - it won't let you run anything but what is listed under help (so, no fdisk, sys, etc).

I'm getting very frustrated. I tried reinstalling XP, but it simply copies files over to the HD, resets the computer and then tries to boot from the hard drive (which it cannot do).

I'm lost for a solution.

Ok folks.

Fixmbr and fixboot are not working for me.  It says it has revised the boot sector etc, but when I restart the computer it still says the hard drive is not bootable.  Tried from the Windows XP CD.  The options are limited - it won't let you run anything but what is listed under help (so, no fdisk, sys, etc).

I'm getting very frustrated.  I tried reinstalling XP, but it simply copies files over to the HD, resets the computer and then tries to boot from the hard drive (which it cannot do).

I'm lost for a solution.

585845486[/snapback]

I am not sure why your XP is refusing to boot. Really, all that needs to be done is get Windows to restore the MBR and you are done.

What I would recommend at thsi point (you did try a Win98 boot disk from http://www.bootdisk.com/ right?) is that you back up whatever data you can - use a Knoppix LiveCD if you must to get access to your data. Then fdisk and remove all partitions and reinstall XP completely from scratch. You may have some bad data in your partition table that prevents it from accessing the correct Microsoft data outside the MBR.

  • 3 months later...

The easiest way to fix this problem (I know, ive had to do it quite a few times) is to go on and start the installion, and format the drive. THEN go into the recovery console and in this order type fixmbr then fixboot and reinstall windows. I have not yet figured out how to keep windows on a seperate partition and have it still boot

I am not sure why your XP is refusing to boot.  Really, all that needs to be done is get Windows to restore the MBR and you are done.

What I would recommend at thsi point (you did try a Win98 boot disk from http://www.bootdisk.com/ right?) is that you back up whatever data you can - use a Knoppix LiveCD if you must to get access to your data.  Then fdisk and remove all partitions and reinstall XP completely from scratch.  You may have some bad data in your partition table that prevents it from accessing the correct Microsoft data outside the MBR.

585847112[/snapback]

dont need to start fdisk. just use the windows xp or 2000 cd and format there then reboot.

about people not getting this to work. not taking you all for stupid or anything like that, i would say check if the error says ntloader missing, if so you have to copy it from the xp cd. that is a whole other operation i dont have at hand rigth now. *there work houres are done, driving home*

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 "fixmbr" (without the quotes of course)

4.  Restart your computer.

585565400[/snapback]

Better hope u only have on partition, or you will trash them all (well, they will exist, but u won't be able to boot them)!!! You should warn people ahead of tyme....

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

    • No registered users viewing this page.
  • Posts

    • I've been on Deezer for over a decade, but glad that Tidal joined them in fighting AI slop. Can't stand such takes as Spotify's: "Spotify's CEO recently pushed back against listeners who call AI music "slop," urging people to stop using the term and instead embrace the creative potential of AI music."
    • “Could” … in the IS the healthcare is run by insurance companies that make indecent profits denying basic treatments to people that are paying money for nothing. Besides, where are all the Trump epigones who were stating that the tariffs were going to paid by foreign companies and not the US citizens? …
    • Microsoft Teams gets smarter at spotting sneaky meeting bots by Usama Jawad Microsoft Teams is set to receive a couple of new features soon, including a dedicated Recap app and a rather controversial location tracking functionality. The Redmond tech giant has also explained how it has made online communication and collaboration a lot more performant this year. Now, the company has detailed more secure bot admission mechanisms, as first reported by us in March 2026, and now available in Teams. As the use of AI has expanded across enterprise environments, Microsoft has begun allowing users to integrate bots into their meetings for various tasks, such as note-taking. While this has a tangible productivity benefit for users, Microsoft has highlighted how misconfiguration has allowed bots to join meetings that they shouldn't. This has created security and privacy risks, which Microsoft is now combating using a new Teams admin policy that allows organizers to control how external bots access meetings. Admins can leverage a policy called Manage external bots and their access to meetings. The default configuration is "When detected, require approval before joining", which places detected bots in a lobby before they are explicitly admitted into the meeting. The other option disables the experience. Microsoft has also requested admins to only allow organizers and co-organizers to manage access to a meeting, so that other people don't randomly allow bots into meetings. Teams will now be able to leverage infrastructure signals to intelligently detect and distinguish between bots and humans. Microsoft will soon also trial a registration experience for independent software vendors (ISVs) to build a system that registers a bot with Microsoft, so it is marked as a "known" bot. Teams will also categorize bots as trusted and suspected threats so that organizers can quickly identify which bots they want to allow into a meeting. Additional safeguards to block accidental admission of a bot into a meeting include: No one-click Admit option for identified bots Confirmation prompts when admitting participants that include bots Warnings when organizers choose Admit all, and bots are included Microsoft has begun rolling out this experience, and it will be retiring the current CAPTCHA verification implementation. In the future, the company plans to roll out new capabilities like allow-lists, organization-wide policies, admin reports, audit logs, and more granular controls.
    • With the current hardware prices Microsoft should lift the restriction. Then if you have the correct TPM then allow you to use X feature, if you don't have the correct TPM then don't but still actually let you run windows. 11. With a disclaimer during install that X features would be unavailable.
    • It's good for recycling of course. But commence inflation of a second hand RAM bubble and price gouging on DDR 4 inventory in 3... 2... 1...
  • Recent Achievements

    • Reacting Well
      NovaEdgeX earned a badge
      Reacting Well
    • Week One Done
      NovaEdgeX earned a badge
      Week One Done
    • One Year In
      BA the Curmudgeon earned a badge
      One Year In
    • Conversation Starter
      rosiecharles earned a badge
      Conversation Starter
    • First Post
      KMilenkoski1202 earned a badge
      First Post
  • Popular Contributors

    1. 1
      +primortal
      538
    2. 2
      +Edouard
      266
    3. 3
      PsYcHoKiLLa
      151
    4. 4
      Steven P.
      98
    5. 5
      macoman
      66
  • Tell a friend

    Love Neowin? Tell a friend!