locked
FTI Making Changes to the Boot Configuration Data RRS feed

  • Question

  • Making Changes to the Boot Configuration Data

    Before making any changes or attempting to use the commands below, run the command bcdedit or bcdedit /enum all to make sure that you use the correct GUID tag. These have been seen to change from build to build and it may be necessary to use {ntldr} instead of {legacy} for example.

    bcdedit /set {legacy} Description “Windows XP Professional SP2” Changes the text description of the “Legacy” OS line in the boot menu. The quotation marks must be included in the command

    bcdedit /set {current} description "Windows Vista Build 5270 x86" 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 {5189b25c-5558-4bf2-bca4-289b11bd29e2} description “Windows Vista Build 5270 x64” 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 one runs the bcdedit or bcdedit /enum all command

    bcdedit /default {current} Sets the current Windows installation one is booted to as the default Windows boot OS

    bcdedit /default {5189b25c-5558-4bf2-bca4-289b11bd29e2} Sets the referenced Windows OS as the {default} Windows boot OS

    bcdedit /default {legacy} Sets the legacy (Windows XP) OS as {default} boot item

    bcdedit /displayorder Sets the display order of boot menu items for example:

    bcdedit.exe /displayorder {legacy} {current}

    bcdedit /timeout 15 Changes the default 30 second time-out of the boot menu to 15 seconds or any other value inserted.

    Thursday, June 15, 2006 8:15 PM

Answers

  • Jay, your post was extremely helpful. Thanks for very complete instructions on using BCD.

    One minor note, your description references for the Vista build number are using 5270, and we're up to 5384. This of course doesn't make any of your post invalid, but it's more informational if someone is just copying these commands and need to represent their build numbers correctly.

    Thanks again.
    Friday, June 23, 2006 6:06 PM