Event ID 1306 — BCD File Access and Creation

Updated: December 3, 2008

Applies To: Windows Server 2008 R2

yellow

Each boot image is represented in the Boot Configuration Data (BCD) store as an available boot loader option. The BCD store contains boot configuration parameters and controls how the operating system is started in Windows Vista and Windows Server 2008 operating systems. These parameters were previously in the Boot.ini file (in BIOS-based operating systems) or in the nonvolatile RAM (NVRAM) entries (in Extensible Firmware Interface–based operating systems).

Each boot image on the Windows Deployment Services server has a corresponding BCD file that contains a Boot Loader entry. The entry describes how to boot that particular operating system image. The BCD file contains information such as the boot device (RAMDISK), the image name (obtained from the .wim metadata), the detect HAL option, and the operating system type (Windows PE).

Event Details

Product: Windows Operating System
ID: 1306
Source: BINLSVC
Version: 6.1
Symbolic Name: W_BINL_BCD_DEFAULT_IMAGE_NOT_FOUND
Message: The default Boot Image %1 was not found for architecture %2.

Resolve

Specify a default boot image

To perform this procedure, you must either be a member of the local Administrators group or have been delegated the appropriate authority.

To specify a boot image to be selected by default:

  1. Open the Windows Deployment Services MMC snap-in.
  2. Right-click the Windows Deployment Services server, and then click Properties.
  3. On the Boot tab, insert the path to the specified boot file for each architecture.

Note: You can also set the default boot image by running the following from the command prompt: wdsutil /set-server /BootImage:<path> /Architecture:{x86 | x64 | ia64}

For more information about adding images and configuring computers, see "How to Perform Common Tasks" at http://go.microsoft.com/fwlink/?LinkId=89223.

Verify

To perform this procedure, you must either be a member of the local Administrators group or have been delegated the appropriate authority.

To verify that the BCD file has been generated correctly and is accessible:

  1. Locate the following file on the Windows Deployment Service server: RemoteInstall\Tmp\<arch>.{<GUID>}.bcd, where <arch> is x86, x64, ia64, or x86x64 and <GUID> is 32 characters. Note: By default, the RemoteInstall folder is on drive C.
  2. In the Command Prompt window, run the following command for the file you located in step 1: bcdedit.exe /enum /all /store: <Drive>:\RemoteInstall\Boot\<arch>\default.bcd. The output should contain the contents of the BCD file.
  3. Verify that the output contains entries for each of your boot images.

 

Related Management Information

BCD File Access and Creation

Windows Deployment Services

Community Additions

ADD
Show: