Vista : Startup Troubleshooting and BCD

The Windows Vista boot process has changed from previous versions of Windows, both in the way that boot entries are stored, and the way that those boot entries are managed. This impacts support agents by changing the toolset used for resolving low level startup issues.

Objectives

• Discuss boot process changes in Windows Vista compared with Windows XP.

• Demonstrate techniques for resolving low level boot issues in Windows Vista.

Windows Vista Boot Process Overview

The Windows Vista boot process differs from Windows XP in the way that operating system is located and initialized. Startup begins with the BIOS loading the Master Boot Record (MBR) on the bootable disk, as defined by the boot order configured in the BIOS. The MBR in turn loads the Partition Boot Record (PBR) on the active partition. So far Windows Vista remains relatively unchanged.

Windows Vista is different from XP starting by the fact that the PBR code written by Windows Vista no longer looks for NTLDR. The new boot loader in Windows Vista is BOOTMGR. This is the component which loads the Boot Configuration Database (BCD), which, in turn, loads the OS loader boot application, Winload.exe. Finally, Winload.exe initializes the Windows Vista kernel. This is illustrated below.

Illustration of the Boot Process

You can think of this change in two elements:

• Two key actions performed by NTLDR in previous Windows versions have been divided between two components:

  • Bootmgr: Reads the boot configuration, including device and path locations.

  • WindowsSystem32Winload.exe: Initializes the kernel.

• The boot configuration stored by Boot.ini in previous Windows versions is now stored in a registry-based database in the following location:

  • BootBCD: The Boot Configuration Database (BCD)

Change Consequences

These changes are significant because of the impact they have:

• The boot process can be extended to support other applications, such as other operating systems, or other versions of the OS.

• Only non-version-specific components are stored in the root of the active partition. This means that theoretically Windows Vista could be installed on a machine running some future Windows version with the same boot structure, and it would not break the boot process for that future version. With legacy Windows, installing an older Windows version last causes the newer version to fail on startup. This is due to version-specific code improvements in NTLDR.

• Tool-oriented boot entries are now supported which offer maintenance options on boot. In the past Windows supported an F8 menu provided by a target operating system. This new structure makes tools available earlier in the boot process, which means that they are available even in the event that all OS-specific boot entries are damaged. The Windows Memory Diagnostic tool is provided in the boot menu in this way by default, though this menu can be used by OEMs to reference their recovery tools.

What is the Boot Configuration Database?

The Boot Configuration Database (BCD), which is also referred to as the BCD store, contains boot configuration parameters and controls how the operating system is started in Windows Vista. These parameters were previously stored in the Boot.ini file at the root of the active partition for BIOS-based PCs or in the nonvolatile RAM (NVRAM) for EFI based PCs, such as PCs based on the Itanium 64-bit processor.

The BCD is a database used by Bootmgr. It contains the functions of boot.ini and is located in the boot folder on the active partition.

The BCDEDIT.exe command line tool is provided to manage the entries in the BCD store, and is located in the WindowsSystem32 directory of the Windows Vista partition.

Directory of C:Boot

08/10/2006 02:56 PM

.

08/10/2006 02:56 PM

..

08/10/2006 02:50 PM 36,864 BCD

08/10/2006 02:50 PM 262,144 BCD.LOG

08/10/2006 06:51 PM 29,696 BCD.LOG1

08/10/2006 08:22 AM

en-US

08/10/2006 11:22 PM 219,648 fixfat.exe

08/10/2006 11:22 PM 231,936 fixntfs.exe

08/10/2006 08:22 AM

Fonts

08/10/2006 11:37 PM 381,512 memtest.exe

Boot folder contents

Boot.ini Compared with BCD

BCD eliminates the need for BOOT.INI in Windows Vista, although BOOT.INI will still be present on dual-boot systems for backwards compatibility. Because the BCD boots to the boot environment first instead of NTLDR, the location of NTLDR and the BOOT.INI is not verified unless a legacy operating system is chosen.

Source: Microsoft Windows Vista Help and Support*

From the index select: BCD What happened to the boot.ini file?

* Microsoft Windows Vista Help and Support Center

Key Points

• Discuss when and how to use BCDedit.exe

Configuration Tools

The BCD store can be modified or repaired using several tools, including:

• Control Panel, System Properties, Advanced system settings, Advanced tab, Startup and Recovery

  • Advanced system settings can be accessed directly by running SystemPropertiesAdvanced.exe

• MSConfig

• WinRE Startup Repair

• Bcdedit.exe

• Bootrec.exe

Most of these tools enable you to perform simple tasks, such as setting a boot menu timeout, set a default operating system, or configure boot options such as /SOS and /SAFEBOOT. Others are repair-oriented tools – Startup Repair and Bootrec.exe in particular, provide automated mechanisms for fixing problems in the BCD.

The command line tool Bcdedit.exe gives you the most granular control when modifying the BCD store. You can use Bcdedit to change Bootmgr options, add boot entries, delete boot entries, edit entries, import/export the BCD store, and create a new store in the event that it becomes significantly damaged. Bcdedit.exe is located in the WindowsSystem32 directory of the Windows Vista partition, and is also accessible from the command prompt in WinRE.

Boot Configuration Data Editor Frequently Asked Questions

Source: Boot Configuration Data Editor Frequently Asked Questions*

http://www.microsoft.com/technet/windowsvista/library/85cd5efe-c349-427c-b035-c2719d4af778.mspx

*Microsoft Technet

Key Points

• Where is the BCD file located in the registry?

• What are the ways that I can modify BCD?

• Can I install Windows Vista on a computer that already contains an operating system? Can I install Vista on a partition that already has an OS?

• In a multi-boot environment does modifying BCD on the pre-Windows Vista operating system modify the boot configuration?

• How to change the default operating system entry?

• How to change boot manager time-out?

• How to set the boot manager display order?

• How to create a new Windows Vista operating system entry?

• How to modify BCD when installing a previous version of Windows onto a computer running Windows Vista?

Where is the BCD Store Located?

The BCD store is a Registry hive, stored as BootBCD on the active partition. This hive is loaded, but hidden from view in regedit.exe within Windows Vista. The store is loaded to the following registry location:

HKLMBCD00000000

You can also view the store manually in WinRE by loading the hive from the Boot folder. To obtain a copy of the hive on a running system, use the following command to export a hive file for offline examination:

Bcdedit /export filename

This will export the BCD store to a file called “filename” in the current directory. Directly editing the BCD store in this way is not recommended however, and can have unexpected results.

Related Components

MSConfig

MSConfig is the preferred PSS tool for managing boot settings. This tool supports the BCD, and allows the user to enumerate all BCD objects in the system store. It also allows certain elements to be altered for each OS object, including debug settings, safe mode settings, and other options useful for troubleshooting. It cannot be used from the WinRE console however; BCDEDIT would need to be used in these cases.

BCDEdit.exe

BCDEdit is a command-line tool that can be used to manage settings in the BCD store. BCDEdit.exe is a also a replacement for the bootcfg.exe used in the Windows XP Recovery Console. However it is enhanced to allow for better scripting and to expose some of the more powerful features of BCD that bootcfg.exe didn’t expose for manipulating boot.ini. BCDEdit.exe is designed to run from within down-level operating systems and recovery environments, though it cannot be used to manage the boot.ini used by those previous versions of Windows.

Potential Issues

User receives an “Access Denied” error when running BCDEdit

Issue

I have working copy Windows XP on a different partition and the Windows Vista bootloader did not recognize it and add it as a boot option. I tried BCDEdit logged in as a user in the Administrators group, but it gives me an “Access Denied” error when I run bcdedit /create.

Resolution

You will need to run BCDEDIT from an elevated command prompt in Windows Vista.

How can I repair the BCD store?

It is strongly recommended that you create a backup of the BCD store prior to making any changes. It is possible for the BCD store to become corrupt which may cause Windows Vista to be unable to boot.

The BOOTREC.EXE command is provided for use in WinRE to repair the MBR, Boot Sector and BCD store Bootrec.exe can be run from a command prompt in WinRE and has the following commands:

• /FIXMBR: Writes a master boot record to the system partition

Bootrec.exe /FIXMBR

• /FIXBOOT: Writes a new boot sector onto the system partition

Bootrec.exe /FIXBOOT

• /SCANOS: Scans all disks for Windows installation and displays entries currently not in the BCD store

Bootrec.exe /SCANOS

• /REBUILDBCD: Scans all disks for Windows installations and allows users to choose which entries to add to the BCD store.

Bootrec.exe /REBUILDBCD

Most troubleshooting for boot issues will be done by the startup repair option of WinRE. However if the startup repair option doesn’t work, the bootrec.exe tool might prove useful.

Manually rebuilding entries in the BCD store will require that you run BCDEDIT multiple times, once for each element in the boot entry. In the example below, we provide the steps for manually adding an existing installation of Windows XP to the BCD store. This may be necessary if the user chose to install Windows XP after they installed Windows Vista. Prior to running these commands, it will be necessary to run the command “Bootsect /nt60 ALL” to repopulate the Windows Vista boot sector.

1. This first command creates the boot entry:

bcdedit /create {ntldr} /d “Windows XP Professional”

2. This command adds that boot entry to the display order for the boot menu:

bcdedit /displayorder {ntldr} /addlast

3. The new entry still lacks the pointer to the loader file for the down-level operating system. The partition pointer is set with this command:

Bcdedit /set {ntldr} device partition=c:

4. Finally, this next command sets the path to the legacy boot loader on the partition identified above:

Bcdedit /set {ntldr} path ntldr

How do I remove a legacy boot entry?

Issue

I upgraded from Windows XP to Windows Vista and I see an option in the boot menu for “Earlier version of Windows”. How do I remove this?

Resolution

The steps listed below describe the process for removing the “Earlier version of Windows” option from the boot menu. After making this change, the user’s PC should boot straight into Windows Vista without displaying the boot menu since there will now be just one entry.

1. Open an elevated command prompt.

2. Type the following command and press enter. Be sure to include the “curly braces” style brackets around “{ntldr}”.

Bcdedit /delete {ntldr} –f

This will remove the old Windows XP ntldr entry and the machine will boot directly into Vista.

User is unable to boot to Windows Vista after installing a previous version of Windows.

Issue

Windows Vista no longer starts after I installed an earlier version of the Windows operating system in a dual-boot configuration.

Resolution

For More Information, see the following article in the Microsoft Knowledge Base:
Windows Vista no longer starts after you install an earlier version of the Windows operating system in a dual-boot configuration (919529)

User receives the following error at boot – 0xC0000034

Issue

On boot you may see the following error:

File: BootBCD

Status: 0xc0000034

Info: The Windows Boot Configuration Data file is missing required information

Cause

This error indicates that the BOOTMGR entry is not present in the BCD store. This can be resolved using the following command:

Bcdedit /create {bootmgr} /d “Windows Boot Manager”

This can also indicate that the actual BCD file is missing from the drive or has been moved.

Resolution

When this is the case we can do several things to resolve the issue:

1. Boot the system into WinRE and choose the Startup Repair option, this will attempt to restore the file. Reboot the system after the command completes to verify that it worked.

2. Verify that the BCD has not been moved from the Boot folder and the the Boot folder still exists.

3. If available, restore the BCD from a backup copy.

4. Use the BOOTREC.EXE /RebuildBCD command in WinRE.

   1. If BOOTREC is successful, it will present you with an installation path to a Windows directory. To add the entry type Yes. A confirmation should be presented stating that the entry successfully completed.

User receives the following error at boot – 0xC0000098

Issue

On boot you may see the following error:

File: BootBCD

Status: 0xc0000098

Info: The Windows Boot Configuration Data file is does not contain a valid OS entry

Cause

This error indicates that there are no OS entries in the BCD.

Resolution

This can be resolved using the following command:

Bcdedit /displayorder {} /addlast

Replace “” in the command above with the GUID for the operating system entry.

User receives the following error at boot – Missing NTLDR

Issue

On boot you may encounter an error indicating that the NTLDR is missing.

Cause

This issue can be caused by any one of the following:

• The Windows Vista boot sector is in place, but both bootmgr and ntldr are missing. In the event that bootmgr is missing, the Windows Vista boot code looks for ntldr as a fallback.

• The Windows Vista boot sector is in place and you selected a Legacy OS boot entry during startup, but the entry points to a nonexistent NTLDR file.

• The legacy boot sector is in place, but the NTLDR is missing.

Resolution

You can resolve this issue by first evaluating the desired end state and proceeding from there with your troubleshooting:

1. If you wish to start Windows Vista but are receiving this error, use the following steps:

   1. Start WinRE.

   2. Run the following command to write Windows Vista boot sector code:

bootrec /fixboot

1. Verify that the bootmgr file is in place in the root directory of the active partition.

2. If the boot manager (BOOTMGR) is missing or corrupted, you can try one of the following:

   1. Run Startup Repair in WinRE

   2. Manually copy bootmgr from the Windows Vista DVD.

1. If you wish to start a previous version of Windows using the Windows Vista boot files and you see a boot entry for the legacy version, but the legacy version does not boot, you can check the following:

   1. Run the following command and ensure that the correct device and path are specified for ntldr:

Bcdedit /enum

1. If you do not see a Windows Legacy OS Loader entry when running that command, use the steps specified previously in this document to add the entry for the previous version of Windows to the BCD store.

2. Copy any missing legacy boot files to the root of the drive specified in the BCD boot entry for {NTLDR}. This includes NTLDR, NTDetect.com and Boot.ini. You may also need to construct or restore a boot.ini file if it is missing.

1. If you wish to start a previous version of Windows using the legacy boot files, use standard troubleshooting methods for that operating system. If necessary you can also use Windows Vista tools to repair the boot files:

   1. Start WinRE.

   2. Run the following command to write a Legacy boot sector:

bootsect /nt52 ALL

3. Then copy any missing legacy boot files from a backup or the original installation media to the root of the drive, including NTLDR, NTDetect.com and Boot.ini. You may also need to construct or restore a boot.ini file if it is missing.

Partition or drive changes result in the inability to boot.

Issue

How do I fix a partition or a hard drive that has been added or removed and has caused the partition/disk structure to change?

Resolution

This can be corrected by running these commands in the order shown:

1. The following command is run, with E: changed to the drive where the Vista DVD us

E:boot bootsect /nt60 ALL

2. This next command changes sets the boot device for the boot entry. As with the above command, replace Z: in the command with the drive letter where the BOOT folder is located.

bcdedit /set {GUID} device partition=Z:

Note that if you added a new hard disk to your PC, you will need to ensure that the BIOS boot order was not changed, and that the system is not looking to the new hard disk for a boot sector.

How can I change the default operating system when dual booting?

Issue

This scenario describes the necessary steps for defining which operating system will start by default when in a dual boot configuration. In most cases, the OS that was installed last will be the OS that starts unless another OS is chosen in the boot menu.

Resolution

To change the default OS to point to a previous version of Windows use one of the resolutions listed below.

Resolution 1: (Using Startup and Recovery Options)

1. Boot the system to Windows Vista

2. Click Start, right-click on Computer, and choose properties.

3. Click the Advanced system settings option on the left.

4. Select the Advanced tab.

5. Click the Settings button under Startup and Recovery

6. Under System Startup, set the Default operating system to the desired operating system and click OK.

Note: For a dual-boot system with Windows XP and Windows Vista the option will be titled “Earlier version of Windows”.

Resolution 2: (Using BCDedit.exe)

1. Boot the system to Windows Vista

2. Launch an elevated command prompt.

3. Type the following command and press enter (be sure to include the “curly-braces” style brackets around ntldr)

bcdedit /default {ntldr}

Using MSConfig to Edit Boot Entries

The System Configuration Utility (MSConfig) in Windows Vista can be accessed using the following methods.

• Click Start and type MSCONFIG in the Search box, then hit Enter.

• Click Start, All Programs, Accessories, System Tools, System Configuration.

• Press “Window Key” + R to open the Run dialog, and type MSConfig there.

When compared to BCDEDIT, MSConfig does not have the same level of functionality, but it can be far easier to use when working with a customer. With MSConfig you can change the default boot operating system, delete a boot menu item, or change the timeout display period for the boot menu.

Troubleshooting

This section provides general troubleshooting recommendation for BCD and startup in Windows Vista.

Use MSDT when applicable

You can use the Microsoft Support Diagnostics Tool (MSDT) to obtain both a copy of the customers BCD store, as well as the output of the command BCDEDIT when run from their PC. Use the setup troubleshooting mode of MSDT to gather this information.

Backup and Restore the BCD

Before making changes to BCD with BCDEDIT, it is recommended that you make a backup of the current BCD. This backup can be used to return to the current state later, in the event any problems are encountered.

Export the BCD Store

To export the current BCD store, using the following command:

bcdedit /export C:BCD_Backup

Import a Backup BCD Store

The following command restores the backup previously created backup:

bcdedit /import C:BCD_Backup

Note: Importing a backup BCD store replaces the contents of the current store. As a result, entries added after the backup was created will be removed.

How can I recover from the accidental deletion of a BCD entry?

For example, if the Windows Vista installation is deleted using the following command:

Bcdedit /delete {}

When booting after running the command above, the boot environment screen will no longer show the option to boot into Windows Vista and will either start with a Boot Manager error message, or in the case of a dual boot the PC will automatically boot to the down-level operating system.

To recover the system in this scenario, the system can be booted to the Windows Recovery Environment (WinRE). When this takes place, an error will be displayed, stating the following:

A Windows installation that is currently inaccessible has been found, would you like to repair the startup options and set this Windows installation as the default operating system?

This will attempt to repair the broken BCD entry and prompt the user to restart the PC to verify the repairs.

Resolution

If this is not successful there are other options to resolve this issue:

• Reboot the system to WinRE and use the Startup Repair tool to attempt to repair the BCD.

• Use Bootrec.exe in WinRE to repair the BCD.

• Use BCDEDIT to repair the BCD manually.

WinRE – Startup Repair

Startup Repair is an option provided in WinRE, which checks for errors on the system and attempts to repair them automatically. While this is run automatically in the event of a recorded boot failure, you can also run Startup Repair manually to detect and repair problems.

For More Information on Startup Repair, see the following topic in the Windows Vista Consumer Support Training:
Tools and Troubleshooting – Windows Recovery Environment

WinRE – Bootrec.exe

To recover from a damaged BCD store or missing boot entry you can also use Bootrec.exe. To do this, boot the system into WinRE, and use the following Bootrec command:

bootrec /rebuildbcd

This command will scan local drives for Windows installations and prompt you with each to add it to the BCD store. For each found, you will be prompted to type “Y” and press Enter to add the new entry to the boot menu.

WinRE – BCDEdit.exe

To manually repair the BCD, boot the system into WinRE and choose the Command Prompt option. At the Command Prompt use the following BCDEDIT commands to recover the Windows Vista startup option:

bcdedit /create /d “Windows Vista” /application osloader

bcdedit /enum

bcdedit /displayorder {} /addlast

bcdedit /set {} device partition=C:

bcdedit /set {} path Windowssystem32winload.exe

bcdedit /set {} systemroot Windows

bcdedit /set {} osdevice partition=c:

Note: Replace “C:” in the above commands with the correct drive letter for Windows Vista.

If a down-level operating system had been lost, the following commands would be required to recover the boot entry:

bcdedit /create {ntldr} /d “Windows XP Professional”

bcdedit /displayorder {ntldr} /addlast

bcdedit /set {ntldr} device partition=c:

bcdedit /set {ntldr} path ntldr

BCDEDIT Commands

This section describes the most common BCDEDIT command line switches that are used to read and modify information in the boot configuration database.

Before making any changes or attempting to use the commands below, run the command bcdedit /enum all to make sure that you use the correct GUID associated with the OS entry. Also use the BCDEDIT /export command to make a backup of the BCD..

Bcdedit /set

This switch sets values assigned to BCD entries. Values include the following, among others:

• Description

• Device

• Path

This command changes the text description of the legacy OS line in the boot menu. The quotation marks must be included in the command:

bcdedit /set {ntldr} description “Windows XP Professional SP2”

This command changes the text of the boot menu line for the Vista or non-Vista installation one is currently booted to, from the default “Microsoft Windows” or other description to that shown in the quotation marks:

bcdedit /set {current} description “Windows Vista”

This command changes the text of the boot menu line for any other Vista installation. One must use the GUID for that particular installation as shown when viewing the output of the “bcdedit /enum all” command:

bcdedit /set {5189b25c-5558-4bf2-bca4-289b11bd29e2} description “Other Windows Vista”

Bcdedit /default

This command sets the installation that the user is currently booted into as the default OS in the boot menu:

bcdedit /default {current}

To set the an alternate installation of Windows Vista as the default in the boot menu, first determine the GUID for that installation and then use it in the following command:

bcdedit /default {5189b25c-5558-4bf2-bca4-289b11bd29e2}

Bcdedit /displayorder

This command sets the display order of boot menu items for example:

bcdedit.exe /displayorder {ntldr} {current}

Bcdedit /timeout

This command changes the default 30 second time-out of the boot menu. To change the timeout to 15 seconds, use the following command:

bcdedit /timeout 15

Appendix

Sample BCDEDIT output

Output of a BCDEDIT /ENUM ALL command is provided below. This is the first command you should run on BCD issues to provide detail on everything that currently resides in the store. From the store output below it is apparent that two operating systems are installed on this system; also visible are the memory tester, EFI partition information (when needed), etc.

Windows Boot Manager

——————–

Identifier: {9af34534-9454-11da-a9c3-c88b61128f93}

Type: 10100002

Device: partition=D:

Path: EFIMicrosoftBootbootmgfw.efi

Description: Windows Boot Manager

Locale: en-US

Inherit options: {globalsettings}

Boot debugger: No

Default: {cbd971bf-b7b8-4885-951a-fa03044f5d71}

Timeout: 30

Windows Boot Manager

——————–

Identifier: {bootmgr}

Type: 10100002

Device: partition=D:

Description: Windows Boot Manager

Locale: en-US

Inherit options: {globalsettings}

Boot debugger: No

Default: {current}

Display order: {ntldr}

{current}

Timeout: 30

Windows Boot Loader

——————-

Identifier: {current}

Type: 10200003

Device: partition=C:

Path: Windowssystem32winload.exe

Description: Microsoft Windows

Locale: en-US

Inherit options: {bootloadersettings}

Boot debugger: No

Windows device: partition=C:

Windows root: Windows

Resume application: {9af34538-9454-11da-a9c3-c88b61128f93}

No Execute policy: OptIn

Kernel debugger: No

EMS enabled in OS: No

Resume from Hibernate

———————

Identifier: {9af34538-9454-11da-a9c3-c88b61128f93}

Type: 10200004

Device: partition=C:

Path: Windowssystem32winresume.exe

Description: Windows Resume Application

Locale: en-US

Inherit options: {resumeloadersettings}

Boot debugger: No

Hibernate data path: hiberfil.sys

Windows Memory Tester

———————

Identifier: {9af34535-9454-11da-a9c3-c88b61128f93}

Type: 10200005

Device: partition=D:

Path: bootmemtest.exe

Description: Windows Memory Diagnostic

Locale: en-US

Inherit options: {globalsettings}

Bad RAM access: Yes

Boot debugger: No

Windows Memory Tester

———————

Identifier: {memdiag}

Type: 10200005

Device: partition=D:

Path: bootmemtest.exe

Description: Windows Memory Diagnostic

Locale: en-US

Inherit options: {globalsettings}

Bad RAM access: Yes

Boot debugger: No

Windows Legacy OS Loader

————————

Identifier: {ntldr}

Type: 10300006

Device: partition=D:

Path: ntldr

Description: Legacy (pre-Longhorn) Microsoft Windows Operating System

Boot debugger: No

Windows Legacy OS Loader

————————

Identifier: {9af34536-9454-11da-a9c3-c88b61128f93}

Type: 10300006

Device: partition=D:

Path: ntldr

Description: Legacy (pre-Longhorn) Microsoft Windows Operating System

Boot debugger: No

EMS Settings Group

——————

Identifier: {emssettings}

Type: 20100000

Pre-boot EMS Enabled: Yes

Kernel Debugger Settings Group

——————————

Identifier: {dbgsettings}

Type: 20100000

Debugger type: Serial

Debugger port number: 1

Debugger baudrate: 115200

RAM Defect Group

—————-

Identifier: {badmemory}

Type: 20100000

Global Settings Group

———————

Identifier: {globalsettings}

Type: 20100000

Inherit options: {dbgsettings}

{emssettings}

{badmemory}

Boot Loader Settings Group

————————–

Identifier: {bootloadersettings}

Type: 20200003

Inherit options: {globalsettings}

Resume Loader Settings Group

—————————-

Identifier: {resumeloadersettings}

Type: 20200004

Inherit options: {globalsettings}

It is also important to know the information that BCD is currently trying to use to boot the system. This information can be gathered with the BCDEDIT /V command.

In the example below, we can see that two operating systems are installed on this system, due to the fact that two boot entries are present in the BCD. The Windows Legacy OS Loader indicates that a down-level Windows OS is currently installed to D: and is using the NTLDR file to boot. The Windows Boot Loader section shows that Windows Vista is installed to C: and is using the WINLOAD.EXE file to boot.

:

Windows Boot Manager

——————–

Identifier: {9dea862c-5cdd-4e70-acc1-f32b344d4795}

Type: 10100002

Device: partition=D:

Description: Windows Boot Manager

Locale: en-US

Inherit options: {7ea2e1ac-2e61-4728-aaa3-896d9d0a9f0e}

Boot debugger: No

Default: {9af34537-9454-11da-a9c3-c88b61128f93}

Display order: {466f5a88-0af2-4
f76-9038-095b170dc21c}

{9af34537-9454-11da-a9c3-c88b61128f93}

Timeout: 30

Windows Legacy OS Loader

————————

Identifier: {466f5a88-0af2-4f76-9038-095b170dc21c}

Type: 10300006

Device: partition=D:

Path: ntldr

Description: Legacy (pre-Longhorn) Microsoft Windows Operating System

Boot debugger: No

Windows Boot Loader

——————-

Identifier: {9af34537-9454-11da-a9c3-c88b61128f93}

Type: 10200003

Device: partition=C:

Path: Windowssystem32winload.exe

Description: Microsoft Windows

Locale: en-US

Inherit options: {6efb52bf-1766-41db-a6b3-0ee5eff72bd7}

Boot debugger: No

Windows device: partition=C:

Windows root: Windows

Resume application: {9af34538-9454-11da-a9c3-c88b61128f93}

No Execute policy: OptIn

Kernel debugger: No

EMS enabled in OS: No

The post Vista : Startup Troubleshooting and BCD appeared first on ModSNOTE.