Share via

Event ID 1292 — 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: 1292
Source: BINLSVC
Version: 6.0
Symbolic Name: E_BINL_BCD_CREATE_WIM_BCD_FAILED
Message: An error occurred while creating the BCD store for WIM file %1.

Error Information: %2

Resolve

Ensure that the PXE provider can modify the BCD file

The Pre-Boot Execution Environment (PXE) provider must be able to create or modify the Boot Configuration Data (BCD) file for a boot image. Each boot image on the Windows Deployment Services server has a corresponding BCD file, which 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). To resolve this issue, do the following in the specified order:

  • Ensure that the boot image is valid.
  • Ensure that you have enough disk space and the necessary permissions.

Ensure that the boot image is valid

To ensure that the boot image is valid:

  1. Open the Command Prompt window.
  2. At the command prompt, run wdsutil /get-server /show:images.
  3. Ensure that all of your boot images are listed and that the information is correct.

If the metadata is valid, the events are caused by something that occurred while the BCD file was being created or modified. To resolve these issues, use the procedure in the following section to verify that you have enough disk space and that the PXE provider has the required permissions.

Ensure that you have enough disk space and the necessary permissions

To ensure that you have enough disk space and required permissions:

  1. Verify that you have at least1 MB of free disk space.
  2. Right-click the RemoteInstall folder (by default, it is located on drive C), and then click Properties.
  3. On the Security tab, make sure that **WDSServer **is set to Full control.

 

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