● UK tech experts · info@vividrepairs.co.uk
Vivid Repairs
A Windows desktop PC on a dark workbench displaying a blue screen Windows Boot Manager boot failed error message
Fix It Yourself · Troubleshooting

Windows Boot Manager boot failed

Updated 13 July 202611 min read
As an Amazon Associate, we may earn from qualifying purchases. Our ranking is independent.

Most guides on Windows Boot Manager boot failed recycle the same three steps and leave you stuck. This one doesn't. I fix this exact problem several times a week via remote support, and what actually works depends on the cause. Get that wrong and you're wasting an hour going in circles. So let's work through this properly, fastest fixes first.

TL;DR

Windows Boot Manager boot failed is usually caused by a wrong boot order, corrupted BCD files, or a dodgy drive. Start by disconnecting USB devices and checking BIOS boot order (5 mins). If that fails, run Startup Repair from a Windows USB. Still broken? Use bootrec.exe commands from the recovery Command Prompt to rebuild the boot record and BCD store.

⏱️ 13 min read ✅ Up to 90% success rate 📅 Updated June 2026

Key Takeaways

  • Windows Boot Manager boot failed is fixable in most cases without reinstalling Windows.
  • Always disconnect USB drives first. A rogue USB stick causes this more often than you'd think.
  • Run OEM drive diagnostics before spending time on software fixes. A failing drive needs replacing, not repairing.
  • The bootrec.exe command set fixes the majority of BCD corruption and BOOTMGR missing errors.
  • If bcdedit edits are needed, tread carefully. One wrong entry and you've made things worse.

At a Glance

  • Difficulty: Easy to Advanced
  • Time Required: 5 to 45 mins
  • Success Rate: Up to 90% when drive is healthy

What Causes Windows Boot Manager Boot Failed?

The error message itself is vague, which is annoying. It can mean several different things happening at the hardware or software level, and the fix for one cause won't touch the others. Here's what's actually going on under the hood.

Wrong boot order or BIOS mode. This is the most common cause and the easiest to fix. Your BIOS/UEFI is pointing at a USB stick, an empty optical drive, or a secondary disk instead of your Windows drive. Or the boot mode (UEFI vs Legacy/CSM) doesn't match how Windows was installed. The firmware can't find a valid bootloader, so you get the Windows Boot Manager boot failed screen. Annoying, but sorted in two minutes once you know where to look.

Corrupted or missing boot loader files. BOOTMGR is the small executable that hands control from the firmware to the Windows kernel. The Boot Configuration Data (BCD) store is the database that tells BOOTMGR where Windows lives. If either gets corrupted (bad shutdown, failed update, dodgy partitioning tool), you'll see errors like 'BOOTMGR is missing' or 'Windows failed to start'. This is where bootrec.exe earns its keep.

Failing system drive. A hard drive or SSD with bad sectors on the boot partition will throw Windows Boot Manager boot failed errors that look identical to a software problem. The difference is that software fixes won't stick. You run bootrec, it seems to work, you reboot, same error. That's a hardware problem. OEM diagnostics will tell you definitively. According to Tom's Hardware's drive health guide, catching SMART errors early is the difference between a planned replacement and an emergency one.

Recent changes to the disk or system. Dual-boot setups gone wrong, third-party partitioning tools (I've seen GParted wipe BCD entries on Windows drives), major Windows updates that stall mid-write, or even a new SSD added to the system can all shift the boot configuration into a broken state. System Restore is often the quickest route back from this one.

Firmware issues and CMOS battery failure. A BIOS/UEFI update that didn't complete cleanly, or a flat CMOS battery that resets firmware settings to defaults, can change boot mode, disable the system drive, or clear the boot order entirely. On older machines (5 years plus), a flat CMOS battery is worth checking if the BIOS keeps forgetting settings.

Windows Boot Manager Boot Failed: Quick Fix

Start here. This takes under 10 minutes and fixes a big chunk of cases. No tools needed, no installation media required.

1

Power Drain and Boot Order Check Easy

  1. Disconnect everything external.
    Shut down. Unplug every USB device: drives, dongles, printers, card readers. A USB stick left in the port is a surprisingly common cause of Windows Boot Manager boot failed because the BIOS tries to boot from it and finds nothing useful.
  2. Power drain on laptops.
    If you're on a laptop with a removable battery, pull the power adapter and battery out. Hold the power button for 15 to 20 seconds. This clears residual charge and resets the embedded controller. Refit battery, plug back in, try booting.
  3. Hit the boot menu at power-on.
    Turn the PC on and immediately tap the boot menu key. This is usually F12 (Dell, Lenovo), F9 (HP), or Esc (some ASUS). A one-time boot menu appears. Select your Windows drive or 'Windows Boot Manager' from the list and press Enter.
  4. Verify it boots.
    If Windows loads, great. But go into BIOS/UEFI setup (Del, F2, or F10 at power-on) and make sure the boot order permanently has Windows Boot Manager first. Otherwise you'll be back here next reboot.
If Windows loads after selecting the correct boot device, you're sorted. Fix the permanent boot order in BIOS before closing the lid.
No Windows installation media? If your PC shipped with Windows 10 or 11, there's likely a recovery partition. Look for 'Repair your computer' or a recovery option in the boot menu before buying a USB stick.

More Windows Boot Manager Boot Failed Solutions

Boot order was fine and the drive isn't plugged in wrong? The next step is getting into the Windows Recovery Environment and using its built-in tools. You'll need a Windows installation USB for this if your local recovery partition isn't accessible. You can create one free using Microsoft's Media Creation Tool on another PC.

2

Startup Repair via Windows Recovery Environment Easy

  1. Boot from the Windows USB.
    Insert your Windows 10 or 11 installation USB, restart, and tap the boot menu key to select the USB. Let it load to the setup screen.
  2. Get to Advanced Options.
    On the first setup screen, choose your language and click Next. Then click Repair your computer (bottom left, easy to miss). Go to Troubleshoot, then Advanced options.
  3. Run Startup Repair.
    Click Startup Repair. Select your Windows installation when prompted. The tool scans boot files and BCD, fixes what it can, and restarts. This handles a lot of BOOTMGR missing and Windows failed to start errors automatically.
  4. Run it again if needed.
    Startup Repair sometimes needs two or three passes because some fixes are chained. If it fails once, go back into WinRE and run it again. Took three reboots before this one stuck on a client machine last week, so don't give up after the first attempt.
  5. Try System Restore if Startup Repair fails.
    Back in Advanced options, select System Restore. Pick a restore point from before the problem started. This rolls back system files and registry without touching personal files. Good option if a recent update or software install broke the boot config.
Windows loads normally after restart? Check for any pending updates that may have stalled and caused the original issue, then restart cleanly to confirm stability.
System Restore does not affect personal files, but it will uninstall apps and drivers installed after the chosen restore point. Make a note of what you'll need to reinstall.

If you're dealing with a PC that won't POST at all or has physical damage, those are hardware problems that need hands-on work. But if the machine gets to the boot error screen, you're in software territory and these tools will get you most of the way there. For issues where Windows loads but then crashes repeatedly, our guide on Windows crashing and BSOD errors covers the next layer of diagnosis.

Advanced Windows Boot Manager Boot Failed Fixes

Startup Repair didn't cut it. The BCD is properly broken, or the boot records are corrupted at a level the GUI tool can't handle. This is where we get into the command line. Don't be put off by it. The commands are short and the risk is low as long as you follow the order below.

3

Rebuild Boot Records with bootrec.exe Intermediate

  1. Check the drive first.
    Before touching boot records, run your OEM diagnostics. HP: press Esc at boot, then F2. Lenovo: press Enter then F1 at the Lenovo logo. Dell: press F12 and choose Diagnostics. Run the extended hard drive test. If it reports failure, stop here and replace the drive. Repairing boot files on a failing drive is pointless.
  2. Open Command Prompt in WinRE.
    Boot from your Windows USB as before. Go to Repair your computer, Troubleshoot, Advanced options, then Command Prompt. You'll get a black window with a prompt.
  3. Run bootrec in order.
    Type each command and press Enter, waiting for each to complete before running the next:
    bootrec.exe /fixmbr (writes a new Master Boot Record)
    bootrec.exe /fixboot (writes a new boot sector to the system partition)
    bootrec.exe /scanos (scans all disks for Windows installations)
    bootrec.exe /rebuildbcd (recreates the BCD store with any detected Windows installs)
    When /rebuildbcd finds your Windows installation, type Y and press Enter to add it.
  4. Restart and test.
    Close Command Prompt, remove the USB, and restart. If Windows Boot Manager boot failed has cleared, you're done. If you still see the error, move to the BIOS check below.
bootrec commands complete without errors and Windows loads on restart. Job done.
4

Fix BIOS/UEFI Settings Intermediate

  1. Enter BIOS/UEFI setup.
    Restart and tap the setup key at power-on. This is Del or F2 on most systems, F10 on HP, F1 on Lenovo. You'll land in the firmware settings interface.
  2. Check boot mode.
    Find the Boot or Security section. Look for 'Boot Mode', 'UEFI/Legacy', or 'CSM'. If Windows was installed in UEFI mode (almost all machines from 2013 onwards), this must be set to UEFI. Switching between UEFI and Legacy is a common cause of Windows Boot Manager boot failed after a BIOS reset.
  3. Verify the system drive is visible.
    In the storage or boot section, confirm your main drive appears and is enabled. If it's missing here, there's a hardware connection problem (or a failing drive) rather than a software one.
  4. Set boot order correctly.
    Move Windows Boot Manager (for UEFI systems) or your system disk (for Legacy) to the top of the boot priority list. Save and exit (usually F10).
  5. Load defaults if settings look corrupted.
    If the BIOS settings look scrambled or the date has reset to 2000, use 'Load Setup Defaults' or 'Load Optimised Defaults'. Then re-set the boot order and save. A CMOS battery replacement may be needed on older machines if settings keep resetting.
BIOS shows correct boot mode and drive. Windows Boot Manager is first in boot order. System restarts into Windows normally.
5

Manual BCD Edit with bcdedit Advanced

  1. Only do this if bootrec /rebuildbcd didn't fix it.
    Open Command Prompt in WinRE as before. Run bcdedit and press Enter. You'll see a list of boot entries. Look for the Windows Boot Loader entry and note its identifier (something like {current} or a long GUID).
  2. Set the correct default entry.
    If the default is pointing at the wrong entry, run: bcdedit /default {identifier} replacing {identifier} with the correct GUID from the list. According to Microsoft's official bcdedit documentation, this sets which OS entry loads at startup.
  3. Verify and restart.
    Run bcdedit again to confirm the default entry is now correct. Close Command Prompt, remove USB, restart.
BCDEdit is powerful. One wrong command can make things worse. If you're not confident, stick to Startup Repair and bootrec. That combination fixes the vast majority of Windows Boot Manager boot failed errors without touching bcdedit at all.

Still stuck after all of the above? If the drive is healthy but nothing restores the boot configuration, a clean Windows reinstall from the installation USB is the last resort. Your personal files in the Users folder can be preserved if you choose 'Keep my files' during setup. For data recovery from a drive that won't boot at all, see our guide on recovering files from a PC that won't start.

Preventing Windows Boot Manager Boot Failed

Most of these failures are preventable. Here's what actually matters, in order of importance.

Make a Windows recovery USB now. Seriously, do it today on a spare USB stick while everything is working. Download the Media Creation Tool from Microsoft, run it, and store the USB somewhere you'll find it. When Windows Boot Manager boot failed hits at 9pm before a deadline, you'll thank yourself.

Monitor drive health. Use your OEM diagnostics tool or Windows' built-in drive tools to check SMART status every few months. A drive showing reallocated sectors or pending uncorrectable errors is on its way out. Replace it before it fails completely, not after.

Be careful with partitioning tools. Tools like GParted, MiniTool Partition Wizard, and similar can wipe BCD entries or shift partition boundaries in ways that break the boot loader. If you're setting up a dual boot or resizing partitions, back up the system image first. And follow the instructions exactly.

Shut down properly. Holding the power button to force shutdown during an update is a reliable way to corrupt boot files. If Windows is stuck on an update, give it time (up to 30 minutes) before assuming it's frozen. Use a surge-protected power strip to protect against power cuts doing the same damage.

Keep system images. A full system image backup (Windows has one built in under Control Panel, Backup and Restore) means a failed drive is a restore job, not a rebuild. If you're on Windows 11, Macrium Reflect Free is worth looking at for more flexible imaging options. For a broader look at keeping your system protected, our Windows backup and recovery guide covers the full setup.

Windows Boot Manager Boot Failed: Summary

Windows Boot Manager boot failed sounds catastrophic but it's fixable in the majority of cases without losing data or reinstalling Windows. Start with the simple stuff: disconnect USB devices, check boot order, run OEM drive diagnostics. If the drive is healthy, Startup Repair from a Windows USB will fix most BCD and BOOTMGR corruption automatically. When that's not enough, bootrec.exe /fixmbr, /fixboot, /scanos, and /rebuildbcd run in sequence from the WinRE Command Prompt will handle the rest. Only reach for bcdedit if everything else has failed and you know what you're doing. Work through the tiers in order, check the drive health early, and you'll have this sorted without a reinstall.

Frequently Asked Questions

Start with Tier 1: disconnect all USB drives and external disks, check the boot order in your BIOS/UEFI boot menu, and make sure Windows Boot Manager or your system drive is first. This takes under 10 minutes and fixes a large proportion of cases.

Not always. Some PCs have a local recovery partition you can access from the boot menu. But having a Windows 10 or 11 installation USB is strongly recommended for Tier 2 and Tier 3 repairs. You can create one free from Microsoft's Media Creation Tool on another PC.

/fixmbr rewrites the Master Boot Record, which is the very first sector the firmware reads on a disk. /fixboot rewrites the boot sector on the active system partition. Both are often needed together when boot loader files are corrupted.

If your OEM diagnostics tool (HP, Lenovo, Dell etc.) reports a drive failure, or the extended disk test returns errors, replace the drive. Running bootrec or Startup Repair on a physically failing drive is a waste of time and risks further data loss.

BCDEdit is a legitimate Microsoft tool but it is easy to misconfigure. Only use it if you are comfortable at the command line and understand what each parameter does. If in doubt, stick to Startup Repair or bootrec /rebuildbcd first.