BCD Store BCD System Store in Visual C#.NET

Generation Data Matrix 2d barcode in Visual C#.NET BCD Store BCD System Store

a BCD store normally has at least two (and optionally, many) BCD objects:

This object contains BCD elements that per-

tain to the Windows Boot Manager, such as the entries to display in an operating system selection menu, boot tool selection menu, and time-out for the selection menus. The Windows Boot Manager object and its associated elements serve essentially the same purpose as the [boot loader] section of a Boot.ini file. a store can optionally have multiple instances of the Windows Boot Manager. However, only one of them can be represented by the Windows Boot Manager well-known globally unique identifier (GUID). You can use the GUID s alias, {bootmgr}, to manipulate a store with BCDEdit.

At least one and optionally several Windows Boot loader objects Stores contain one instance of this object for each version or configuration of Windows Vista, Windows Server 2008, or Windows 7 that is installed on the system. These objects contain BCD elements that are used when loading Windows or during Windows initialization such as no-execute (NX) page protection policy, physical address extension (paE) policy, and kernel debugger settings. Each object and its

associated elements serve essentially the same purpose as one of the lines in the [operating systems] section of Boot.ini. When a computer is booted into Windows, the alias {current} represents the associated boot loader object. When manipulating a store with BCDEdit, the default boot loader object has the alias {default}.

The {ntldr} object describes the loca-

tion of Ntldr, which you can execute to boot Windows Xp or earlier versions of Windows. This object is required only if the system includes versions of Windows that are earlier than Windows Vista. It is possible to have multiple instances of objects that describe Ntldr. However, as with the Windows Boot Manager, only one instance can be represented by the {ntldr} well-known GUID alias. You can use the GUID s alias, {ntldr}, to manipulate a store with BCDEdit.

perform other boot-related operations. One example is the Windows Memory Tester, which runs memory diagnostics.

Data in Windows Vista at http://www.microsoft.com/whdc/system/platform /firmware/bcd.mspx, and read Boot Configuration Data Editor Frequently asked Questions at http://technet.microsoft.com/en-us/library/cc721886.aspx.

Windows Vista and Windows 7 replace the Recovery Console troubleshooting tool with the new System Recovery tool (part of WinRE) . Typically, you will start the tool by pressing F8 before starting Windows and then choosing Repair Your Computer from the Advanced Boot Options screen . If that choice is not available because the hard disk has failed, you can start the tool by starting from the Windows 7 DVD and then clicking Repair Your Computer (after configuring the language options) . This loads a specialized version of Windows Preinstallation Environment (Windows PE) and then displays the System Recovery tool . For step-by-step instructions on how to load the System Recovery tools, see the section titled How to Start the System Recovery Tools later in this chapter . The System Recovery tools provide access to the following tools:

Startup Repair The Startup Repair tool can solve many common startup problems automatically . Startup Repair performs an exhaustive analysis to diagnose your startup problems, including analyzing boot sectors, the Boot Manager, disk configuration, disk integrity, BCD registry file integrity, system file integrity, registry integrity, boot logs, and event logs . It will then attempt to solve the problem, which may involve repairing configuration files, solving simple disk problems, replacing missing system files, or running System Restore to return the computer to an earlier state . Because Startup Repair performs these tasks automatically, you can solve startup problems much faster than performing the analysis and repair manually .