

I had to assign a drive letter to the SYSTEM partition in order to see what's on there (U:). You said you don't have Boot directory on C: partition how about other partitions and does BCD file exist within Boot folder? I cloned the eMMC disk to the new SSD disk and now I'm trying to boot from the SSD disk.

This is used to upgrade from one disk to another.

TrueImage has a tool to clone between disks which is meant to copy entire disks (sector by sector). If you want to replace the drive, then I suggest taking it to a computer shop that is equipped to help you achieve this. Some chassis require special tools to take them apart. A far as removing the drive from the eMMC I imagine it can be done, just not easily done by the average person. The structure of Windows is not setup to do that sort of thing. That is essentially trying to do the same thing as booting a live cd or live usb of linux.

Generally how it works, you boot from a True Image live cd that has a copy of True Image on it and you select a source disk (usb drive) and a restore disk (internal eMMC drive) and away it goes, it'll restore the eMMC internal hd back to it's original state.īy the sound of it you want to use the image off the internal eMMC and place it on the USB drive & try and boot from it while attached to a USB port. You can't boot from the True Image backup directly if that is what you're trying to do. Ok when you create a clone of the hd it creates a True Image (image) that can only be used to restore to a internal hd back to it's original state or to a new internal HD. I couldn't delete C:\Boot\Bcd as some posts suggests, since I do not have a C:\Boot directoryĭoes anyone have any idea how to fix this? The fact that it loads via safe mode suggests that there isn't any hardware issue. I tried several things using the command line recovery tool:īootrec /FixBoot (these were intially returning "the system cannot find the file specified", until I made some changes with bcdeditīootrec /RebuildBcd (this returns 0 identified installations)ĭeleting the eMMC partitions using diskpart -> cleanĪssigning the drive letters to C: and U: (for the fat32 partiton) via diskpartĬhanging the partitions to C: and U: via bcdedit However, it will not boot without safe mode. Just after cloning, it let's me choose safe mode, and Windows does start up in safe mode. When booting up on the SSD, it comes up with an INACCESSIBLE_BOOT_DEVICE error. I used TrueImage to clone the eMMC drive (with Windows 10) to the SSD. I have a new Kangaroo Mini PC (with dock) and wanted to use an SSD attached via the dock for Windows (instead of the built-in eMMC).
