Windows 10 INACCESSIBLE_BOOT_DEVICE After Cloning Drive

[johnwinds]

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). I used TrueImage to clone the eMMC drive (with Windows 10) to the SSD.

When booting up on the SSD, it comes up with an INACCESSIBLE_BOOT_DEVICE error. Just after cloning, it let's me choose safe mode, and Windows does start up in safe mode.

However, it will not boot without safe mode. I tried several things using the command line recovery tool:

bootrec /FixBoot (these were intially returning "the system cannot find the file specified", until I made some changes with bcdedit

bootrec /FixMbr

bootrec /RebuildBcd (this returns 0 identified installations)

bootsect /force /nt60 ALL

deleting the eMMC partitions using diskpart -> clean

assigning the drive letters to C: and U: (for the fat32 partiton) via diskpart

changing the partitions to C: and U: via bcdedit

I couldn't delete C:\Boot\Bcd as some posts suggests, since I do not have a C:\Boot directory

Does anyone have any idea how to fix this? The fact that it loads via safe mode suggests that there isn't any hardware issue. Could it be a driver issue?

All partitions from the original drive were copied. Here are screenshot of the volumes and EFI folder:

Thanks!

 

[Colif]

Is this it? http://www.kangaroo.cc/kangarooplus/
Is ssd attached via USB 3? I assume you know the ssd isn't going to be very fast over usb 3.

i only have two fixes for this but one is a fresh install and I assume you don't want that. the other one is

open command prompt and type chkdsk /f and press enter. Might take a while. http://www.toppctech.com/inaccessible-boot-device-error-fixed/


I wonder if its the bios, are you using the windows boot manager as 1st boot item or the ssd? I think Windows Boot manager records the guid of the boot drive in its path and every single GPT drive on earth has a a unique GUID so you may need to reset the bios to get it to boot off that drive, as I suspect its looking for the old drive still.

Normal win 10 installs have 4 partitions but you only missing the MSR and its likely merged into the C drive, so that may not be cause. ITs likely your install only had 2 partitions at one stage and the Anniversary update created the recovery

 

[Colif]

Update: this won't work. The only versions of Win 10 that will boot off an external drive are the Enterprise and educational versions, and only then if installed using Windows 2 Go.

See: http://superuser.com/questions/982577/how-to-run-windows-10-from-an-external-hard-drive

 

[johnwinds]

Thanks for everyone who posted help. I finally got this working by using the Restore Windows option in the recovery menu.

 

[vonastra]

So,

I'm posting here, as it's pretty high up for the Google search "INACCESSIBLE_BOOT_DEVICE ssd clone".

I upgraded my NVMe SSD 500GB to a 1TB m.2 SSD.

The reason why most solutions on the internet don't work from bootrec, bootsect, etc, is because these all try to fix MBR issues. Whereas anyone reading in 2018+ on Win10, will have most likely have GPT paritioning with UEFI.

So if you've already cloned your SSD (otherwise use e.g. Macrium Reflect free, and clone disk), and get boot errors from BSOD INACCESSIBLE_BOOT_DEVICE, or missing wdboot.sys, or BSODs resulting from the SSD clone. Do the following.

*All volumes I select, are based of the images attached to that step

1.
Load up a CMD in recovery mode, with new unbootable SSD.
I personally created a windows recovery USB, by booting my old SSD to the desktop and goto Start/"Create a recovery drive", untick backup system files, plug a 2GB+ USB in, and let it image USB with Windows recovery tools. Then restart PC, using USB to boot, and go through advanced settings to command prompt.

2.
- Load up "diskpart".
- Type "list disk", then select the SSD disk, "sel disk 0"
- Type "list vol", and identify 2 keys volumes: SYSTEM and WINDOWS. They may be named slightly differently or not named, but SYSTEM is about 100MB-500MB. And WINDOWS will be the majority of your SSD size, i.e. 500GB. (GPT doesn't matter if the SYSTEM volume is of type FAT32 or NTFS).

* Now the problem is the disk cloning software assigned C: to WINDOWS, it should be C: for SYSTEM, but you can't just assign the C: letter, it gets assigned when you select the correct GPT boot, so I don't think this can be done via a cloning tool.

3.
*Note: In the screenshot below, I have fixed the issue and rebooted, hence the vol numbers have changed, keep note!
- Select the WINDOWS volume and change letter from C to E
"sel vol 1", "assign letter=e"
- Then most importantly, set SYSTEM volume as C by setting the hardcoded EFI GUID, and diskpart magically sets it to the reserved C:
"sel vol 0", "set id=c12a7328-f81f-11d2-ba4b-00a0c93ec93b"

4. Vo'ila, if no errors. And in "list vol" you see SYSTEM volume assigned as C: you should be able to boot successfully

* Note: WinRE_DRV is the recovery volume, and you may see other volumes apart from SYSTEM and WINDOWS, they don't need to be touched

Thumbs up, or post if it helped you, to get this page to the top. No more "reinstall the OS", which are the majority of the posts on the internet and even Windows forums.

 

[Phillip Corcoran]

vonastra --- this thread was started 2 years ago and is now dead --- please don't post on old/dead threads, it's pointless.

Check the date before you post on an existing thread!

 

[Colif]

So,

I'm posting here, as it's pretty high up for the Google search "INACCESSIBLE_BOOT_DEVICE ssd clone".

This was his reasoning for doing so

think I close thread anyway