Computer Performance, Microsoft Windows Vista


Windows Vista - BCD (Boot Configuration Data)

Windows Vista - BCD (Boot Configuration Data)

Boot.ini really will be the last of the .ini files.  In Vista, Boot.ini is superseded by the BCD (Boot configuration data).  While the acronym BCD is rather anonymous, Boot Configuration Data is a wonderfully descriptive expression, more importantly, it gives you control of what should happen when Vista starts.

Naturally BCD supports both BIOS and Extensible Firmware Interface (EFI) machines.  However, I cannot help wondering if the new EFI has prompted Microsoft to finally abandon boot.ini in favour of BCD.

Trap: Before launching CMD, right click CMD and select, RunAs, administrator.  To get a handle on BCD type: bcdedit /? at the command prompt.  This command fires up bcdedit.exe which is stored in the %systemroot%\system32 folder.

Bcdedit is a comprehensive utility with numerous switches, here is the information displayed by the simple switch: bcdedit /enum.

 

Windows Boot Manager
--------------------
Identifier: {bootmgr}
Type: 10100002
Device: partition=C:
Description: Windows Boot Manager
Locale: en-US
Inherit options: {globalsettings}
Boot debugger: No
Default: {current}
Display order: {current}
Timeout: 30

Windows Boot Loader
-------------------
Identifier: {current}
Type: 10200003
Device: partition=C:
Path: \Windows\system32\winload.exe
Description: Microsoft Windows
Locale: en-US
Inherit options: {bootloadersettings}
Boot debugger: No
Windows device: partition=C:
Windows root: \Windows
Resume application: {224b014c-a08e-11da-b308-ed83a3b7e795}
No Execute policy: OptIn
No integrity checks: Yes
Kernel debugger: No
EMS enabled in OS: No

 

 

/enum all /v

With the 'all' and the verbose (/v) switches you can retrieve hex information about the various parameters for example:

Output from the above command.

 

Windows Boot Manager
--------------------
Identifier: {224b0148-a08e-11da-b308-ed83a3b7e795}
Type: 10100002
Device: partition=C:
Path: \EFI\Microsoft\Boot\bootmgfw.efi
Description: Windows Boot Manager
Locale: en-US
Inherit options: {7ea2e1ac-2e61-4728-aaa3-896d9d0a9f0e}
Boot debugger: No
Default: {cbd971bf-b7b8-4885-951a-fa03044f5d71}
Timeout: 30

Windows Boot Manager
--------------------
Identifier: {9dea862c-5cdd-4e70-acc1-f32b344d4795}
Type: 10100002
Device: partition=C:
Description: Windows Boot Manager
Locale: en-US
Inherit options: {7ea2e1ac-2e61-4728-aaa3-896d9d0a9f0e}
Boot debugger: No
Default: {224b014b-a08e-11da-b308-ed83a3b7e795}
Display order: {224b014b-a08e-11da-b308-ed83a3b7e795}
Timeout: 30

Windows Boot Loader
-------------------
Identifier: {224b014b-a08e-11da-b308-ed83a3b7e795}
Type: 10200003
Device: partition=C:
Path: \Windows\system32\winload.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: {224b014c-a08e-11da-b308-ed83a3b7e795}
No Execute policy: OptIn
No integrity checks: Yes
Kernel debugger: No
EMS enabled in OS: No
 

 

Default: {224b014b-a08e-11da-b308-ed83a3b7e795}

Editing BCD Settings

Making change to BCD is possible, but beware, the syntax is tricky because you have to be accurate with the hex code.

Here is an easy change:
bcdedit /timeout 7

Here is an example of a tricky change
bcdedit /bootsequence {802d5e32-0784-11da-bd33-000476eba25f}

BCD's help will point you to the correct default codes.  For example type at the command prompt:
bcdedit /enum bootmgr

.

Identifying then changing the Default Boot Manager

I have to say that I am not finding bcdedit easy to use.  Here is an example where you examine the setting for the default boot manager.

bcdedit /enum all /v

Part of the output from the above command.

 

Windows Boot Manager
--------------------
Identifier: {224b0148-a08e-11da-b308-ed83a3b7e795}
Type: 10100002
Device: partition=C:
Path: \EFI\Microsoft\Boot\bootmgfw.efi
Description: Windows Boot Manager
Locale: en-US
Inherit options: {7ea2e1ac-2e61-4728-aaa3-896d9d0a9f0e}
Boot debugger: No
Default: {cbd971bf-b7b8-4885-951a-fa03044f5d71}
Timeout: 30

 

 

Amongst the entries for Windows Boot Manager is:

Default: {cbd971bf-b7b8-4885-951a-fa03044f5d71}   (Meaning Vista)

If you wanted to change it to an XP Boot Manager then type

bcdedit /default {466f5a88-0af2-4f76-9038-095b170dc21c}  (Meaning XP)

To be fair to Vista, perhaps it's because I am not familiar with these hex numbers that I have difficulty getting in tune with bcdedit.

Summary of BCD

In Windows Vista, BCD and bcdedit replace the boot.ini found in XP and older Windows operating systems.


TrainSignal - Recommended Vista Training VideosTrain Signal has just released their New Windows Vista Training Course.  As an MCT trainer, I am a huge advocate of Train Signal’s products.  What impresses is me is that they demonstrate everything that they teach and they stay away from traditional 'lecture-style' training.  If you are looking for a complete DETAILED coverage of Windows Vista, then I highly recommend that you give this course a try.  I have reviewed their 18 hours of videos myself, and I guarantee that you will not be disappointed!

Watch a Vista Training Video Demo.


Configuring Windows Vista Topics:

 

     Vista Tools and Extras

 

   Tweak the Registry ebook

Download your Tweak the Registry Ebook for only $6.45

This ebook will explain the workings of the registry.  I thoroughly enjoy tweaking the registry, and I want to distill the best of my experiences and pass them on to you.

Each registry tweak has two aims; to solve a specific problem, and to provide general learning points, which help you to master regedit. 

Over 60 pages ebook and PDF format

 

^


Google
WebComputerperformance.co.uk

GFi Events Manager

Guy Recommends: GFi EventsManager

Here is a solution to monitor, manage and archive thousands of events that are generated by devices across your entire network.  Get your free evaluation copy of GFI EventsManager.