"no system" on source drive on system reboot after clone to outboard drive windows 10
PLEASE NOTE, this is on a WINDOWS 10 Pro, 64 bit machine!
After cloning operation to an outboard drive of proper capacity, attempting to then reboot from the source internal drive fails, with a "no system found" error. This EXACT operation has worked perfectly, and STILL DOES with Windows 8.1 - so what has changed in Acronis/Windows 10 to cause this action and modification of the source drive? And YES, I prefer to use the "clone" operation rather than other backup/recovery methods - and since Acronis PROVIDES that function, it SHOULD work! NOR does then cloning the outboard drive BACK to the original drive work, using the Acronis rescue DVD - the re-cloned original source drive still displays the same error. I've had to reclone back to Windows 8.1, then re-download and install Windows 10 3 times - it's getting sorta old and irritating.
Any clues?


- Log in to post comments

If you boot with both drives attached after clone they have the same hardware ID and confuses Windows. I've cloned for testing and it works with Win 10 for me so not sure what happened in your case. Your OS BCD may have been updated outside of Acronis as a result of having both drives connected when the machine started (if that was the case).The ducumentation recommends using the bootable media as well since Windows will attempt to do this on its own but success is more likely when it's all done offline. It also recommends taking a full disk image first as a precaution because that will allow you to recover if cloning errors occur. Yes, cloning should work but Windows, custom hardware, bios confine, etc add other layers of complexity too. Taking full disk images before any major change, to include cloning, is a step worth taking if your data and or OS setup are important.
- Log in to post comments