Skip to main content

TI 2016 cannot locate backup ?

Thread needs solution

After updating to Windows 10 Anniversary Update, I am getting strange errors this week.

First,  TI 2016 says it could not read bitlock drive. I rebooted, manage to backup drive C. But when I try to backup another drive, TI 2016 says it could not locate the backup. 

How do I get TI 2016 to read the files that I can read in Explorer ?

0 Users found this helpful

Thank you for the images in the document file.

Please can you set your View options in Explorer to Show full path in the Title Bar as shown in the screen shot below, then post the image of your X:\My backups\M\ folder again to confirm that this is shown correctly, as this looks different to how a similar folder is shown on my Windows 10 system with X:WD(X:) > My backups > M >

I would also recommend downloading and using the Log File Viewer app from the link below in my signature to check what messages are shown in the Service logs for your second backup task?

Attachment Size
383209-132475.png 21.3 KB

With each major Windows update, it's actually a full blown OS install and then a port of the user profile, apps and settings.  Because of this, the recovery parition gets recreated in the process and this may change the hard signature as a result.  This is most likely causing Acronis to read the disk as a "different" hard drive than the backup was originally created with.  If you modify the the source and destination of your backup task and re-run it, I have a feeling it will work again.  The downside is that when you modify a task, it will reset the versino chain so if you have say 3 incremetnals of 5 completed, then 5 more will have to take place before the next full.  Not a huge issue in most cases, but something to be aware of.  

This is not a unique issue to Acronis.  Retrospect and a few other backup applications I have used have similar behavior whenever you make changes to the partitions on a hard drive.  McAfee EndPoint Encryption also behaves similarly if you make a change to the partions in anyway and will result in a non-bootable hard drive until you decrypt and re-encrypt again since it thinks the drive is not the same one it was originally installed on.

We're likely to see more of this behavior with Windows 10 "upgrades" in the future since they are really a full OS install and the recovery partiion is recreated each time.