antonio esposito

Wonderful! (so in the end, it was an almost silly question...) Thank you very much!

I don't know if this feature is already implemented... I looked at the VC documentation but found nothing; If I understand well, an Evil Maid Attack is the replacement of the VC Boot sector with a tampered one, which first does its magic and then goes normally on with Pre-Boot authentication and what follows... A way to check/avoid this could be to store a copy of the untampered sector within the encrypted volume, and compare it (once the system has booted) with the current boot sector; this way...

Wonderful! I upgraded to 1.26.15 and made my new 2-stage encrypted disk using fast format and it worked flawlessly :) Just 2 thoughts: 1. why does Fast Format need 2 minute to complete the format? I don't remember this wait when I used TrueCrypt for my old disks... Why installing 1.26.15 over 1.25.9 makes VC say "Updated VeraCrypt Bootblock"? What is changed? (Note: I don't see all the worries about Truecrypt compatibility removed in latest VeraCrypt releases; it just suffices... to keep TrueCrypt...

Wonderful! I upgraded to 1.26.15 and made my new 2-stage encrypted disk using fast format and it worked flawlessly :) Just 2 thoughts: 1. why does Fast Format need 2 minute to complete the format? I don't remember this wait when I used TrueCrypt for my old disks... Why installing 1.26.15 over 1.25.9 makes VC say "Updated VeraCrypt Bootblock"? What is changed? (Note: I don't see all the worries about Truecrypt compatibility removed in latest VeraCrypt releases; it just suffices... to keep TrueCrypt...

That's very interesting! I believed that GUI- and line- usage were equivalent, but now I'm going to test the /FastCreateFile switch and see; unless more recent versions of VeraCrypt (I use 1.25.9) will incorporate this option in GUI too... moreover, since I have to fill almost completely the inner archive, and after that I fill it up using a file generator, the security problem does not arise, but I avoid writing every sector twice :) Thanx!

Hi, the disks are usually formatted in exFat (since in it there is only one gigantic file and no cluster waste); the most frequent size is 2TB. I usually do this to new disks, so I create the external container with Quick format. the inner file (which exact size determination requires a lot of trial-and-error work) is the maximum size within the encrypted drive; usually it is NTFS. I use a 256-char password for both volumes, a custom PIM for the VC disk and keyfiles for both containers. The workload...

I have a number of hard disks with 2 nested encryptions: the disk itself (no partition) is encrypted with VeraCrypt; inside it there is a file encrypted with TrueCrypt. No problem ever. Recently I tried to make a 2-stage Veracrypt-only encryption (i.e. both the disk and the inner file encrypted with VC), but Veracrypt doesn't work: once encrypted and mounted the disk, it takes forever to create the inner file. I never got to see the end of the process. Why is this?

Thank you very much @morton and @Enigma2Illusion for your info; please see the attached picture; the arrow-pointed disk is the encrypted one, which I attached to this PC via an USB docking station; as you can see, the partitions are visible, both from Disk Management and Veracrypt. Now I suspect I'm doing somenthing wrong; my procedure is: -install windows; -create second partition; -install Veracrypt; -launch Veracypt and do full disk encryption, including the extra sectors at the end of the disk...