From Wikipedia, the free encyclopedia - View original article
|This article needs additional citations for verification. (May 2010)|
The startup process of Windows Vista, Windows Server 2008 and their successors differs from that of previous versions of Windows. (In this article, unless otherwise specified, what is said about "Windows Vista" also applies to all these operating systems.) For Windows Vista, the boot sector loads the Windows Boot Manager (a file named BOOTMGR on either the system or the boot partition), accesses the Boot Configuration Data store and uses the information to load the operating system.
Boot Configuration Data are stored in a data file that has the same format as the Windows Registry hives and is eventually loaded at registry key [HKEY_LOCAL_MACHINE\BCD00000]. The file is located either on the EFI System Partition (on machines that use Extensible Firmware Interface firmware) or in \Boot\Bcd on the system volume (on machines that use IBM PC compatible firmware).
Boot Configuration Data may be altered using a command-line tool (bcdedit.exe), using Registry Editor (regedit.exe), using Windows Management Instrumentation, or with third-party tools such as EasyBCD, BOOTICE, or Visual BCD Editor.
Boot Configuration Data contain the menu entries that are presented by the Windows Boot Manager, just as boot.ini contained the menu entries that were presented by NTLDR. These menu entries can include:
Boot Configuration Data allows for third-party integration, so anyone can implement tools like diagnostics or recovery options.
The Windows Boot Manager invokes winload.exe—the operating system boot loader—to load the operating system kernel executive (ntoskrnl.exe) and core device drivers. In that respect, winload.exe is functionally equivalent to the operating system loader function of NTLDR in prior versions of Windows NT.
|This operating system–related article is a stub. You can help Wikipedia by expanding it.|
|This Microsoft Windows article is a stub. You can help Wikipedia by expanding it.|