Possibly the worst software or version ever written
Last week, I cloned a 500GB SSD to a 1TB SSD without any issues. A couple days ago, I updated True Drive to the latest version, and decided to replace the ScanDisk 1TB SSD with a Samsung 1TB SSD.
Tried cloning with True Drive in Windows. When it gets to Exclude Files, I select nothing, and just click Next. It thinks for a minute, then returns to the Exclude Files screen, and I can never get past it.
I try from a freshly created Acronis (Win) Rescue Disk. It tells me it can't lock the drive(s), and to use a Linux boot.
I try a freshly created Acronis Linux Rescue Disk. It tells me I need 0MB of additional space on the target drive. I exclude a large (unneeded) file. It too gets stuck at the Exclude Files section.
I make a fresh backup of the drive that's being replaced (the OS drive) on an external drive.
I try to restore and it tells me tells me it can't restore to the target drive.
The target drive is fine - It shows up fine as a D drive in Windows - I can write to it, etc.
What's the friggin' deal???


- Log in to post comments

Enchantech wrote:The way around that is to select Restart from the Power Menu options which will close out all open apps clearing up all open data. Once that has been done the drive should be in a state that will allow it to be locked so that low level disk operations like Clone can function properly.
The suggestion is click the Start Button, and select Restart - Boot the the Bootable Rescue Media and try again?
I'm almost positive this is how I've tried it several times, but just to be certain, I'll try again Friday. Wouldn't booting to the Rescue disk from a powered off state have the safe affect?
- Log in to post comments

So I am not talking about booting to bootable rescue media at all. I am talking about using Windows Restart to restart the computer and then perform the clone from within the installed Clone tool in Windows.
The issue you have now is that the 1TB Sandisk drive cannot be locked while Windows is booted. This is the result of having Fast Startup enabled on the computer in all likelihood. A restart will clear that issue with Fast Startup so that the drive can be locked. At that point it will be possible to clone that drive to the Samsung drive while booted to Windows using the Clone Tool.
You can run the Clone tool from within the True Image application or from the Start menu via the Aconis entry there.
If the Samsung drive has been previously used as an OS drive you might wish to clear the drive of all data prior to running the clone tool. This is not absolutely necessary but can help in some instances. With True Image 2018 there were times when running the clone tool in this manner to a previously used drive would fail requiring a reboot of the machine to complete which brought other problems. In my testing with 2019 I could not reproduce that issue. In all cases the clone functioned as designed and carried out the clone to the target drive regardless if it previously had an OS install on it or not so again, clearing the drive of old data is not necessary with the 2019 product.
- Log in to post comments

I usually disable fastboot as it makes relatively little difference on systems and can cause unexpected outcomes if you are not paying attention to what you are doing.
Ian
- Log in to post comments

I agree with both Ian and Enchantech. Fast Startup is an EVIL feature of Windows 10. I always disable it immediately after installing a Windows system. It could also explain why you are having problems from the recovery media. It's a very bad idea to boot recovery media and work on a drive that is in a state of hibernation. It is also not recommended to enter your BIOS while a drive is in hibernation.
- Log in to post comments


I sorted it out... I used a free cloning tool the other night, but after the clone, I was getting an "MBR Error 1" message when trying to boot. I eventually discovered that my source drive was set to MBR mode, and the target was set to GPT. I changed the target to MBR. True Drives Clone tool still wouldn't get past the Exclude Files section. But, I cloned again using the free tool, and booted fine.
- Log in to post comments

Good news that you managed to get the solution you wanted. Not sure why you were still having issues with ATI once the GPT v MBR issue was dealt with.
Ian
- Log in to post comments