MICHAEL LAVIGNE - 2022-04-16

I have an interesting issue regarding my use of VeraCrypt for both a decoy and hidden OS (Win10). I have implemented this arrangement in the past with Win7 and TrueCrypt (before UEFI). For that build, I could boot either system using only the correct passwords (no USB "key"). With the new VeraCrypt build, I now have a decoy system that boots with only a password and a hidden OS that requires both the USB "key" and password. In the past I used Acronis True Home to back up my disk. I created a backup file using a partition-by-partition (bit-for-bit) scheme that included unallocated space. When I restored my disk from backup, both decoy and hidden OS were accessible. I used my original Acronis backup scheme with the new VeraCrypt build but this time only the decoy will boot. It is curious though in that the password I use for the hidden OS along with the original USB "key" do not produce a password error nor does it display the success message. Instead what I get (after the expected time for the success message to display) is the screen clears and the UEFI boot manager reappears asking for my selection of media to boot from.

My question is, can such a backup actually succeed now with the VeraCrypt system? If so, what steps are required to restore the ability to boot the hidden OS that requires the USB "key" to be plugged in? At this point I am ready to rebuild the hidden OS from scratch. I will retain the backup file I created in case this question is answered so that I may implement the suggestions. Many thanks for your attention to this issue.

 
alternate