You are here: Windows Bare Metal Protection > Windows image-based bare metal recovery > Additional considerations for Windows imaged-based bare metal > When a system does not boot following an image-based restore

When a system does not boot following an image-based restore

This section is specific to WinPE 2.0 clients that fail to reboot with the following symptoms after a bare metal restore:

After completion of the BIOS post routines, the system remains at a blank console screen without attempting to boot from any internal hard drive.
After completion of the BIOS post routines, the boot procedure fails with a message similar to BOOTMGR missing.

In these cases, the probable cause of the boot failure is that the Windows BOOTMGR and Boot Configuration Database (BCD) were not restored during the bare metal restore. By default, the Windows installer places these components into a small partition separate from the partition that contains the Windows system. If the server contains multiple internal hard drives, the Windows installer may place this partition on a disk different from the Windows system. Below is a configuration where this is the case:

The Windows system partition C:\Windows is on disk 0 and the Windows BOOTMGR has been installed on disk 3 in a partition named System Reserved. The partition containing C:\Windows is not marked as Active and the System Reserved partition on disk 3 is marked Active. An Active partition is a bootable partition. Therefore, in this configuration, a bare metal backup only backs up the partition containing C:\Windows. The System Reserved partition containing the Windows BOOTMGR is not backed-up since it is on a separate physical disk.

In a configuration where the Windows system partition and the BOOTMGR partition are on the same physical disk, a bare metal backup and restore completes successfully, since both partitions are backed up and restored together.

The following procedure allows the Windows BOOTMGR configuration to be recovered after a bare metal restore so that the server will boot properly.