Aller au contenu principal

TIH 2017 no longer backs up to unlocked Bitlocker destination

Thread needs solution

TIH 2017 suddenly stopped backing up to an unlocked Bitlocker encrypted drive following a "Feature update to Windows 10, version 1709".  The drive is an "External Drive" in Acronis terms.  It is a MicroSD card.

The Bitlocker drive is unlocked, and the backups worked for months.  Suddenly, following the update to Win10 version 1709, it stopped working, giving a message that says "The last backup has failed.  Cannot open a backup on an encrypted volume.  Unlock the volume or turn off Bitlocker, and then try again."  However, as I mentioned, the drive is already unlocked.  An attempt to create a new backup with the destination on an unlocked Bitlocker drive fails with the same message.

Does anyone know, will upgrading to TIH 2018 fix this problem, or has something changed in Win10 that has broken all versions of TIH?

0 Users found this helpful

Jim, I am not aware of any problems specifically around ATI and BitLocker protected drives with the Windows 10 Fall Creators Update (1709).  I have an external USB drive which is BitLocker encrypted which I have been able to use for backups from ATI 2018 with no issue on Win 10 1709.

Have you checked that the drive letter for your drive has remained the same as it was before doing the 1709 update?

Is your drive set to Auto unlock as shown in the BitLocker Control Panel settings?

2018-04-03 23_12_22 BitLocker Control Panel.png

It may be worth trying to turn off auto-unlock then turn it on again (followed by a restart).

En réponse à par truwrikodrorow…

Thanks Steve.  

No, I have not got Bitlocker set to auto-unlock.  For my situations, that would kind of defeat the purpose for which I have it encrypted.  I manually unlock it when needed and then re-lock it afterwards.  This has not been a problem for the past 2 years, but suddenly TIH2017 doesn't like the Bitlocker drive as a destination any more.

I have not tried turning Bitlocker off and back on.  I could try that but, given the hassle of re-saving the new key securely for future use if necessary, I was hoping to avoid that.  It also takes a good portion of a day to decrypt the drive and then another good portion of a day to re-encrypt it.  Quite the hassle for what chat-support has recently told me is a "known bug in TIH2017 and TIH2018" with an unknown fix date.  I suspect most Acronis customers don't use Bitlocker so the bug doesn't seem to be a very high-priority issue.

I have found a work-around that I'll use for now.  I created a VeraCrypt-encrypted folder on the Bitlocker-encrypted drive which I use as a repository for Acronis backups.  Acronis doesn't complain about storing to the VeraCrypt mounted drive.  So now, to perform my Acronis backups, I first unlock the Bitlocker-encrypted drive (drive D:) and then mount the VeraCrypt-encrypted drive (D:\AcronisBackups.hc) as drive G:.  Then I do Acronis backups to drive G:.  A bit cumbersome, but workable.

Jim

frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Contributions: 250
Commentaires: 7092

Hello Jim,

I've found a similar bug logged in our internal system. According to the comments from the dev team some fixes have been already implemented, but the tested and approved code will be likely included in the next version of Acronis True Image, no ETA though. I'd welcome you to install a free trial once we've released the new version.