[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

    • My father still uses a programme written in dbase3. Still manages to work with a little help from dosbox. 
    • Microsoft hides these secret Windows 11 performance boost settings available on every PC by Sayan Sen Windows enthusiasts often look for ways to extract as much performance out of their systems as possible, and it's often the case that they try and do so while trying to minimize the heat and power consumption. This is especially relevant in the case of mobile Windows PCs since laptops and notebooks tend to get hot and management of that heat and power is harder in such a form factor. As such users often turn to techniques like under-volting which can be used to squeeze out the maximum capabilities of a chip while also maintaining lowered power levels. There are official apps from AMD and Intel with the likes of Ryzen Master and XTU (Extreme Tuning Utility). While these are quite handy, most enthusiasts probably prefer to dig into the BIOS and play around with settings there like Curve Optimizer on Ryzen, which lets users set various frequency-voltage scaling values. These are essentially called P-States. If you are not familiar with them, Processor Power Management is done through Advanced Configuration and Power Interface (ACPI) P-states and C-states. While P-states or performance pwoer states handle CPU voltage-frequency scaling, C-states deal with CPU sleep states so that some of the CPU functions, which are not necessary at that moment, can be disabled. The P-states and C-states work together to make the processor run more efficiently. It helps the OS and apps determine which cores can be parked and which should be boosted. Of course not every user is an enthusiast or knows the technicalities and integrities of how things like overclocking or undervolting work. Thankfully for them Windows itself offers something pretty cool, though it is hidden by default on all systems. By default, Windows only has two P-States, "Minimum Processor State" and "Maximum Processor State." However, this can be changed with a Registry trick to expand the options under a secret "Processor performance boost mode" dropdown. This essentially enables the HWP or hardware P-States available on a device, and these are not controlled just by the OS itself as the underlying hardware gets involved too. In total there are five Processor Performance Boost Mode profiles that control how Windows requests and allows CPU turbo/boost behavior under the different power policies. They are: Disabled: In this mode, processor boosting is effectively turned off. The CPU will avoid entering turbo or boost frequencies and instead operate closer to its base frequency ceiling. This can significantly reduce power consumption and heat output, but at the cost of reduced burst performance and responsiveness in short workloads. Enabled: This is the standard behavior where boost functionality is allowed under normal conditions. The processor can opportunistically increase frequency when workload demands it, balancing performance gains with power and thermal constraints as managed by the system. Aggressive: Aggressive mode favors performance more heavily, allowing the CPU to enter higher boost states more readily and sustain them longer. This should in theory improve responsiveness under bursty or heavy workloads but increases power draw and thermal output compared to the default enabled behavior. Efficient Enabled: This mode still allows boosting, but with a stronger bias toward energy efficiency. The system attempts to use boost more selectively, avoiding unnecessary frequency spikes when the performance gain is marginal. Efficient Aggressive: This is a hybrid approach where boost is still performance-responsive, but the system continuously weighs efficiency more heavily than in Aggressive mode. It aims to deliver noticeable performance improvements while reducing wasted power in less demanding scenarios. Here's how to enable the Processor performance boost mode: Open Registry Editor: Press Win+R, type regedit, and click OK. Go to: HKLM\SYSTEM\CurrentControlSet\Control\Power\PowerSettings\54533251-82be-4824-96c1-47b60b740d00\be337238-0d82-4146-a960-4f3749d470c7 (where HKLM stands for HKEY_LOCAL_MACHINE_) Modify the value of Attributes from 1 to 2 (you can find modify option by right-clicking) After that, exit Registry, you should now be able to see the new "Processor performance boost mode" dropdown menu: As you can see there are now five new P-States or CPPC states or power profile available that help define the boost mode processor setting on your PC. Wrapping it up here's a quick run-down of the settings as defined by Microsoft itself. Setting Description Disabled The corresponding P-state-based behaviour is disabled. Collaborative Processor Performance Control (CPPC) behaviour is disabled. Enabled The corresponding P-state-based behaviour is enabled. CPPC behaviour is Efficient Enabled. Aggressive The corresponding P-state-based behaviour is enabled. CPPC behaviour is Aggressive. Efficient Enabled The corresponding P-state-based behaviour is Efficient. CPPC behaviour is Efficient Enabled. Efficient Aggressive The corresponding P-state-based behaviour is Efficient. CPPC behaviour is Aggressive. Aggressive At Guaranteed Windows calculates the desired extra performance above the guaranteed performance level, and asks the processor to deliver that specific performance level. Efficient Aggressive At Guaranteed Windows always asks the processor to deliver the highest possible performance above the guaranteed performance level. In the next part we shall be comparing these settings to explore how much of a benefit or regression they can provide in terms of performance and power efficiency. If you decide to change the values on your system and are experiencing problems like crashes or an overheating PC, make sure to revert the steps back to the original state.
    • I think he means you haven't reviewed previous UFC games. Of course it doesn't matter... Every time you just report on something that involves the President even if just simply what happened you guys usually get accused of being anti-Trump. We live in fun times.
  • Recent Achievements

    • 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
    • One Month Later
      agatameier earned a badge
      One Month Later
  • Popular Contributors

    1. 1
      +primortal
      518
    2. 2
      +Edouard
      198
    3. 3
      PsYcHoKiLLa
      147
    4. 4
      ATLien_0
      93
    5. 5
      Steven P.
      78
  • Tell a friend

    Love Neowin? Tell a friend!