New
#1
BCD store deleted after disk cloning with Macrium, why?
I used Macrium Reflect to clone a disk. Immediately after the procedure, the BCD store disappeared.
This is the second time this happened. any idea why that happened?
BCD store deleted after disk cloning with Macrium, why?
-
-
New #2
Did you clone the whole disk or just paritions have you got a second drive in that may have boot files on it?
-
New #3
I wiped clear the second drive with a disk cleaning program, several random wipes.
Then I did the 'image' from Macrium onto that second drive. I cloned the entire disk.
There is no rhyme or reason why that should remove the BCD folder.
The C:\boot\bcd folder is still there but the bcdedit command chokes.
BCD registry file is located in the \Boot\Bcd
-
New #4
Where is the BCD store physically located?
- BIOS-based operating systems. The BCD registry file is located in the \Boot\Bcd directory of the active partition.
- EFI–based operating systems. The BCD registry file is located on the EFI system partition.
Post a screen capture of Disk Management
See this tutorial: Disk Management - How to Post a Screenshot of
Make sure you expand the fields as shown so all data can be seen.
BTW, you already have a thread open on this problem in the General Support forum:
bcdedit: The boot configuration data store could not be opened. You should stay in that thread and not start a new one in a different forum.
See my post in the other thread.
-
New #5
I am not getting enough traction on it, the problem is not resolved. BTW the installation forum is exactly where I need to be since I am thinking I will do the Windows install disk procedure.BTW, you already have a thread open on this problem in the General Support forum:
bcdedit: The boot configuration data store could not be opened. You should stay in that thread and not start a new one in a different forum.
- - - Updated - - -
I cloned disk C: to F: using Macrium Reflect and that's when the problems started.
-
New #6
Probably could have averted all this if you had disconnected all but Disk 0 and 2 (I suspect).
I would have created an image of the old C:, removed it, put in the new disk and restored the image.
When I clone, I usually use a external USB adapter cloning from the internal HDD to the new HDD attached to the USB adapter, then remove the old, install the new and boot. If problems, use Macrium's fix boot problems tool.
-
New #7
I figured it out, what the problem is, Macrium had nothing to do with it per se..
The machine had 3 disks in it with the identical Win10-1903 bootable OS.. Two were SSD, Samsung PM981 , both PCIe/NVME and the third one I stuck in was this HDD. I cloned the OS from C: to F: and that's when the bcdedit stuff disappeared. I have no understanding why. maybe because F: was a SATAIII disk that was not even supposed to be bootable and things got confused.
I put a data disk back in its place, bcdedit started to work and here is what the disk layout looks like now:
- - - Updated - - -
bcdedit:
Quote
Related Discussions
