Bitlocker works in the same way, see Microsoft FAQ: "Why are two partitions required? Why does the system drive have to be so large?" The only way to overcome it is to use the second storage for this data, i.e. In both cases, there must be some unencrypted data on a hard disk to start the booting process, whether it is MBR record or EFI partition in case of GPT. I suppose this thread was devoted to discussing VeraCrypt working with GPT disks, because in my experience this situation with a checkbox ("Encrypt the whole drive greyed out") happens with GPT, not MBR.
How would BIOS find the master boot record if the disc is encrypted? One of the absolute best guides to the process is available at: Especially when you take into account the need for compatibility with so much hardware. If you wanted the MBR to be encrypted you would need a VeraCrypt bios, which is outside the scope of this project. How would BIOS find the master boot record if the disc is encrypted? The Veracrypt boot loader is started by referencing the master boot record, if it's encrypted BIOS can't start the boot loader.
Isn't Ver圜rypt running in background and decrypting the starting partition too? And why does such a big corporation like Microsoft defines such an insecure concept (the mandatory to start from an unencrypted partition)? :o Also, their own encryption program (Windows BitLocker) is encrypting the entire drive too (afaik) and Windows can still start from it. I am not sure if original poster had MBR or GPT, but I have no issues with VeraCrypt at the moment. You can still encrypt the main Windows partition on GPT disk. I got an answer on Sourceforge and realised that you can not encrypt "the whole drive" with GPT as Windows needs an unencrypted partition to start boot process.
0 kommentar(er)
