Disclaimer: It's very likely that I have NO idea what I'm talking about. This is a blog, not a technical article or official anything. Listening to me may well kill your pet kitten and render both your computer and you personally unbootable. Run away in fear as this is all completely useless information.
I paved (reformatted and started over) my main machine, formerly named QUADPOWER, now QUADPOWER7 to use the new Windows 7 RC a few days ago. I went through the process, but wasn't really paying attention. I have a tendency to just Next>Next>Next>Finish my way through most wizards. This will likely be the death of me at some point.
Anyway, my system is a little non-standard and I had at some point a year ago switched hard drives around to make the faster one be my boot drive. I did this by changing the boot order in the BIOs.
Fast forward a bit, and today I wanted to format my DATA drive - my D: drive - and the format applet said "not so fast."
I opened up Disk Management and it showed me this...
Yikes! See how my D: drive is Disk 0 and is marked as System, but my C: drive is Disk 1 and marked as Boot? That means that the Boot Configuration Data (BCD) is on my D: drive. I checked my BIOs, and it turned out, in fact, that I had told it to boot of that drive. However, I'd installed Windows to the other drive and got myself into this situation:
- Disk 0 - D: Drive with BCD
- Disk 1 - C: Drive with C:\windows and other booty
I couldn't format D: because it was what I booted off of. Poop.
I searched around and found all sorts of hard and scary descriptions of how to fix this. Basically it boiled down to:
Approach 1: Nuclear Option. Wipe and Start Over.
Approach 2: Copy the Hidden/System Boot Manager and Boot Folder over to the C: drive and run a tool called BCDEdit to move things around in 12 short steps. ;)
This was a scary prospect for me, because from my point of view, while this was a fairly advanced operation, I just wanted to switch where the boot info comes from.
Turns out there is a new (profoundly advanced, you have been warned) command line tool called BCDBoot.
C:\windows\system32>bcdboot /?
Bcdboot - Bcd boot file creation and repair tool.
The bcdboot.exe command-line tool is used to copy critical boot files to the
system partition and to create a new system BCD store.
bcdboot <source> [/l <locale>] [/s <volume-letter>] [/v]
[/m [{OS Loader ID}]]
source Specifies the location of the windows system root.
/l Specifies an optional locale parameter to use when
initializing the BCD store. The default is US English.
/s Specifies an optional volume letter parameter to designate
the target system partition where boot environment files are
copied. The default is the system partition identified by
the firmware.
/v Enables verbose mode.
/m If an OS loader GUID is provided, this option merges the
given loader object with the system template to produce a
bootable entry. Otherwise, only global objects are merged.
Examples: bcdboot c:\windows /l en-us
bcdboot c:\windows /s h:
bcdboot c:\windows /m {d58d10c6-df53-11dc-878f-00064f4f4e08}
This means that I could type this from an Administrator Command Prompt:
bcdboot c:\windows /s c:
And BCDBoot would basically re-gen the BCD stuff I needed on the C: drive given what it knows about the C:\Windows install.
I ran it, and rebooted. I immediately went into the BIOS and changed the Boot Order so that my 300 GIG C: faster drive (the one I thought I was booting off of all the time) was my startup drive.
Now, Disk Management shows that C:\ is both System and Boot and all is right with the world.
More subtle awesomeness from Windows 7.
Hosting By
My one-hundred-and-sixty-second podcast is up. Scott's at TechEd and bumps into Hal Rottenberg and Kirk Munro. Hal's a PowerShell IT guy and Kirk's a Powershell-focused Dev. What's new in PowerShell 2.0 and what's in it for the .NET developer or Windows power user?
My