BCDEDIT - How to Use

How to Use the BCDEDIT Command Line Tool​

   Information

This will show you how to use BCDEDIT in the command prompt and avoid the need of third party applications like EasyBCD.

   Note

Bcdedit is a really powerful tool that Windows Vista and Windows 7 uses to manage the boot loader entries.

BCDEDIT needs a boot manager to boot your system.



A boot manager is a file that contains necessary information that instruct the system how to boot/start an operating system.

• Windows 7 and Vista boot manager file is \bootmgr
• Windows XP boot manager file is \ntldr

BCDEDIT can support other boot managers too, like grub for linux. You just have to place the boot file on the root of the boot manager partition. e.g. \grldr and you have a grub boot loader enabled.

Bcdedit edits a file called bcd , which is located in Windows 7's hidden partition under \boot\bcd.
In Vista, its located under C:\boot\bcd.

   Warning

You must be logged on in an administrator account to be able to do this tutorial.

To Use bcdedit:
1. Open an elevated command prompt.

2. Type bcdedit and press enter.
NOTE: By typing just bcdedit you just list your boot entries.


A boot entry consists of 4 main elements:
1. Identifier
The identifier is how the system has named the boot entry.
2. Device
The device is the drive or virtual image that the system will use to boot the boot entry.
3. Path
The path is the location on the device where the bootloader file is found.
4. Description
The description is the friendly name we give to our boot entry, e.g. "Windows 7"
You see next to the identifiers their UUIDs in {}. The UUID is the unique codename that the system gives to each boot entry and cannot be changed.

The standard identifier UUIDs are explained below:
{bootmgr} = the boot manager
{current} = the OS you selected to boot at startup.
{default} = the default OS selected to boot the PC.
{ntldr} = Windows Legacy OS Loader (for windows xp)
there are others like {memdiag} or {ramdisk} but they can't be of much use right now.

   Warning

IMPORTANT: make a backup of your bcd file first. To do that, type:

bcdedit /export C:\SAVEDBCD

This will create a file c:\savebcd which is your boot entry backup.
If you mess up, you can always undo changes by:

bcdedit /import c:\savedbcd

Now to see how we can control the above entries, here are some examples:
bcdedit /set {current} description "My edited Windows Boot Entry"
NOTE: This changes the title of the boot menu entry "{current}".

bcdedit /set {ntldr} device partition=E:
NOTE: This tells bcd that Windows XP partition is drive E:

bcdedit /set {ntldr} path \ntldr
NOTE: This tells bcd that the ntldr file which is the winxp bootloader is on root folder "\" (of drive e: as stated above)

bcdedit /displayorder {ntldr} /addfirst
NOTE: This places Windows XP as the first OS on the menu list.

bcdedit /default {ntldr}
NOTE: This places Windows XP as the default OS to boot first with.

bcdedit /displayorder {33342343-3424-2342342342-2344} /addlast
NOTE: This tells bcd that the boot entry with UUID 3334... should be the last entry on the menu.
You can copy your existing VISTA or W7 boot entry to another identical. Then you can change settings on the new entry to experiment. You will always have the first entry available, so it's safe to play with.
bcdedit /copy {current} /d "New W7 boot entry I just copied!"
this will give you a line:
NOTE: The entry was successfully copied to {4c21825f-e04b-11dd-b760-00195b61617a}. The {4c21825f-e04b-11dd-b760-00195b61617a} is the UUID of the new entry that the system just created. Yours will be different than mine! This is its identifier and you should use this to address that entry. Example:

bcdedit /set {4c21825f-e04b-11dd-b760-00195b61617a} numpoc 2
NOTE: This adds the 2 CPU Core support during boot, like you do in msconfig.

bcdedit /deletevalue {4c21825f-e04b-11dd-b760-00195b61617a} numproc
NOTE: This deletes the numproc parameter from entry {4c21825f....}

bcdedit /delete {4c21825f-e04b-11dd-b760-00195b61617a}
NOTE: This deletes the boot entry {4c21825f....} completely. In order to delete an {ntldr} entry, you must use the /f switch to force deletion: bcdedit /delete {ntldr} /f

You can always type just bcdedit to see your current settings.

What else can I do with BCDEDIT?

You can use BCDEDIT to alter any boot parameter , like you would in msconfig, only more. BCDEDIT works from booting with installation dvd too, so it can be handy for recovery purposes.
bcdedit /timeout 5
NOTE: This sets the wait-to-select-OS menu timeout at startup to 5 seconds . You will notice that I didn't give a UUID above. If you omit the UUID, it applies automatically to the relavant UUID. So: bcdedit /timeout 5 is identical to bcdedit /set {bootmgr} timeout 5
Some more advanced examples:
bcdedit /set {current} detecthal yes
bcdedit /set {current} detecthal no
NOTE: The above commands sets the detecthal to yes or no for entry {current}
To create a new boot entry to load Windows XP from a partition on your disk:
NOTE: The example below uses F: as the Windows XP partition. Replace with your xp drive letter.
bcdedit /create {ntldr} /d "Windows XP"

bcdedit /set {ntldr} device partition=F:

bcdedit /set {ntldr} path \ntldr

bcdedit /displayorder {ntldr} /addlast

   Note

Final note: BCDEDIT works from installation boot dvd too. If you mess up with a setting and you cannot boot, just boot from DVD and enter Repair Computer, then go to command prompt and there you go. You can play again with bcdedit to restore your system back.

Related Tutorials

---

How to Change the OS Name in Windows Boot Manager

 

[edioilha]

Thanx for your reply!!

Is there any method to do that in diferent hard drives insted of diferent Partitions? without installing windows 7 after. I have Windows 7 installed in the first one Hard(500gb) drive and Windows xp in the second one Hard drive(160gb), not just partitions. I tried to setup with easyBCD but it shows me C:, D: and Boot options, not Disc0, Disc1 like when you go to Linux Tab options.

Linux Tab

Windows Tab

EasyBCD View Settings Button

EasyBCD View Settings

Thx a lot

EdioIlha

@theog
Thx a lot. Solved using EasyBcd2.0Beta, It copies the Netedetect and NTLDR to 200mb Windows 7 Partition(Just for who whants to know).

Thx
EdioIlha

 

[Neophile]

Resetting

Hello limneos,

Very good tutorial!

I want to reset the place where the BCD file should be. On your example on point 2, we can read under the Windows Boot Manager title:

Windows Boot Manager
--------------------
identifier . . . . . . . . . {bootmgr}
device . . . . . . . . . . Partition=G:
path . . . . . . . . . . . . \bootmgr
description . . . . . . . . Windows Boot Manager
locale . . . . . . . . . . . .en-US
inherit . . . . . . . . . . . <globalsettings>
default . . . . . . . . . . .{default}
resumeobject . . . . . . {xxxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx}
displayorder . . . . . . . {default}

I can change settings for the partitions under any Windows Boot Loader title, but not for these ones. I tried with VistaBootPROO, but couldn't change it either.

Can you tell me please, how do I have to do to change the setting that I marked in bold? Can I edit the BCD file directly at C:\Boot\BCD? Is this file editable in the Notepad or the DOS Editor? I cannot risk to do it without being sure, or the PC will not boot.

 

[Anak]

Could an incorrect entry in BCDEDIT cause startup to stutter, stop, and then restart again to a point where it asks:

Do you want to startup repair, that finds no wrong then finishes booting into the OS.
Or
Do you want to load windows normally, and when you say yes it also finishes booting to the OS.

In either case win runs fine until the next boot.
http://www.sevenforums.com/100352-cpu-stress-test-prime95.html

 

[slade]

Followed your bcdedit instructions for booting to XP and all looks good except when XP is selected from boot menu it just reboots to the boot menu again and must select Windows 7. I'm thinking your instructions only work if Windows 7 and haveing XP installed on the same hard drive? If this is true how to you point the path to XP on a seperate hard drive? Thanks for your tutorial on bcdedit. Also, how would you do that with DOS?

 

[d3u]

I used easybcd to set linux as the default and set timeout to 0s... now i cant boot into windows 7.. i tried using the "bcdedit.exe /timeout" from command prompt in the recovery menu from the boot disk but that is not working... any ideas?????

 

[boyans]

bcdedit /timeout 15 - should do.

If not, just 'bcdedit' <enter> and post the output.

 

[d3u]

Windows Boot Manager

identifier {default}
device partition=G:
path \windows\system32\winload.exe
description Windows 7
locale en-us
inherit {boot loader settings}
osdevice partition=G:
systemroot \Windows
resumeobject {a495e948-de35-11df-8a10-ee14ee42bdb8}
nx Optln
detecthal Yes

Windows Boot Loader

identifier {a495e94a-de35-11df-8a10-ee14ee42bdb8}
device partition=D:
path \Windows\System32\winload.exe
description Windows7 Ultimate (recovered)
locale en-us
osdevice partition=D:
systemroot \Windows

--that's what i got

 

[boyans]

d3u
The output of bcdedit says that there are two installs of win 7 - on G: and on D:
but it seems incomplete - either your bootmanager entry is missing or you didn't post the whole output of bcdedit.

Try "bcdedit >a.txt" and then copy-paste the contents of a.txt.

Also - which partition is active? where is linux installed ?

You could try on the command line: "diskmgmt.msc" (OS disk management) and then post the picture.

 

[sangean99]

Hi!

How can I configure it so that it wont offer a recovery option but starts windows normally? Or if offers then at least how can I configure it so that the "Start Windows normally" will be the default one in the list?

 

[boyans]

sangean99,


The default choice for the boot menu is in stored in "BCD-bootmgr-DefaultObject".

There is a utility called "Visual BCD Editor" - can be found here -> Free Windows BCD Editor - Windows 7 and Vista

This utility offers the full functionality of 'bcdedit' in an explorer like GUI. Moreover it is the first GUI utility to implement the full functionality of 'bcdedit'.

You can set your default loader choice by selecting the loader in the tree-view to the left, then click on the 'object' tab and in the tab click 'Set as Default Loader' button.

You can delete a loader by selecting the loader in the tree-view, right click, delete, confirm.

You can delete the menu entry for a loader by selecting {bootmgr} in the tree-view, then in Elements-view select 'DisplayOrder' and dbl-click. In the window that pops-up select the loader entry you want to delete, click on 'Delete' and then OK.

Success.

 

[paul1149]

BCDEdit not recognized

I'm on Win7 Home Premium 64b, as an administrator. In a command window I keep getting:

'bcdedit' is not recognized as an internal or external command,
operable program or batch file.

Is this a Pro tool?

 

[Dwarf]

Strange. You should be able to access that no matter which edition of Windows 7 you have. Check to see if that file exists on your system. It is located in C:\Windows\System32\bcdedit.exe

 

[paul1149]

Yes, it is there. Here's a path copy: C:\Windows\System32\bcdedit.exe. I just tried the full path in the command window, and I tried the full file name. Nothing. I definitely am the administrator here.

I had another odd command window occurrence yesterday. There was a file (rstrui.exe - system restore) that I could plainly see in Explorer, but no DIR command, with Archive switches, would show it in the command window. Let me see if that's happening here too...

Indeed, this seems to be the problem. Here's the output:

C:\Windows\System32>dir bc*

 Directory of C:\Windows\System32
07/13/2009  08:11 PM            80,896 bcrypt.dll
07/13/2009  08:17 PM           249,680 bcryptprimitives.dll
               2 File(s)        330,576 bytes
               0 Dir(s)  146,007,564,288 bytes free

C:\Windows\System32>dir /a:s bc*
 Directory of C:\Windows\System32

File Not Found

C:\Windows\System32>dir /a:h bc*
 Directory of C:\Windows\System32

File Not Found

C:\Windows\System32>

For some reason my command window is not seeing system files.

 

[Dwarf]

Very strange. This is what I get:

 

[paul1149]

Ok, here's my problem. I just opened an elevated Command Window, and now I can see the system file without even using the a:s switch, just as you can. I don't understand why I need to take that step, however, since I am an administrator (and I just double-checked that). I've never had any problem doing anything via the command window before yesterday.

Thanks,
p.

 

[Dwarf]

So you can now access the file?

This is to do with privileges, and is a good reason for not disabling UAC. Although you may be running as an Administrator, you are only running with standard privileges. In order to run as a true Administrator, you need to elevate.

Think of this analogy. You and several others work in an office (representing standard privileges), inside which there is a locked cupboard (representing elevated privileges). Everyone has a key to get into the office, but only you (as an Administrator) have a key for the locked cupboard. If you wish to access the cupboard, you can simply unlock it (this is the equivalent of confirming that you want to run in elevated mode). For the others, who do not have the key, they need to ask you first (equivalent to entering a name and password of an administrative account when prompted).

 

[paul1149]

Yes, I have command line access to the file now. What I don't understand is that I've had the machine for three months and have done countless installations and work under the hood, including via the command line, and never once did I have to elevate the window. And I've changed nothing in privileges in all that time, as I'm aware.

I wonder how this affects the command window in Safe Mode. That is where I would want to invoke System Restore in a dire emergency. There must be a way to elevate the window there too.

IAC, thanks for your help.

p.

 

[mjf]

I suppose it depends on the levels to which you can muck the system up. You can do a fair amount of mucking up with bcdedit. There is a level above elevated command prompt (hidden administrator) where you can do even more mucking up or fix things of course.

 

[tyee]

Greetings
First post here! I have installed a dual boot with WinXP and Win7 and it's working fine. I want to backup my BCD using bcdedit. I start my Win7 install DVD. Hit Shift F10 to get command prompt, enter bcdedit and I get that response that the file cannot be found. This is with the boot DVD!! Shouldn't we be at elevated prompt with the DVD?

When I was setting up that dual boot a few weeks ago I was using bcdedit just fine!

 

[tyee]

Well, now I am in big trouble. I tried imaging my main HD to external drive and it worked. Tried to boot from it into WinXP and it worked. Tried to boot into Win7 didn't work. I wanted to try another imaging program but things got so confusing, I had more than one bootable HD attached at once and now I can't get into any windows system. It says ntldr missing. I've disconnected all other drives from the machine and I've started the Win7 install disk to repair. I entered the command mode and entered "bootsect /nt52 c: /force /mbr" just to get the WinXP part working again and now it boots. When I get to the blue screen to sign on, there is no sign on button to click to enter my password at all. Nothing happens, can't click anything.

So...I started up the WinXP install CD, got into the recovery console, it found the c:\windows partition, but now wants the admin password which I type what I'm using currently and it doesn't take. Now what?? Can I somehow forcibly reset the admin password. I'm stuck.