Event ID 1290 — 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: | 1290 |
| Source: | BINLSVC |
| Version: | 6.0 |
| Symbolic Name: | W_BINL_BCD_WIM_NAME_MISSING |
| Message: | An image in the WIM file %1 does not have an image name. The Windows Deployment Services server will use the image filename instead. |
Resolve
Specify an image name
You can specify a friendly image name for an image, if you want. Otherwise, the image file name will be used.
To perform this procedure, you must either be a member of the local Administrators group or have been delegated the appropriate authority.
To specify an image name:
- Open the Windows Deployment Services MMC snap-in.
- Right-click the image you want to name, and then click Properties.
- Type the name and description you want for the image.
Note: The name of the image that caused this issue is specified in BINLVC event 1290. To find this event, open Event Viewer, expand Custom Views, expand Server Roles, and then click Windows Deployment Services.
For more information about adding images and configuring computers, 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:
- 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.