Knowledge Base

Windows Server - Solutions for error message: BOOTMGR is missing




This articles provides information about the "BOOTMGR is missing" error when booting a Windows Server operating system.


Table of Contents:

  1. Issue
  2. Solution
  3. Additional Information

1. Issue

The "BOOTMGR is missing" error displays shortly after the computer is turned on immediately after the POST is complete. Windows has only initially started to load when the BOOTMGR when the error message appears.



2. Solution

Method 1 : Reboot

  • The BOOTMGR error could be a generated by mistake and a reboot should be attempted first.

Method 2 : Check Optical drives/External media/Boot Order

  • Check your optical drives, USB ports, and floppy drives for media. Often times, the "BOOTMGR is missing" error will appear if the computer is trying to boot to a non-bootable disc, external drive, or floppy disk.

Method 3 : Reseat physical connections

  • Reseat all physical connections with the storage subsystem that effect the affected disk or virtual disk.

Method 4 : Perform a Windows Startup Repair

  • This should replace any missing or corrupt files, including BOOTMGR.

More information about Windows Server boot reparation:
Article SLN167714 : How to Repair the Boot Files in Windows Server 2008 or 2008 R2 if the Server Won't Boot

Method 5 : Write a new partition boot sector by using the Bootrec.exe tool

This step requires booting to the recovery console.

  • Boot to the recovery console using a Windows installation disc.
Note: On Windows Server 2008 R2 repair has been known to be more successful using a Windows 7 disc opposed to a Windows Server 2008 R2 Disc
  • From the recovery console prompt, enter bootrec /fixboot
  • The screen should show "The operation completed successfully."
  • Restart the computer.

Method 6 : Rebuild the BCD store by using the Bootrec.exe tool

If the previous method does not resolve the problem, you can rebuild the BCD store by using the Bootrec.exe tool in the Windows Recovery Environment. To do this, follow these steps:

  • Boot to the recovery console using a windows installation disc.
  • From the recovery console prompt, type Bootrec /RebuildBcd, and then press ENTER.
  • If the Bootrec.exe tool runs successfully, it presents you with an installation path of a Windows directory. To add the entry to the BCD store, type Yes. A confirmation message appears that indicates the entry was added successfully.
  • If the Bootrec.exe tool cannot locate any missing Windows installations, you must remove the BCD store, and then you must re-create it. To do this, type the following commands in the order in which they are presented. Press ENTER after each command.
    1. Bcdedit /export C:\BCD_Backup
    2. ren c:\boot\bcd bcd.old
    3. Bootrec /rebuildbcd
    4. Restart the computer.

Method 7 : Recovery using startrep.exe

  • Boot to the recovery console using a windows installation disc.
  • From the recovery console prompt, type change the drive to C: instead of X: and type the following -> sfc /scannow /offbootdir=d:\ /offwindir=d:\windows
  • Restart the computer.
Note: /offbootdir=d:\ and /offwindir=d:\windows, D: = the drive that the windows installation disc is in.
Note: The Windows install disc must be the same as the version installed for this step.​

3. Additional Information

The most common reasons for BOOTMGR errors are corrupt and misconfigured files, hard drive and OS upgrade issues, corrupt hard drive sectors, an outdated BIOS/Firmware, and damaged or loose hard drive connections.

Find more information about the OS related reasons in following Microsoft Knowledgebase article (ID = 2622803):
Windows error message "Bootmgr is missing Press Ctrl+Alt+Del to restart"


Need more help?
Find additional PowerEdge and PowerVault articles

Visit and ask for support in our Communities

Create an online support Request


Article ID: SLN248681

Last Date Modified: 10/12/2016 07:57 AM


Rate this article

Accurate
Useful
Easy to understand
Was this article helpful?
Yes No
Send us feedback
Comments cannot contain these special characters: <>()\
Sorry, our feedback system is currently down. Please try again later.

Thank you for your feedback.