Event ID 1287 — BCD File Access and Creation
Applies To: Windows Server 2008 R2
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: | 1287 |
Source: | BINLSVC |
Version: | 6.1 |
Symbolic Name: | E_BINL_BCD_ENUM_FAILED |
Message: | An error occurred while trying to enumerate Boot Images from directory %1 for architecture %2. Error Information: %3 |
Resolve
Reinitialize the server
Windows Deployment Services relies on the RemoteInstall folder for configuration information and access to images. If the RemoteInstall folder is missing files, Windows Deployment Services will fail. To resolve this issue, use the following procedure to reinitialize the server.
To perform these procedures, you must either be a member of the local Administrators group or have been delegated the appropriate authority.
To reinitialize the server:
- Open the Command Prompt window.
- At the command prompt, run wdsutil /uninitialize-server.
- At the command prompt, run wdsutil /initialize-server /reminst:<path>,** **where <path> is the path where you would like the RemoteInstall folder to be located.
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:
- 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.
- 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.
- Verify that the output contains entries for each of your boot images.