Event ID 1289 — BCD File Access and Creation

  • Article

Applies To: Windows Server 2008

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: 1289
Source: BINLSVC
Version: 6.0
Symbolic Name: E_BINL_BCD_WIM_ARCH_MISMATCH
Message: An error occurred while enumerating boot images. The architecture of an image in the WIM file %1 does not match the architecture of the directory %2. Images in this file will be ignored.

Resolve

Add the .wim file to the correct directory

Boot images must be located in the appropriate directories for their architecture. To add a boot image to the correct architecture, you must delete it from the Windows Deployment Services server and then add it back in the correct directory.

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

To delete the image and then add it again:

  1. Open the Windows Deployment Services MMC snap-in.
  2. Click the Boot Images node.
  3. Right-click the boot image, and then click Delete.  
  4. Right-click the Boot Images node, and then click Add Boot Image.
  5. Follow the instructions in the wizard.

For more information, see "How to Perform Common Tasks" at https://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.

 

BCD File Access and Creation

Windows Deployment Services