Share via

Event ID 1301 — 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: 1301
Source: BINLSVC
Version: 6.0
Symbolic Name: E_BINL_BCD_PROCESS_WIM_BCD_FAILED
Message: An error occurred while trying to process WIM file %1.

Error Information: %2

Resolve

Verify file and registry permissions

To provide client boot services over the network, the Pre-Boot Execution Environment (PXE) provider must be able to create or modify necessary files and directories. For example, this provider must access the Boot Configuration Data (BCD) file because it 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).

If there is not enough disk space (memory) to create the BCD file, or if the PXE provider does not have read/write permissions for the parent directory or access to the registry, the provider will not be able to access these files.

To resolve this issue, do the following in the specified order:

  • Ensure that there is sufficient disk space.
  • Ensure that the provider has the necessary file permissions.
  • Ensure that the machine account has the necessary registry permissions.

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

Ensure that there is sufficient disk space

Make sure that you have at least 1 MB of free disk space. This issue may have occurred because there is not enough available disk space. If you are certain that you have sufficient disk space, use the procedure in the following section to make sure that the required file permissions have been granted.

Ensure that the provider has the necessary file permissions

To ensure that the PXE provider has the correct file permissions:

  1. Right-click the RemoteInstall folder (by default, this folder is located on drive C).
  2. On the Security tab, make sure that **WDSServer **is set to Full control.

If there is sufficient disk space and the files permissions are correct, use the procedure in the following section to ensure that the local computer account has the required registry permissions.

Ensure that the machine account has the necessary registry permissions

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

Caution: Incorrectly editing the registry might severely damage your system. Before making changes to the registry, you should back up any valued data.

To ensure that the machine account has the required registry permissions:

  1. Open Registry Editor. (Click Start, type regedit in the Start Search box, and then press ENTER.)
  2. Ensure that the following registry key exists: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WDSServer\.
  3. Verify that the machine account used by BINLSVC has permission to read from the registry. To do this, right-click the WDSServer node, click Permissions, click SYSTEM, and then make sure that Full Control is selected.

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