Cannot open a backup in an encrypted volume, Bitlocker. But volume is unlocked!
True Image 2016 has started with this message just today. I have an encrypted volume with Bitlocker and True Image has been working fine with it until today. The volume is configured for auto-unlock. I've tried to start the backup manually but keep getting this message. I've restarted my PC already but nothing. The volume is clearly unlocked as other applications do have access to it. So, what's the deal with True Image? Why it was working fine until yesterday and now backups are failing??


- Log in to post comments

Thanks @Bobbo_3C0X1. I didn't reply before because was waiting for Windows to finish decrypting my disk which took forever. I can confirm that after that the backup process didn't have issues. What is weird thought is that the other computer I also had updated didn't have any issues with the encrypted disk. I'll have to keep Bitlocker off for now.
- Log in to post comments

Hi Cesar: I don't have an answer, but can confirm that you are not alone. The "standard" backup of my bitlockered OS drive to an external bitlockered USB backup drive was working fine on 10/2 (and many times before) using TIH 2016, then today (10/4) I get this error message when I try to initiate a manual backup:
"The last backup failed. It will be restarted at 12:17 PM.
Cannot open a backup on an encrypted volume. Unlock the volume or turn off BitLocker, and then try again."
The automatic retries also fail. As you said, all volumes are unlocked and accessible, so there isn't much I can do to mitigate this except to decrypt (which I won't do, switching backup solutions would be the sensible thing to do if this doesn't get solved).
I haven't knowingly done any updates to Win 10 in the period between 10/2 and 10/4 but Microsoft is getting more obtuse about their automatic updates ... so who knows? But I use the Win 10 Anniversary edition for several weeks already, so I don't think that by itself is the reason. I've submitted feedback to Acronis with a system report, presumably others will run into the same issues and it gets elevated internally at Acronis.
Separately, I started checking and troubleshooting this because a simple disk clone from one un-encyrpted disk to another blank disk came back with the same error message on this computer (which made no sense whatsoever to me). I ended up doing that clone on another computer that does not have any bitlockered partitions where it worked fine.
- Log in to post comments