(PeteCresswell) wrote:
Per Mark Lloyd:
Now, with that nice shiny-new SDD in there, we'll see if the dreaded
"BOOTMGR MISSING" pops again over the next week or so.

Windows used to be very fragile that way.

Can anybody shed some light on what's going on in that situation?

i.e. Is it usually the same single cause and, if so, what is the cause ?

A typical tutorial here.

http://www.sevenforums.com/tutorials...ssing-fix.html

1) Use recovery CD and Repair thingy or...

2) At the C:\ prompt, type cd boot and press Enter.

At the C:\Boot prompt, type the following commands
and press Enter after each command.

bootrec /FixMbr --- puts boot code in MBR (446 bytes)
bootrec /FixBoot --- puts boot code in a boot partition (a sector or two maybe?)
bootrec /RebuildBcd --- rebuilds the BCD file

And another thread suggests, that if the boot flag (0x80) is
removed from the partition table entry for the partition
that helps boot the system, then you'll also get your message.

I think DiskPart has an option to make a partition active
(toggle the boot flag for you). From a recovery CD, you could
use DiskPart to put a boot flag back. I found the interface
particularly annoying, and I had trouble verifying where
the boot flag went. It's supposed to be an asterisk next
to one of the partitions.

And I don't think, even if I gave you the recipe for
converting Win7 from a two partition install (SYSTEM RESERVED, C
to a one partition install ( C: ) that this problem would
stop. Doing such a transition just saves you one primary
partition. Running with ( C: ) only as your configuration,
where the boot flag is on C: as well, isn't compatible
with BitLocker in an OS like Win7 Ultimate, and that's
about the only reason to have the two partitions. If
you don't use BitLocker for full disk encryption,
you could switch to one partition.

I switched to one partition on my laptop. I did a backup
first. And I got the recipe right on the first try (which
is unusual for one of my experiments).

http://www.terabyteunlimited.com/kb/article.php?id=409

All the same failures could happen if you have it set up
that way. Nothing really changes. It's just during
cloning, it's a tiny bit harder to leave something
behind.

*******

Always review the Disk Management labels, especially
if you have multiple disks!

The labels System, Boot, Active, help warn you whether
something nasty has caused your setup to be split
between two disks. When cloning such a mess, you
only clone half of it, leading to "problemo". Make
absolutely sure what you see in Disk Management makes
sense, while the computer is still running.

*******

If you type "bcdedit" in a Command Prompt window,
it'll show you the contents of the BCD file. The
disk identifiers in there, could be damaged with
not a lot of work, such as cloning a disk, only
doing half a job, and now the BCD no longer points
to the (cloned) C: .

The last post here addresses "generalize" the BCD for
cloning purposes.

http://www.sevenforums.com/installat...ed-drives.html

"You could generalise the running bcd store first.

bcdedit /set {current} osdevice boot
bcdedit /set {current} device boot
bcdedit /set {bootmgr} device boot

optional:
bcdedit /set {memdiag} device boot

Then you will be fine to clone to your heart's content.

***

If you have done the cloning, then you can do the same,
but point at the clone bcd store, e.g. if clone is on drive D:

bcdedit /store D:\boot\bcd /set {default} osdevice boot
bcdedit /store D:\boot\bcd /set {default} device boot
bcdedit /store D:\boot\bcd /set {bootmgr} device boot
bcdedit /store D:\boot\bcd /set {memdiag} device boot

The other ( easier ) way is to use a program which will
update all bcd stores automatically.

Paragon products which include a cloning function will do that.
"

And while watching a Macrium 6 run the other day, I noticed
a message (multiple lines) in the console where it seemed to
be fixing something up. So yes, some cloning tools actually
do this stuff for you (so you're not learning anything).

Paul