Macrium Reflect wiped out my BCD store


  1. Posts : 504
    Microsoft Windows 10 Home 64-bit 18363 Multiprocessor Free
       #1

    Wiped out my BCD store


    this is the second time it happened. I have 3 bootable disks in the machine, cloned one disk to another disk and now none of the bcd commands work. The BCD store is gone.

    The machine was bootable before Macrium and is unbootable now. I think there is a serious bug in it.

    EDIT: The issue was traced to the fact a third, SATAIII HDD was made bootable thus creating a conflict.

    Macrium Reflect wiped out my BCD store-image.png
    Last edited by dictum; 11 Oct 2019 at 22:55.
      My Computer


  2. Posts : 2,790
    Linux Mint 20.1 Win10Prox64
       #2

    I don't think there's a serious bug as stated. When you clone one disk to another, you might cause disk collision ie. 2 disks with the same signature (Disk ID). Better to backup to an image then restore so that they have unique disk signature.
    Disconnect the cloned disk then try to reboot again.
      My Computer


  3. Posts : 504
    Microsoft Windows 10 Home 64-bit 18363 Multiprocessor Free
    Thread Starter
       #3

    I don't see how disk collusion can wipe out the BCD store. It's wiped out clean. No entries.

    Even if I removed the disk now, how would I boot without rebuilding the BCD? It caused some downtime.
      My Computer


  4. Posts : 1,020
    Windows 10 Pro 20H2 19042.572
       #4

    Two things, If your your booted from the Macrium recovery environment performing a clone, and you lost any of the drives BCD store, then there is a problem with Macrium.

    But if your running from the SOURCE disks OS and running a Macrium Clone and the BCD store got wiped out on the SOURCE disk ? If that is true, then yes there is a potential problem Macrium.

    But If the BCD store is wiped out on the TARGET drive, then its more related to a collision not a collusion. When the designated boot drive is booting and find's a similar drives with the same "Disk ID", it will attempt to disable all of them. That would not be a Macrium problem.
      My Computers


  5. Posts : 2,608
    trying to install win10
       #5

    If you need a new store:
    bcdedit /createstore c:\emptystore
    bcdedit /import c:\emptystore /clean
    bcdboot c:\windows
      My Computer


  6. Posts : 504
    Microsoft Windows 10 Home 64-bit 18363 Multiprocessor Free
    Thread Starter
       #6

    storageman said:
    Two things, If your your booted from the Macrium recovery environment performing a clone, and you lost any of the drives BCD store, then there is a problem with Macrium.


    But if your running from the SOURCE disks OS and running a Macrium Clone and the BCD store got wiped out on the SOURCE disk ? If that is true, then yes there is a potential problem Macrium.

    But If the BCD store is wiped out on the TARGET drive, then its more related to a collision not a collusion. When the designated boot drive is booting and find's a similar drives with the same "Disk ID", it will attempt to disable all of them. That would not be a Macrium problem.

    Right before I ran Macrium, everything worked. bcdedit, everything. Rebooted just fine. I am sure of it.

    Right after I ran Macrium disk cloning process (Image this disk), the BCD store on the SOURCE drive got corrupt. I have no idea how that's possible. Nor does it make any sense. But it did.
    The bcdedit command just chokes now. What logical connection is there between Macrium reflect and BCD breaking?

    C:\>bcdedit
    The boot configuration data store could not be opened.
    The system cannot find the file specified.

    - - - Updated - - -

    SIW2 said:
    If you need a new store:
    bcdedit /createstore c:\emptystore
    bcdedit /import c:\emptystore /clean
    bcdboot c:\windows

    Macrium Reflect wiped out my BCD store-image.png
      My Computer


  7. Posts : 2,608
    trying to install win10
       #7

    That seems to indicate there is something wrong with the system partition. File system corruption possibly.
    Probably easiest to fix it from boot media.You could try running checkdisk from boot media, if no joy, then format the system partition and run startup repair to create the boot critical files.
      My Computer


  8. Posts : 504
    Microsoft Windows 10 Home 64-bit 18363 Multiprocessor Free
    Thread Starter
       #8

    I already tried running startup repair to no avail... Yet it still booted, always on the second try. I had to hit CTRl-ALT-DELETE twice to get it to boot and skip the "Your computer needs to be repaired" message.

    - - - Updated - - -

    You can close this thread.. resolved.

    Turns out the 3rd disk that I cloned to, that was the source of the problem. Once I removed it, everything started working. I have no idea why it caused this conflict.

    The boot disk is a PCIe/NVMe disk, so is its clone. I created yet another clone to a SATAIII disk in the MSI laptop that I suspect was never intended to be a boot disk and that's when the issues began.

    - - - Updated - - -

    topgundcp said:
    I don't think there's a serious bug as stated. When you clone one disk to another, you might cause disk collision ie. 2 disks with the same signature (Disk ID). Better to backup to an image then restore so that they have unique disk signature.
    Disconnect the cloned disk then try to reboot again.
    that was actually right on the money. With the disk removed, everything went back to normal.
      My Computer


  9. Posts : 7,122
    Windows 10 Pro 64 bit
       #9

    This must be the third thread on the same issue!
      My Computers


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 17:40.
Find Us




Windows 10 Forums