Hi, Hoping to get a bit of insight to find out what's going on. I just installed Windows 10 on a new computer. This was installed initially on Samsung Evo 850 500GB drive. Prior to that I had win 7 loaded on Evo 970 500GB so I decided to swap them over. I bought a Evo 860 1TB drive and imaged win7 to that. Then imaged win10 from the 850 to the 970. No problems both images booted up fine. But (and using Samsungs migration software) started experimenting because the imaging was so fast I decided to just whilst getting to know win 10 imaging across to the 1 TB as I loaded stuff and played with it. However, the problems start when I test the 1TB image. It simply doesn't boot nor did it ever go into recovery after 3 unsuccessful boots and I don't know why. I then tried the windows system backup image. This didn't work either. The result is a BSOD which says INACCESSIBLE BOOT DRIVE and will reboot ad infinitum never going to recovery (because as I discovered later there is no winre.wim present) Just to recap: 1) Clone 500GB Evo 970 to 500GB 850 (Windows 10) - OK 2) Clone 500GB Evo 970 to 500GB 850 (Windows 7) - OK 3) Clone 500GB Evo 970 to 1TB 860 (Windows 7) - OK 4) Clone 500GB Evo 970 to 1TB 860 (Windows 10) - Not OK The process to get this to boot was painful booting from a recovery cd. format the boot partition using : Code: format m: /fs:ntfs bcdboot d:\windows /s m: /f all then just for good measure (not sure if these could be left out but so many attempts led me to do them anyway: Code: bootrec /fixmbr bootrec /fixboot (returns: access denied ) bootrec /scanos (says 0 os found) bootrec /rebuildbcd At this point I finally I get a recovery screen F8 for options leading to a big list, one of them being to boot to safe mode. I do that , it enters fine and then I reboot and it boots normally with no problems after that. After all that I tested the process several times and found that the above tends to work and the only thing that does. As to why the Winre.wim is not present I have no idea but trying to enable it gave me the missing winre.wim message in the source (so it was never installed). I later extracted it from install.wim and put it into \windows\system32\recover and ran Code: reagentc /enable and that put winre.wim into the system reserved partition after which I tested it going to restart to recovery. however, subsequent tests of the above imaging process still leads to no recovery begin invoked and hence the "inaccessible boot disk" stop code and infinite reboots. So .. sorry for the ramble .. head is spinning after so much of this but I'm trying to give as much info as possible for anyone that may be able to shed some light on why the imaging of windows is failing just under the above circumstances. I would point out one thing about Samsung Migrate vs Windows system image backup. The former ends up cloning the drive but not the partitions whereas the latter actually clones the partitions and therefore leaves a final 465GB unallocated partition. Initially I thought maybe the Samsung method was the problem but SIB shows it's nothing to do with the problem. Any help figuring this out would be appreciated, I just want to know why and searches for this specific problem has not really given me any joy.