Event ID 1288 — BCD File Access and Creation
Applies To: Windows Server 2008
.jpg)
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: | 1288 |
| Source: | BINLSVC |
| Version: | 6.0 |
| Symbolic Name: | W_BINL_BCD_WIM_NOT_BOOTABLE_FAILED |
| Message: | The Windows Imaging (WIM) file %1 does not contain any bootable images. Images in this file will be ignored. |
Resolve
Add a bootable image to the .wim file
Boot images must be marked as bootable. When you are capturing an image with ImageX, you must specify the /boot option to mark the image as bootable. For more information about ImageX command-line options, see https://go.microsoft.com/fwlink/?LinkID=104386.
To resolve this issue, do one of the following:
- If the affected image is a custom image, you will need to recreate the image by using the /boot option. For more information about how to do this, download and install the Windows Automated Installation Kit (AIK) at https://go.microsoft.com/fwlink/?LinkId=81030.
- If you accidentally added an install image as a boot image, delete the install image from the server by using the Windows Deployment Services management tools. To do this, open the MMC snap-in, right-click the image you added incorrectly, and then click Delete. (Note: To perform this procedure, you must be a member of the local Administrators group.)
Note: The name of the image that caused this issue is specified in BINLVC event 1288. To find this event, open Event Viewer, expand Custom Views, expand Server Roles, and then click Windows Deployment Services.
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.