Event ID 1298 — BCD File Access and Creation

Updated: December 3, 2008

Applies To: Windows Server 2008 R2

red

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: 1298
Source: BINLSVC
Version: 6.1
Symbolic Name: E_BINL_BCD_DEVICE_RESTAGED_IMAGE_NOT_FOUND
Message: An error occurred while locating the specified Boot Image %3 for the device with MAC address %1 and GUID %2. As a result the device will not be serviced.

Resolve

Associate the correct boot image

Windows Deployment Services must be able to access the boot image that is associated with the client computer. To resolve this issue, ensure that the client computer is prestaged with the correct image and that the image has been uploaded to the Windows Deployment Services image store.

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

To ensure that the associated boot image is correct:

  1. Open the Command Prompt window.
  2. Using the globally unique identifier (GUID) specified in the event log message, run the following command to see which boot image is associated with the client: WDSUTIL /get-device /id:<MAC or GUID>  Note: The name of the image and client GUID that caused this issue is specified in BINLVC event 1298. To find this event, open Event Viewer, expand Custom Views, expand Server Roles, and then click Windows Deployment Services.
  3. If you need to change the boot image, run the wdsutil /get-allimages /show:boot command to see a list of the boot images.
  4. To specify another boot image for the device, run the WDSUTIL /set-device /device:<name> /bootprogram:<path> command, where <path> is the relative path to the specified boot program from the shared RemoteInstall folder. 

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: