Cloning Required Reboot on one Windows 10 Pro 64 to run but not on another?
I recently installed Acronis True Image 2018 on a desktop computer that had no previous Acronis software on it. When the installation was completed I cloned the system (c) drive (twice) and it did so without having to reboot the system as previous versions had done.
When I went to install True Image 2018 on another desktop computer (one that had an installation of True Image 2017) I first uninstalled the old software, then installed True Image 2018. When I did a clone of the C drive it rebooted to DOS and ran like it did before.
These two computers have the same motherboards, video cards, RAM, CPU's and Windows 10 Pro 64bit. Why the difference and how do I fix it?


- Se connecter pour poster des commentaires
En réponse à I suspect that the second… par truwrikodrorow…

No that is not it. Out of 4 machines one only one is exhibiting this behavior. On the other 3 machines, 2 had a previous clone on it (and thus a Windows OS), the third was a new disk and the trouble machine was like the 2 that worked just fine, a previous disk that had a clone on it and thus a Windows OS. Two of the computers this did work fine on ran Windows 7 64bit, and the other 2 Windows 10 Pro 64bit
- Se connecter pour poster des commentaires

Your post is a bit confusing but I assume the trouble machine is one of the 2 Win 10 machines?
You are cloning to a disk that contains a previous clone correct? That clone, is it a clone of the same source?
If you are running the clone to a disk that already has a cloned image that is from the same source the behavior is as you describe. I believe this to be the result of identical disk ID's which confuses the clone tool and results in the requirement to reboot.
I had this experience in the BETA testing of 2018 myself and ran several test to confirm the behavior which were all confirmed.
- Se connecter pour poster des commentaires

Sorry for the confusion. The clones are a clone of the same source. The issue does not happen on two computers running Windows 7 but it does on one of the two computer running Windows 10. Both of the Window 10 computers are hardware clones of each other, same MB, same RAM, same Graphics card, different monitors, keyboard, mouse and cases. Windows 10 was a clean install on both machines, one last March and the other in October. Both are currently running the same version and both use Samsung SSD for the OS, one is a 2Tb and the other is a 1Tb drive.
On all of the computers the clone is being done to a plug-in drive bay. Very curious indeed. We build all of the computers custom to what we need them to do.
- Se connecter pour poster des commentaires

My failures were with Windows 10 but I am confident it is not so much the version of windows here as it is how the machines are booted. UEFI booted machines are where this problem occurs. I would say that your Win 10 computers probably are UEFI boot whereas your Win 7 computers are not. In any case clearing a previously used drive of data fixes the issue. This can be easily done using Diskpart clean command and runs fairly quickly. Once you do that use Disk Management to create a new volume NTFS GPT format then run the clone.
- Se connecter pour poster des commentaires